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
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. stamp and InactiveExitTim estamp do show matching string values with the timestampl recoreded in cloud-init.log
Currently ActiveEnterTime
# 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 stamp cloud-init-local stamp=Mon 2019-06-24 20:24:25 UTC estamp cloud-init-local estamp= Mon 2019-06-24 20:24:25 UTC
root@x1:~# systemctl show -p ActiveEnterTime
ActiveEnterTime
root@x1:~# systemctl show -p InactiveExitTim
InactiveExitTim
So I think that maybe the timestamp arithmetic in the branch may be suspect