Comment 18 for bug 1993836

So it appears the status update to register as a KVM host is happening earlier than intended, prior to the node requesting the user-data endpoint, this results in agent_name being unset at the time the node attempts to register as a kvm host, this results in a broken state for the node that goes unhandled, and MAAS will not mark the node as DEPLOYED. The cloud-init config MAAS is serving is identical between image versions, was there a change in cloud-init that could result in these requests being made out of order?