Comment 9 for bug 1721580

I made a debug and on the percona-cluster side it fails at the beginning of the "shared-db-relation-changed" hook:

@hooks.hook('shared-db-relation-changed')
def shared_db_changed(relation_id=None, unit=None):
    #log("DEBUG: shared_db_changed")
    if not seeded():
        print ("TYTUS 1")
        log("Percona cluster not yet bootstrapped - deferring shared-db rel "
            "until bootstrapped", DEBUG)
        return

The following is being logged:

2017-10-09 14:12:11 INFO juju.worker.uniter resolver.go:121 no operations in progress; waiting for changes
2017-10-09 14:12:11 INFO juju.worker.uniter.relation relations.go:431 joining relation "designate:shared-db percona-cluster:shared-db"
2017-10-09 14:12:11 INFO juju.worker.uniter.relation relations.go:467 joined relation "designate:shared-db percona-cluster:shared-db"
2017-10-09 14:12:11 INFO juju.worker.uniter resolver.go:121 no operations in progress; waiting for changes
2017-10-09 14:12:24 INFO juju.worker.uniter resolver.go:121 no operations in progress; waiting for changes
2017-10-09 14:12:24 INFO juju.worker.uniter.operation runhook.go:116 skipped "shared-db-relation-joined" hook (missing)
2017-10-09 14:12:24 INFO juju.worker.uniter resolver.go:121 no operations in progress; waiting for changes
2017-10-09 14:12:29 INFO juju-log shared-db:628: Sufficient number of peer units to form cluster 3
2017-10-09 14:12:31 INFO juju-log shared-db:628: Sufficient number of peer units to form cluster 3
2017-10-09 14:12:32 INFO shared-db-relation-changed * Percona XtraDB Cluster up and running
2017-10-09 14:12:32 INFO juju-log shared-db:628: Unit is ready
2017-10-09 14:12:34 INFO shared-db-relation-changed TYTUS 1
2017-10-09 14:12:34 INFO shared-db-relation-changed TYTUS 1
2017-10-09 14:12:34 INFO shared-db-relation-changed TYTUS 1
2017-10-09 14:12:34 INFO shared-db-relation-changed TYTUS 1
2017-10-09 14:12:34 INFO shared-db-relation-changed TYTUS 1
2017-10-09 14:12:34 INFO shared-db-relation-changed TYTUS 1
2017-10-09 14:12:34 INFO shared-db-relation-changed TYTUS 1
2017-10-09 14:12:34 INFO shared-db-relation-changed TYTUS 1
2017-10-09 14:12:34 INFO shared-db-relation-changed TYTUS 1
2017-10-09 14:12:34 INFO shared-db-relation-changed TYTUS 1
2017-10-09 14:12:34 INFO shared-db-relation-changed TYTUS 1
2017-10-09 14:12:34 INFO shared-db-relation-changed TYTUS 1
2017-10-09 14:12:34 INFO shared-db-relation-changed TYTUS 1
2017-10-09 14:12:34 INFO shared-db-relation-changed TYTUS 1
2017-10-09 14:12:34 INFO shared-db-relation-changed TYTUS 1
2017-10-09 14:12:34 INFO shared-db-relation-changed TYTUS 1
2017-10-09 14:12:34 INFO shared-db-relation-changed TYTUS 1
2017-10-09 14:12:34 INFO shared-db-relation-changed TYTUS 1
2017-10-09 14:12:34 INFO shared-db-relation-changed TYTUS 1
2017-10-09 14:12:34 INFO shared-db-relation-changed TYTUS 1
2017-10-09 14:12:34 INFO juju.worker.uniter.operation runhook.go:113 ran "shared-db-relation-changed" hook

However, I cannot see the "Percona cluster not yet bootstrapped" message. Also, percona-cluster is bootstrapped:

percona-cluster/0 active executing 27/lxd/0 100.107.3.11 3306/tcp (update-status) Unit is ready
  check-mk-agent/548 active idle 100.107.3.11 ready
  nrpe/121 unknown idle 100.107.3.11
  pxc-hacluster/1 active idle 100.107.3.11 Unit is ready and clustered
percona-cluster/1 active idle 31/lxd/1 100.107.67.12 3306/tcp Unit is ready
  check-mk-agent/552 active idle 100.107.67.12 ready
  nrpe/123 unknown idle 100.107.67.12
  pxc-hacluster/0 active idle 100.107.67.12 Unit is ready and clustered
percona-cluster/3* active idle 75/lxd/2 100.107.130.40 3306/tcp Unit is ready
  check-mk-agent/554 active idle 100.107.130.40 ready
  nrpe/111 unknown idle 100.107.130.40
  pxc-hacluster/3* active idle 100.107.130.40 Unit is ready and clustered