mysql trusty charm on vivid: hook failed: "slave-relation-changed" (Slave is not configured or failed to initialize properly)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| mysql (Juju Charms Collection) |
New
|
Undecided
|
Unassigned | ||
Bug Description
mysql trusty charm on vivid: hook failed: "slave-
For each of the mysql slave units, the applied server_id values are all 0, instead of being a unique ID as required.
Here are two as an example:
# from mysql-slave/0 unit:
$ mysql --version
mysql Ver 14.14 Distrib 5.6.23, for debian-linux-gnu (x86_64) using EditLine wrapper
$ mysql -u root -p -e "SHOW VARIABLES;"
http://
# from mysql-slave/10 unit:
$ mysql --version
mysql Ver 14.14 Distrib 5.6.23, for debian-linux-gnu (x86_64) using EditLine wrapper
$ mysql -u root -p -e "SHOW VARIABLES;"
http://
$ juju-deployer -B -v -c bundles/
...
2015-04-15 23:57:21 [INFO] deployer.import: Adding relations...
2015-04-15 23:57:21 [INFO] deployer.import: Adding relation mysql-slave:slave <-> mysql:master
2015-04-15 23:57:22 [DEBUG] deployer.import: Waiting for relation convergence 60s
2015-04-15 23:58:22 [ERROR] deployer.env: The following units had errors:
unit: mysql-slave/16: machine: 19 agent-state: error details: hook failed: "slave-
unit: mysql-slave/7: machine: 10 agent-state: error details: hook failed: "slave-
unit: mysql-slave/2: machine: 5 agent-state: error details: hook failed: "slave-
unit: mysql-slave/17: machine: 20 agent-state: error details: hook failed: "slave-
unit: mysql-slave/5: machine: 8 agent-state: error details: hook failed: "slave-
unit: mysql-slave/8: machine: 11 agent-state: error details: hook failed: "slave-
unit: mysql-slave/11: machine: 14 agent-state: error details: hook failed: "slave-
unit: mysql-slave/6: machine: 9 agent-state: error details: hook failed: "slave-
unit: mysql-slave/4: machine: 7 agent-state: error details: hook failed: "slave-
unit: mysql-slave/14: machine: 17 agent-state: error details: hook failed: "slave-
unit: mysql-slave/15: machine: 18 agent-state: error details: hook failed: "slave-
unit: mysql-slave/0: machine: 3 agent-state: error details: hook failed: "slave-
unit: mysql-slave/13: machine: 16 agent-state: error details: hook failed: "slave-
unit: mysql-slave/10: machine: 13 agent-state: error details: hook failed: "slave-
unit: mysql-slave/3: machine: 6 agent-state: error details: hook failed: "slave-
unit: mysql-slave/12: machine: 15 agent-state: error details: hook failed: "slave-
unit: mysql-slave/9: machine: 12 agent-state: error details: hook failed: "slave-
unit: mysql-slave/18: machine: 21 agent-state: error details: hook failed: "slave-
unit: mysql-slave/1: machine: 4 agent-state: error details: hook failed: "slave-
2015-04-15 23:58:22 [INFO] deployer.cli: Deployment stopped. run time: 352.28
# from mysql-slave/0 unit (same errors on all slave units):
2015-04-15 23:57:41 INFO unit.mysql-
ERROR 1794 (HY000) at line 1: Slave is not configured or failed to initialize properly. You must at least set --server-id to enable either a master or a slave. Additional error messages can be found in the MySQL error log.
2015-04-15 23:57:41 ERROR juju.worker.
juju stat: http://
mysql-slave/0 unit log: http://
mysql-slave/0 unit syslog: http://
mysql-slave/0 unit dmesg: http://
mysql-slave/0 unit mysql error.log: http://
mysql-slave/0 unit pkg versions: http://
bundle as tested: http://
bundle on lp: http://
FYI: the -d trusty target does deploy successfully (http://
Related branches
| Ryan Beisner (1chb1n) wrote | #1 |
| description: | updated |
Just in case anyone is wondering what the heck I do with such an odd bundle... I use it in place of a full OpenStack deployment bundle for basic undercloud testing, environment validation, and for exercising juju/proposed, juju/devel andjuju-deployer. The OpenStack bundles have a ton of relations and hooks firing off, all of which take time and increase potential for race or other issues. In comparison, the bundle used here is fast and simple, and roughly the same machine footprint.