Unable to convert a LXD KVM into a libvirt KVM (and vice-versa)

Bug #1966474 reported by Alexsander de Souza
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Alexsander de Souza

Bug Description

Testing KVM host deployment:

$ LXD to libvirt
$ maas $ADMIN machine deploy $MACHINE install_kvm=True
    Fails with: maasserver.exceptions.PodProblem: Failed talking to pod: Pod 12: Failed to connect to the LXD REST API.

# libvirt to LXD
$ maas $ADMIN machine deploy $MACHINE register_vmhost=True
    Fails with: provisioningserver.drivers.pod.virsh.VirshError: Failed to login to virsh console.

MAAS installs the correct KVM type in the host, but cannot register it in MAAS

Related branches

Revision history for this message
Alexsander de Souza (alexsander-souza) wrote :

to reproduce the first issue, you can deploy a machine as LXD KVM, release it and try to deploy it as a libvirt KVM. MAAS doesn't remove the LXD certs from NodeMetadata during the release, and _create_vmhost_for_deployment() tries to create a LXD pod if it finds the certs.

the second issue is similar, converting a virsh kvm to LXD. The libvirsh secret is still in the DB, and MAAS tries to use it first

Changed in maas:
status: New → Triaged
importance: Undecided → High
milestone: none → next
Changed in maas:
status: Triaged → In Progress
assignee: nobody → Alexsander de Souza (alexsander-souza)
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
milestone: next → 3.2.0-beta3
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.