yahoo-eng-team team mailing list archive

[OpenStack Infra <1496664@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/288960
Committed: https://git.openstack.org/cgit/openstack/api-site/commit/?id=96c0a3e8382017f168d61b72cf3c4ff8279693e6
Submitter: Jenkins
Branch:    master

commit 96c0a3e8382017f168d61b72cf3c4ff8279693e6
Author: Matt Riedemann <mriedem@xxxxxxxxxx>
Date:   Sat Mar 5 21:03:15 2016 -0500

    Compute: doc v2.12 microversion in os-virtual-interfaces
    
    Nova commit 45d1e3c1fa8f7921aeb1b04a2452ae10ccc6aa06 added
    the net_id attribute back to the os-virtual-interfaces response
    with the v2.12 microversion.
    
    Change-Id: Ibe7c0f99467e0a4b852348418a0e2e84afdc3a65
    Closes-Bug: #1496664


** Changed in: openstack-api-site
       Status: In Progress => Fix Released

-- 
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:
  Fix Released

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