api services need better error handling on startup
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
In Progress
|
Undecided
|
Unassigned |
Bug Description
Recently when deploying Heat on CentOS 6 (Python 2.6) we got following errors for all api services due to missing config files:
2014-09-12 09:59:27.461 2383 CRITICAL heat [-] UnicodeError: Message objects do not support str() because they may contain non-ascii characters. Please use unicode() or translate() instead.
2014-09-12 09:59:27.461 2383 TRACE heat Traceback (most recent call last):
2014-09-12 09:59:27.461 2383 TRACE heat File "/usr/bin/
2014-09-12 09:59:27.461 2383 TRACE heat sys.exit("ERROR: %s" % e)
2014-09-12 09:59:27.461 2383 TRACE heat File "/usr/lib/
2014-09-12 09:59:27.461 2383 TRACE heat raise UnicodeError(msg)
2014-09-12 09:59:27.461 2383 TRACE heat UnicodeError: Message objects do not support str() because they may contain non-ascii characters. Please use unicode() or translate() instead.
The actual error in fact was
Unable to load heat-api from configuration file /etc/heat/
Got: ImportError('No module named keystonemiddlew
but was masked by the traceback above.
Looks like we should "sixify" error handling in heat-api-* scripts to better present errors to deployers.
Changed in heat: | |
assignee: | nobody → Pavlo Shchelokovskyy (pshchelo) |
Changed in heat: | |
assignee: | Pavlo Shchelokovskyy (pshchelo) → nobody |
Fix proposed to branch: master /review. openstack. org/121473
Review: https:/