Code review comment for ~samgilson/cloud-init:cloud-init-analyze-boot

Revision history for this message
Chad Smith (chad.smith) wrote :

Marking needs information until we have an idea of how best to align cloud-init start time to something that aligns more with the timestamp in cloud-init logs.
Currently ActiveEnterTimestamp and InactiveExitTimestamp do show matching string values with the timestampl recoreded in cloud-init.log

# cloud-init.log

2019-06-24 20:24:25,463 - util.py[DEBUG]: Cloud-init v. 19.1-11-ge44586f2-1~bddeb running 'init-local' at Mon, 24 Jun 2019 20:24:25 +0000. Up 0.00 seconds.

# systemctl properties
root@x1:~# systemctl show -p ActiveEnterTimestamp cloud-init-local
ActiveEnterTimestamp=Mon 2019-06-24 20:24:25 UTC
root@x1:~# systemctl show -p InactiveExitTimestamp cloud-init-local
InactiveExitTimestamp=Mon 2019-06-24 20:24:25 UTC

So I think that maybe the timestamp arithmetic in the branch may be suspect

review: Needs Information

« Back to merge proposal