Glance does not recover database connection automatically after DB restart
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Fix Released
|
Low
|
Unmesh Gurjar | ||
glance (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Scenario: Configure Glance Registry to use MySQL for metadata storage. While Glance Registry is running, restart the MySQL service. Now execute the 'glance index' command to fetch image list from glance.
Actual Response: HTTP 500 Internal Server Error, with following error in the stack trace "OperationalError: (OperationalError) (2006, 'MySQL server has gone away')".
Expected Response: HTTP 200 (with list of registered images in response body).
Branch: milestone-proposed
This typically happens for the first connection (to database) after the database service restarts, the following requests work fine.
Once the database server comes up, Glance should re-establish the database connection and not return error.
Changed in glance: | |
status: | New → Confirmed |
assignee: | nobody → Unmesh Gurjar (unmesh-gurjar) |
description: | updated |
Changed in glance: | |
milestone: | none → essex-rc2 |
Changed in glance: | |
milestone: | essex-rc2 → 2012.1 |
Changed in glance (Ubuntu Precise): | |
status: | New → Fix Released |
Changed in glance (Ubuntu): | |
status: | New → Fix Released |
Setting to low priority since the subsequent requests work fine...