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

[ubuntu-server-builder]

This bug was originally filed in Launchpad as LP: #1713158

Launchpad details

affected_projects = []
assignee = raharper
assignee_name = Ryan Harper
date_closed = 2017-09-23T02:35:38.669379+00:00
date_created = 2017-08-25T21:59:54.655606+00:00
date_fix_committed = 2017-08-25T22:08:16.296944+00:00
date_fix_released = 2017-09-23T02:35:38.669379+00:00
id = 1713158
importance = medium
is_complete = True
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1713158
milestone = None
owner = smoser
owner_name = Scott Moser
private = False
status = fix_released
submitter = smoser
submitter_name = Scott Moser
tags = []
duplicates = []

Launchpad user Scott Moser(smoser) wrote on 2017-08-25T21:59:54.655606+00:00

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

2017-08-23 19:11:08,115 - util.py[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.

[ubuntu-server-builder]

Launchpad user Scott Moser(smoser) wrote on 2017-09-23T02:35:40.067858+00:00

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.

[ubuntu-server-builder]

Launchpad user xiaoyi chen(xiachen-rh) wrote on 2021-05-21T07:44:20.600700+00:00

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.

thanks,
Amy