Unable to find boot image when erasing disks when releasing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
High
|
Unassigned | ||
2.2 |
Won't Fix
|
High
|
Unassigned |
Bug Description
Unable to find boot image for a node that was deployed with a kernel image provided by the previous image source(
cat /var/log/
Jul 19 06:43:06 maas maas.node: [info] h12: Status transition from DEPLOYED to DISK_ERASING
Jul 19 06:43:06 maas maas.power: [info] Changing power state (on) of node: h12 (4y3h7x)
Jul 19 06:43:06 maas maas.node: [info] h12: Disk erasure started
Jul 19 06:43:31 maas maas.power: [info] Changed power state (on) of node: h12 (4y3h7x)
Jul 19 06:49:19 maas maas.node: [info] h12: Status transition from DISK_ERASING to FAILED_DISK_ERASING
Jul 19 06:49:19 maas maas.node: [error] h12: Marking node failed: Missing boot image ubuntu/
Jul 19 06:49:42 maas maas.node: [info] h12: Status transition from FAILED_DISK_ERASING to DISK_ERASING
Jul 19 06:49:42 maas maas.power: [info] Changing power state (on) of node: h12 (4y3h7x)
Jul 19 06:49:42 maas maas.node: [info] h12: Disk erasure started
Jul 19 06:50:07 maas maas.power: [info] Changed power state (on) of node: h12 (4y3h7x)
Jul 19 06:52:45 maas maas.node: [info] h12: Status transition from DISK_ERASING to FAILED_DISK_ERASING
Jul 19 06:52:45 maas maas.node: [error] h12: Marking node failed: Missing boot image ubuntu/
Jul 19 06:54:22 maas maas.node: [info] h12: Status transition from FAILED_DISK_ERASING to DISK_ERASING
Jul 19 06:54:22 maas maas.power: [info] Changing power state (on) of node: h12 (4y3h7x)
Jul 19 06:54:22 maas maas.node: [info] h12: Disk erasure started
Jul 19 06:54:47 maas maas.power: [info] Changed power state (on) of node: h12 (4y3h7x)
Jul 19 06:57:21 maas maas.node: [info] h12: Status transition from DISK_ERASING to FAILED_DISK_ERASING
Jul 19 06:57:21 maas maas.node: [error] h12: Marking node failed: Missing boot image ubuntu/
dpkg -l '*maas*'|cat
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii maas 2.1.5+bzr5596-
ii maas-cli 2.1.5+bzr5596-
un maas-cluster-
ii maas-common 2.1.5+bzr5596-
ii maas-dhcp 2.1.5+bzr5596-
ii maas-dns 2.1.5+bzr5596-
ii maas-proxy 2.1.5+bzr5596-
ii maas-rack-
ii maas-region-api 2.1.5+bzr5596-
ii maas-region-
un maas-region-
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-
ii python3-django-maas 2.1.5+bzr5596-
ii python3-maas-client 2.1.5+bzr5596-
ii python3-
Changed in maas: | |
status: | New → Won't Fix |
status: | Won't Fix → Incomplete |
Changed in maas: | |
milestone: | none → 2.3.0 |
importance: | Undecided → High |
Changed in maas: | |
milestone: | 2.3.0 → 2.3.x |
Hi There,
Starting from Xenial, the kernel naming has changed and a 'hwe-x' no longer exists. That, however, means that you need to use 'ephemeral-v3' as a stream, and MAAS 2.1+ requires you to use it. That provides the ga-16.04 kernel (or hwe-16.04). That said, I have a few questions:
1. Are you using the ephemeral-v3 stream or ephemeral-v2?
2. Was this machine deployed in a previous version of MAAS, you upgraded MAAS, and now trying to release the machine?