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
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.
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 :)
Created attachment 329231 [details] Test Kickstart file Uploaded the KS file with the correct filename extension.
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.
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?
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.
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 :)
Created attachment 329460 [details] Anaconda log file ( /var/log/anacoda.log )
Comment on attachment 329460 [details] Anaconda log file ( /var/log/anacoda.log ) Log file from wrong machine !
Created attachment 329473 [details] Correct anaconda log file
Closing as duplicate of bug #461526 per comment #7. *** This bug has been marked as a duplicate of bug 461526 ***