commissioning failing due to no-such-image in boot string
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Won't Fix
|
Critical
|
Unassigned |
Bug Description
MAAS Version 1.8.0 (beta8+bzr3951)
The image kinda explains everything...
Sometimes you force the VM off and back on and it boots fine. I've also had to abort commissioning and re-commission to get it to work.
ubuntu@
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii maas 1.8.0~beta8+
ii maas-cli 1.8.0~beta8+
ii maas-cluster-
ii maas-common 1.8.0~beta8+
ii maas-dhcp 1.8.0~beta8+
ii maas-dns 1.8.0~beta8+
ii maas-proxy 1.8.0~beta8+
ii maas-region-
ii maas-region-
ii python-django-maas 1.8.0~beta8+
ii python-maas-client 1.8.0~beta8+
ii python-
Changed in maas: | |
status: | New → Incomplete |
Seems to be random. Of four VM's I just commissioned:
1 had this happen, force off and restart the VM and it worked
1 had this happen, force reset it happened again, force off and restart the VM and it worked
1 had this happen, two force off and restart the VM still not working; aborted commissioning and recommissioned and it worked
1 commissioned normally with no intervention