Upgrade ignores '--agent stream proposed' (2.4.2)
Bug #1788082 reported by
Christopher Lee
This bug report is a duplicate of:
Bug #1742342: upgrade-juju can't find a released-style version in the proposed stream.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
High
|
Unassigned |
Bug Description
As found by the functional test 'nw-upgrade-
We can see that in these logs and example[1].
I can confirm that the generated streams for the test include a xenial 2.4.3 agent in the proposed stream but not released (hence the failure to upgrade).
Changed in juju: | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in juju: | |
milestone: | 2.4.3 → none |
Changed in juju: | |
milestone: | none → 2.4.4 |
Changed in juju: | |
milestone: | 2.4.4 → none |
To post a comment you must log in.
The issue appears to be the the upgrade-juju command correctly processes the requested agent-stream argument and finds the agent binaries in the right place and handles the controller upgrade.
However, as each machine agent is notified that they should upgrade, at that point these agents don't have access to the requested stream passed in via the CLI arg - they just see the model config agent-stream value. So they look in the wrong place.
The work around is to continue to use the model config agent stream as was needed before the CLI arg was introduced.