[upgrade][8.0] Mcollective on slaves can hang after upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Sergey Abramov | ||
8.0.x |
Fix Released
|
High
|
Sergey Abramov | ||
Mitaka |
Fix Released
|
High
|
Sergey Abramov | ||
Newton |
Fix Committed
|
High
|
Sergey Abramov |
Bug Description
This bug occurs not often and can be easily workarounded
Steps to reproduce:
1 Deploy any 7.0 cluster
2 Upgrade fuel master to 8.0 using fuel-octane
3 Verify networks/Change cluster and deploy/Generate diag.snapshot
Expected result:
No errors
Actual Result:
Nodes can be unavailable via mcollective. In /var/log/
Failed to handle message: incompatible marshal file format (can't be read)
format version 4.8 required; 89.111 given - TypeError
Reproducibility:
Rarely
Workaround:
Restart mcollective on unavailable slaves using "service mcollective restart"
Impact:
User not able to change existing cluster and generate diagnostic snapshot
Env info:
Fuel 7.0 + MU2, Fuel 8.0 Release
tags: | added: area-python |
Changed in fuel: | |
assignee: | nobody → Fuel Octane (fuel-octane-team) |
milestone: | none → 9.0 |
importance: | Undecided → High |
status: | New → Confirmed |
tags: | added: team-upgrades |
Changed in fuel: | |
assignee: | Fuel Octane (fuel-octane-team) → Fuel Python Team (fuel-python) |
tags: | added: release-notes |
Changed in fuel: | |
milestone: | 9.0 → 10.0 |
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Fuel Octane (fuel-octane-team) |
Changed in fuel: | |
importance: | High → Low |
tags: | added: feature-testing |
tags: |
added: release-notes-done removed: release-notes |
Changed in fuel: | |
status: | Confirmed → In Progress |
summary: |
- [upgrade][8.0] Mcollective on slaves can hangs after upgrade + [upgrade][8.0] Mcollective on slaves can hang after upgrade |
Dmitry, let's leave it Medium importance for now. It is not frequent and does not affect the deployment in general. It also has a workaround.