list-boot-images reports synced after only syncing bootloader/uefi for arm64
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Lee Trager | ||
| 2.3 |
Triaged
|
High
|
Unassigned | ||
Bug Description
maas is telling me my arm64 images are synced, but they really aren't.
After updating my boot-source-
https:/
When I tried to enlist nodes, arm64 nodes failed to enlist and I got this error in regiond.log:
regiond.
90 minutes later when I went to debug this run, the ubuntu/xenial images for arm64 were there:
https:/
An amd64 VM node enlisted/
This is with maas 2.3.2-6485-
Related branches
- MAAS Lander: Needs Fixing
- Andres Rodriguez (community): Approve
-
Diff: 218 lines (+134/-18)2 files modifiedsrc/maasserver/bootresources.py (+36/-12)
src/maasserver/tests/test_bootresources.py (+98/-6)
- Andres Rodriguez (community): Needs Fixing
- Blake Rouse (community): Approve
- MAAS Lander: Approve
-
Diff: 195 lines (+126/-15)2 files modifiedsrc/maasserver/bootresources.py (+33/-14)
src/maasserver/tests/test_bootresources.py (+93/-1)
| Jason Hobbs (jason-hobbs) wrote | #1 |
| description: | updated |
| summary: |
- list-boot-images reports synced after only syncing bootloader/uefi + list-boot-images reports synced after only syncing bootloader/uefi for + arm64 |
| Andres Rodriguez (andreserl) wrote | #2 |
| Changed in maas: | |
| status: | New → Triaged |
| milestone: | none → 2.4.0rc1 |
| Changed in maas: | |
| assignee: | nobody → Lee Trager (ltrager) |
| Jason Hobbs (jason-hobbs) wrote | #3 |
| Changed in maas: | |
| importance: | Undecided → Medium |
| Changed in maas: | |
| status: | Triaged → In Progress |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → New |
| Changed in maas: | |
| importance: | Medium → High |
| Changed in maas: | |
| status: | New → Fix Committed |
| Changed in maas: | |
| milestone: | 2.4.0rc1 → 2.4.0beta3 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
While we investigate the issues, please try one of these options:
# This is what we currently do in the MAAS CI.
1. stop image import
2. add boot selections (e.g. arm64)
3. restart image import
or:
1. wait for amd64 images to be imported
2. add boot selections for arm64
3. start image import again.