Comment 4 for bug 2067474

Can you please provide exact steps you followed during MAAS installation?

I just did a clean install in a VM and failed to reproduce it:

lxc launch ubuntu:jammy --vm -c limits.cpu=4 -c limits.memory=4GiB
lxc shell game-shrew

root@game-shrew:~# snap install maas-test-db --channel 3.5/edge
root@game-shrew:~# snap install maas --channel 3.5/candidate
root@game-shrew:~# maas init region+rack
root@game-shrew:~# maas createadmin --username admin --password admin --email admin@localhost --ssh-import gh:troyanov

root@game-shrew:~# ls -al /run/snap.maas
total 0
drwxr-xr-x 3 root root 80 May 29 13:46 .
drwxr-xr-x 28 root root 820 May 29 13:46 ..
drwxr-x--- 2 root root 80 May 29 13:46 chrony
srw-rw---- 1 root root 0 May 29 13:46 httpproxy.sock

root@game-shrew:~# journalctl -u snap.maas.pebble -t maas-agent
May 29 13:46:26 game-shrew maas-agent[2652]: INF Logger is configured with log level "info"
May 29 13:46:26 game-shrew maas-agent[2652]: INF Started Worker Namespace=default TaskQueue=w6t3nr@agent:main WorkerID=w6t3nr@agent:2652
May 29 13:46:27 game-shrew maas-agent[2652]: INF Started Worker Namespace=default TaskQueue=agent:power@vlan-1 WorkerID=w6t3nr@agent:2652
May 29 13:46:27 game-shrew maas-agent[2652]: INF Started Worker Namespace=default TaskQueue=agent:power@vlan-1 WorkerID=w6t3nr@agent:2652
May 29 13:46:27 game-shrew maas-agent[2652]: INF Started Worker Namespace=default TaskQueue=w6t3nr@agent:power WorkerID=w6t3nr@agent:2652
May 29 13:46:27 game-shrew maas-agent[2652]: INF Starting power-service Attempt=1 Namespace=default RunID=ef734129-b998-4e3e-9414-179f3ff1ee97 TaskQueue=w6t3nr@agent:main>
May 29 13:46:27 game-shrew maas-agent[2652]: INF Starting httpproxy-service Attempt=1 Namespace=default RunID=01702bd7-8aae-499b-b7f5-469b40df529b TaskQueue=w6t3nr@agent:>
May 29 13:46:27 game-shrew maas-agent[2652]: INF Service MAAS Agent started