Keystone DB gets all non vip endpoints + openstack service conf files get keystone non vip
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Keystone Charm |
Fix Released
|
High
|
Edward Hope-Morley |
Bug Description
After battling with HA deploys for a while now, I have found the root cause(s) of my problems.... they are such that keystone creates non vip endpoints in the keystone.endpoints table for each openstack service to which it is related, AND all openstack service charms get non vip keystone endpoints transcluded into their .conf files.
I'm deploying all next branch charms minus glance-
juju --version <- 1.24.6-trusty-amd64
juju status --format tabular <- http://
deployer.yaml <- http://
It would be nice to see this fixed before the 15.10 release so as we can move forward into the next cycle with more stable HA deployment capability!
Thanks!
Changed in keystone (Juju Charms Collection): | |
assignee: | nobody → David Ames (thedac) |
status: | New → In Progress |
Changed in keystone (Juju Charms Collection): | |
importance: | Undecided → Medium |
Changed in charm-keystone: | |
assignee: | nobody → David Ames (thedac) |
importance: | Undecided → Medium |
status: | New → Incomplete |
Changed in keystone (Juju Charms Collection): | |
status: | Incomplete → Invalid |
no longer affects: | keystone (Juju Charms Collection) |
Changed in charm-keystone: | |
status: | Fix Committed → Fix Released |
"they are such that keystone creates non vip endpoints in the keystone.endpoints table for each openstack service to which it is related, AND all openstack service charms get non vip keystone endpoints transcluded into their .conf files."
This would indicate that clustered never successfully completed; the principle charms won't re-registered VIP's until the hacluster subordinates have indicated that clustering has been completed.
A 'sudo crm status' on any of the haclustered' services would be useful at this point as well.