Bug 1641525 - OVN - IPv6 DHCP fails for OSP14 (advanced image) jobs
Summary: OVN - IPv6 DHCP fails for OSP14 (advanced image) jobs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tempest
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 14.0 (Rocky)
Assignee: Chandan Kumar
QA Contact: Martin Kopec
URL:
Whiteboard:
Depends On:
Blocks: 1643923
TreeView+ depends on / blocked
 
Reported: 2018-10-22 07:43 UTC by Daniel Alvarez Sanchez
Modified: 2019-09-09 14:07 UTC (History)
12 users (show)

Fixed In Version: openstack-tempest-19.0.0-2.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1643923 (view as bug list)
Environment:
Last Closed: 2019-03-18 13:04:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1795891 0 None None None 2018-12-12 15:43:10 UTC
OpenStack gerrit 607958 0 None master: MERGED tempest: Change way how second NIC in guest OS is configured (I397b1c3584a045f9ca4f47b4e691385628d35efa) 2019-01-07 12:28:50 UTC
Red Hat Product Errata RHBA-2019:0591 0 None None None 2019-03-18 13:04:16 UTC

Description Daniel Alvarez Sanchez 2018-10-22 07:43:31 UTC
Tests failing:

 tempest.scenario.test_network_v6.TestGettingAddress.test_dualnet_dhcp6_stateless_from_os
 tempest.scenario.test_network_v6.TestGettingAddress.test_dualnet_multi_prefix_dhcpv6_stateless
 tempest.scenario.test_network_v6.TestGettingAddress.test_dualnet_multi_prefix_slaac
 tempest.scenario.test_network_v6.TestGettingAddress.test_dualnet_slaac_from_os



The VM's boot but the IPv6 address is not present when tempest checks for it:


Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/tempest/common/utils/__init__.py", line 89, in wrapper
    return f(*func_args, **func_kwargs)
  File "/usr/lib/python2.7/site-packages/tempest/scenario/test_network_v6.py", line 245, in test_dualnet_dhcp6_stateless_from_os
    self._prepare_and_test(address6_mode='dhcpv6-stateless', dualnet=True)
  File "/usr/lib/python2.7/site-packages/tempest/scenario/test_network_v6.py", line 196, in _prepare_and_test
    (ip, srv['id'], ssh.exec_command("ip address")))
  File "/usr/lib/python2.7/site-packages/unittest2/case.py", line 666, in fail
    raise self.failureException(msg)
AssertionError: Address 2003::f816:3eff:fe4f:67bb not configured for instance 1b099e67-686b-4b12-b683-c780406d6e81, ip address output is
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1442 qdisc pfifo_fast state UP qlen 1000
    link/ether fa:16:3e:1f:d6:dc brd ff:ff:ff:ff:ff:ff
    inet 10.100.0.7/28 brd 10.100.0.15 scope global dynamic eth0
       valid_lft 42988sec preferred_lft 42988sec
    inet6 fe80::f816:3eff:fe1f:d6dc/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1442 qdisc pfifo_fast state UP qlen 1000
    link/ether fa:16:3e:4f:67:bb brd ff:ff:ff:ff:ff:ff

Comment 2 Daniel Alvarez Sanchez 2018-10-22 07:44:35 UTC
Initially assigned to Numan for triaging as per our IRC conversation.

Comment 8 Terry Wilson 2018-12-07 16:28:20 UTC
I would bet that this was actually fixed two months ago in upstream tempest by slawek here: https://github.com/openstack/tempest/commit/c5c7ba997eb194e8428bfcb802bfabfdfb5ef5fe

The tempest version on the test machine is 19.0.0-0.20180914114331.8316f96.el7ost.noarch
 which was built before that patch existed. I verified the patch was not in the installed python module.

The patch has been backported to OSP13, but OSP14 doesn't seem to have any backports at all and the Source isn't set to an upstream tgz like previous releases, though there is a 19.0.0 upstream tag now.

Comment 20 errata-xmlrpc 2019-03-18 13:04:08 UTC
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-2019:0591


Note You need to log in before you can comment on or make changes to this bug.