python-neutronclient

2.4.0 release destroys grenade since stable/juno isn't capped properly

Bug #1442367 reported by Matt Riedemann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-neutronclient
Fix Released
Critical
Akihiro Motoki
Matt Riedemann (mriedem)
Changed in python-neutronclient:
importance: Undecided → Critical
status: New → Confirmed
Revision history for this message
Kyle Mestery (mestery) wrote :

IT is here: https://review.openstack.org/#/c/172150/

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

Love the title of the bug, next time I'd go instead with "python-neutronclient release release plague on humanity".

Kyle Mestery (mestery)
Changed in python-neutronclient:
assignee: nobody → Akihiro Motoki (amotoki)
Revision history for this message
Adam Gandelman (gandelman-a) wrote :

Waiting on these now: https://review.openstack.org/#/q/owner:%22OpenStack+Proposal+Bot%22+status:open+branch:stable/juno,n,z

Matt Riedemann (mriedem)
Changed in python-neutronclient:
status: Confirmed → Fix Committed
Akihiro Motoki (amotoki)
Changed in python-neutronclient:
milestone: none → 2.4.1
Revision history for this message
Akihiro Motoki (amotoki) wrote :

It was fixed in global-requirements for stable/juno.

Changed in python-neutronclient:
milestone: 2.4.1 → none
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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