[Bug 1805658] Re: [18.11] nova-consoleauth not starting up due to config bug

[Corey Bryant]

On Wed, Nov 28, 2018 at 12:53 PM Drew Freiberger <1805658 at bugs.launchpad.net>
wrote:

> Since the real issue was CRM not starting the process after detecting
> failures, I'm wondering if the CacheDirectory warning is a red herring.
>
> When I instrumented my cloud with nrpe related to all the hacluster
> applications, I found that gnocchi, keystone, openstack-dashboard, nova-
> cloud-controller, aodh, and mysql (percona-cluster) all had failures or
> stopped items in crm.  This was seen on both 18.08 and 18.11
> xenial/queens environments.  Is it possible that there needs to be a crm
> cleanup phase in the charms at some appropriate point where it knows
> that all of the pre-req services and relations are all available?
>
>
When I triaged this I missed Drew's comment #8. Sorry!

Drew, by any chance are you setting 'single-nova-consoleauth: false' for
nova-cloud-controller? If you not likely want to in conjunction with using
memcached. This change is relavent: https://review.openstack.org/#/c/469555/
.

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1805658

Title:
  [18.11] nova-consoleauth not starting up due to config bug

Status in OpenStack nova-cloud-controller charm:
  New
Status in Ubuntu Cloud Archive:
  Triaged

Bug description:
  We are seeing this error when attempting to start nova-consoleauth
  under 18.11 charms on xenial/queens clouds.

  systemd[1]: [/lib/systemd/system/nova-consoleauth.service:13] Unknown
  lvalue 'CacheDirectory' in section 'Service'

  This prevents the user from retrieving console URLs from the nova api
  due to messaging timeout.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1805658/+subscriptions