Comment 5 for bug 1443291

I found that mcollective is started via the cloud-init process post install and configured there as well. As far as I can tell we aren't actively managing mcollective via puppet as part of the deployment. I'm working on a fix to the fuel-agent cloud-init configuration to address this for centos.