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

Bug #1713158 reported by Scott Moser on 2017-08-25
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
Medium
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 - 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.

Scott Moser (smoser) on 2017-08-25
Changed in cloud-init:
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → Ryan Harper (raharper)
Scott Moser (smoser) on 2017-08-25
Changed in cloud-init:
status: Confirmed → Fix Committed

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
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers