Not possible to set 'sst-password' after installation.
Bug #1603497 reported by
Jorge Niedbalski
This bug report is a duplicate of:
Bug #1436093: Support changes to root and sstuser passwords.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Percona Cluster Charm |
Triaged
|
Medium
|
Unassigned | ||
| percona-cluster (Juju Charms Collection) |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
[Description]
If the user tries to set the sst-pass configuration directive after the charm
has been deployed, the new password value is not applied.
This also affects the scale-out scenario, since the replication mechanism requires
the existence of the sst-user with a previously configured password.
[Fix]
The fix should take in consideration the following:
1) Create/Update the current sst-user password on config-changed.
2) If another unit of the percona-cluster service joins and there is no a
sst-password set, then it needs to block the operation, until the administrator provides one (or maybe use the current mysql password?)
| Changed in percona-cluster (Juju Charms Collection): | |
| importance: | Undecided → Medium |
| tags: | added: sts |
Revision history for this message
| James Page (james-page) wrote | #1 |
| Changed in percona-cluster (Juju Charms Collection): | |
| status: | New → Triaged |
| Changed in charm-percona-cluster: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| Changed in percona-cluster (Juju Charms Collection): | |
| status: | Triaged → Invalid |
To post a comment you must log in.
I'd actually like to look at this from two ways
a) support not providing passwords at all, using leader storage and leader election
This complicates bootstrap of the cluster, so the charm will need some refactoring.
b) support changing the password after deployment
Much more tricky - but probably manageable from the lead unit.