| 2020-01-14 18:31:33 |
Sean Feole |
bug |
|
|
added bug |
| 2020-01-14 18:31:33 |
Sean Feole |
attachment added |
|
curtinlogs.txt https://bugs.launchpad.net/bugs/1859656/+attachment/5320163/+files/curtinlogs.txt |
|
| 2020-01-14 18:31:47 |
Sean Feole |
summary |
[2.6] Unable to reboot s390x machine after initial deploy |
[2.6] Unable to reboot s390x KVM machine after initial deploy |
|
| 2020-01-14 18:41:54 |
Sean Feole |
description |
MAAS version: 2.6.1 (7832-g17912cdc9-0ubuntu1~18.04.1)
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, (Which does work 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/maas/rackd.log <==
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] boots390x.bin requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/65a9ca43-9541-49be-b315-e2ca85936ea2 requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/01-52-54-00-e5-d7-bb requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/0AF64BA0 requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/0AF64BA requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/0AF64B requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/0AF64 requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/0AF6 requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/0AF requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/0A requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/0 requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/default requested by 10.246.75.160 |
MAAS version: 2.6.1 (7832-g17912cdc9-0ubuntu1~18.04.1)
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/maas/rackd.log <==
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] boots390x.bin requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/65a9ca43-9541-49be-b315-e2ca85936ea2 requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/01-52-54-00-e5-d7-bb requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/0AF64BA0 requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/0AF64BA requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/0AF64B requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/0AF64 requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/0AF6 requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/0AF requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/0A requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/0 requested by 10.246.75.160
2020-01-14 18:21:24 provisioningserver.rackdservices.tftp: [info] s390x/default requested by 10.246.75.160 |
|
| 2020-01-15 16:16:59 |
Frank Heimes |
bug task added |
|
ubuntu-z-systems |
|
| 2020-01-16 12:31:24 |
Frank Heimes |
ubuntu-z-systems: status |
New |
Triaged |
|
| 2020-01-16 12:31:44 |
Frank Heimes |
ubuntu-z-systems: importance |
Undecided |
High |
|
| 2020-01-16 12:32:36 |
Frank Heimes |
ubuntu-z-systems: assignee |
|
MAAS (maas) |
|
| 2020-01-16 15:00:50 |
Adam Collard |
maas: assignee |
|
Lee Trager (ltrager) |
|
| 2020-01-16 20:59:00 |
Lee Trager |
maas: status |
New |
Incomplete |
|
| 2020-01-17 20:14:25 |
Lee Trager |
bug task added |
|
qemu-kvm |
|
| 2020-01-21 06:18:45 |
Po-Hsu Lin |
bug |
|
|
added subscriber Po-Hsu Lin |
| 2020-01-21 14:54:02 |
Christian Ehrhardt |
affects |
qemu-kvm |
qemu |
|
| 2020-01-21 15:24:17 |
Christian Ehrhardt |
qemu: status |
New |
Incomplete |
|
| 2020-01-22 11:14:33 |
Frank Heimes |
maas: status |
Incomplete |
New |
|
| 2020-01-23 06:17:52 |
Frank Heimes |
tags |
|
s390x |
|
| 2020-01-28 10:58:17 |
Frank Heimes |
attachment added |
|
boot_console.txt https://bugs.launchpad.net/ubuntu-z-systems/+bug/1859656/+attachment/5323507/+files/boot_console.txt |
|
| 2020-02-10 14:13:54 |
Christian Ehrhardt |
attachment added |
|
Guest XML "as it was once working" https://bugs.launchpad.net/maas/+bug/1859656/+attachment/5327027/+files/vm1-as-deployed-by-maas.xml |
|
| 2020-02-10 14:14:15 |
Christian Ehrhardt |
attachment added |
|
Serial log "as it was once working" https://bugs.launchpad.net/maas/+bug/1859656/+attachment/5327028/+files/working-guest-serial.log |
|
| 2020-02-11 17:53:27 |
Adam Collard |
maas: status |
New |
Triaged |
|
| 2020-02-11 17:53:33 |
Adam Collard |
maas: importance |
Undecided |
Low |
|
| 2020-04-09 14:34:59 |
Sean Feole |
attachment added |
|
focal-s390x-deploy.txt https://bugs.launchpad.net/maas/+bug/1859656/+attachment/5350338/+files/focal-s390x-deploy.txt |
|
| 2020-07-18 14:33:40 |
Thomas Huth |
affects |
qemu |
qemu (Ubuntu) |
|
| 2021-09-07 16:56:17 |
Adam Collard |
maas: assignee |
Lee Trager (ltrager) |
|
|
| 2022-10-13 08:24:13 |
Jerzy Husakowski |
summary |
[2.6] Unable to reboot s390x KVM machine after initial deploy |
Unable to reboot s390x KVM machine after initial deploy |
|
| 2022-10-13 08:31:45 |
Jerzy Husakowski |
maas: status |
Triaged |
Incomplete |
|
| 2022-10-14 13:34:21 |
Alberto Donato |
maas: status |
Incomplete |
New |
|
| 2022-10-14 13:34:24 |
Alberto Donato |
maas: status |
New |
Incomplete |
|
