Comment 16 for bug 1778033

The machine 115 which hosts the unit testing-osd2/3 is informing that the there
are still pending storages to be processed[0], this message comes from the
uniter/storage/resolver.go[1] after this message there is a check if the state
install hook was already run, if it hasn't, then it will keep waiting.

A fresh "juju status" shows that the machine is in "allocating" state[2], so the
question here is why the agent hasn't reached "ready" state.

[0] $ grep "still pending" juju-{1,2,3}/var/log/juju/logsink.log |grep testing-osd2-3
juju-2/var/log/juju/logsink.log:dc746ae6-fac2-415c-88e8-cad7c6e2c41e: unit-testing-osd2-3 2018-11-20 14:02:28 DEBUG juju.worker.uniter.storage resolver.go:91 still pending [storage-osd-devices-46 storage-osd-devices-47]
juju-2/var/log/juju/logsink.log:dc746ae6-fac2-415c-88e8-cad7c6e2c41e: unit-testing-osd2-3 2018-11-20 14:07:27 DEBUG juju.worker.uniter.storage resolver.go:91 still pending [storage-osd-devices-46 storage-osd-devices-47]
juju-2/var/log/juju/logsink.log:dc746ae6-fac2-415c-88e8-cad7c6e2c41e: unit-testing-osd2-3 2018-11-20 14:12:12 DEBUG juju.worker.uniter.storage resolver.go:91 still pending [storage-osd-devices-46 storage-osd-devices-47]
juju-2/var/log/juju/logsink.log:dc746ae6-fac2-415c-88e8-cad7c6e2c41e: unit-testing-osd2-3 2018-11-20 14:17:19 DEBUG juju.worker.uniter.storage resolver.go:91 still pending [storage-osd-devices-46 storage-osd-devices-47]
juju-2/var/log/juju/logsink.log:dc746ae6-fac2-415c-88e8-cad7c6e2c41e: unit-testing-osd2-3 2018-11-20 14:21:26 DEBUG juju.worker.uniter.storage resolver.go:91 still pending [storage-osd-devices-46 storage-osd-devices-47]
[1] https://github.com/juju/juju/blob/2.3/worker/uniter/storage/resolver.go#L91
[2] testing-osd2/3 waiting allocating 115 100.80.51.1 agent initializing