# Pastebin j4ASsCWL
  OK, here's what we need to do. 
   So the repro is to deploy a Gen2 VM running Linux to an Azure node running 1.65. Then we need to cause that VM to move to a 1.8 node. 
    I thought we  might just be able to deploy to 1.65 node, deprovision the VM, then upgrade to 1.8 and start the VM, but I don't know if the UUID that cloud-init is looking at will change in that case (which is the thing that would trigger reprovisioning).
    So this will take a little bit to set up. We'll need to get two 1.65 TIP nodes, then upgrade one to 1.8. The two nodes would be part of a single availability set that we can pin a VM to. We'd exclude the 1.8 node to force the VM to be deployed to the 1.65. Then un-exclude the 1.8 node, kill the 1.65 node to force service healing to move the VM to the 1.8 node