Cannot commission machine in pod

[Marian Gasparovic]

MaaS 2.2.2 (6099-g8751f91-0ubuntu1~16.04.1) running in LXD container on host with 17.10

I create a pod, target is virsh on remote notebook with 17.10.
I can compose a machine, it appears in a list, VM on remote KVM is created, but it reports (on remote KVM)

2017-12-14 18:12:20.899+0000: starting up libvirt version: 3.6.0, package: 1ubuntu6 (Christian Ehrhardt <email address hidden> Tue, 24 Oct 2017 14:30:34 +0200), qemu version: 2.10.1(Debian 1:2.10+dfsg-0ubuntu3.1), hostname: bravo
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-system-x86_64 -name guest=m02,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-2-m02/master-key.aes -machine pc-i440fx-artful,accel=kvm,usb=off,dump-guest-core=off -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid c1b8b95a-b48b-48c1-8c89-aa6462bdaece -display none -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-2-m02/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive file=/var/lib/libvirt/images/76467625-8500-4af7-a816-7f818544c129,format=raw,if=none,id=drive-virtio-disk0 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x3,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -netdev tap,fd=27,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:60:07:60,bus=pci.0,addr=0x4,bootindex=1 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x2 -msg timestamp=on
2017-12-14T18:12:20.941945Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/1 (label charserial0)
warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]

Nothing appears on VM's console

in maas log I get
Dec 14 18:12:17 maasmg maas.drivers.pod.virsh: [info] m02: Successfully set network boot order
Dec 14 18:12:19 maasmg maas.node: [info] m02: Status transition from NEW to COMMISSIONING
Dec 14 18:12:19 maasmg maas.power: [info] Changing power state (on) of node: m02 (ekerqa)
Dec 14 18:12:19 maasmg maas.node: [info] m02: Commissioning started
Dec 14 18:12:24 maasmg maas.power: [info] Changed power state (on) of node: m02 (ekerqa)
Dec 14 18:19:09 maasmg maas.import-images: [info] Starting rack boot image import
Dec 14 18:19:09 maasmg maas.import-images: [info] Downloading image descriptions from http://localhost:5240/MAAS/images-stream/streams/v1/index.json
Dec 14 18:19:09 maasmg maas.import-images: [info] Updating boot image iSCSI targets.
Dec 14 18:19:10 maasmg maas.import-images: [info] Finished importing boot images, the region does not have any new images.
Dec 14 18:19:10 maasmg maas.import-images: [info] Starting rack boot image import
Dec 14 18:33:11 maasmg maas.node: [info] m02: Status transition from COMMISSIONING to FAILED_COMMISSIONING
Dec 14 18:33:11 maasmg maas.node: [error] m02: Marking node failed: Node operation 'Commissioning' timed out after 20 minutes.

[Marian Gasparovic (marosg)]

KVM works ok, when I create VM manually and start it, it tries to PXE boot.

[Andres Rodriguez (andreserl)]

Hi Marian,

I have a few questions:

1. What's the configuration of the POD? Did you configure it with the 'default' network or the 'maas' network?

2. What's the configuration of MAAS. Can you share /etc/maas/rackd.conf ?

[Andres Rodriguez (andreserl)]

(also, please mark this bug as 'New' once you have provided the required info).

[Marian Gasparovic (marosg)]

Andres, here is xml of the machine generated by MaaS. It uses default network. Let me be clear about one thing - I know PXE will not work as they are not on the same network (maas is running in lxd on my notebook and accessing another notebook on local LAN, going through NAT on my notebook etc) but I would expect to see VM console starting, trying to PXE boot and fail there.

<domain type='kvm'>
  <name>m1</name>
  <uuid>7eee0679-61fa-4e92-bdc1-12cf4b7d4e07</uuid>
  <memory unit='KiB'>1048576</memory>
  <currentMemory unit='KiB'>1048576</currentMemory>
  <vcpu placement='static'>1</vcpu>
  <os>
    <type arch='x86_64' machine='pc-i440fx-artful'>hvm</type>
    <boot dev='network'/>
    <boot dev='hd'/>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <clock offset='utc'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <pm>
    <suspend-to-mem enabled='no'/>
    <suspend-to-disk enabled='no'/>
  </pm>
  <devices>
    <emulator>/usr/bin/kvm-spice</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw'/>
      <source file='/var/lib/libvirt/images/pool1/b732b363-f968-4323-a3db-d73b13e1d2a2'/>
      <target dev='vda' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </disk>
    <controller type='pci' index='0' model='pci-root'/>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </controller>
    <controller type='usb' index='0' model='piix3-uhci'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
    </controller>
    <interface type='network'>
      <mac address='52:54:00:b9:41:c6'/>
      <source network='default'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target port='0'/>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </memballoon>
  </devices>
</domain>

cat /etc/maas/rackd.conf
cluster_uuid: bbc4b94b-ea3a-4941-b6ea-93728fddb702
maas_url: http://localhost:5240/MAAS

[Newell Jensen (newell-jensen)]

Marian,

rackd.conf is showing the maas_url at localhost but you said your MAAS is running in a LXD container correct? If so, the maas_url should be pointing to the IP address of your container and not to localhost.

[Launchpad Janitor (janitor)]

[Expired for MAAS because there has been no activity for 60 days.]