maasserver Unable to identify boot image for (ubuntu/amd64/generic/trusty/poweroff): cluster 'maas' does not have matching boot image.
Bug #1376028 reported by
Jason Hobbs
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Blake Rouse |
Bug Description
After hitting bug 1375980, my nodes booted up in New state, so they should have been fed a 'poweroff' pxeconfig and powered off. That didn't happen, and instead I got a bunch of these errors in my log:
ERROR 2014-10-01 03:43:29,742 maasserver Unable to identify boot image for (ubuntu/
ERROR 2014-10-01 03:43:34,396 maasserver Unable to identify boot image for (ubuntu/
version: 1.7.0~beta4+
Related branches
lp:~blake-rouse/maas/handle-poweroff-purpose
- Graham Binns (community): Approve
-
Diff: 97 lines (+39/-20)2 files modifiedsrc/maasserver/api/pxeconfig.py (+12/-0)
src/maasserver/api/tests/test_pxeconfig.py (+27/-20)
summary: |
maasserver Unable to identify boot image for (ubuntu/amd64/generic/trusty/poweroff): cluster 'maas' does not have - matching boot image. ERROR 2014-10-01 03:43:34,396 maasserver Unable to - identify boot image for (ubuntu/amd64/generic/trusty/poweroff): cluster - 'maas' does not have matching boot image. + matching boot image. |
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Critical |
milestone: | none → 1.7.0 |
assignee: | nobody → Blake Rouse (blake-rouse) |
Changed in maas: | |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.