cloud-init.log message do not contain timezone offset info and thus may appear to go backwards

Bug #1713158 reported by Scott Moser
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
Ryan Harper

Bug Description

the logging info in /var/log/cloud-init.log does not include a timezone offset:

2017-08-23 19:11:08,115 -[DEBUG]: Attempting to remove /var/lib/cloud/instance

that causes a problem when cloud-init applies the timezone during boot it can appear
to jump forward or backward.

Scott Moser (smoser)
Changed in cloud-init:
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → Ryan Harper (raharper)
Scott Moser (smoser)
Changed in cloud-init:
status: Confirmed → Fix Committed
Revision history for this message
Scott Moser (smoser) wrote : Fixed in Cloud-init 17.1

This bug is believed to be fixed in cloud-init in 17.1. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in cloud-init:
status: Fix Committed → Fix Released
Revision history for this message
xiaoyi chen (xiachen-rh) wrote :

Hi Scott,
May I ask a question about this change, is there any document letting user know that cloud-init log always use UTC time except ChangeLog? I checked the online doc but didn't find any.


Revision history for this message
James Falcon (falcojr) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.