Comment 1 for bug 2025746

Yup, you've entered 'undefined behaviour' territory for the keystone charm; the design is not really set up to swap out a keystone and swap in another; there's obviously some behaviour on either the related charms (e.g. glance) or on keystone on the relations that's causing the issue.

You could try the "rotate-service-user-password" action on the keystone charm, which will generate a new password and then try to push it out to the related service. This may correct things // however, it's definitely not been tested in this environment.

I'm setting this to wish-list as it will probably require some clean-up code/action to 'reset' the relation and re-fetch all the data from keystone in related charms. need a bit of digging to work out what is going on.