Looks like there are three bugs conspiring to cause this:
1) Ceph config is registered with incomplete context when identity relation fires
2) CephContext does not stop looping through relids when it has a complete context
which means if ceph/0 has a full set of data but ceph/1 does not. The returned
context is incomplete
3) When once a glance unit has issued a CephRequests it can never issue another
one because the relation data making the request is never cleared or changed
so a subsequent request sets the same relation data as was there previously
being no hooks fire on the ceph side.
4) When once the ceph leader has responded to a CephRequests it can never issue another
response because the relation data making the request is never cleared or changed
so a subsequent response sets the same relation data as was there previously
being no hooks fire on the client side.
Looks like there are three bugs conspiring to cause this:
1) Ceph config is registered with incomplete context when identity relation fires
2) CephContext does not stop looping through relids when it has a complete context
which means if ceph/0 has a full set of data but ceph/1 does not. The returned
context is incomplete
3) When once a glance unit has issued a CephRequests it can never issue another
one because the relation data making the request is never cleared or changed
so a subsequent request sets the same relation data as was there previously
being no hooks fire on the ceph side.
4) When once the ceph leader has responded to a CephRequests it can never issue another
response because the relation data making the request is never cleared or changed
so a subsequent response sets the same relation data as was there previously
being no hooks fire on the client side.