[centos] mcollective autostart is not ensured on nodes
Bug #1443291 reported by
Bogdan Dobrelya
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Critical
|
Alex Schultz | ||
5.0.x |
Invalid
|
Critical
|
Unassigned | ||
5.1.x |
Invalid
|
Critical
|
Unassigned | ||
6.0.x |
Won't Fix
|
Medium
|
Unassigned | ||
6.1.x |
Fix Released
|
Critical
|
Alex Schultz |
Bug Description
# chkconfig | grep mcollective
mcollective 0:off 1:off 2:off 3:off 4:off 5:off 6:off
This results in nodes became unmanaged for Fuel orchestration after reboot.
Reproduced at 6.1 dev ISO #291
Changed in fuel: | |
importance: | Undecided → Critical |
milestone: | none → 6.1 |
assignee: | nobody → Fuel Library Team (fuel-library) |
status: | New → Confirmed |
tags: | added: low-hanging-fruit |
Changed in fuel: | |
assignee: | Alex Schultz (alex-schultz) → Dmitry Pyzhov (dpyzhov) |
To post a comment you must log in.
So I looked into this bug on 6.1 and while chkconfig reports mcollective as being off, if you reboot and mcollectived is being started. Are there additional steps required to reboot and result in mcollective in not running?
As far as I can tell, it is being started via rc.local which calls fix-configs- on-startup.