add-chassis with virsh doesn't work anymore

[Radu Popescu]

add-chassis with virsh doesn't work anymore.

virsh -c qemu+ssh://<user>@<remote_ip>:22/system?keyfile=/path/to/maas/private.key works and I can see SSH authentication on the remote host.

Whenever I try with both SSH keys or user/password, MAAS doesn't even try to login to the remote host.

Nothing relevant in the logs. All I can see is the API request coming to region controller.

MAAS version: 3.4.1-14343-g.a552d2522

[Radu Popescu (rpopescu-cbs)]

Might be related to: https://bugs.launchpad.net/maas/+bug/2053033

maas.log shows:

./common/log/maas.log:2024-03-21T20:00:49.079689+00:00 maas maas.rpc.cluster: [error] Failed to probe and enlist virsh nodes: Failed to login to virsh console.
./common/log/maas.log:2024-03-21T20:06:16.106421+00:00 maas maas.rpc.cluster: [error] Failed to probe and enlist virsh nodes: Failed to login to virsh console.
./common/log/maas.log:2024-03-21T20:06:43.983522+00:00 maas maas.rpc.cluster: [error] Failed to probe and enlist virsh nodes: Failed to login to virsh console.
./common/log/maas.log:2024-03-21T20:11:50.136092+00:00 maas maas.rpc.cluster: [error] Failed to probe and enlist virsh nodes: Failed to login to virsh console.
./common/log/maas.log:2024-03-21T20:13:41.665473+00:00 maas maas.rpc.cluster: [error] Failed to probe and enlist virsh nodes: Failed to login to virsh console.

and /var/log/kern.log:

./kern.log:Mar 21 20:06:16 maas kernel: [105847.495815] audit: type=1400 audit(1711051576.000:1963): apparmor="DENIED" operation="exec" profile="snap.maas.supervisor" name="/usr/bin/pkttyagent" pid=139536 comm="virsh" requested_mask="x" denied_mask="x" fsuid=0 ouid=0
./kern.log:Mar 21 20:06:43 maas kernel: [105875.373362] audit: type=1400 audit(1711051603.874:1964): apparmor="DENIED" operation="exec" profile="snap.maas.supervisor" name="/usr/bin/pkttyagent" pid=139556 comm="virsh" requested_mask="x" denied_mask="x" fsuid=0 ouid=0
./kern.log:Mar 21 20:11:50 maas kernel: [106181.519394] audit: type=1400 audit(1711051910.024:1970): apparmor="DENIED" operation="exec" profile="snap.maas.supervisor" name="/usr/bin/pkttyagent" pid=140558 comm="virsh" requested_mask="x" denied_mask="x" fsuid=0 ouid=0
./kern.log:Mar 21 20:13:41 maas kernel: [106293.055388] audit: type=1400 audit(1711052021.557:1976): apparmor="DENIED" operation="exec" profile="snap.maas.supervisor" name="/usr/bin/pkttyagent" pid=141295 comm="virsh" requested_mask="x" denied_mask="x" fsuid=0 ouid=0

[Radu Popescu (rpopescu-cbs)]

As per this comment:

https://forum.snapcraft.io/t/enabling-polkitd-on-ubuntu-core/31295/2

Downgrading to revision from this build https://launchpad.net/~ubuntu-core-service/+snap/core22/+build/2305181, which is 1033, and restart maas works as a temporary workaround:

sudo snap refresh core22 --channel=latest/stable --revision=1033
sudo snap restart maas.supervisor

maas profile machines add-chassis chassis_type=virsh hostname=qemu+ssh://user@192.168.100.1/system

[Björn Tillenius (bjornt)]

Yes, this should be the same as bug 2053033. If you're still experiencing the issue, please unmark the bug as as duplicate.