| 2013-03-19 18:40:28 |
Lorin Hochstein |
description |
Error condition: A "glance" database has been created, and the correct credentials are in /etc/glance/glance-*.conf files, but "glance_mange version_control 0" and "glance_manage db_sync" have not yet been run.
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.registry.client [f8bb7547-2c91-4ae7-9d02-ded5fb07ebe0 8a44600ac8c6402fb781584022ceeb91 8283efb2e53d46e1a6bdbb2bdef9cb9a] Registry request GET /images/detail Exception
2013-03-19 14:09:14 29229 TRACE glance.registry.client Traceback (most recent call last):
2013-03-19 14:09:14 29229 TRACE glance.registry.client File "/usr/lib/python2.7/dist-packages/glance/registry/client.py", line 89, in do_request
2013-03-19 14:09:14 29229 TRACE glance.registry.client action, **kwargs)
2013-03-19 14:09:14 29229 TRACE glance.registry.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 63, in wrapped
2013-03-19 14:09:14 29229 TRACE glance.registry.client return func(self, *args, **kwargs)
2013-03-19 14:09:14 29229 TRACE glance.registry.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 444, in do_request
2013-03-19 14:09:14 29229 TRACE glance.registry.client headers=headers)
2013-03-19 14:09:14 29229 TRACE glance.registry.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 80, in wrapped
2013-03-19 14:09:14 29229 TRACE glance.registry.client return func(self, method, url, body, headers)
2013-03-19 14:09:14 29229 TRACE glance.registry.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 581, in _do_request
2013-03-19 14:09:14 29229 TRACE glance.registry.client raise exception.ServerError()
2013-03-19 14:09:14 29229 TRACE glance.registry.client ServerError: The request returned 500 Internal Server Error.
However, glance-registry will not contain any information about the nature of the error.
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). |
Error condition: A "glance" database has been created, and the correct credentials are in /etc/glance/glance-*.conf files, but "glance_mange version_control 0" and "glance_manage db_sync" have not yet been run.
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.registry.client [f8bb7547-2c91-4ae7-9d02-ded5fb07ebe0 8a44600ac8c6402fb781584022ceeb91 8283efb2e53d46e1a6bdbb2bdef9cb9a] Registry request GET /images/detail Exception
2013-03-19 14:09:14 29229 TRACE glance.registry.client Traceback (most recent call last):
2013-03-19 14:09:14 29229 TRACE glance.registry.client File "/usr/lib/python2.7/dist-packages/glance/registry/client.py", line 89, in do_request
2013-03-19 14:09:14 29229 TRACE glance.registry.client action, **kwargs)
2013-03-19 14:09:14 29229 TRACE glance.registry.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 63, in wrapped
2013-03-19 14:09:14 29229 TRACE glance.registry.client return func(self, *args, **kwargs)
2013-03-19 14:09:14 29229 TRACE glance.registry.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 444, in do_request
2013-03-19 14:09:14 29229 TRACE glance.registry.client headers=headers)
2013-03-19 14:09:14 29229 TRACE glance.registry.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 80, in wrapped
2013-03-19 14:09:14 29229 TRACE glance.registry.client return func(self, method, url, body, headers)
2013-03-19 14:09:14 29229 TRACE glance.registry.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 581, in _do_request
2013-03-19 14:09:14 29229 TRACE glance.registry.client raise exception.ServerError()
2013-03-19 14:09:14 29229 TRACE glance.registry.client ServerError: The request returned 500 Internal Server Error.
However, /var/log/glance/registry.log will not contain any information about the nature of the error.
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). |
|
