Unable to reboot s390x KVM machine after initial deploy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Incomplete
|
Low
|
Unassigned | ||
Ubuntu on IBM z Systems |
Triaged
|
High
|
MAAS | ||
qemu (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
MAAS version: 2.6.1 (7832-g17912cdc
Arch: S390x
Appears that MAAS can not find the s390x bootloader to boot from the disk, not sure how maas determines this. However this was working in the past. I had originally thought that if the maas machine was deployed then it defaulted to boot from disk.
If I force the VM to book from disk, the VM starts up as expected.
Reproduce:
- Deploy Disco on S390x KVM instance
- Reboot it
on the KVM console...
Connected to domain s2lp6g001
Escape character is ^]
done
Using IPv4 address: 10.246.75.160
Using TFTP server: 10.246.72.3
Bootfile name: 'boots390x.bin'
Receiving data: 0 KBytes
TFTP error: file not found: boots390x.bin
Trying pxelinux.cfg files...
Receiving data: 0 KBytes
Receiving data: 0 KBytes
Failed to load OS from network
==> /var/log/
2020-01-14 18:21:24 provisioningser
2020-01-14 18:21:24 provisioningser
2020-01-14 18:21:24 provisioningser
2020-01-14 18:21:24 provisioningser
2020-01-14 18:21:24 provisioningser
2020-01-14 18:21:24 provisioningser
2020-01-14 18:21:24 provisioningser
2020-01-14 18:21:24 provisioningser
2020-01-14 18:21:24 provisioningser
2020-01-14 18:21:24 provisioningser
2020-01-14 18:21:24 provisioningser
2020-01-14 18:21:24 provisioningser
description: | updated |
Changed in ubuntu-z-systems: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → MAAS (maas) |
Changed in maas: | |
assignee: | nobody → Lee Trager (ltrager) |
affects: | qemu-kvm → qemu |
Changed in maas: | |
status: | Incomplete → New |
tags: | added: s390x |
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Low |
affects: | qemu → qemu (Ubuntu) |
Changed in maas: | |
assignee: | Lee Trager (ltrager) → nobody |
summary: |
- [2.6] Unable to reboot s390x KVM machine after initial deploy + Unable to reboot s390x KVM machine after initial deploy |
Changed in maas: | |
status: | Incomplete → New |
status: | New → Incomplete |
Powering off the machine after its initial deployment renders the machine unusable.
Workaround:
Release & Redeploy again.