[2.4,b1] images never finish syncing to rack controller
Bug #1754493 reported by
Jason Hobbs
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Blake Rouse |
Bug Description
On a single node region/rack controller setup, images never finish syncing to the rack controller. The rack controller has stayed in out-of-sync status for over 30 minutes.
In the UI, I only have 16.04/amd64 selected in the UI, but those don't even show up on the rack-controller list-boot-images output; instead, i386 and ppc64el show up.
http://
This is with 2.4.0~alpha1-
Related branches
~blake-rouse/maas:fix-1754493
Merged
into
maas:master
- Mike Pontillo (community): Approve
- MAAS Lander: Approve
-
Diff: 59 lines (+22/-7)2 files modifiedsrc/provisioningserver/rpc/boot_images.py (+7/-1)
src/provisioningserver/rpc/tests/test_boot_images.py (+15/-6)
Changed in maas: | |
importance: | Critical → High |
summary: |
- images never finish syncing to rack controller + [2.4,b1] images never finish syncing to rack controller |
Changed in maas: | |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Changed in maas: | |
status: | New → Fix Released |
To post a comment you must log in.
I can confirm this is the case, although it doesn't happen always. In our case this is what happens:
1. Install & configure MAAS
2. Add arm64 or ppc64 boot resources
3. Add centos boot resources
4. MAAS imports all images in the region
5. MAAS imports /some/ images in the rack, but the last boot resources added never get into the rack
6. The images page reports "that its waiting for rack controllers to finish syncing" for the centos boot resource.