Comment 2 for bug 1345014

There is a race in the provisioner that may explain this. If the machine agent on the provisioned instance comes up before the provisioner has recorded its instance ID in state, then the machine agent may connect to state and find that it doesn't exist in state, and then kill itself. I can reproduce this easily by adding a sleep in the provisioner.