Mcollective problem with nodes
Bug #1470620 reported by
Big Switch Networks
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
High
|
Vladimir Sharshov |
Bug Description
During the 3 controller 3 compute node deployment, observed below error
Mcollective problem with nodes [{"uid"=>"5", "error"=>"Node not answered by RPC."}, {"uid"=>"6", "error"=>"Node not answered by RPC."}, {"uid"=>"7", "error"=>"Node not answered by RPC."}, {"uid"=>"8", "error"=>"Node not answered by RPC."}, {"uid"=>"9", "error"=>"Node not answered by RPC."}, {"uid"=>"10", "error"=>"Node not answered by RPC."}], please check log for details
snapshot is attached.
Changed in fuel: | |
importance: | Undecided → High |
milestone: | none → 6.1-updates |
assignee: | nobody → Pavel Boldin (pboldin) |
status: | New → Confirmed |
Changed in fuel: | |
assignee: | Pavel Boldin (pboldin) → Vladimir Kozhukalov (kozhukalov) |
To post a comment you must log in.
Could you please describe the whole action flow? I mean what did you do step by step right before you got this error? Looks like nodes were booted and then the master node was redeployed. Nodes were not able to connect to rabbit due to wrong password.