percona cluster next charm seeing issues in HA with 'hook failed: "shared-db-relation-changed" for mysql:shared-db'

Bug #1376779 reported by JuanJo Ciarlante
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
mysql (Juju Charms Collection)
New
Undecided
Unassigned

Bug Description

We have the percona cluster next charm rev 37 setup in a 3 node HA mode in LXC
containers, and are seeing a hook failure fairly consistantly across different
services (heat, glance, etc) while deploying:

   'hook failed: "shared-db-relation-changed" for mysql:shared-db'

In the unit log, I see:

  2014-10-02 05:39:02 INFO shared-db-relation-changed 2014-10-02 05:39:02.368 18707 CRITICAL glance [-] OperationalError: (OperationalError) (1045, "Access denied for user 'glance'@'x-y-z-101.maas' (using password: YES)") None None

But looking on the mysql unit, I see:

mysql> select user, host from mysql.user where user = 'glance';
+--------+----------------+
| user | host |
+--------+----------------+
| glance | x.y.z.101 |
| glance | x.y.z.90 |
+--------+----------------+

mysql> show grants for 'glance'@'x.y.z.101';
+--------------------------------------------------------------------------------------------------------------------+
| Grants for glance@x.y.z.101 |
+--------------------------------------------------------------------------------------------------------------------+
| GRANT USAGE ON *.* TO 'glance'@'x.y.z.101' IDENTIFIED BY PASSWORD '*THISISREALLYNOTMYPASSWORD' |
| GRANT ALL PRIVILEGES ON `glance`.* TO 'glance'@'x.y.z.101' |
+--------------------------------------------------------------------------------------------------------------------+

A quick duplication of the grants for 'glance'@'x-y-z-101.maas' later, and then
juju resolved --retry on the glance unit works.

This seems like another issue with using LXCs and not getting the right
hostnames added for access.

Please let us know if you need any further information.

JuanJo Ciarlante (jjo)
tags: added: canonical-bootstack
Revision history for this message
JuanJo Ciarlante (jjo) wrote :

NOTE this consistently happens when deploying perconaas per its README:
1 unit at a time ( FYI if deployed with -n3 it doesn't show this
behavior).

Additionally, after resolving as per above and continuing with
deployment, at the end shows the issue filed at
lp#1376466: "credentials lacking from some percona mysql relations".

no longer affects: opnfv
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.