[stable/stein] neutron-tempest-plugin jobs fail with "AttributeError: module 'tempest.common.utils' has no attribute 'is_network_feature_enabled'"

[Bernard Cafarelli]

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)

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/813840

[Bernard Cafarelli (bcafarel)]

More details available in tempest LP https://bugs.launchpad.net/tempest/+bug/1946321 but for the short version we are now using an older version in stein (to avoid the change in python dependencies). To align with that, the WIP patch in neutron-tempest-plugin is aiming at using a smiliarly older neutron-tempest-plugin in stein jobs.
Currently I am fiddling to add a few tests to skip as they were more unstable in this capped releases

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/813840
Committed: https://opendev.org/openstack/neutron-tempest-plugin/commit/1fc809735f1914dd7fb6f8f916f6d10bd9bab60c
Submitter: "Zuul (22348)"
Branch: master

commit 1fc809735f1914dd7fb6f8f916f6d10bd9bab60c
Author: Bernard Cafarelli <email address hidden>
Date: Wed Oct 13 16:26:07 2021 +0200

    Use an older version of neutron-tempest-plugin for stein jobs

    Since [0], stein uses an older version of tempest to fix jsonschema
    issue observed in newer releases. This tag does not have
    utils.is_network_feature_enabled used in test_metadata scenario.

    As stein is in Extended Maintenance, use an older version for n-t-p to
    fix gates. Also filter out port forwarding test as it is unstable in
    this pinned version.

    Closes-Bug: #1946748

    [0] https://review.opendev.org/c/openstack/devstack/+/812092

    Change-Id: I724da80bc440cd5d5b947d0c0a08cbead95628e9

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron-tempest-plugin 1.8.0 release.