Virsh Power address of VM changes by itself
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Expired
|
Medium
|
Unassigned |
Bug Description
Hi,
So a little overview of the setup I am working on:
I have three baremetal nodes: NodeA, NodeB & NodeC
NodeA: MaaS v.2.2.1 installed on baremetal. This node hosts 6 VMs.
NodeB: 5 Mirtual Machines
NodeC: 6 Virtual Machines
-- I have enlisted all the VMs on MaaS GUI with the power options as below:
Power Type: Virsh (virtual systems)
Virsh Address: qemu+ssh:
Virsh Password: ubuntu
Virsh VM ID: <VM_Name_
-- Once I configure the power setting, I can see the MaaS communicating with the VM. By initially printing the message: Queried node's BMC - Power state queried: off. I can commission, deploy, power ON/OFF the VM. This verifies that the power settings are working for that particular VM.
-- The test scenario is where I have two VM (lets call them VM1 and VM2), one hosted on NodeA and other on NodeB. The power address for the VMS is as below:
VM1: qemu+ssh:
VM2: qemu+ssh:
-- If I commission and deploy OS on VM1, the VM2 goes in to error state and when I check the power settings of VM2, the power address has been changed to "qemu+ssh:
-- I have reproduced this issue for VM2 as well, I have seen the same issue comes up for VM1 (goes in to error state and its power address is changed to "qemu+ssh:
description: | updated |
description: | updated |
summary: |
- Power address of VM changes by itself + Virsh Power address of VM changes by itself |
Changed in maas: | |
milestone: | none → 2.3.0beta2 |
status: | New → Triaged |
importance: | Undecided → Critical |
Changed in maas: | |
milestone: | 2.3.0beta2 → 2.3.0beta3 |
Changed in maas: | |
milestone: | 2.3.0beta3 → 2.3.0beta4 |
Changed in maas: | |
milestone: | 2.3.0beta4 → 2.3.x |
Changed in maas: | |
status: | Invalid → Confirmed |
Changed in maas: | |
status: | Incomplete → Opinion |
status: | Opinion → Incomplete |
Changed in maas: | |
milestone: | next → none |
Dear user,
This is an automated message.
We believe this bug report is no longer an issue in the latest version of MAAS. For such reason, we are making this issue as Won't Fix. If you believe this issue is still present in the latest version of MAAS, please re-open this bug report.