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
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1182732
Title:
bad dependency on quantumclient breaks metadata agent
Status in OpenStack Neutron (virtual network service):
Confirmed
Bug description:
https://review.openstack.org/#/c/24639/ which landed in trunk depends on this
change in quantumclient
commit 6f7e76ec3b4777816e0a5d7eaeef0026d75b60e6
Author: Oleg Bondarev <obonda...@mirantis.com>
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1182732/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
