I tested deploying only a very simple bundle with only keystone instead of whole openstack (after first step with ceph+vault+mysql-innodb-cluster as described earlier).
So, to be more specific:
- install ceph + vault + mysql-innodb-cluster
- wait for them to settle
- unlock vault
- init CA (using auto option)
- wait for it to settle
- deploy a very small bundle with only keystone + hacluster-keystone + keystone-mysql-router
- wait for it to settle
- deploy rest of openstack
Interesting is that just after deploying (with this small keystone bundle) all three keystone units go active/idle.
Then, after I deploy the rest of openstack and other charms start relating to keystone, then one of the keystone units fail.
Unit Workload Agent Machine Public address Ports Message
keystone/0* error idle 3/lxd/3 100.126.1.30 5000/tcp hook failed: "identity-service-
relation-changed"
It cycles between "updating endpoint for xxx" and "hook failed: identity-service-relation-changed".
I tested deploying only a very simple bundle with only keystone instead of whole openstack (after first step with ceph+vault+ mysql-innodb- cluster as described earlier).
So, to be more specific:
- install ceph + vault + mysql-innodb- cluster mysql-router
- wait for them to settle
- unlock vault
- init CA (using auto option)
- wait for it to settle
- deploy a very small bundle with only keystone + hacluster-keystone + keystone-
- wait for it to settle
- deploy rest of openstack
Interesting is that just after deploying (with this small keystone bundle) all three keystone units go active/idle.
Then, after I deploy the rest of openstack and other charms start relating to keystone, then one of the keystone units fail.
Unit Workload Agent Machine Public address Ports Message
keystone/0* error idle 3/lxd/3 100.126.1.30 5000/tcp hook failed: "identity-service-
relation-changed"
It cycles between "updating endpoint for xxx" and "hook failed: identity- service- relation- changed" .