RETIRED, Node discovery agent for Fuel
Go to file
Georgy Kibardin 50bcd8448e Do restart mcollective after provisioning
nailgun agent must not change mcollective config after provisioning
cloudinit is responsible for that.

It may happen that nailgun agent may be started by cron earlier than
it is reconfigured and started by cloudinit. This leads to the
situation when cloudinit reconfigures mcollective and issues start
which doesn't do anything since it is already started by nailgun agent.
Finally, mcollective is left started with incorrect default
configuration.

Change-Id: I0c6f3720943ad21e22899368832e451bc906b098
Closes-Bug: #1455489
2016-05-05 17:54:30 +03:00
debian Bump version to 10.0 2016-03-27 20:30:20 +00:00
specs Bump version to 10.0 2016-03-27 20:30:20 +00:00
.gitignore Add gemspec and Gemfile 2015-11-19 15:02:47 +03:00
.gitreview Update .gitreview for new namespace 2015-10-17 22:20:25 +00:00
Gemfile Add gemspec and Gemfile 2015-11-19 15:02:47 +03:00
LICENSE Spliting Nailgun-agent from fuel-web repository 2015-07-13 16:23:08 +03:00
MAINTAINERS Spec for packages MUST be reviewed by mos packaging team 2015-12-20 20:29:14 +00:00
Rakefile Add Rakefile for openstack CI 2015-11-11 20:21:09 +03:00
agent Do restart mcollective after provisioning 2016-05-05 17:54:30 +03:00
nailgun-agent.cron Fix flock wait timeout in crontask 2015-11-25 11:41:21 +00:00
nailgun-agent.gemspec Add gemspec and Gemfile 2015-11-19 15:02:47 +03:00
run_tests.sh Basic test run script for CI 2015-07-22 17:48:42 +00:00