I’ve searched around the forum as suggested by billwear here but has come out empty-handed, someone mentioned a network misconfiguration, but not the resolution. I’ve included a gif recording of the proxmox test-vm I’m testing provisioning with along with a print-screen of the final state.
Sadly searching the forum doesn’t give me much, or anything. The issue appeared out of the wild, I might’ve reconfigured which VLAN’s have DHCP, set the TTL on the builtin DNS server, but trying to revert haven’t helped.
I’ve enabled some extra logging in nginx and squid, i can’t really tell what’s wrong but something about maas-regiond-webapp.sock doesn’t seem to be right.
This discourse is configured to not allow file uploading so I’ve taken the liberty of uploading my logs directory to https://filebin.net/asow7rmjh5h6ulyh.
I’ve seen this issue lingering around since 2017 in various places online when searching, and the resolution seems to be to set MAAS up from scratch and not touch anything related to networking ever again.
root@rvlpmaas03:/var/snap/maas/common# cat /etc/hosts 127.0.0.1 localhost #127.0.1.1 rvlpmaas03 127.0.0.1 rvlpmaas03 # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters
root@rvlpmaas03:/var/snap/maas/common# cat ../current/regiond.conf database_host: /var/snap/maas/common/test-db-socket database_name: maasdb database_user: maas maas_url: http://100.64.30.250:5240/MAAS
root@rvlpmaas03:/var/snap/maas/common# cat ../current/rackd.conf maas_url: http://100.64.30.250:5240/MAAS
It seems after further testing (after messing with various things) that my vlan 2505 still works while 2407 doesn’t, they both worked earlier.
Any help with troubleshooting to resolve this once and for all and document it for the rest of MAAS users would be greatly appreciated.