I’m still stuck here and I’m not able to deploy servers anymore, it is not a DHCP problem, it seems my server are not able to connect to curtin datasource on the next reboot after install.
But at the end of the deployment, just before the reboot, I can see it connects well to the database :
Jan 15 20:01:14 dc1-8gpu-77 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jan 15 20:01:14 dc1-8gpu-77 ec2: #############################################################
Jan 15 20:01:14 dc1-8gpu-77 cloud-init[3397]: Cloud-init v. 18.4-0ubuntu1~16.04.2 running ‘modules:final’ at Tue, 15 Jan 2019 19:57:00 +0000. Up 46.91 seconds.
Jan 15 20:01:14 dc1-8gpu-77 cloud-init[3397]: Cloud-init v. 18.4-0ubuntu1~16.04.2 finished at Tue, 15 Jan 2019 20:01:14 +0000. Datasource DataSourceMAAS [http://192.168.172.3:5240/MAAS/metadata/curtin]. Up 301.31 seconds
Jan 15 20:01:14 dc1-8gpu-77 systemd[1]: Started Execute cloud user/final scripts.
Jan 15 20:01:14 dc1-8gpu-77 systemd[1]: Reached target Cloud-init target.
Jan 15 20:01:14 dc1-8gpu-77 systemd[1]: Startup finished in 13.357s (kernel) + 4min 48.134s (userspace) = 5min 1.491s.
Jan 15 20:01:15 dc1-8gpu-77 systemd[1]: Unmounting /media/root-ro…
Jan 15 20:01:15 dc1-8gpu-77 systemd[1]: Stopping ACPI event daemon…
Jan 15 20:01:15 dc1-8gpu-77 systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jan 15 20:01:15 dc1-8gpu-77 systemd[1]: Stopping Authenticate and Authorize Users to Run Privileged Tasks…
Jan 15 20:01:15 dc1-8gpu-77 systemd[1]: Stopped target Cloud-init target.
Then it reboots and it displays error messages of my last comment, without being able to connect to cloud-init datasource.
I tried to restart MaaS.
Thank you !
Ludwig