xml namespace of limits call is incorrect

Bug #949098 reported by Gabe Westmaas
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Undecided
Philip Knouff

Bug Description

Docs: http://docs.openstack.org/api/openstack-compute/2/content/ProgramaticLimits.html#d6e634
xmlns is supposed to be: "http://docs.openstack.org/common/api/v1.0"
Currently it is: "http://docs.openstack.org/compute/api/v1.1"

You can reproduce this by making a call to /limits with "accept: application/json" as a header.

Revision history for this message
Gabe Westmaas (westmaas) wrote :

Just realized this same problem may apply to the versions resource, should be confirmed.

Changed in nova:
assignee: nobody → Philip Knouff (philip-knouff)
Revision history for this message
Brian Waldon (bcwaldon) wrote :

gabriel: should the accept header be application/json or application/xml?

Revision history for this message
Gabe Westmaas (westmaas) wrote :

To recreate the issue, yes, that should have been application/xml.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/5047

Changed in nova:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/5047
Committed: http://github.com/openstack/nova/commit/26b97b5515c81ae104c714a217dc3fdf3f7c37cf
Submitter: Jenkins
Branch: master

commit 26b97b5515c81ae104c714a217dc3fdf3f7c37cf
Author: Philip Knouff <email address hidden>
Date: Wed Mar 7 22:43:48 2012 +0000

    Fix XML namespaces for limits extensions and versions

    fixes bug #949098

    Change-Id: I7e745c45fc142eb18e16dca63da15ebc3cb6ba36

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
milestone: none → essex-rc1
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: essex-rc1 → 2012.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.