vmtest: ZestyTestNetworkIPV6 incorrect gw count

[Joshua Powers]

Date: Mar 2, 2017
Job: curtin-vmtest-devel-amd64
Run: #793
Console: https://jenkins.ubuntu.com/server/job/curtin-vmtest-devel-amd64/793/console

Failure:
FAIL: test_ip_output (vmtests.test_network_ipv6.ZestyTestNetworkIPV6)
self.assertEqual(len(found_gws), len(configured_gws))
AssertionError: 0 != 2

Logs for failed test:
https://jenkins.ubuntu.com/server/job/curtin-vmtest-devel-amd64/793/artifact/output/ZestyTestNetworkIPV6/

The very next run however passed with no errors. From my quick analysis it looks like some routes were not present:

0.0.0.0 65.61.151.37 0.0.0.0 UG 0 0 0 bond0.108
10.184.225.120 0.0.0.0 255.255.255.252 U 0 0 0 bond0.208
65.61.151.36 0.0.0.0 255.255.255.252 U 0 0 0 bond0.108

versus on the successful run:

Kernel IP routing table
0.0.0.0 65.61.151.37 0.0.0.0 UG 0 0 0 bond0.108
10.176.0.0 10.184.225.121 255.240.0.0 UG 0 0 0 bond0.208
10.184.225.120 0.0.0.0 255.255.255.252 U 0 0 0 bond0.208
10.208.0.0 10.184.225.121 255.240.0.0 UG 0 0 0 bond0.208
65.61.151.36 0.0.0.0 255.255.255.252 U 0 0 0 bond0.108

[Ryan Harper (raharper)]

Some of the networking tests are racy w.r.t the speed at which the network
says it's up vs. when we run our collection scripts.

On Thu, Mar 2, 2017 at 9:35 AM, Joshua Powers <email address hidden>
wrote:

> Public bug reported:
>
> Date: Mar 2, 2017
> Job: curtin-vmtest-devel-amd64
> Run: #793
> Console: https://jenkins.ubuntu.com/server/job/curtin-vmtest-
> devel-amd64/793/console
>
> Failure:
> FAIL: test_ip_output (vmtests.test_network_ipv6.ZestyTestNetworkIPV6)
> self.assertEqual(len(found_gws), len(configured_gws))
> AssertionError: 0 != 2
>
> Logs for failed test:
> https://jenkins.ubuntu.com/server/job/curtin-vmtest-
> devel-amd64/793/artifact/output/ZestyTestNetworkIPV6/
>
> The very next run however passed with no errors. From my quick analysis
> it looks like some routes were not present:
>
> 0.0.0.0 65.61.151.37 0.0.0.0 UG 0 0 0
> bond0.108
> 10.184.225.120 0.0.0.0 255.255.255.252 U 0 0 0
> bond0.208
> 65.61.151.36 0.0.0.0 255.255.255.252 U 0 0 0
> bond0.108
>
> versus on the successful run:
>
> Kernel IP routing table
> 0.0.0.0 65.61.151.37 0.0.0.0 UG 0 0 0
> bond0.108
> 10.176.0.0 10.184.225.121 255.240.0.0 UG 0 0 0
> bond0.208
> 10.184.225.120 0.0.0.0 255.255.255.252 U 0 0 0
> bond0.208
> 10.208.0.0 10.184.225.121 255.240.0.0 UG 0 0 0
> bond0.208
> 65.61.151.36 0.0.0.0 255.255.255.252 U 0 0 0
> bond0.108
>
> ** Affects: curtin
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to curtin.
> Matching subscriptions: curtin-bugs-all
> https://bugs.launchpad.net/bugs/1669481
>
> Title:
> vmtest: ZestyTestNetworkIPV6 incorrect gw count
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1669481/+subscriptions
>

[Ryan Harper (raharper)]

Zesty is EOL