Unclear error message if database has not been initialized
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Won't Fix
|
Low
|
Unassigned | ||
glance (openSUSE) |
New
|
Undecided
|
Unassigned |
Bug Description
Error condition: A "glance" database has been created, and the correct credentials are in /etc/glance/
When a user does a "glance index", then the glance-api.log will contain this trace, suggesting an error in glance-registry
2013-03-19 14:09:14 ERROR glance.
2013-03-19 14:09:14 29229 TRACE glance.
2013-03-19 14:09:14 29229 TRACE glance.
2013-03-19 14:09:14 29229 TRACE glance.
2013-03-19 14:09:14 29229 TRACE glance.
2013-03-19 14:09:14 29229 TRACE glance.
2013-03-19 14:09:14 29229 TRACE glance.
2013-03-19 14:09:14 29229 TRACE glance.
2013-03-19 14:09:14 29229 TRACE glance.
2013-03-19 14:09:14 29229 TRACE glance.
2013-03-19 14:09:14 29229 TRACE glance.
2013-03-19 14:09:14 29229 TRACE glance.
2013-03-19 14:09:14 29229 TRACE glance.
However, /var/log/
It would help admins if the glance-registry did a check for this and outputted a meaningful error message to its log.
This was tested against folsom on Ubuntu 12.04 (cloud archive).
summary: |
- Confusing error messages if database has not been initialized + Unclear error message if database has not been initialized |
tags: | added: ops |
description: | updated |
Changed in glance: | |
assignee: | nobody → Lee Li (lilinguo) |
Changed in glance: | |
importance: | Undecided → Low |
Changed in glance: | |
assignee: | Lee Li (lilinguo) → nobody |
status: | Confirmed → Incomplete |
Changed in glance: | |
assignee: | nobody → Dharini Chandrasekar (dharini-chandrasekar) |
Changed in glance: | |
assignee: | Dharini Chandrasekar (dharini-chandrasekar) → nobody |
This information really helps me!