yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #47484
[Bug 1496664] Re: V2.1 comp mode behavior should be fixed for diff of v2 and v2.1 APIs
** Also affects: openstack-api-site
Importance: Undecided
Status: New
--
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/1496664
Title:
V2.1 comp mode behavior should be fixed for diff of v2 and v2.1 APIs
Status in OpenStack Compute (nova):
Fix Released
Status in openstack-api-site:
New
Bug description:
There are some cases where v2.1 is different than v2.0 -
- VIF API - no net-id in v2.1
- rate limit bits - not present in v2.1
- extension info - namespace diff
For above cases, current v2.1 compatible mode behaves same as v2.1 not v2.
Failure in - http://logs.openstack.org/86/224386/1/check/gate-nova-tox-functional/b98e535/testr_results.html.gz
As v2.1 comp mode should behave same as v2 instead of v2.1, we should
fix those cases to return same response as v2 APIs does.
I am not sure about rate limit and extension info things, should we
fix those?
It was found when we start running v2.1 comp mode sample test against
v2 sample files instead of v2.1 one. -
https://review.openstack.org/#/c/224386/
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1496664/+subscriptions
References