Mcollective agents must be updated prior to starting the upgrade procedure
Bug #1637176 reported by
Dmitry Nikishov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Invalid
|
High
|
Fuel Sustaining | ||
Bug Description
When upgrading an environment using upgrade graphs, sometimes astute is not able to retrieve puppet's status.
Current astute seems to be incompatible with mcollective agents running on the original environment's nodes (pre-9.0). So these agents must be updated before the operator attempts to perform the upgrade procedure.
Astute log: http://
| tags: | added: area-python |
| Changed in fuel: | |
| assignee: | nobody → Fuel Sustaining (fuel-sustaining-team) |
| milestone: | none → 9.2 |
| Changed in fuel: | |
| importance: | Undecided → High |
| status: | New → Confirmed |
Revision history for this message
| Alexey Shtokolov (ashtokolov) wrote | #1 |
| Changed in fuel: | |
| status: | Confirmed → Invalid |
To post a comment you must log in.
Mc-agents upgrades are up to upgrades procedure.