Failed to login to virsh console error doesn't go away

[Chris Johnston]

In setting up the power config for a new VM, I originally typo'ed the Virsh address, which resulted in:

Error:Failed to login to virsh console.

This is expected behaviour.

After I fixed the Virsh address typo and saved the changes, the error still appears in the UI (see "vm_new_on" showing that the VM has been powered on, MAAS shows it as powered on, but the error still exists).

I then commissioned and deployed the VM using the web UI (see "vm_deploying"), however, the error has not gone away. Even clicking "Edit" for Power configuration and saving again does not make the error go away.

2.6.1-7832-g17912cdc9-0ubuntu1~18.04.1

From maas.log:

2019-10-31T19:29:41.747866+00:00 maasctl maas.power: [error] maas-04: Power state could not be queried: Failed to login to virsh console.
2019-10-31T19:29:41.765762+00:00 maasctl maas.power: [error] maas-04: Failed to refresh power state: Failed to login to virsh console.
2019-10-31T19:30:36.004036+00:00 maasctl maas.interface: [info] eth0 (physical) on maas-04: IP address automatically unlinked: None:type=AUTO
2019-10-31T19:30:36.034946+00:00 maasctl maas.node: [info] maas-04: Status transition from NEW to COMMISSIONING
2019-10-31T19:30:36.144606+00:00 maasctl maas.power: [info] Changing power state (cycle) of node: maas-04 (87pcnx)
2019-10-31T19:30:36.147710+00:00 maasctl maas.node: [info] maas-04: Commissioning started
2019-10-31T19:30:42.007211+00:00 maasctl maas.power: [info] Changed power state (on) of node: maas-04 (87pcnx)
2019-10-31T19:33:12.494413+00:00 maasctl maas.node: [info] maas-04: Storage layout was set to flat.
2019-10-31T19:33:12.735585+00:00 maasctl maas.node: [info] maas-04: Status transition from COMMISSIONING to TESTING
2019-10-31T19:33:16.843428+00:00 maasctl maas.node: [info] maas-04: Status transition from TESTING to READY
2019-10-31T19:34:11.630734+00:00 maasctl maas.node: [info] maas-04: Status transition from READY to ALLOCATED
2019-10-31T19:34:11.637616+00:00 maasctl maas.node: [info] maas-04: allocated to user admin
2019-10-31T19:34:11.824111+00:00 maasctl maas.interface: [info] Allocated automatic IP address 10.10.10.3 for eth0 (physical) on maas-04.
2019-10-31T19:34:11.843332+00:00 maasctl maas.node: [info] maas-04: Status transition from ALLOCATED to DEPLOYING
2019-10-31T19:34:11.917963+00:00 maasctl maas.power: [info] Changing power state (on) of node: maas-04 (87pcnx)
2019-10-31T19:34:16.807027+00:00 maasctl maas.power: [info] Changed power state (on) of node: maas-04 (87pcnx)
2019-10-31T19:34:20.733619+00:00 maasctl maas.interface: [info] ens4 (physical) on maasctl: New MAC, IP binding observed: 52:54:00:ae:6b:3d, 10.10.10.3
2019-10-31T19:37:42.000853+00:00 maasctl maas.node: [info] maas-04: Status transition from DEPLOYING to DEPLOYED

[Alberto Donato (ack)]

I see this error for a VM created from a KVM POD, which always had the correct address (as it was composed from MAAS). I can run power checks fine, so power details are correct

[Alberto Donato (ack)]

Note that there is a past event with a power error for the node in my case.

[Caleb Ellis (caleb-ellis)]

Fix here: https://github.com/canonical-web-and-design/maas-ui/pull/670