OpenStack Compute (Nova)

nova-api returns 500 if an aggregate is created in a non existent availability zone

Reported by Armando Migliaccio on 2012-02-28
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Undecided
John Garbutt

Bug Description

This is because InvalidAggregateAction is not caught in the OSAPI extension for aggregates.

a 4xx code is more appropriate.

Changed in nova:
assignee: nobody → Citrix OpenStack development team (citrix-openstack)
status: New → Confirmed
Changed in nova:
assignee: Citrix OpenStack development team (citrix-openstack) → John Garbutt (johngarbutt)
Changed in nova:
status: Confirmed → In Progress

Reviewed: https://review.openstack.org/4640
Committed: http://github.com/openstack/nova/commit/9f7595aa0f464dc7344e0639951ea731dcfbeca5
Submitter: Jenkins
Branch: master

commit 9f7595aa0f464dc7344e0639951ea731dcfbeca5
Author: John Garbutt <email address hidden>
Date: Tue Feb 28 18:14:25 2012 +0000

    Fixes bug 942549

    Ensure a more meaninful error is reported when an aggregate is created in a
    non-exsistent availability zone.

    Change-Id: I15ea6c884bb6f326df1d88019ee0ecf070196d1e

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

Other bug subscribers