blank vars in conf file can cause tests to choke
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Provider for Plainbox - Canonical Certification (Legacy) |
Fix Released
|
Medium
|
Jeff Lane |
Bug Description
in the conf file canonical-
#KVM_TIMEOUT =
And
#TEST_PASS =
The problem we're seeing is that testers uncomment these as necessary but forget to fill them in.
Scenario 1: Tester using local cloud image for virt testing, uncomments these lines:
#KVM_TIMEOUT =
#KVM_IMAGE =
But only fill in KVM_IMAGE. This can cause the virtualization test to choke as the env var KVM_TIMEOUT overrides the default in the script and can create issues.
Scenario 1: Tester donig iperf testing uncomments the four lines for network testing correctly but fails to fill in
#TEST_PASS =
with a generic fake password. The network script sees this is empty and still tries evaluating the var and can choke because it's left empty.
To be honest, this is not something I've encountered myself, but based on feedback. IN any case, the MR that changes these values in the config file is innocuous enough that it wont hurt anything.
Related branches
- Daniel Manrique (community): Approve
-
Diff: 19 lines (+2/-2)1 file modifieddebian/extras/canonical-certification-config/canonical-certification.conf (+2/-2)
Changed in plainbox-provider-canonical-certification: | |
status: | New → In Progress |
assignee: | nobody → Jeff Lane (bladernr) |
importance: | Undecided → Medium |
Changed in plainbox-provider-canonical-certification: | |
status: | In Progress → Fix Committed |
Changed in plainbox-provider-canonical-certification: | |
milestone: | none → 0.1 |
Changed in plainbox-provider-canonical-certification: | |
status: | Fix Committed → Fix Released |
Thanks! Still, as seen in the comment for the merge request, I'd like to see the underlying problem in the script get fixed at some point. Leaving it there is only going to come to make our lives miserable down the line. It can be done later though.