mcollective can't see the discovered nodes after cold reboot
Bug #1274847 reported by
Gleb
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Fix Released
|
Medium
|
Vladimir Sharshov | ||
Bug Description
Unwittingly I reboot the Fuel node (with Reset). After the reboot all nodes which was discovered before are not visible by mco ping., they exists in GUI though.
mcollective on the nodes are running.
Revision history for this message
| Vladimir Sharshov (vsharshov) wrote | #1 |
| Changed in fuel: | |
| importance: | Undecided → Medium |
| assignee: | nobody → Vladimir Sharshov (vsharshov) |
| status: | New → Confirmed |
| milestone: | none → 4.1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to fuel-main (master) | #2 |
| Changed in fuel: | |
| status: | Confirmed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to fuel-main (master) | #3 |
| Changed in fuel: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Andrey Sledzinskiy (asledzinskiy) wrote | #4 |
| Changed in fuel: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Mcollective in bootstrap stage do not have heartbeat option. In this case unexpected restart of master node do this nodes broken while mcollective will be restarted manually. Problem can be detected only if run mco ping, because node send correct online status using nailgun agent