Activity log for bug #1520545

Date Who What changed Old value New value Message
2015-11-27 11:21:17 Florian Haas bug added bug
2015-11-27 11:22:10 Florian Haas description The single-nova-consoleauth parameter is intended to make sure that at any given time, there is only one, Pacemaker-managed, instance active of the nova-consoleauth service in an HA cluster. While the charm correctly injects an override file for the nova-consoleauth service, ensuring that the service isn't started on system startup, Juju *itself* still starts the service on startup, and on any execution of the config-changed hook. Steps to reproduce: - In an HA configuration with multiple nova-cloud-controller units, reboot one controller node. - Alternatively, change any parameter on the nova-cloud-controller service with "juju set" - Log into the controller node after reboot. Make sure that the node does *not* run the res_nova_consoleauth resource - Observe that an instance of nova-consoleauth is now running. This should not happen. In an OpenStack environment that misbehaves in this way, novnc console access will break with this issue: https://ask.openstack.org/en/question/32888/unable-to-run-vnc-due-to-consoleauth-failing/ The single-nova-consoleauth parameter is intended to make sure that at any given time, there is only one, Pacemaker-managed, instance active of the nova-consoleauth service in an HA cluster. While the charm correctly injects an override file for the nova-consoleauth service, ensuring that the service isn't started on system startup, Juju *itself* still starts the service on startup, and on any execution of the config-changed hook. Steps to reproduce: - In an HA configuration with multiple nova-cloud-controller units, reboot one controller node. - Alternatively, change any parameter on the nova-cloud-controller service with "juju set" - Log into the controller node after reboot. Make sure that the node does *not* run the res_nova_consoleauth resource - Check your process table - Observe that an instance of nova-consoleauth is now running. This should not happen. In an OpenStack environment that misbehaves in this way, novnc console access will break with this issue: https://ask.openstack.org/en/question/32888/unable-to-run-vnc-due-to-consoleauth-failing/
2015-11-27 12:22:05 James Page nova-cloud-controller (Juju Charms Collection): status New Confirmed
2015-11-27 12:24:12 James Page nova-cloud-controller (Juju Charms Collection): importance Undecided High
2015-11-27 12:24:15 James Page nova-cloud-controller (Juju Charms Collection): milestone 16.01
2015-11-27 12:33:53 James Page nova-cloud-controller (Juju Charms Collection): status Confirmed Triaged
2016-01-28 14:09:22 James Page nova-cloud-controller (Juju Charms Collection): milestone 16.01 16.04
2016-04-22 08:25:01 James Page nova-cloud-controller (Juju Charms Collection): milestone 16.04 16.07
2016-04-27 11:29:43 Edward Hope-Morley tags openstack
2016-07-29 07:20:59 Liam Young nova-cloud-controller (Juju Charms Collection): milestone 16.07 16.10
2016-10-14 09:03:59 James Page nova-cloud-controller (Juju Charms Collection): milestone 16.10 17.01
2017-02-23 19:00:54 James Page charm-nova-cloud-controller: importance Undecided High
2017-02-23 19:00:54 James Page charm-nova-cloud-controller: status New Triaged
2017-02-23 19:00:56 James Page nova-cloud-controller (Juju Charms Collection): status Triaged Invalid
2017-03-12 16:29:40 Dominique Poulain bug added subscriber Dominique Poulain
2017-06-16 15:27:20 Jorge Niedbalski bug task deleted nova-cloud-controller (Juju Charms Collection)
2017-06-16 15:27:24 Jorge Niedbalski charm-nova-cloud-controller: status Triaged Fix Released
2017-06-16 15:27:26 Jorge Niedbalski charm-nova-cloud-controller: assignee Jorge Niedbalski (niedbalski)
2017-06-16 15:27:30 Jorge Niedbalski charm-nova-cloud-controller: milestone 17.08