After adding virsh machine with existing address, multiple machines share address info

[Seyeong Kim]

Steps to reproduce
- Prepare MAAS and two KVM hosts(Let's say Host A and B) without adding to MAAS
- Create VMs on those hosts A and B
- In MAAS, add a machine with a VM from host A with correct power configuration
- In MAAS, add a machine with a VM from host B but with the power configuration of host A which is wrong IP address and leads to fail commissioning
- In MAAS, modify the power configuration of the VM from host B with correct IP. This will allow the VM from host B to succeed commissioning but result the VM from host A refer to the power configuration of host B because they have been sharing the power configuration since the VM from host B were added with the power configuration of host A.

- Changing Virsh VM ID is fine. only Address is changed on both machine.
- After adding machine with different virsh vm id, It can be edit separately.

[Björn Tillenius (bjornt)]

This is a known problem, due to the way BMCs are shared in the model, but not exposed as such in the UI/API.

Fixing this problem is quite a lot of work, and more of a feature request.

To work around it, you can change the power to be "manual", and then change it back to virsh with the correct IP.

[Alan Baghumian (alanbach)]

This becomes pretty annoying when orchestrating a whole bunch of KVM-based VMs across multiple hosts on MAAS.

Perhaps sharing BMCs was not the best idea to begin with.

Could you elaborate on how the workaround can help?

Imagine performing a juju deploy while juju wants to turn VMs on across multiple hosts via MAAS and it fails.

Thanks.

[Alan Baghumian (alanbach)]

OK, If you like me land on this bug, there is a workaround. This apparently happens only if you have individual VMs registered under MASS, but their respective KVM host is not.

If it is a KVM host with no VMs or if you don't mind MASS taking over existing VMs (be careful here since it is going to try to commission any existing VMs in), go ahead and add the KVM host under KVM > Virsh.

This resolved the issue for me.

In case you add a KVM host with existing VMs, just abort commissioning for those VMs and turn them back on. Let them sit under the "New" section of MAAS. I know it is not very clean, but hey.

[Jerzy Husakowski (jhusakowski)]

Feature request moved to the internal backlog for further prioritisation.