Public bug reported:
When mcollective is already installed in the system it may happen that
it starts before cloud-init starts to reconfigure it. This leads to a
situation when cloud-init changes mcollective config and invokes
"service mcollective start" which does nothing because the service is
already started - ending up mcollective running with a default
configuration.
The fix could be to invoke "service mcollective restart" instead.
** Affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1570776
Title:
mcollective reconfiguration sometimes doesn't work
Status in cloud-init:
New
Bug description:
When mcollective is already installed in the system it may happen that
it starts before cloud-init starts to reconfigure it. This leads to a
situation when cloud-init changes mcollective config and invokes
"service mcollective start" which does nothing because the service is
already started - ending up mcollective running with a default
configuration.
The fix could be to invoke "service mcollective restart" instead.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1570776/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
