Nova should retry connections if started before MySQL
Bug #876663 reported by
IT Archmerc
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Wishlist
|
Unassigned | ||
Diablo |
Fix Released
|
Undecided
|
Unassigned | ||
OpenStack Dashboard (Horizon) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I had a working installation of a cloud and compute node on a single server running Ubuntu 11.04. Everything was fine until I rebooted the server and found that upon each reboot, the nova services were starting prior to MySQL. Once the server came up, MySQL was running, but nova-compute, nova-network, nova-volume, and nova-scheduler had all failed with messages about not able to connect to MySQL.
Nova should probably be able to retry until MySQL is available.
summary: |
- Nova should be able to start before MySQL + Nova should retry connections if started before MySQL |
Changed in nova: | |
importance: | Undecided → Wishlist |
status: | Incomplete → Confirmed |
Changed in nova: | |
status: | Confirmed → Fix Committed |
status: | Fix Committed → Fix Released |
tags: |
added: verification-done removed: verification-needed |
To post a comment you must log in.
I think the reason mysql is not included in the `start on` field is because installs with more than 1 server will likely not have mysql installed on every server...