yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #64025
[Bug 1306381] Re: A new agent should be represented as "id"
This needs to change the API response, so we need bump a new
microversion. And we need a nova-spec for this kind of API change. But
this is very low priority
** Changed in: nova
Status: In Progress => Confirmed
** Changed in: nova
Importance: Low => Wishlist
** Changed in: nova
Assignee: stgleb (gstepanov) => (unassigned)
** Changed in: nova
Status: Confirmed => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1306381
Title:
A new agent should be represented as "id"
Status in OpenStack Compute (nova):
Opinion
Status in python-novaclient:
In Progress
Bug description:
When creating a new entity, most APIs return a response which includes
"id" to represent a new id. However, only agent API returns "agent_id"
as a new entity. This behavior seems inconsistent from the viewpoint
of whole Nova API.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1306381/+subscriptions
References