Unable to convert a LXD KVM into a libvirt KVM (and vice-versa)
Bug #1966474 reported by
Alexsander de Souza
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.
# libvirt to LXD
$ maas $ADMIN machine deploy $MACHINE register_
Fails with: provisioningser
MAAS installs the correct KVM type in the host, but cannot register it in MAAS
Related branches
~alexsander-souza/maas:lp1966474_ignore_unused_creds
Merged
into
maas:master
- Alberto Donato (community): Approve
- MAAS Lander: Approve
-
Diff: 289 lines (+149/-8)7 files modifiedsrc/maasserver/models/node.py (+5/-0)
src/maasserver/models/nodemetadata.py (+18/-0)
src/maasserver/models/tests/test_nodemetadata.py (+21/-0)
src/metadataserver/api_twisted.py (+7/-4)
src/metadataserver/tests/test_api_twisted.py (+66/-0)
src/metadataserver/tests/test_vendor_data.py (+26/-0)
src/metadataserver/vendor_data.py (+6/-4)
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.
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