If Glance is temporarily unavailable, handle gracefully

Bug #951200 reported by Devin Carlen on 2012-03-09
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
John Postlethwait

Bug Description

Currently if glance is unavailable an uncaught exception bubbles up and the generic 500 error is raised. This should be trapped internally and a note saying "Image Registry is currently unavailable."

Exception at /nova/images_and_snapshots/
Unknown error occurred! <html><body><h1>503 Service Unavailable</h1>
No server is available to handle this request.

Tres Henry (tres) on 2012-03-10
Changed in horizon:
status: Confirmed → In Progress
Tres Henry (tres) wrote :

If I kill Glance API in a fresh devstack here's what I see: http://i.imgur.com/ZT1RC.png

I'm wondering if the error you were seeing was from a different service being unavailable?

Changed in horizon:
assignee: Nebula (nebula) → John Postlethwait (john-postlethwait)
Tres Henry (tres) wrote :

The issue here is that 503's are not being gracefully handled. We should add some code to exceptions.handle so that 503's returned from API calls add a message instead of bubbling up to the generic 503 error page.

This Glance issue is related to this: https://bugs.launchpad.net/glance/+bug/952618

Short of it is Glance raises Exception classed exceptions for unknown HTTP error codes. Not very easy to deal with those so I will be writing something in to api/glance.py to deal with them.

Fixed in change id: I7cbfa74d340d25d523ab8fb18138f5cf7d33a9d9

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

Other bug subscribers