add-machine containers should default to latest lts
Bug #1363971 reported by
Kapil Thangavelu
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
High
|
Ian Booth | ||
| 1.20 |
Fix Released
|
High
|
Ian Booth | ||
Bug Description
currently its hardcoded due to default-series detection to precise. ie add-machine 2:lxc on a trusty host will get a precise container.
| Changed in juju-core: | |
| milestone: | none → next-stable |
| importance: | Undecided → High |
| status: | New → Incomplete |
| status: | Incomplete → Triaged |
| tags: | added: 14.10 |
| Changed in juju-core: | |
| milestone: | next-stable → 1.21-alpha1 |
Revision history for this message
| Ian Booth (wallyworld) wrote | #1 |
| Changed in juju-core: | |
| assignee: | nobody → Ian Booth (wallyworld) |
| 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.
The preferred series to use when creating a container is:
1. default-series if specified in config
2. latest lts as determined by "distro-info --lts"
3. hard coded fallback
The easiest option is to change the hard coded fallback from precise -> trusty. For whatever reason, distro-info is not being run so the hard coded fallback is being used.
There is a suggestion that for non-local providers, the series to use for new containers should fallback to that of the host machine (if series is not configured via default-series). This is a change in behaviour from the attempt to use the latest lts, and is more far reaching in terms of code changes. I'd prefer to fix the fallback issue first, and then decide if we want to change the behaviour.