bad dependency on quantumclient breaks metadata agent

Bug #1182732 reported by Robert Collins
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
High
Mark McClain

Bug Description

https://review.openstack.org/#/c/24639/ which landed in trunk depends on this change in quantumclient
commit 6f7e76ec3b4777816e0a5d7eaeef0026d75b60e6
Author: Oleg Bondarev <email address hidden>
Date: Tue Mar 12 16:13:02 2013 +0400

but quantum depends on quantumclient >=2.2.0 - however the quantumclient change isn't available in a release, so the quantum change should not have been merged - or should have been merged with backwards compat.

Revision history for this message
yong sheng gong (gongysh) wrote :

It seems we must release a new quantum client

Changed in quantum:
status: New → Confirmed
importance: Undecided → High
milestone: none → havana-1
summary: - bad dependency on quantumclient
+ bad dependency on quantumclient breaks metadata agent
Changed in quantum:
milestone: havana-1 → havana-2
Changed in tripleo:
status: New → Triaged
importance: Undecided → Critical
Revision history for this message
Robert Collins (lifeless) wrote :

Removing the tripleo task; we have a separate bug for working around this.

no longer affects: tripleo
Changed in neutron:
milestone: havana-2 → none
Changed in neutron:
status: Confirmed → Incomplete
Revision history for this message
Robert Collins (lifeless) wrote :

How is this incomplete?

Changed in neutron:
status: Incomplete → New
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

Robert, it looks like neutronclient 2.2.6 is now available from pip. Is that enough to mark this bug as invalid now?

Thanks,
Armando

Changed in neutron:
status: New → Invalid
Revision history for this message
Robert Collins (lifeless) wrote :

Huh, Invalid - how do you get that?

It's either fixed or it's not.

I'm not sure if 2.2.6 was the earliest client release to have the fix.
The current requirements list python-neutronclient>=2.2.3,<3.0.0
So if 2.2.3 has the requisite code, then this is fix released.
If it doesn't, then this is still a bug.

Bugs should only be made invalid if they are shown to be *not a bug* - e.g. a) the relevant code has been deleted or b) the bug reporter was mistaken.

Changed in neutron:
status: Invalid → Confirmed
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

Invalid as in 'no longer applies' to the current state of things. So long as no further action needs to be taken I am not sure there is any point in arguing how to label it, but I get your point; feel free to set it to 'fix released' if you think it's more appropriate.

Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 1182732] Re: bad dependency on quantumclient breaks metadata agent

Thanks! I need to check for the first release after I filed this bug
to see if the current requirements are in fact strict enough.

Revision history for this message
Mark McClain (markmcclain) wrote :

The current global requirements of "python-neutronclient>=2.3.0,<3" Contains the fix client release. We can include this as being fixed in H3.

Changed in neutron:
status: Confirmed → Fix Committed
milestone: none → havana-rc1
assignee: nobody → Mark McClain (markmcclain)
tags: added: metadata neutron-core
Thierry Carrez (ttx)
Changed in neutron:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in neutron:
milestone: havana-rc1 → 2013.2
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.