[Yahoo-eng-team] [Bug 1306381] Re: A new agent should be represented as "id"

2017-05-16 Thread Alex Xu
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

[Yahoo-eng-team] [Bug 1306381] Re: A new agent should be represented as "id"

2016-03-28 Thread Preeti
** Changed in: nova Assignee: Preeti (pandey-preeti1) => (unassigned) ** Changed in: tempest Assignee: Preeti (pandey-preeti1) => (unassigned) ** No longer affects: tempest -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is

[Yahoo-eng-team] [Bug 1306381] Re: A new agent should be represented as "id"

2016-03-19 Thread Preeti
** Also affects: tempest Importance: Undecided Status: New ** Changed in: tempest Assignee: (unassigned) => Preeti (pandey-preeti1) ** Changed in: tempest Status: New => Incomplete ** Changed in: tempest Status: Incomplete => In Progress -- You received this bug

[Yahoo-eng-team] [Bug 1306381] Re: A new agent should be represented as "id"

2016-03-14 Thread Preeti
** Also affects: nova Importance: Undecided Status: New ** Changed in: nova Assignee: (unassigned) => Preeti (pandey-preeti1) ** No longer affects: nova ** Also affects: python-novaclient Importance: Undecided Status: New ** Changed in: python-novaclient