add-unit deploys wrong agent version after controller is upgraded
Bug #1705628 reported by
Menno Finlay-Smits
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Unassigned | ||
| 2.2 |
Fix Released
|
High
|
Eric Claude Jones | ||
Bug Description
When add-unit is used after the controller has been upgraded, the new unit uses the tools version of the controller, not the model agent version.
To reproduce:
* bootstrap a controller with 2.1
* deploy "ubuntu" in the default model
* use `juju upgrade-juju -m controller ...` to upgrade the controller to 2.2
* juju add-unit ubuntu
* wait
* the new machine for ubuntu/1 is running 2.2, not 2.1.x as per the model version
I tested with 2.1.2 and 2.2.3 (tip of current 2.2 branch).
| Changed in juju: | |
| milestone: | none → 2.3-alpha1 |
Revision history for this message
| John A Meinel (jameinel) wrote | #1 |
| Changed in juju: | |
| status: | New → Triaged |
Revision history for this message
| Ian Booth (wallyworld) wrote | #2 |
Revision history for this message
| William Grant (wgrant) wrote | #3 |
| Changed in juju: | |
| milestone: | 2.3-beta1 → 2.3-beta2 |
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #4 |
| Changed in juju: | |
| status: | Triaged → Fix Committed |
| Changed in juju: | |
| milestone: | 2.3-beta2 → 2.3-beta1 |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
new machines created in a model should be trying to create agents according to *that model's* target 'agent version', not the controller's 'agent version'.