Root password update via config can cause hook error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Percona Cluster Charm |
Fix Released
|
High
|
Liam Young |
Bug Description
This bug is down to hook ordering and the caching of the config context.
1) Root password via config
2) An update-status hook *1 is already queued on unitX
3) unitX runs update-status which does not act on the password change but does cache the new config value
4) config-changed hook runs on unitX, config(
Reproduce: This is slightly artificial but illustrates the point.
1) Enter a debug-hooks session on unitX.
2) Change the root password via config.
3) In the config-changed session on unitX run the update-status script *not* config-changed.
4) Change an unrelated option via config like nagios_
5) Run the config-changed hook on unitX. After the hook completes the root password on unitX is still the old value and does not match what is in the leaderdb or charm config.
Changed in charm-percona-cluster: | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Liam Young (gnuoy) |
Changed in charm-percona-cluster: | |
milestone: | none → 19.07 |
Changed in charm-percona-cluster: | |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. opendev. org/673132
Review: https:/