unit agent upgrade steps not run
Bug #1494070 reported by
Ian Booth
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
Critical
|
Tim Penhey | ||
| 1.25 |
Fix Released
|
Critical
|
Tim Penhey | ||
Bug Description
There are 2 upgrade steps meant to be run by the unit agent.
123 - AddStoppedField
126 - AddInstalledToU
However, only the machine agent runs upgrade steps and so these are ignored as the wrong tag type is passed in.
We need to support unit agent upgrade steps.
| Changed in juju-core: | |
| assignee: | nobody → Tim Penhey (thumper) |
Revision history for this message
| Tim Penhey (thumper) wrote | #1 |
| Changed in juju-core: | |
| status: | Triaged → In Progress |
| 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.
This needs some real thought.
Upgrade steps have never run in any unit agent. And I don't think we should start now, especially considering how we'd like to fold the unter processes into the machine agent.
What we should do is have a simple way to run a step for each unit on a machine.
So have an explicit list of unit upgrade steps, and these would be run for every unit on a machine if there are some.
To facilitate this, we need to get the tags for each unit on a machine. That should be easy enough to get.