Public bug reported: These recent backports started to fail recently on stein: neutron-tempest-plugin-scenario-linuxbridge-stein neutron-tempest-plugin-scenario-openvswitch-stein neutron-tempest-plugin-scenario-openvswitch-iptables_hybrid-stein
Sample backport and log failure: https://review.opendev.org/c/openstack/neutron/+/808501 https://zuul.opendev.org/t/openstack/build/868e5fd3b7c643b7865a7a40f50c5d95 setUpClass (neutron_tempest_plugin.scenario.test_metadata.MetadataTest) ----------------------------------------------------------------------- Captured traceback: ~~~~~~~~~~~~~~~~~~~ b'Traceback (most recent call last):' b' File "/opt/stack/tempest/tempest/test.py", line 188, in setUpClass' b' six.reraise(etype, value, trace)' b' File "/opt/stack/tempest/.tox/tempest/lib/python3.6/site-packages/six.py", line 693, in reraise' b' raise value' b' File "/opt/stack/tempest/tempest/test.py", line 165, in setUpClass' b' cls.skip_checks()' b' File "/opt/stack/tempest/.tox/tempest/lib/python3.6/site-packages/neutron_tempest_plugin/scenario/test_metadata.py", line 51, in skip_checks' b" if not utils.is_network_feature_enabled('ipv6_metadata'):" b"AttributeError: module 'tempest.common.utils' has no attribute 'is_network_feature_enabled'" b'' The relevant line in neutron-tempest-plugin has been there for almost a year (8bbd743, 2020-11-04), so I suspect a recent change in tempest configuration (for stein branch)? Maybe related to previous failure we saw in https://bugs.launchpad.net/tempest/+bug/1946321 and now we use a version of tempest too old? Train and newer branches are fine, rocky looks OK (though latest backport was on Oct 7, so maybe before that started to fail) ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1946748 Title: [stable/stein] neutron-tempest-plugin jobs fail with "AttributeError: module 'tempest.common.utils' has no attribute 'is_network_feature_enabled'" Status in neutron: New Bug description: These recent backports started to fail recently on stein: neutron-tempest-plugin-scenario-linuxbridge-stein neutron-tempest-plugin-scenario-openvswitch-stein neutron-tempest-plugin-scenario-openvswitch-iptables_hybrid-stein Sample backport and log failure: https://review.opendev.org/c/openstack/neutron/+/808501 https://zuul.opendev.org/t/openstack/build/868e5fd3b7c643b7865a7a40f50c5d95 setUpClass (neutron_tempest_plugin.scenario.test_metadata.MetadataTest) ----------------------------------------------------------------------- Captured traceback: ~~~~~~~~~~~~~~~~~~~ b'Traceback (most recent call last):' b' File "/opt/stack/tempest/tempest/test.py", line 188, in setUpClass' b' six.reraise(etype, value, trace)' b' File "/opt/stack/tempest/.tox/tempest/lib/python3.6/site-packages/six.py", line 693, in reraise' b' raise value' b' File "/opt/stack/tempest/tempest/test.py", line 165, in setUpClass' b' cls.skip_checks()' b' File "/opt/stack/tempest/.tox/tempest/lib/python3.6/site-packages/neutron_tempest_plugin/scenario/test_metadata.py", line 51, in skip_checks' b" if not utils.is_network_feature_enabled('ipv6_metadata'):" b"AttributeError: module 'tempest.common.utils' has no attribute 'is_network_feature_enabled'" b'' The relevant line in neutron-tempest-plugin has been there for almost a year (8bbd743, 2020-11-04), so I suspect a recent change in tempest configuration (for stein branch)? Maybe related to previous failure we saw in https://bugs.launchpad.net/tempest/+bug/1946321 and now we use a version of tempest too old? Train and newer branches are fine, rocky looks OK (though latest backport was on Oct 7, so maybe before that started to fail) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1946748/+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
