machine agent enters "upgrade mode" unnecessarily
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Menno Finlay-Smits | ||
1.20 |
Fix Released
|
High
|
Menno Finlay-Smits |
Bug Description
As the machine agent comes up it is in "upgrade mode" from the moment it starts until the upgrade-steps worker starts and finishes, even when no actual upgrade is required.
While in upgrade mode, API logins from other agents are blocked resulting in "upgrade in progress" errors in the logs. Although "upgrade mode" is typically short-lived it can be confusing to see the "upgrade in progress" messages in the logs, especially when the user hasn't actually requested an upgrade.
It should be possible to avoid entering upgrade mode unnecessarily (or at least reducing its length somewhat) if there is no need for an upgrade (i.e. the agent config version matches agent-version in the environment's config).
Changed in juju-core: | |
importance: | Low → High |
status: | New → Triaged |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
milestone: | next-stable → 1.21-alpha1 |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
https:/ /github. com/juju/ juju/pull/ 486