Comment 20 for bug 1719436

@chris

The attachment in #19 does not indicate reproduction of this bug. In that run, there was an undercloud juju machine (#3) in perpetual pending state, causing a ceph-osd unit to never receive a jujud agent. This is from the archive zip:

Model Controller Cloud/Region Version SLA
auto-osci-sv02 auto-osci-sv02 serverstack/serverstack 2.2.4 unsupported

App Version Status Scale Charm Store Rev OS Notes
ceph-mon 10.2.7 error 3 ceph-mon local 0 ubuntu
ceph-osd 10.2.7 blocked 2/3 ceph-osd local 15 ubuntu
ntp waiting 0 ntp local 0 ubuntu

Unit Workload Agent Machine Public address Ports Message
ceph-mon/0* active idle 0 172.17.102.9 Unit is ready and clustered
ceph-mon/1 active idle 1 172.17.102.8 Unit is ready and clustered
ceph-mon/2 error idle 2 172.17.102.4 hook failed: "mon-relation-changed"
ceph-osd/0 waiting allocating 3 172.17.102.24 waiting for machine
ceph-osd/1* blocked idle 4 172.17.102.11 Missing relation: monitor
ceph-osd/2 blocked idle 5 172.17.102.17 Missing relation: monitor

Machine State DNS Inst id Series AZ Message
0 started 172.17.102.9 c6137c36-423c-4fe4-8b13-cc74b35e2495 zesty nova ACTIVE
1 started 172.17.102.8 ea33ac65-3078-4254-ab3d-912b022a8e6c zesty nova ACTIVE
2 started 172.17.102.4 ba7fd29f-fb84-46da-b6ad-256f2045529f zesty nova ACTIVE
3 pending 172.17.102.24 1f4db575-dd06-4536-9d3b-fccf0ab04169 zesty nova ACTIVE
4 started 172.17.102.11 e56800c5-25fd-40d3-a87a-b6df5ae23fbd zesty nova ACTIVE
5 started 172.17.102.17 2b47c03c-12b4-4091-b792-9c5992698282 zesty nova ACTIVE

Relation provider Requirer Interface Type
ceph-mon:mon ceph-mon:mon ceph peer
ntp:ntp-peers ntp:ntp-peers ntp peer