But in this case we are using only one static IP during deployment from the /27 subnet. I dont think so we are running out of Ip’s
Might be worth to enable a user with
/var/snap/maas/current/preseeds/curtin_userdata
#cloud-config
debconf_selections:
maas: |
{{for line in str(curtin_preseed).splitlines()}}
{{line}}
{{endfor}}
late_commands:
00_maas: [wget, '--no-proxy', {{node_disable_pxe_url|escape.json}}, '--post-data', {{node_disable_pxe_data|escape.json}}, '-O', '/dev/null']
10_adduser: ["curtin", "in-target", "--", "sh", "-c", "adduser --disabled-password --gecos '' maas"]
20_addpwd: ["curtin", "in-target", "--", "sh", "-c", "echo 'maas:maas' | chpasswd"]
30_addsudo: ["curtin", "in-target", "--", "sh", "-c", "usermod -aG sudo maas"]
and when you get error you can login into the machine and poke around. In particular I’d check if under /etc/netplan you have the proper configuration
@troyanov fyi…can u pls look into this and suggest any fix
