Don't use rc.local to start fix-configs-on-startup

It looks like mcollective is restarted two times duting boot
process. First, it simply restarted by nailgun-agent to change
node's ID. And then it gets restarted by fix-configs-on-startup
after it fixes mcollective's configuration file.

It turns out that such sequence of restarts may cause node's
provisioning problems when node's boot process is delayed. The
simpe workaround is to run fix-configs-on-startup by nailgun-agent
and exclude fix-configs-on-startup from rc.local

Change-Id: I28b8d632faa753b693eb2277c5989092f29afa21
Closes-bug: #1642377
This commit is contained in:
Alexey Stupnikov 2016-11-18 15:00:10 +03:00
parent 9bfd81edb6
commit 34489daa3f
1 changed files with 4 additions and 2 deletions

View File

@ -3,8 +3,10 @@
# Perform multipath reload
multipath-reload || true
# Perform fuel bootstrap configuration
fix-configs-on-startup || true
# fuel-nailgun-agent is now used to start fix-configs-on-startup on starup
# instead of simply restarting mcollective, since we don't need two separate
# restart which causing bug #1642377
#fix-configs-on-startup || true
# Unlocking nailgun-agent for discovering
rm -f /etc/nailgun-agent/nodiscover