Comment 34 for bug 1818113

Looking at the artifacts referenced in #33

    units:
      keystone/0:
        workload-status:
          current: active
          message: Unit is ready
          since: 07 May 2020 20:14:44Z
        juju-status:
          current: executing
          message: running identity-service-relation-joined hook
          since: 07 May 2020 20:14:55Z
          version: 2.7.6
        leader: true
      keystone/1:
        workload-status:
          current: blocked
          message: Charm and its dependencies not yet at expected scale
          since: 07 May 2020 20:04:49Z
        juju-status:
          current: executing
          message: running identity-credentials-relation-changed hook
          since: 07 May 2020 20:15:13Z
      keystone/2:
        workload-status:
          current: blocked
          message: Charm and its dependencies not yet at expected scale
          since: 07 May 2020 20:03:55Z
        juju-status:
          current: executing
          message: running identity-service-relation-joined hook
          since: 07 May 2020 20:15:17Z

octavia_0/var/log/juju/unit-octavia-0.log:2020-05-07 20:09:25 DEBUG juju-log identity-service:135: tracer: set flag identity-service.available
octavia_0/var/log/juju/unit-octavia-0.log:2020-05-07 20:09:28 DEBUG juju-log identity-service:135: tracer: set flag identity-service.available.auth
octavia_1/var/log/juju/unit-octavia-1.log:2020-05-07 20:09:24 DEBUG juju-log identity-service:135: tracer: set flag identity-service.available
octavia_1/var/log/juju/unit-octavia-1.log:2020-05-07 20:09:27 DEBUG juju-log identity-service:135: tracer: set flag identity-service.available.auth
octavia_2/var/log/juju/unit-octavia-2.log:2020-05-07 20:09:23 DEBUG juju-log identity-service:135: tracer: set flag identity-service.available
octavia_2/var/log/juju/unit-octavia-2.log:2020-05-07 20:09:26 DEBUG juju-log identity-service:135: tracer: set flag identity-service.available.auth

So this could either be that the fix provided for Keystone does not cover all cases, or it could be something wrong with the detection of availability in the keystone reactive interface.

While we look for local a reproducer would it be possible to get a dump of relation data the next time this hits:

- from the peer relation from the perspective of all the keystone units
- from the identity-service relation from the perspective of all the octavia units