It seems the issue is when boot config is fetched the MAC being passed has its `:` replaced with `-`, this has worked in the past, however the query for finding the machine just uses the reformatted mac, while stored in the database with the `:`. This causes MAAS to think the machine does not exist and sets the kernel params to those for commissioning, which then does not load the correct configuration and deployment stalls.
It seems the issue is when boot config is fetched the MAC being passed has its `:` replaced with `-`, this has worked in the past, however the query for finding the machine just uses the reformatted mac, while stored in the database with the `:`. This causes MAAS to think the machine does not exist and sets the kernel params to those for commissioning, which then does not load the correct configuration and deployment stalls.