[all][qa] Gate status of stable stein's legacy jobs with tempest plugins

Ghanshyam Mann gmann at ghanshyammann.com
Wed Feb 24 00:46:04 UTC 2021

 ---- On Sun, 21 Feb 2021 12:52:39 -0600 Ghanshyam Mann <gmann at ghanshyammann.com> wrote ----
 > Hello Everyone,
 > We recently pinned the Tempest version 26.0.0 in devstack for stable/stein branch testing.[1]. In CI/CD workflow
 > tempest venv can be re-created many times in devstack, devstack-gate (for legacy jobs) or run-tempest roles etc. With
 > the Tempest 26.0.0 version, we need to make tempest venv to use the stable constraints instead of master constraints.  And
 > used constraints should be consistent otherwise tempest venv gets recreated which end up removing the previously
 > installed tempest plugins.
 > We have taken care of constraints consistency for zuulv3 native jobs in run-tempest ansible role but for the legacy job which
 > uses the devstack-gate path still use the master constraints and recreate the tempest venv. So your legacy job which uses the
 > tempest plugins will be failing.
 > Example: designate-devstack-pdns4 - https://zuul.opendev.org/t/openstack/build/35fd0a4c76e0482e88ed32ef0840291d
 > I have pushed the fixes which are on devstack, devstack-gate, and tempest(tempest patch is merged). If you are seeing
 > a similar issue please do not recheck and wait for the below patches to merge:
 > - https://review.opendev.org/c/openstack/devstack-gate/+/776722
 > - https://review.opendev.org/c/openstack/devstack/+/776811

Both fixes are merged now, feel free to recheck.


 > [1] https://review.opendev.org/c/openstack/devstack/+/774103
 > -gmann

More information about the openstack-discuss mailing list