[neutron-lib][stable] Wallaby CI, tempest failing: unknown environment 'integrated-full'

Bug #2007986 reported by Rodolfo Alonso
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Invalid
Critical
Unassigned
tempest
Fix Released
Undecided
Unassigned

Bug Description

Neutron-lib Wallaby CI, job "tempest-full-py3" is failing with error:
  controller | ERROR: unknown environment 'integrated-full'

Logs: https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_cf8/874412/1/check/tempest-full-py3/cf87e9c/job-output.txt

Tags: tempest
Changed in neutron:
importance: Undecided → Critical
Revision history for this message
Rodolfo Alonso (rodolfo-alonso-hernandez) wrote :

I think this patch is the culprit here: https://review.opendev.org/c/openstack/tempest/+/873055

tags: added: tempest
Changed in tempest:
status: New → In Progress
Revision history for this message
yatin (yatinkarel) wrote :
Changed in neutron:
status: New → Invalid
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tempest (master)

Reviewed: https://review.opendev.org/c/openstack/tempest/+/874704
Committed: https://opendev.org/openstack/tempest/commit/11d4fc9e417d5cfcd6c6075e27d052aecc69c385
Submitter: "Zuul (22348)"
Branch: master

commit 11d4fc9e417d5cfcd6c6075e27d052aecc69c385
Author: Ghanshyam Mann <email address hidden>
Date: Tue Feb 21 13:29:44 2023 -0800

    Fix tempest-full-py3 for stable/ussuri to wallaby

    tempest-full-py3 job started using the new tox env
    'integrated-full' which is not present in old
    tempest used in stable/ussuri to wallaby. This
    commit preapre a separate job definiton for stable
    ussuri to wallaby which use 'full' tox env.

    Closes-Bug: #2007986
    Depends-On: https://review.opendev.org/c/openstack/devstack/+/874625
    Change-Id: I5f1c4de0e7ec0cc6d7f6ba7d7aa78aabc931d23e

Changed in tempest:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tempest 34.0.0

This issue was fixed in the openstack/tempest 34.0.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.