From my findings, it looks like we either expect credentials to come from the os-credentials config option, or that keystone.get_creds() always provides credentials, which clearly didn't happen in this situation.
The README mentions: "This charm supports relating to keystone, but keystone-credentials
interface seems to be flaky," so it may be more of an issue outside of this charm.
A workaround for this would be to set the os-credentials config option to the correct values.
From my findings, it looks like we either expect credentials to come from the os-credentials config option, or that keystone. get_creds( ) always provides credentials, which clearly didn't happen in this situation.
The README mentions: "This charm supports relating to keystone, but keystone- credentials
interface seems to be flaky," so it may be more of an issue outside of this charm.
A workaround for this would be to set the os-credentials config option to the correct values.