endpoint information sometime missing from keystone relation

[James Page]

depending on the order of unit deployment the trilio-wlm charm does not always get information on the identity-service relation to keystone about endpoints it is interested in.

Toggle debug logging on/off post deployment resolves this issue.

Basically if other endpoints are registered before the trilio wlm endpoint registration occurs, the endpoint data is never presented in the relation.

This is a missing feature/bug in the ep_changed function of the relation to keystone

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/741617

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/741617
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=0a054f17e1589487d533252e22920385cc490b94
Submitter: Zuul
Branch: master

commit 0a054f17e1589487d533252e22920385cc490b94
Author: James Page <email address hidden>
Date: Fri Jul 17 12:16:07 2020 +0100

    notifications: provide complete set of endpoints

    Depending on the order of hook execution its possible for a charm
    requesting notification of endpoint changes via the subscribe_ep_change
    relation key will only get a partial set of information based on
    services which are registered after their service is registered.

    If this situation happens and a subscribed to service already exists
    in the endpoint catalog add these to the JSON dict of information
    passed to the requesting charm.

    Change-Id: Ibac7ea6de013674b570c3de205d95c0a9d1cd8ae
    Closes-Bug: 1887394