Red Hat Bugzilla – Bug 1312135
timezone.py defaults to LOCAL time when using a kickstart file where timezone is not specified
Last modified: 2016-11-03 19:22:39 EDT
Description of problem:
Kickstarting an install with Timezone not specified and instead selected from the GUI, causes the resulting system time to be off by the timezone selected offset because the hwclock and adjtime are set to LOCAL.
Removing the check for flags.automatedInstall from timezone.py corrects the issue
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a kickstart file for a fully automated install, except don't specify timezone or root's password
2. Install system using kickstart file
3. After install verify time is now LOCAL by running:
Installed system has the wrong time and is using LOCAL time
Installed system has the correct time and is using UTC time
I think this is actually the correct behavior and it has been like this at least since RHEL 5 - if you do a kickstart installation and want the hwclock to be considered in UTC you need to use the --utc option:
RHEL 5: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/5/html/Installation_Guide/s1-kickstart2-options.html
RHEL 6: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-kickstart2-options.html
RHEL 7: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/sect-kickstart-syntax.html
Of that does not really cover the case where you install with partial kickstart and want the user to set the timezone manually while assuming the hwclock is in UTC.
Maybe making it possible to just use "timezone --utc" without a timezone would work ? It would still ask the user to set the timezone but assume the hwclock is in UTC.
Patches posted for review:
Option timezone --utc without specific timezone is now able to use to instruct anaconda to use UTC instead of LOCAL.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.