@Anh Vo,
Thanks for looking at this.
It almost seemed too perfect for me to believe the pre-provisioning
stuff kicked in, and that there were exactly zero journal entries in
almost 9 days.
I would think it'd be nice for cloud-init to clearly state "pre-
provisioned system waited X seconds" or
This is by-design for VMs that are pre-provisioned. When a VM goes
through pre-provisioning cloud-init would block on network change
(waiting for media disconnect/connect). When the network change happens
the VM will be configured based on customer's specified configuration.
While I am not
In my head there are a few possibilities here:
a.) azure correctly guessed that I was going to launch an instance and
"pre-provisioned" it a week before I did it. this seems unlikely to me for a
number of reasons, but I could be convinced that if this happened, everything
is working as
