Currently, cloud-init configures mcollective and then runs the following command
service mcollective start
But if mcollective was already installed into an image, System V subsystem starts it before mcollective and starting it again does give nothing. So, in order to make sure that mcollective is able to see config file changes made by cloud-init it must be restarted.
Fortunately, nailgun-agent slightly changes the config and then restarts mcollective. This bug is motivated by the results of investigation done for this one https://bugs.launchpad.net/fuel/+bug/1454741
Currently, cloud-init configures mcollective and then runs the following command
service mcollective start
But if mcollective was already installed into an image, System V subsystem starts it before mcollective and starting it again does give nothing. So, in order to make sure that mcollective is able to see config file changes made by cloud-init it must be restarted.
Fortunately, nailgun-agent slightly changes the config and then restarts mcollective. This bug is motivated by the results of investigation done for this one https:/ /bugs.launchpad .net/fuel/ +bug/1454741