I’m attempting to set up MAAS/3.3.2 via snap for the first time. If if allow MAAS to managed DHCP on one of my subnets, I’m able to get a node booted and visible in the UI (where presumably I could proceed to commission the system). If I use my existing DHCP servers though, and point my client to download
ipxe.cfg from my MAAS server the client eventually fails with:
cloud-init: 2023-05-02 18:43:45,807 - url_helper.py[ERROR]: Timed out, no response from urls: ['http://10.110.100.36/MAAS/metadata/2012-03-01/meta-data/instance-id'] cloud-init: 2023-05-02 18:43:45,808 - url_helper.py[CRITICAL]: Timed out, no response from urls: ['http://10.110.100.36/MAAS/metadata/2012-03-01/meta-data/instance-id'] after 120 seconds cloud-init: 2023-05-02 18:43:45,808 - util.py[WARNING]: No instance datasource found! Likely bad things to come!
When I do a packet capture from my MAAS server during this time I see this:
16:35:19.884514 IP myhost-u22-1.my.domain.53144 > maas.my.domain.http: Flags [S], seq 4218718519, win 64240, options [mss 1460,sackOK,TS val 1708093121 ecr 0,nop,wscale 7], length 0 16:35:19.884559 IP maas.my.domain.http > myhost-u22-1.my.domain.53144: Flags [R.], seq 0, ack 1, win 0, length 0
So, it looks like the client is trying to reach the server, but the server keeps resetting the connections. This happens in a loop for a few minutes before the client continues to boot in to a host named “ubuntu” rather than the “maas-enlisting-node” host I get when I let MAAS manage DHCP (and when the host appears in the MAAS UI as expected).
I know that external DHCP is officially not supported, but I’m perplexed by this decision as I don’t know how that would be very useful to most folks wanting to deploy MAAS.