nova-consoleauth service started twice on systemd machines
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Nova Cloud Controller Charm |
Fix Released
|
Medium
|
Jorge Niedbalski |
Bug Description
[Environment]
Xenial 16.04
OpenStack >= kilo.
[Description]
When using the nova-cloud-
set to true, its expected for the nova-consoleauth service to be run in just a single unit at the time. The service management (start/stop) is performed by pacemaker in accordance with the cluster health using the OCF resource agent[0], so its required for the service to be disabled by default on upstart (trusty) or systemd (>=xenial).
This works on Trusty machines because is currently creating a manual override file for the service but isn't working properly for Xenial machines.
As an example, I deployed 3 units of NCC + hacluster and the service was started twice
nova 5555 1 2 20:55 ? 00:00:04 /usr/bin/python /usr/bin/
nova 24269 1 0 20:44 ? 00:00:04 /usr/bin/python /usr/bin/
-- Unit nova-consoleaut
May 25 20:43:53 juju-c0d788-
-- Subject: Unit nova-consoleaut
-- Defined-By: systemd
-- Support: http://
--
-- Unit nova-consoleaut
May 25 20:55:34 juju-c0d788-
-- Subject: Unit nova-consoleaut
-- Defined-By: systemd
-- Support: http://
--
-- Unit nova-consoleaut
May 25 20:55:34 juju-c0d788-
-- Subject: Unit nova-consoleaut
-- Defined-By: systemd
-- Support: http://
--
-- Unit nova-consoleaut
root@juju-
5555 1 5555 nova-consoleauth
24269 1 24268 nova-consoleauth
[0]https:/
Changed in charm-nova-cloud-controller: | |
importance: | Undecided → Medium |
assignee: | nobody → Jorge Niedbalski (niedbalski) |
tags: | added: sts |
Changed in charm-nova-cloud-controller: | |
milestone: | none → 17.08 |
Changed in charm-nova-cloud-controller: | |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. openstack. org/468955
Review: https:/