A perfectly valid kickstart line: timezone --utc US/Pacific Will produce this error. WARNING : Timezone US/Pacific set in kickstart is not valid, will ask
The choice of timezone specifiers is limited to that present in timeconfig tool, that is in file /usr/share/zoneinfo/zone.tab (http://fedoraproject.org/wiki/Anaconda/Kickstart).
This is too pedantic and should be fixed. Whatabout the astronomer who's using Fedora/kickstart to deploy a cluster with right time? Whatabout the sysadmin who has an acceptable/valid enterprise standard beyond that short list? I'll go away if you feel strongly it should only support zone.tab listed values. Frankly, I prefer to just symlink /etc/localtime -> ../usr/share/zoneinfo/whatever in %post anyways. :-/ Which has it's own pros/cons.
It seem that the Etc/GMT (+...) timezones would be particularly useful and easy to add. (See addNoGeoZones in /usr/share/system-config-date/zonetab.py)
(In reply to comment #3) > It seem that the Etc/GMT (+...) timezones would be particularly useful and easy > to add. (See addNoGeoZones in /usr/share/system-config-date/zonetab.py) They are supported in current anaconda. As for other specifiers, now when we have all zoneinfo files back in stage 2, we could allow all respective specifiers in ks.
Should be fixed in version 12.11 of anaconda. Thanks for the report.