upgrading from charmstore version 15 to >= 16 results in loss of db access
Bug #1451890 reported by
James Page
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| percona-cluster (Juju Charms Collection) |
Fix Released
|
Critical
|
Edward Hope-Morley | ||
Bug Description
Upgrading percona-cluster from charmstore revision 15 to a greater version causes all relation presented passwords to be changed, without any related change in the underlying grants.
This results in all remote clients being blocked from the database when they reconfigure themselves with the new password.
Related branches
lp:~hopem/charm-helpers/fix-peerstore-passwd-lp1451890
- Liam Young (community): Approve
-
Diff: 190 lines (+129/-9)2 files modifiedcharmhelpers/contrib/database/mysql.py (+30/-9)
tests/contrib/database/test_mysql.py (+99/-0)
lp:~hopem/charms/trusty/percona-cluster/fix-peerstore-passwd-lp1451890
- Liam Young (community): Approve
-
Diff: 320 lines (+108/-26)9 files modifiedhooks/charmhelpers/contrib/charmsupport/nrpe.py (+3/-1)
hooks/charmhelpers/contrib/database/mysql.py (+32/-11)
hooks/charmhelpers/core/hookenv.py (+40/-1)
hooks/charmhelpers/core/host.py (+5/-1)
hooks/charmhelpers/core/services/helpers.py (+2/-2)
hooks/charmhelpers/core/strutils.py (+2/-2)
hooks/charmhelpers/core/unitdata.py (+1/-1)
tests/charmhelpers/contrib/amulet/utils.py (+8/-1)
tests/charmhelpers/contrib/openstack/amulet/deployment.py (+15/-6)
lp:~hopem/charm-helpers/fix-peerstore-passwd-lp1451890-stable-backport
- Liam Young (community): Approve
-
Diff: 190 lines (+129/-9)2 files modifiedcharmhelpers/contrib/database/mysql.py (+30/-9)
tests/contrib/database/test_mysql.py (+99/-0)
lp:~hopem/charms/trusty/percona-cluster/fix-peerstore-passwd-lp1451890-stable-backport
- Liam Young (community): Approve
-
Diff: 330 lines (+109/-27)10 files modifiedcharm-helpers.yaml (+1/-1)
hooks/charmhelpers/contrib/charmsupport/nrpe.py (+3/-1)
hooks/charmhelpers/contrib/database/mysql.py (+32/-11)
hooks/charmhelpers/core/hookenv.py (+40/-1)
hooks/charmhelpers/core/host.py (+5/-1)
hooks/charmhelpers/core/services/helpers.py (+2/-2)
hooks/charmhelpers/core/strutils.py (+2/-2)
hooks/charmhelpers/core/unitdata.py (+1/-1)
tests/charmhelpers/contrib/amulet/utils.py (+8/-1)
tests/charmhelpers/contrib/openstack/amulet/deployment.py (+15/-6)
Revision history for this message
| James Page (james-page) wrote | #1 |
| Changed in percona-cluster (Juju Charms Collection): | |
| importance: | Undecided → Critical |
| status: | New → Confirmed |
| tags: | added: backport-potential openstack |
| Changed in percona-cluster (Juju Charms Collection): | |
| milestone: | none → 15.07 |
| Changed in percona-cluster (Juju Charms Collection): | |
| assignee: | nobody → Edward Hope-Morley (hopem) |
| Changed in percona-cluster (Juju Charms Collection): | |
| status: | Confirmed → In Progress |
| Changed in percona-cluster (Juju Charms Collection): | |
| status: | In Progress → Fix Committed |
| Changed in percona-cluster (Juju Charms Collection): | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
The issue is that the key used to store access credentials on the peer relation was changed between these two versions - e.g
cinder.passwd: XXXXyyyy (revision 15)
mysql-cinder.
the original data is still present, and its possible to fix by using juju run to set the data back manually:
juju run --service mysql/0 "relation-set -r <cluster:id> mysql-cinder=
get the data first by using
juju run --service mysql/0 "relation-get -r <cluster:id> - mysql/0"
note that this must be run on the unit leading the cluster - at this point its the unit owing the VIP