| 2021-02-24 21:49:46 |
Lee Trager |
description |
A MAAS user used a single host as a rack controller and libvirt KVM host in MAAS 2.6. They setup a parallel MAAS 2.9 environment and registered the combination MAAS rack 2.6/KVM host with MAAS 2.9. This is incorrect and should be prevented(LP:1916089). One of the odd side effects of this is all VMs on the host were deleted however they remained in the MAAS 2.6 database. This caused data loss for the user. MAAS should never delete a VM unless explicitly told to by the user. |
A MAAS user deployed an 18.04 libvirt KVM host with MAAS 2.6.2. They then installed a MAAS 2.6.2 rack controller on the KVM host they just deployed. They setup a parallel MAAS 2.9.2 environment by cloning the database the MAAS 2.6.2 used. They turned off DHCP on one VLAN in the MAAS 2.6.2 environment so they could enable it in the MAAS 2.9.2 environment. They then connected the rack controller, running MAAS 2.6.2 to the MAAS 2.9.2 environment. This resulted in both VMs on the libvirt KVM host being deleted. The VMs remained modeled in both MAASes.
Attempting to connect one rack controller to two different MASSs is not possible. Connecting a MAAS 2.6.2 rack to a MAAS 2.9.2 region is incorrect and should be prevented(LP:1916089). MAAS should never delete a VM unless explicitly told to by the user. |
|
