[Bug 1355848] Re: Removing unit from existing percona cluster causes shared-db failure to related services

[James Page]

I see the issue; only the leader sets the username/password, and as we
don't have hooks (yet) in Juju for when the leader of a service changes,
we can't set it somewhere else easily when the existing leader is
removed.

This will be easily fixed when the leader election features land in
Juju; in the meantime we need to work something into the charms to deal
with this.

I think the same problem will happen with any charm that provides
credentials so raising a bug task for rabbitmq and keystone as well.

** Changed in: charms
       Status: New => Triaged

** Package changed: charms => rabbitmq-server (Juju Charms Collection)

** Also affects: keystone (Ubuntu)
   Importance: Undecided
       Status: New

** No longer affects: keystone (Ubuntu)

** Also affects: keystone (Juju Charms Collection)
   Importance: Undecided
       Status: New

** Changed in: keystone (Juju Charms Collection)
   Importance: Undecided => High

** Changed in: keystone (Juju Charms Collection)
       Status: New => Triaged

** Also affects: percona-cluster (Juju Charms Collection)
   Importance: Undecided
       Status: New

** Changed in: percona-cluster (Juju Charms Collection)
       Status: New => Triaged

** Changed in: percona-cluster (Juju Charms Collection)
   Importance: Undecided => High

** Summary changed:

- Removing unit from existing percona cluster causes shared-db failure to related services
+ Removing lead unit from existing service deployment causes failure to related services

** Summary changed:

- Removing lead unit from existing service deployment causes failure to related services
+ Removing lead unit from existing service deployment causes failure in related services due to incomplete contexts

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1355848

Title:
  Removing lead unit from existing service deployment causes failure in
  related services due to incomplete contexts

To manage notifications about this bug go to:
https://bugs.launchpad.net/charms/+source/keystone/+bug/1355848/+subscriptions