maas serving old image to nodes
Bug #1554636 reported by
Andreas Hasenack
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Lee Trager | ||
1.9 |
Won't Fix
|
Critical
|
Unassigned | ||
2.0 |
Fix Released
|
Critical
|
Unassigned |
Bug Description
This is a difficult bug to file. I can just say what was happening, provide logs, but not really pinpoint at one or two log lines that show what's wrong.
What was happening is that my maas 1.9.1 server (upgraded from 1.9.0) supposedly had only xenial images from March 8th, 2016, but nodes were still deploying the March 5th image. I kicked another import, via API and UI, I even rm -rf'ed all of the on-disk boot resources, but the nodes were still getting March 5th images.
At last, I rebooted the maas server, and after that the new deploys started using the March 8th image.
Related branches
lp:~ltrager/maas/lp1554636
- Mike Pontillo (community): Approve
-
Diff: 243 lines (+167/-5)2 files modifiedsrc/provisioningserver/import_images/boot_resources.py (+13/-4)
src/provisioningserver/import_images/tests/test_boot_resources.py (+154/-1)
lp:~ltrager/maas/lp1554636_2.0
- Lee Trager (community): Approve
-
Diff: 256 lines (+178/-7)2 files modifiedsrc/provisioningserver/import_images/boot_resources.py (+23/-6)
src/provisioningserver/import_images/tests/test_boot_resources.py (+155/-1)
tags: | added: kanban-cross-team landscape |
tags: | removed: kanban-cross-team |
Changed in maas: | |
milestone: | none → 2.0.0 |
Changed in maas: | |
importance: | Undecided → Critical |
status: | New → Triaged |
milestone: | 2.0.0 → 2.0.1 |
milestone: | 2.0.1 → 2.1.0 |
Changed in maas: | |
milestone: | 2.1.0 → 2.1.1 |
no longer affects: | maas/trunk |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Andreas, can you please attach the logs after the reboot (/var/log/ maas/*. log)