[2.3] Default install is now importing bionic by default instead of xenial.
Bug #1767137 reported by
Chris Gregan
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Andres Rodriguez |
Bug Description
Overnight MAAS 2.3 deployments of Xenial now fail. It seems a change to make Bionic a default download in 2.4 has effected 2.3
{github.
Related branches
~andreserl/maas:lp1767137_2.3_xenial_default
- MAAS Lander: Needs Fixing
- Blake Rouse (community): Approve
- Andres Rodriguez (community): Approve
-
Diff: 37 lines (+12/-3)2 files modifiedsrc/provisioningserver/drivers/osystem/tests/test_ubuntu.py (+5/-1)
src/provisioningserver/drivers/osystem/ubuntu.py (+7/-2)
summary: |
- MAAS 2.3.x Xenial deploys now fail 00 BAD REQUEST ({"distro_series": + MAAS 2.3.x Xenial deploys now fail 400 BAD REQUEST ({"distro_series": ["'xenial' is not a valid distro_series. |
summary: |
- MAAS 2.3.x Xenial deploys now fail 400 BAD REQUEST ({"distro_series": - ["'xenial' is not a valid distro_series. + [2.3] Default install is now importing bionic by default instead of + xenial. |
Changed in maas: | |
milestone: | none → 2.3.3 |
importance: | Undecided → High |
status: | New → Triaged |
Changed in maas: | |
assignee: | nobody → Andres Rodriguez (andreserl) |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
no longer affects: | maas (Ubuntu) |
no longer affects: | maas (Ubuntu Xenial) |
To post a comment you must log in.
The workaround is to explicitly sync xenial images. You can go to the images tab and select xenial there. If you're using foundation engine, you can add this to your infra.yaml:
maas_boot_ source_ selections:
- release: 'xenial'
arches: ['amd64']