Deploying HA configuration at the same time as adding all relations fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
keystone (Juju Charms Collection) |
Fix Released
|
High
|
Unassigned |
Bug Description
Deploying a clustered keystone service at the same time as adding all relations causes hook execution failures in the identity-changed hook; This is because the cluster-changed hooks don't get fired prior to the identity-changed hooks, so the charm looks for the local endpoint on the wrong port (keystone has not been configured to listen on default port -10):
2014-11-16 19:45:21 INFO juju-log cluster:3: Creating requested role: Member
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 INFO cluster-
2014-11-16 19:45:21 ERROR juju.worker.uniter uniter.go:486 hook failed: exit status 1
The best workaround I've found is to deploy a single keystone unit, wait for all relation hook events to complete, and then add another two units to complete clustering configuration.
We should probably make the function that determines the port check actual ports, rather than guess based on relation state - or maybe even query the keystone.conf file.
tags: | added: ha openstack |
Changed in keystone (Juju Charms Collection): | |
status: | New → Confirmed |
importance: | Undecided → High |
status: | Confirmed → Triaged |
tags: | added: landscape |
tags: | added: canonical-bootstack |
yep just hit this 4 times in a row using the autopilot. Closing lp:1413857 as duplicate