Merge lp:~gnuoy/charms/trusty/percona-cluster/sstpasswd2 into lp:~le-charmers/charms/trusty/percona-cluster/leadership-election
Proposed by
Liam Young
Status: | Rejected |
---|---|
Rejected by: | Liam Young |
Proposed branch: | lp:~gnuoy/charms/trusty/percona-cluster/sstpasswd2 |
Merge into: | lp:~le-charmers/charms/trusty/percona-cluster/leadership-election |
Diff against target: |
217 lines (+78/-10) (has conflicts) 3 files modified
hooks/charmhelpers/contrib/database/mysql.py (+21/-6) hooks/percona_hooks.py (+54/-2) hooks/percona_utils.py (+3/-2) Text conflict in hooks/percona_hooks.py |
To merge this branch: | bzr merge lp:~gnuoy/charms/trusty/percona-cluster/sstpasswd2 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Edward Hope-Morley | Pending | ||
Review via email: mp+258979@code.launchpad.net |
This proposal supersedes a proposal from 2015-05-12.
To post a comment you must log in.
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.