Bug 480226

Summary: Anaconda not setting UTC or timezone from kickstart file.
Product: [Fedora] Fedora Reporter: Keith Roberts <keith>
Component: anacondaAssignee: Radek Vykydal <rvykydal>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 10CC: anaconda-maint-list
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-07-20 12:19:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Kickstart test file
none
Test Kickstart file
none
Anaconda log file ( /var/log/anacoda.log )
none
Correct anaconda log file none

Description Keith Roberts 2009-01-15 19:26:02 UTC
Description of problem:

Anaconda does not set the UTC option or the timezone correctly when reading a kickstart file with ks=http://my-server/ks.cfg

Example kickstart file:

# Perform an installation from CD-ROM or DVD, in text mode.
install
cdrom
text

# Installation uses interactive mode.
interactive

# Select language.
lang en_US.UTF-8

# Select keyboard.
keyboard uk

# Select timezone.
timezone --utc Europe/London

Comment 1 Radek Vykydal 2009-01-16 14:53:50 UTC
Can you be more specific? I tested your example kickstart file
and it works for me. Your link to ks.cfg is broken. You can
attach the file to bugzilla.

Comment 2 Keith Roberts 2009-01-16 16:58:03 UTC
Created attachment 329230 [details]
Kickstart test file

Attachment as requested. The URL was just an example of using the http protocol for getting the kickstart file :)

Comment 3 Keith Roberts 2009-01-16 17:02:28 UTC
Created attachment 329231 [details]
Test Kickstart file

Uploaded the KS file with the correct filename extension.

Comment 4 Radek Vykydal 2009-01-19 15:03:25 UTC
If you mean setting the timezone during install (i.e. for post install ks scripts), it doesn't work indeed, and I will mark this bug as duplicate of bug #461526, which I am going to work on.
After first boot, the timezone should be set correctly. If your issue is not that of bug #461526, please describe it here and attach log file /var/log/anaconda.log.

Comment 5 Keith Roberts 2009-01-19 21:08:58 UTC
No, I mean setting the timezone directly form the kickstart file in the main part of the kickstart configuration, as per the 2nd attachment.

Would it have anything to do with me using the:

# Select language.
lang en_US.UTF-8

I don't know what the equivalent language code is to set the language to UK English?

There are other problems with this kickstart file as well.

The /etc/resolv.conf file is not populated with any DNS servers.

I guess each issue is best  reported as a seperate bug?

Comment 6 Radek Vykydal 2009-01-20 09:45:18 UTC
Yes, I meant setting the timezone with kickstart file too
in comment #4.
My question was if your issue (concerning timezone
setting, please report another issues as separate bugs)
is the same as the bug #461526 (comment #3, and comment #4),
which, in your case, would be that the timezone used during
install is not Europe/London.

Comment 7 Keith Roberts 2009-01-20 13:22:44 UTC
Yes, bug #461526 (comment #3, and comment #4) does seem to be very similar to my report. I also attach the /var/log/anaconda.log file. Will open new bug reports for other issues with anaconda and K/S files :)

Comment 8 Keith Roberts 2009-01-20 13:31:56 UTC
Created attachment 329460 [details]
Anaconda log file ( /var/log/anacoda.log )

Comment 9 Keith Roberts 2009-01-20 15:24:45 UTC
Comment on attachment 329460 [details]
Anaconda log file ( /var/log/anacoda.log )

Log file from wrong machine !

Comment 10 Keith Roberts 2009-01-20 15:36:25 UTC
Created attachment 329473 [details]
Correct anaconda log file

Comment 11 Radek Vykydal 2009-07-20 12:19:06 UTC
Closing as duplicate of bug #461526 per comment #7.

*** This bug has been marked as a duplicate of bug 461526 ***