Read the code I can see how this occurs - nova-consoleauth should be managed differently once this configuration option has been set ensuring that it does not get restarted by the charm on subsequent configuration file changes.
Its also possible to use a memcache backend for the consoleauth processes - the charm should support this option, allowing multiple instances to be run.
Marking as 'Triaged' and setting to High importance.
Read the code I can see how this occurs - nova-consoleauth should be managed differently once this configuration option has been set ensuring that it does not get restarted by the charm on subsequent configuration file changes.
Its also possible to use a memcache backend for the consoleauth processes - the charm should support this option, allowing multiple instances to be run.
Marking as 'Triaged' and setting to High importance.