transient failure in vmtests.test_network
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
curtin |
Fix Released
|
Medium
|
Ryan Harper |
Bug Description
curtin c-i caught failure today in vmtests.
compare XenialTestNetwo
https:/
https:/
Per Ryan,
| it's a race
| between dhcp setting gateway and static configuration
| we should change the test
| it's checking that we setup a gateway 10.0.2.1 for eth with ip 10.0.2.100
| eth1 has the correct ip, and I'm sure it set the gateway
| but dhcp of the other eth clobbered it
| and depending on the order of the operations (dhcp vs static) there can be only one gateway
Related branches
- Scott Moser (community): Approve
- Server Team CI bot: Needs Fixing (continuous-integration)
-
Diff: 11 lines (+0/-1)1 file modifiedexamples/tests/basic_network.yaml (+0/-1)
Changed in curtin: | |
status: | Confirmed → In Progress |
Changed in curtin: | |
status: | In Progress → Fix Committed |
Note, the diff here also shows arbitrary ordering differences in /etc/network/ interfaces and 70-persistent- net.rules
We really should be consistent on ordering when we write those files.