[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug 1859656] Re: [2.6] Unable to reboot s390x KVM machine after initial
From: |
Sean Feole |
Subject: |
[Bug 1859656] Re: [2.6] Unable to reboot s390x KVM machine after initial deploy |
Date: |
Thu, 09 Apr 2020 14:34:59 -0000 |
It would appear that this bug is once again causing problems with some of our
automated testing.
S390x KVM deployments are failing for Focal. When attempting to investigate a
big I found that it is indeed this bug.
Our MAAS Server is Version:
maas:
Installed: 2.7.0-8232-g.6e1dba4ab-0ubuntu1~18.04.1
Candidate: 2.7.0-8232-g.6e1dba4ab-0ubuntu1~18.04.1
Version table:
I've attached the console log of the -KVM machine deploying.
On MAAS the rack controller reports the following:
sfeole@bsg75:~$ cat focal-s390x-maas.txt
==> rackd.log <==
2020-04-09 14:14:59 provisioningserver.rackdservices.tftp: [info] boots390x.bin
requested by 10.246.75.177
2020-04-09 14:14:59 provisioningserver.rackdservices.tftp: [info]
s390x/65a9ca43-9541-49be-b315-e2ca85936ea2 requested by 10.246.75.177
2020-04-09 14:14:59 provisioningserver.rackdservices.tftp: [info]
s390x/01-52-54-00-e5-d7-bb requested by 10.246.75.177
==> regiond.log <==
2020-04-09 14:14:59 maasserver.rpc.leases: [info] Lease update: commit for
10.246.75.177 on 52:54:0:e5:d7:bb at 2020-04-09 14:14:59 (lease time: 600s)
==> rackd.log <==
2020-04-09 14:14:59 provisioningserver.rackdservices.tftp: [info]
s390x/0AF64BB1 requested by 10.246.75.177
2020-04-09 14:14:59 provisioningserver.rackdservices.tftp: [info] s390x/0AF64BB
requested by 10.246.75.177
2020-04-09 14:14:59 provisioningserver.rackdservices.tftp: [info] s390x/0AF64B
requested by 10.246.75.177
2020-04-09 14:14:59 provisioningserver.rackdservices.tftp: [info] s390x/0AF64
requested by 10.246.75.177
2020-04-09 14:14:59 provisioningserver.rackdservices.tftp: [info] s390x/0AF6
requested by 10.246.75.177
2020-04-09 14:15:00 provisioningserver.rackdservices.tftp: [info] s390x/0AF
requested by 10.246.75.177
2020-04-09 14:15:00 provisioningserver.rackdservices.tftp: [info] s390x/0A
requested by 10.246.75.177
2020-04-09 14:15:00 provisioningserver.rackdservices.tftp: [info] s390x/0
requested by 10.246.75.177
2020-04-09 14:15:00 provisioningserver.rackdservices.tftp: [info] s390x/default
requested by 10.246.75.177
** Attachment added: "focal-s390x-deploy.txt"
https://bugs.launchpad.net/maas/+bug/1859656/+attachment/5350338/+files/focal-s390x-deploy.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1859656
Title:
[2.6] Unable to reboot s390x KVM machine after initial deploy
Status in MAAS:
Triaged
Status in QEMU:
Incomplete
Status in Ubuntu on IBM z Systems:
Triaged
Bug 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.
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1859656/+subscriptions
- [Bug 1859656] Re: [2.6] Unable to reboot s390x KVM machine after initial deploy,
Sean Feole <=