Bug 181737

Summary:	timezone --utc in kickstart file ignored if MS-Windows is found
Product:	[Fedora] Fedora	Reporter:	Alexandre Oliva <oliva>
Component:	anaconda	Assignee:	Chris Lumens <clumens>
Status:	CLOSED RAWHIDE	QA Contact:	Mike McLean <mikem>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	Keywords:	Reopened
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-08-14 17:58:11 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:

Description Alexandre Oliva 2006-02-16 04:29:10 UTC

Description of problem:
The timezone specified in the timezone line in a kickstart file selects the
right timezone, but if --utc is there, it makes no difference to the timezone
selection screen, at least in an interactive install: the UTC check box is not
checked.

Version-Release number of selected component (if applicable):
anaconda-10.92.4-1

How reproducible:
Every time

Steps to Reproduce:
1.Create a kickstart file with timezone --utc America/Sao_Paulo, for an
interactive kickstart install
2.Start the installer using that file

Actual results:
When you get to the timezone screen, the UTC check box is not checked, and the
installed system does not assume the BIOS clock is in UTC

Expected results:
The box should be checked, and the directive should take effect

Additional info:
It might be that a non-interactive install works, but I sort of doubt it.  It's
more likely another fallout from the ks parser rewrite.

Comment 1 Alexandre Oliva 2006-02-16 11:40:31 UTC

FWIW, I've verified that a non-interactive install works.  It only drops --utc
in interactive ks installs.

Comment 2 Chris Lumens 2006-02-16 15:17:10 UTC

Close, but this is actually fallout from reworking the timezone screen.  Too
late for test 3, but this will be fixed in Rawhide.

Comment 3 Alexandre Oliva 2006-08-04 16:46:50 UTC

This is back in the current tree :-(  In the interactive install, the local time
is in UTC button is not checked even though I have the --utc option in the ks
file.  Unfortunately I can't test non-interactive installs atm due to other
installer bugs :-(

Comment 4 Alexandre Oliva 2006-08-04 17:38:06 UTC

Hmm...  Odd...  On another box, it worked.  Differences: the one on which it
didn't work is x86_64, whereas the other is i386; the working one didn't boot
with `expert', but the faulty one did because it has a USB disk on raid 1 for
the root-containing volume group physical volumes.  I hope this helps.

I've double-checked the timezone line, and they are bit-by-bit identical on both
boxes.

Comment 5 Chris Lumens 2006-08-08 16:08:48 UTC

Anything in the log files for the machine that doesn't work?

Comment 6 Alexandre Oliva 2006-08-09 04:47:06 UTC

Nope, but it hit me when I proceeded to install it on another notebook that also
had a MS-Windows left-over :-)

./iw/timezone_gui.py:        self.utcCheckbox.set_active(not
hasWindows(anaconda.id.bootloader))

Surely this shouldn't override the ks setting.  I don't care if Windows gets the
time wrong (I never use it anyway :-)

Comment 7 Chris Lumens 2006-08-09 14:18:53 UTC

Ah yes, that would do it.  Thanks for figuring that out.  Let me know if the
next anaconda build works better for you.