BootStack encountered this same error today, when removing and re-adding a keystone unit on a cloud.
the cloud is running focal/ussuri, and keystone is on cs:keystone-330 . In our case, mysql did not go into an error state, but we were able to work around the issue by setting the db-initialised flag:
$ juju run -u keystone/leader 'leader-set db-initialised=True'
Note that we had verified keystone itself was running as expected, but relational data was not being shared (nor relations created) with sibling units, via the identity-service interface.
BootStack encountered this same error today, when removing and re-adding a keystone unit on a cloud.
the cloud is running focal/ussuri, and keystone is on cs:keystone-330 . In our case, mysql did not go into an error state, but we were able to work around the issue by setting the db-initialised flag:
$ juju run -u keystone/leader 'leader-set db-initialised= True'
Note that we had verified keystone itself was running as expected, but relational data was not being shared (nor relations created) with sibling units, via the identity-service interface.