Trusty deployments fail when custom archive keys are configured
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Andres Rodriguez | ||
2.3 |
Fix Released
|
High
|
Andres Rodriguez | ||
cloud-init (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
TLDR: when MAAS is configured to use custom archives, Trusty deployments fail.
When custom archive configurations are in use, MAAS renders cloud-init config which cloud-init reads in order to set up apt details.
The cloud-init config format it renders is only compatible with the cloud-init in Xenial. That version is currently:
0.7.9-
It looks something like this:
apt:
source1:
I fetched that example from http://
The cloud-init version in Trusty is 0.7.5-0ubuntu1.22 and the equivalent stanza looks like this:
- source: "deb http://
key: |
I fetched that example from http://
Looking at src/maasserver/
Related branches
- Andres Rodriguez (community): Approve
-
Diff: 91 lines (+62/-0)2 files modifiedsrc/maasserver/compose_preseed.py (+22/-0)
src/maasserver/tests/test_compose_preseed.py (+40/-0)
- Blake Rouse (community): Approve
- Gábor Mészáros (community): Approve
-
Diff: 91 lines (+62/-0)2 files modifiedsrc/maasserver/compose_preseed.py (+22/-0)
src/maasserver/tests/test_compose_preseed.py (+40/-0)
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Critical |
Changed in maas: | |
assignee: | nobody → Andres Rodriguez (andreserl) |
importance: | Critical → High |
tags: | added: cpe-onsite |
tags: | added: 4010 |
Changed in maas: | |
status: | Incomplete → In Progress |
status: | In Progress → Triaged |
summary: |
- Trusty deployments fail when custom archives are configured + Trusty deployments fail when custom archive keys are configured |
Changed in cloud-init (Ubuntu): | |
assignee: | nobody → Andres Rodriguez (andreserl) |
importance: | Undecided → High |
importance: | High → Undecided |
assignee: | Andres Rodriguez (andreserl) → nobody |
Changed in maas: | |
milestone: | none → 2.4.0alpha2 |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
tags: | removed: 4010 |
There are at least two ways this could be fixed:
1. To backport the cloud-init change to Trusty; note that cloud-init is backwards- compatible and widely tested, but also widely in use
2. To have MAAS generate stanzas in both formats, selecting the right one according to the ephemeral environment being used.
It would be worth considering what will happen as cloud-init continues to evolve and our LTS backlog grows due to ESM.