Need to detect if zero nova-consoleauths are enabled

Bug #1805665 reported by Drew Freiberger
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
charm-openstack-service-checks
Won't Fix
Medium
Unassigned

Bug Description

In a new 18.11 charms deployment, it was identified that there is a bug lp#1805658 that caused nova-consoleauth startup failures on all nodes of the cluster. This was not detected by monitoring, and took several days to troubleshoot why consoles weren't working. A simple addition to the nova services checks would be to ensure that at least one nova-consoleauth is in enabled/up state.

Stretch goal, find a way to related to nova-cloud-controller to receive the single-nova-consoleauth attribute and if set to "false" check for $num_nova-consoleauth_enabled == $num_nova-cloud-controller_units.

Revision history for this message
Xav Paice (xavpaice) wrote :

First step for fixing this is to evaluate if this check should actually be in the nova-cloud-controller charm or in openstack-service-checks, and if it's still relevant for the newest versions.

Changed in charm-openstack-service-checks:
status: New → Confirmed
importance: Undecided → Medium
Eric Chen (eric-chen)
Changed in charm-openstack-service-checks:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.