Description of problem: some DHCPv6 API tests fail in CI runs, like: tempest.api.network.test_dhcp_ipv6.NetworksTestDHCPv6.test_dhcp_stateful tempest.api.network.test_dhcp_ipv6.NetworksTestDHCPv6.test_dhcpv6_64_subnets This upstream change fixes this problem (removing the expectation that assigned IP will be the first or second in the pool): https://review.openstack.org/#/c/185616/ Version-Release number of selected component (if applicable): openstack-tempest-kilo-20151020.1.el7ost How reproducible: 100% Steps to Reproduce: 1. Deploy RHOSP 7 2. Run Tempest API DHCP IPv6 tests Actual results: Traceback (most recent call last): File "/home/stack/tempest-dir/tempest/api/network/test_dhcp_ipv6.py", line 224, in test_dhcpv6_two_subnets str(dhcp_ip))) File "/usr/lib/python2.7/site-packages/testtools/testcase.py", line 354, in assertIn self.assertThat(haystack, Contains(needle), message) File "/usr/lib/python2.7/site-packages/testtools/testcase.py", line 433, in assertThat raise mismatch_error MismatchError: u'2003:0:0:1::4' not in [u'2003:0:0:1::2', '2003:0:0:1::3']: Real IP is 2003:0:0:1::4, but shall be one from [u'2003:0:0:1::2', '2003:0:0:1::3'] Expected results: tests pass fine Additional info: same failure was observed and fixed for newer versions (see linked bug)
Sorry, I misread #1384631 this is not the same bug
The openstack-tempest-kilo-20151020.2.el7ost package contains backported code, so marking this as verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:1745