Merge lp:~gnuoy/charms/trusty/percona-cluster/sstpasswd into lp:~le-charmers/charms/trusty/percona-cluster/leadership-election
Proposed by
Liam Young
Status: | Superseded |
---|---|
Proposed branch: | lp:~gnuoy/charms/trusty/percona-cluster/sstpasswd |
Merge into: | lp:~le-charmers/charms/trusty/percona-cluster/leadership-election |
Diff against target: |
22 lines (+7/-3) 1 file modified
hooks/percona_hooks.py (+7/-3) |
To merge this branch: | bzr merge lp:~gnuoy/charms/trusty/percona-cluster/sstpasswd |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Edward Hope-Morley | Needs Fixing | ||
Review via email: mp+258857@code.launchpad.net |
This proposal has been superseded by a proposal from 2015-05-13.
To post a comment you must log in.
Unmerged revisions
- 79. By Liam Young
-
Fix le bug where non-leaders try and migrate on disk passwords to peer relation and explode
I'm surprised this has not given is more issue in production. So, unfortunately the way you are doing things here will break the case where no password is provided in config.yaml sst-passwd and is therefore auto-generated and shared on the peer relation. A better option might be to add a new param to get_mysl_password() e.g. create_ if_none= False so that we check the peer rel and only create a new one if create_if_none if True which we would be the case only if we were the leader. FTR get_mysql_ password( ) is also called from install() and config_changed() so will need protection there too.