get Floating IP Pools response is 403 (forbidden)

Bug #1091668 reported by Mauro S M Rodrigues
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
High
Mauro S M Rodrigues

Bug Description

Once you try to request using GET in Floating IP Pools extension, the response is always 403 (forbidden).

This is caused by incompatibilities between then method name in backend (get_floating_pools) and the name in the policy.json (get_floating_**ip**_pools).

Changed in nova:
status: New → Confirmed
assignee: nobody → Mauro Sergio Martins Rodrigues (maurosr)
importance: Undecided → High
Changed in nova:
status: Confirmed → In Progress
Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote :

Mauro, Is there a review for this bug already?

Revision history for this message
Mauro S M Rodrigues (maurorodrigues) wrote :

Hi dims!
yes, I don't know why hudson didn't post a reference here automatically. The link is: https://review.openstack.org/#/c/18311/

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

Reviewed: https://review.openstack.org/18311
Committed: http://github.com/openstack/nova/commit/93516a528d83d4802421cfb3ee0695f06bdd5f8b
Submitter: Jenkins
Branch: master

commit 93516a528d83d4802421cfb3ee0695f06bdd5f8b
Author: Mauro S. M. Rodrigues <email address hidden>
Date: Mon Jan 21 12:39:47 2013 -0500

    Fix get Floating ip pools action name to match with its policy

    Get Floating IP Pools is always responding 403 (Forbidden) cause its method
    name, which is also being used as action name, doesn't match with the name in
    policy.json file.
    I opted for this approach cause it also fixes the different names between the
    extension (which is named floating **ip** pools instead of floating pools) and
    the backend.
    Another good practice would be change the default_floating_pool option to
    default_float_ip_pool, but that would require change the conf file and possibly
    break some compatibility.

    Fixes bug 1091668

    Change-Id: I2627e8b0f45c5c39bbbf1a4a12b448e1992fa4b4

Changed in nova:
status: In Progress → Fix Committed
tags: added: folsom-backport-potential
Thierry Carrez (ttx)
Changed in nova:
milestone: none → grizzly-3
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: grizzly-3 → 2013.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.