Comment 5 for bug 1813915

Ignore the "ERROR no relation id specified" messages - these are a bit of a red herring in terms of cause for this problem.

I've endeavoured to reproduce this issue with keystone+percona-cluster in one model, and neutron+nova+glance+dashboard+percona-cluster in a second one - the relation appears to be working for me, with all services ready and active and all catalog entries created by the keystone charm.

I also reviewed the data on the keystone identity-service interface - none of it relies on unit names for completeness so it should be fine and its all network space aware so again this should be ok.