We had a patch recently go in that increased the probability of a router interface being observable in gate runs that doesn't have an IP address.
https://review.openstack.org/#/c/408143/ results in a separate read for IP addresses from the DB rather than a complex join. This means that if there is a port list call right at the same time a port is being deleted, it may be visible to the port list call having no IP addresses. Even though this is a slight behavior change in Neutron, Tempest is actually making a couple of bad assumptions in that test. One is that there will always be an IP address on a router port and the other is that there will only be one IP address on the port. The latter is not true in the case of of a port attached to multiple IPv6 subnets and the former is not necessarily true for out of tree L3 implementations. I think we should just adjust the tempest test to match the possible port states and mark this as invalid for Neutron since a port without an IP has been possible for a long time. ** Changed in: neutron Status: Confirmed => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1664020 Title: TestSecurityGroupsBasicOps.test_cross_tenant_traffic fails with "IndexError: list index out of range" Status in neutron: Invalid Status in tempest: In Progress Bug description: Seen here: http://dal05.objectstorage.softlayer.net/v1/AUTH_3d8e6ecb-f597-448c- 8ec2-164e9f710dd6/pkvmci/nova/07/432707/2/check/tempest-dsvm-full- xenial/f6b6842/console.html 2017-02-12 03:22:45.727 | tempest.scenario.test_security_groups_basic_ops.TestSecurityGroupsBasicOps.test_cross_tenant_traffic[compute,id-e79f879e-debb-440c-a7e4-efeda05b6848,network] 2017-02-12 03:22:45.728 | ------------------------------------------------------------------------------------------------------------------------------------------------------------- 2017-02-12 03:22:45.728 | 2017-02-12 03:22:45.729 | Captured traceback: 2017-02-12 03:22:45.729 | ~~~~~~~~~~~~~~~~~~~ 2017-02-12 03:22:45.730 | Traceback (most recent call last): 2017-02-12 03:22:45.730 | File "tempest/scenario/test_security_groups_basic_ops.py", line 186, in setUp 2017-02-12 03:22:45.731 | self._verify_network_details(self.primary_tenant) 2017-02-12 03:22:45.731 | File "tempest/scenario/test_security_groups_basic_ops.py", line 246, in _verify_network_details 2017-02-12 03:22:45.732 | if net_info.is_router_interface_port(i)] 2017-02-12 03:22:45.732 | IndexError: list index out of range That's the power kvm 3rd party CI but it's also happening in the openstack CI: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22if%20net_info.is_router_interface_port(i)%5D%5C%22&from=7d 12 hits in 7 days, check and gate, all failures. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1664020/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
