Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1062089

Summary: The clock shows always maybe the greenwhich time
Product: Red Hat Enterprise Linux 6 Reporter: jari.kosonen <jari.kosonen>
Component: setupAssignee: Ondrej Vasik <ovasik>
Status: CLOSED NOTABUG QA Contact: qe-baseos-daemons
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.5   
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-06 07:12:55 UTC Type: Bug
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
snapshot of the settings of the clock
none
snapshot of the settings of the clock (when not use UTC, same results)
none
that redhat site does not allow making support case for the product 'clock'. none

Description jari.kosonen@rayence.com 2014-02-06 05:51:43 UTC 
Created attachment 859996 [details]
snapshot of the settings of the clock

Description of problem:
Clock time zone settting seem not work.

Version-Release number of selected component (if applicable):
clock 2.30.2
system-config-date 

How reproducible:
-

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
I suspect I have some configuration error... 
- but I could not find way to configure it.
Whether I select "System clock uses UTC" or not, the results did not change.
My timezone is Seoul, but the displayed time does not seem to be correct.
Comment 2 jari.kosonen@rayence.com 2014-02-06 05:56:58 UTC 
Created attachment 859997 [details]
snapshot of the settings of the clock (when not use UTC, same results)
Comment 3 Ondrej Vasik 2014-02-06 07:12:55 UTC 
Setup component has nothing to do with your issue. In addition, bugzilla is not the correct way how to reach Red Hat Enterprise Linux product support, it is direct link to engineering.
Anyway, problem is not clear from your description. System clock uses UTC option has nothing to do with the timezone. This is just something for automated sync when daylight saving time change occurs or if you want to use ntp servers for time synchronization. You probably need to set the correct time first and/or connect to some ntp synchronization server and wait - as it is not immediately changed. 
I'm closing it not a bug - as you didn't described any issue with operating system. 24timezones.com doesn't use the system clock time, therefore it shows the correct time. It uses a time from the server. You have to set the time of your computer manually based on the 24timezones.com webtime or you have to connect to ntp server with precise enough time (using deployment guide and network time protocol chapter). For manual setting, date or hwclock commands do the job. Read manual pages for these to choose the right options for you (I can't give you good advice, because I don't know if you have only system or both system (doesn't survive reboot) and hwclock (does survive reboot) unsynced with the real time).
Comment 4 jari.kosonen@rayence.com 2014-02-06 07:16:51 UTC 
could you let me know how to check with "Red Hat Enterprise Linux product support" (what is their web URL?)
Comment 5 Ondrej Vasik 2014-02-06 15:37:38 UTC 
https://access.redhat.com/site/support
Comment 6 jari.kosonen@rayence.com 2014-02-07 07:59:55 UTC 
That site does not allow make support case except in regards of Redhat Customer portal or Redhat Network.
Comment 7 jari.kosonen@rayence.com 2014-02-07 08:00:57 UTC 
Created attachment 860388 [details]
that redhat site does not allow making support case for the product 'clock'.