Neutron Client version 2.3.11 breaks icehouse

Bug #1423753 reported by Henry Gessau
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-neutronclient
Fix Released
High
Henry Gessau
Henry Gessau (gessau)
Changed in python-neutronclient:
assignee: nobody → Henry Gessau (gessau)
Revision history for this message
Matt Riedemann (mriedem) wrote :
Revision history for this message
Matt Riedemann (mriedem) wrote :

A series of devstack changes starting here https://review.openstack.org/#/c/157535/ need to be backported from master to the stable branches before the neutronclient cap on stable/icehouse g-r is going to pass.

Revision history for this message
Alan Pevec (apevec) wrote :

Alternative workaround is https://review.openstack.org/157654 which is blocked on swift-dsvm-functional issue fixed by https://review.openstack.org/157670 which is blocked on neutronclient i.e. we got a cyclic dep here which will require ninja merge to resolve.

I suggest to start with ninja merging 157670 which looks the most innocent.

Kyle Mestery (mestery)
Changed in python-neutronclient:
milestone: none → 2.3.12
importance: Undecided → High
Revision history for this message
Zane Bitter (zaneb) wrote :

Elastic Recheck is also reporting that this bug is responsible for failures in stable/juno.

Revision history for this message
Alan Pevec (apevec) wrote :

> failures in stable/juno

That's I->J grenade job failing on Icehouse side.
https://review.openstack.org/157606 still has not be merged.

Revision history for this message
Kyle Mestery (mestery) wrote :

Is this bug still happening? Henry, any update on what's happening here?

Changed in python-neutronclient:
milestone: 2.4.0 → none
Revision history for this message
Ihar Hrachyshka (ihar-hrachyshka) wrote :

The client is capped in Icehouse as: "python-neutronclient>=2.3.4,<2.3.11" I assume the bug is complete.

Changed in python-neutronclient:
status: New → Fix Committed
Changed in python-neutronclient:
milestone: none → 2.6.0
status: Fix Committed → Fix Released
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.