tempest-slow-py3 is failing while creating initial network in neutron

Bug #1936983 reported by Slawek Kaplonski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Critical
Slawek Kaplonski
Revision history for this message
Ghanshyam Mann (ghanshyammann) wrote :

tempest-full-py3 also failing with same error

- https://zuul.openstack.org/builds?job_name=tempest-full-py3

Revision history for this message
Akihiro Motoki (amotoki) wrote :

I found the same error in neutron-ovn-tempest-slow job (in the check queue) of https://review.opendev.org/c/openstack/neutron/+/776701.
https://zuul.opendev.org/t/openstack/build/5344d9bdec9346738499114c10a81aff/log/controller/logs/screen-q-svc.txt#1993

neutron-ovn-tempest-slow job runs tempest-slow job but it is non-voting, so the error was not detected when reviewing the patch.

I believe reverting https://review.opendev.org/c/openstack/neutron/+/776701 will fix the issue.

Changed in neutron:
status: Confirmed → In Progress
Revision history for this message
Akihiro Motoki (amotoki) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to neutron (master)

Related fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/neutron/+/801598

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

Reviewed: https://review.opendev.org/c/openstack/neutron/+/801478
Committed: https://opendev.org/openstack/neutron/commit/c3b99a64fc117a3dc8f6d0ff92272183753fcf3e
Submitter: "Zuul (22348)"
Branch: master

commit c3b99a64fc117a3dc8f6d0ff92272183753fcf3e
Author: Slawek Kaplonski <email address hidden>
Date: Tue Jul 20 21:25:54 2021 +0000

    Revert "[OVN][Placement] Add a SB Chassis event to track changes in BW config"

    This reverts commit df5cb28737453e2dfee17e177160fa6d7a59b7e0.

    The reverted commit triggers the failure of tempest-slow-py3 job.
    tempest-slow-py3 is equal to non-voting neutron-ovn-tempest-slow job
    in the neutron CI. It is a non-voting job so the error was not detected
    before merging it. To recover the tempest job in OpenStack wide,
    this commit reverts it.

    See http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023764.html

    Closes-Bug: #1936983
    Change-Id: Id8cdd9c69e4fef2d9c335447b498958add8b7816

Changed in neutron:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to neutron (master)

Reviewed: https://review.opendev.org/c/openstack/neutron/+/801598
Committed: https://opendev.org/openstack/neutron/commit/02c0b47d2267ee3c48d9991e5da7fd53dcf56556
Submitter: "Zuul (22348)"
Branch: master

commit 02c0b47d2267ee3c48d9991e5da7fd53dcf56556
Author: Slawek Kaplonski <email address hidden>
Date: Wed Jul 21 08:50:12 2021 +0200

    Promote neutron-ovn-tempest-slow job to be voting and gating

    This jobs is almost the same as tempest-slow-py3 since we switched
    OVN to be default backend in Neutron. And that tempest-slow-py3 job
    is used by many projects. So to avoid potential breaks of the gate for
    other projects (like we did recently, see related bug for details)
    let's make this job voting and gating.
    As it is really used in many different projects as voting and gating
    job already I don't think there is any issue with doing the same in
    the Neutron gate.

    Related-bug: #1936983
    Related-bug: #1930402

    Change-Id: I85d3830e9cc65162db846e4858871e1db547a04b

tags: added: neutron-proactive-backport-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 19.0.0.0rc1

This issue was fixed in the openstack/neutron 19.0.0.0rc1 release candidate.

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.