"neutron-ovs-grenade-multinode" and "neutron-ovn-grenade-multinode" failing in 2023.1 and Zed
Bug #2052915 reported by
Rodolfo Alonso
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Won't Fix
|
Low
|
Unassigned | ||
neutron |
Triaged
|
Critical
|
Unassigned |
Bug Description
The issue seems to be in the neutron-lib version installed:
2024-02-07 16:19:35.155231 | compute1 | ERROR: neutron 21.2.1.dev38 has requirement neutron-lib>=3.1.0, but you'll have neutron-lib 2.20.2 which is incompatible.
That leads to an error when starting the Neutron API (an API definition is not found) [1]:
Feb 07 16:13:54.385467 np0036680724 neutron-
Setting priority to Critical because that affects to the CI.
Changed in neutron: | |
importance: | Undecided → Critical |
tags: | added: gate-failure |
Changed in neutron: | |
status: | New → Triaged |
To post a comment you must log in.
At a first glance I only found broken jobs on stable/zed. Where grenade is upgrading from yoga. Could the stable/yoga -> unmaintained/yoga branch rename affect this?