Comment 12 for bug 2053033

I can confirm this can impact any existing deployments if refreshing the core22 to the latest stable version *and* restarting MAAS snap after.

With the previous version of the snap core22, there is no error related to pkttyagent like below :
#
# before refresh
#
ubuntu@infra-1:~$ sudo snap run --shell maas
root@infra-1:/home/ubuntu# virsh -c qemu+ssh://maas@10.244.40.30/system pool-info pool_virt_images
Name: pool_virt_images
...

#
# refreshing core22 snap
#
ubuntu@infra-1:~$ sudo snap refresh core22
core22 20240111 from Canonical✓ refreshed
#
# restart maas
#
ubuntu@infra-1:~$ sudo snap restart maas
2024-02-16T04:12:09Z INFO Waiting for "snap.maas.supervisor.service" to stop.
Restarted.
ubuntu@infra-1:~$ sudo snap run --shell maas
root@infra-1:/home/ubuntu# virsh -c qemu+ssh://maas@10.244.40.30/system pool-info pool_virt_images
libvirt: error : cannot execute binary /usr/bin/pkttyagent: Permission denied
Name: pool_virt_images
...