Keystone does not provide relation data when clustered
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Keystone Charm |
Fix Released
|
Critical
|
Liam Young |
Bug Description
When deploying keystone with a hacluster relation it does not provide relation data to its identity-service clients because it never thinks it is clustered.
The reason is that the charm uses goal state to see how many units it should have a relation with.
goal-state reports:
# goal-state
units:
keystone/0:
status: active
since: 2018-11-05 13:43:12Z
keystone/1:
status: active
since: 2018-11-05 13:49:29Z
keystone/2:
status: active
since: 2018-11-05 13:48:28Z
relations:
ha:
keystone-
status: joined
since: 2018-11-05 13:40:07Z
keystone-
status: active
since: 2018-11-05 13:50:48Z
keystone-
status: active
since: 2018-11-05 13:51:00Z
keystone-
status: active
since: 2018-11-05 13:52:53Z
So each keystone unit thinks it should have a relation with all the keystone-
root@juju-
clustered: "yes"
egress-subnets: 10.5.0.21/32
ingress-address: 10.5.0.21
private-address: 10.5.0.21
root@juju-
ERROR cannot read settings for unit "keystone-
Changed in charm-keystone: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
assignee: | nobody → Liam Young (gnuoy) |
milestone: | none → 18.11 |
status: | Confirmed → In Progress |
Changed in charm-keystone: | |
status: | Fix Committed → Fix Released |
https:/ /bugs.launchpad .net/juju/ +bug/1801765