curtin

transient failure in vmtests.test_network

Bug #1533770 reported by Scott Moser
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
curtin
Fix Released
Medium
Ryan Harper

Bug Description

curtin c-i caught failure today in vmtests.test_network.WilyTestNetwork

compare XenialTestNetwork/collect output from build 22 (pass) and build 23 (fail)
https://server-team-jenkins.canonical.com/job/curtin-vmtest-venonat/22/artifact/output/XenialTestNetwork/collect/
https://server-team-jenkins.canonical.com/job/curtin-vmtest-venonat/23/artifact/output/XenialTestNetwork/collect/

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

lp:~raharper/curtin/trunk.fix-lp1533770
Scott Moser (community): Approve
Server Team CI bot: Needs Fixing (continuous-integration)
Diff: 11 lines (+0/-1)
1 file modified
examples/tests/basic_network.yaml (+0/-1)
lp:~curtin-dev/curtin/trunk
Revision history for this message
Scott Moser (smoser) wrote :
Revision history for this message
Scott Moser (smoser) wrote :

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.

Revision history for this message
Ryan Harper (raharper) wrote :

Fix will include updating test_network.yaml to split that into test_network_static.yaml (which will only have static configuration) and test_network_dhcp.yaml (which will include dhcp configuration, and some static, but without gateway configurations).

Changed in curtin:
assignee: Ryan Harper (rharper) → Ryan Harper (raharper)
Revision history for this message
Ryan Harper (raharper) wrote :

https://bugs.launchpad.net/curtin/+bug/1533795 will address the ordering of written network files.

Ryan Harper (raharper)
Changed in curtin:
status: Confirmed → In Progress
Ryan Harper (raharper)
Changed in curtin:
status: In Progress → Fix Committed
Revision history for this message
Scott Moser (smoser) wrote : Fixed in Curtin 17.1

This bug is believed to be fixed in curtin in 17.1. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in curtin:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.