Just ran into this as confirmation.
Filed this bug which may or may not be a duplicate of this one. The root cause looks like the DB not being ready before corosync attempts to start nova-consoleauth.
https://bugs.launchpad.net/charm-hacluster/+bug/1674683
If we decide single-nova-consoleauth=true is not valid with memcache we should enforce it early with a clear message in juju status.
Just ran into this as confirmation.
Filed this bug which may or may not be a duplicate of this one. The root cause looks like the DB not being ready before corosync attempts to start nova-consoleauth.
https:/ /bugs.launchpad .net/charm- hacluster/ +bug/1674683
If we decide single- nova-consoleaut h=true is not valid with memcache we should enforce it early with a clear message in juju status.