Code review comment for ~samgilson/cloud-init:cloud-init-analyze-boot
Revision history for this message
| Sam Gilson (samgilson) wrote | # |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
It seems that on Azure VMs that have been pre-provisioned, the ActiveEnter and ExecMainStart timestamps are incorrect due to the waiting that the pre-provisioning must do during the cloud-init-local phase of cloud-init in order to get the necessary data from Azure. Due to this, the more consistent time stamp is the InactiveExit timestamp, as it is written before any pre-provisioning occurs. However, InactiveExit is consistently 4 seconds off of the cloud-init.log timestamp.
However, when on a VM that has not been pre-provisioned, using ActiveEnter instead of InactiveExit always nets you the correct answer.