@Ryan,
Marking this as invalid for curtin again. I looked closely to the log and saw this:
May 21 11:00:35 geodude cloud-init[1643]: --2018-05-21 11:00:35-- http://10.244.40.33/MAAS/metadata/latest/by-id/gnbttp/ May 21 11:00:35 geodude cloud-init[1643]: Connecting to 10.244.40.33:80... connected. May 21 11:00:35 geodude cloud-init[1643]: HTTP request sent, awaiting response... 200 OK May 21 11:00:35 geodude cloud-init[1643]: Length: unspecified [text/plain] May 21 11:00:35 geodude cloud-init[1643]: Saving to: ‘/dev/null’ May 21 11:00:35 geodude cloud-init[1643]: 0K 138K=0s May 21 11:00:35 geodude cloud-init[1643]: 2018-05-21 11:00:35 (138 KB/s) - ‘/dev/null’ saved [2]
That means curtin run the correct netboot_off command, which should have told MAAS that the machine is to localboot on next reboot.
As such, I need the HAProxy logs to continue to be able to debug as it was done against: 10.244.40.33:80
@Ryan,
Marking this as invalid for curtin again. I looked closely to the log and saw this:
May 21 11:00:35 geodude cloud-init[1643]: --2018-05-21 11:00:35-- http:// 10.244. 40.33/MAAS/ metadata/ latest/ by-id/gnbttp/
May 21 11:00:35 geodude cloud-init[1643]: Connecting to 10.244.40.33:80... connected.
May 21 11:00:35 geodude cloud-init[1643]: HTTP request sent, awaiting response... 200 OK
May 21 11:00:35 geodude cloud-init[1643]: Length: unspecified [text/plain]
May 21 11:00:35 geodude cloud-init[1643]: Saving to: ‘/dev/null’
May 21 11:00:35 geodude cloud-init[1643]: 0K 138K=0s
May 21 11:00:35 geodude cloud-init[1643]: 2018-05-21 11:00:35 (138 KB/s) - ‘/dev/null’ saved [2]
That means curtin run the correct netboot_off command, which should have told MAAS that the machine is to localboot on next reboot.
As such, I need the HAProxy logs to continue to be able to debug as it was done against: 10.244.40.33:80