upgradedToVersion in agent.conf not being upgraded when no upgrade steps are run
Bug #1359484 reported by
Menno Finlay-Smits
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
High
|
Menno Finlay-Smits | ||
| 1.20 |
Fix Released
|
High
|
Menno Finlay-Smits | ||
Bug Description
Recent changes to avoid entering "upgrade mode" unnecessarily have meant that the upgradedToVersion field in a machine agent's config isn't getting updated when upgrade mode is skipped. This can have a variety of negative effects.
This fix should be fairly easy.
| Changed in juju-core: | |
| importance: | Undecided → High |
| assignee: | nobody → Menno Smits (menno.smits) |
Revision history for this message
| Menno Finlay-Smits (menno.smits) wrote | #1 |
Revision history for this message
| Menno Finlay-Smits (menno.smits) wrote | #2 |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
PR for trunk: https:/