Merge ~rodsmith/plainbox-provider-certification-server:fix-precheck-script-multiple-subnets into plainbox-provider-certification-server:master
Status: | Merged |
---|---|
Approved by: | Rod Smith |
Approved revision: | e300544bbd326e1e1c4beedc71a27f113cf67cac |
Merged at revision: | 4d7d5bf72ef54522ac9efee76e49fc6a2fc99ee2 |
Proposed branch: | ~rodsmith/plainbox-provider-certification-server:fix-precheck-script-multiple-subnets |
Merge into: | plainbox-provider-certification-server:master |
Diff against target: |
139 lines (+73/-17) 2 files modified
tools/canonical-certification-precheck (+68/-17) units/packaging.pxu (+5/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Jeff Lane | Approve | ||
Review via email: mp+381318@code.launchpad.net |
Commit message
Improve precheck script handling of multi-network configurations
Description of the change
This MR holds two interrelated changes to the canonical-
* A failure of the Network_Subnets check is demoted from a failure
to a warning.
* The Iperf check is expanded to verify that there's an iperf3 server
accessible on every subnet to which the SUT connects.
The second is, by far, the biggest change. In principle, the Network_Subnets check is no longer needed; however, I've left it because I thought it might be useful to warn users about this should the Iperf check fail -- if a user has accidentally misconfigured a NIC, it would likely fail the Iperf test, and the warning about the Network_Subnets problem issued in the summary would then help the user track down the cause of the Iperf failure. I'm not wedded to this, though; if desired, the Network_Subnets check could instead be completely eliminated.
Oh, BTW, I've tested this on three SUTs, one connected to a single network and two connected to two networks each. In both cases, I tried with iperf3 servers accessible on all networks and with one network missing an iperf3 server. It worked as expected in all cases.