[Openstack-operators] novnc client authenticating on the wrong nova-consoleauth at random
jp.methot at planethoster.info
Thu Jul 20 16:09:17 UTC 2017
I'm running a multi-region openstack setup. I'm running into a strange
issue where when I try to open the novnc console, it will try to
authenticate on a nova-consoleauth service in a random region. So, if I
try to access a novnc console of an instance in regiontwo, the client
will sometimes try to authenticate on the nova-consoleauth in region
one. This results in the token either getting rejected (if I don't have
regiontwo tokens in memcached) or nova-consoleauth not finding the
instance (if I also store regiontwo tokens in regionone memcached).
I must also specify that I am using horizon that's running in regionone.
Also interesting is the fact that the client accessing instance consoles
in regionone will NEVER try to authenticate on nova-consoleauth in
regiontwo. Only regiontwo instances will try to do so (and fail).
Any idea on what could be causing this?
Cloud system administrator
More information about the OpenStack-operators