Newly provisioned machines start off at the controller's version.
Bug #1573742 reported by
Eric Snow
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Won't Fix
|
High
|
Unassigned | ||
Bug Description
Per lp:1570917, deploying a charm resulted in a machine provisioned at the juju version of the admin model's version, rather than the version of the machine's model. The machine should have started out at the model's version rather than triggering a downgrade.
| Changed in juju-core: | |
| status: | New → Triaged |
| tags: | added: juju-release-support |
| Changed in juju-core: | |
| importance: | Undecided → High |
| milestone: | none → 2.0.1 |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.0.1 → none |
| milestone: | none → 2.0.1 |
| Changed in juju: | |
| milestone: | 2.0.1 → none |
Revision history for this message
| Heather Lanigan (hmlanigan) wrote | #1 |
| Changed in juju: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
this appears to have been fixed sometime in the last 5 years.