OpenStack Heat

heat.db.sqlalchemy.manage doesn't respect config sql_connection option

Bug #1087741 reported by Steven Hardy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
High
Steven Hardy
OpenStack Heat 2013.1 "grizzly"
Grizzly
Fix Released
High
Steven Hardy
OpenStack Heat grizzly-2 "g2"

Bug Description

Running heat-db-setup, or the underlying python -m heat.db.sqlalchemy.manage * will fail if you want a different configuration to that hard-coded in the heat/db/sqlalchemy/manage.py file

We should check cfg.CONF.sql_connection so we can pick up non-default DB details from /etc/heat/heat-engine.conf

Revision history for this message
Steven Hardy (shardy) wrote :

We actually can't very easily use cfg.CONF because it insists on parsing the CLI and there's no easy way to just retrieve the config-file values

Changed in heat:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Steven Hardy (shardy)
Revision history for this message
Steven Hardy (shardy) wrote :

Fix committed:

14d8a7a heat-db-setup read engine config file for DB connection details

Changed in heat:
status: Triaged → Fix Committed
Thierry Carrez (ttx)
Changed in heat:
milestone: none → grizzly-2
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in heat:
milestone: grizzly-2 → 2013.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.