Comment 37 for bug 1719436

Revision history for this message
Frode Nordahl (fnordahl) wrote :

For extra validation I also launched a test-cluster with a artificially low value for timeout (10 seconds) to ceph-create-keys exercising the retry part with success.

Excerpt from log:
2018-03-12 12:33:28 INFO juju-log mon:0: Retrying 'add_keyring_to_ceph' 3 more times (delay=5)
2018-03-12 12:33:33 DEBUG mon-relation-changed creating /var/lib/ceph/tmp/juju-d7cf7e-1.mon.keyring
2018-03-12 12:33:33 DEBUG mon-relation-changed added entity mon. auth auth(auid = 18446744073709551615 key=AQBnc6ZaCYEUJRAAqiR95fWY9B8wKiHmbk9vWg== with 0 caps)
2018-03-12 12:33:33 DEBUG mon-relation-changed '/var/lib/ceph/mon/ceph-juju-d7cf7e-1' already exists and is not empty: monitor may already exist
2018-03-12 12:33:37 INFO juju-log mon:0: Waiting for quorum to be reached
2018-03-12 12:33:44 DEBUG juju-log mon:0: Hardening function 'install'
2018-03-12 12:33:44 DEBUG juju-log mon:0: Hardening function 'config_changed'
2018-03-12 12:33:44 DEBUG juju-log mon:0: Hardening function 'upgrade_charm'
2018-03-12 12:33:44 DEBUG juju-log mon:0: Hardening function 'update_status'
2018-03-12 12:33:46 INFO juju-log mon:0: Making dir /var/lib/charm/ceph-mon ceph:ceph 555
2018-03-12 12:33:48 INFO juju-log mon:0: bootstrap_monitor_cluster: mon already initialized.

Excerpt from juju status:
Unit Workload Agent Machine Public address Ports Message
ceph-mon/0* active idle 0 10.130.236.223 Unit is ready and clustered
ceph-mon/1 active idle 1 10.130.236.162 Unit is ready and clustered
ceph-mon/2 active idle 2 10.130.236.184 Unit is ready and clustered