Comment 6 for bug 1859988

ok. Using different version of plugin and Tempest can cause even more issue. We should not only pin plugins without pinning Tempest on devstack stable/xyz branch. Also pinning only neutron-tempest-plugin is risky from upper-contraint point of view also. Tempest venv (which install plugins also) use master u-c. so using Temepst master + master u-c + old plugins can break anytime.

We can solve this by two ways:
1. use master neutron-tempest-plugin the same as done for Tempest.
2. pin Tempest and plugins alogn with upper-contraints on devstack stable/queens.

I am not aware of exact reason about pining neutron-tempest-plugin. Policy about stable branch testing even they are in EM state is to use master Tempest & plugins. Once master Tempest or plugins start failing on EM stable for valid reason then, pin those.

We are hitting py2 drop issue on stable/queens and it is EM so its time to pin Tempest & plugins with u-c on devstack which is option2.

Once Tempest 23.0.0 release[1] is done then I will push patch on devstack stable/queens.

[1] https://review.opendev.org/#/c/703521/