Database not initialised after mysql scale up/down
Bug #1947317 reported by
Brett Milford
This bug report is a duplicate of:
Bug #1942289: Keystone become "Database not initialised" after scale up and scale down.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Keystone Charm |
New
|
Undecided
|
Unassigned | ||
Bug Description
Keystone status reports "Database not initialised" after mysql (Percona cluster) has been scaled up then down.
The key to this appears to be that at some point
db-initialised: "True"
Is removed from leader settings and is never restored.
Steps to reproduce
1. Deploy bundle: https:/
2. juju add-unit mysql
3. juju remove-unit mysql
4. keystone units become blocked i.e https:/
| description: | updated |
| description: | updated |
To post a comment you must log in.
