Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 529071

Summary: Fix system-config-date to change date and time together
Product: Red Hat Enterprise Linux 5 Reporter: Flavio Leitner <fleitner>
Component: system-config-dateAssignee: Nils Philippsen <nphilipp>
Status: CLOSED ERRATA QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: medium    
Version: 5.3CC: azelinka, kvolny, twoerner
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-28 14:43:10 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
Suggested patch fixing it to change date and time together.
none
nanosleep program. none

Description Flavio Leitner 2009-10-14 20:32:07 UTC
Created attachment 364804 [details]
Suggested patch fixing it to change date and time together.

Description of problem:
When the system time on XEN host is adjusted forward, their threads in 
their application on XEN host get stuck in the nanosleep call and 
never return from the call.

The XEN VMs works with relative time since boot, so when you change date
and time with default independent_clock, the XEN VM time will also change.

The problem happens because the clock applet runs 'system-config-date' and
when you adjust clock forward, it first changes the date, i.e.:

date -s 2009/7/26

and then the time, i.e.:

date -s 19:50:00

The first date command is actually changing to: 2009/7/26 00:00:00
which will move VM's time ahead. On the second date command the time 
is fixed. However, as the VM update time in the virtual timer IRQ handler,
there is a chance that some threads get the wrong time scheduling timers
far away in the future causing the hang we are seeing.

Test package available at:
https://brewweb.devel.redhat.com/taskinfo?taskID=1905093

Version-Release number of selected component (if applicable):
1.8.12-4.el5

How reproducible:
Often

Steps to Reproduce:
Forward time using system-config-date and check if the thread is hung.
  
Actual results:
The thread inside VM's is stuck on nanosleep()

Additional info:
There is a small C program that keeps printing periodically so when it stops
the problem is reproduced.

Comment 1 Flavio Leitner 2009-10-14 20:33:26 UTC
Created attachment 364805 [details]
nanosleep program.

Comment 2 Flavio Leitner 2009-10-14 20:35:35 UTC
BTW, that test package in brew has the patch applied.
Unfortunately, the customer has not responded for quite some time now but
local tests shows the patch has it fixed.

Comment 5 RHEL Program Management 2009-11-06 19:14:55 UTC
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".

Comment 7 RHEL Program Management 2010-08-09 18:38:46 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 9 RHEL Program Management 2011-01-11 21:05:15 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 10 RHEL Program Management 2011-01-12 15:13:12 UTC
This request was erroneously denied for the current release of
Red Hat Enterprise Linux.  The error has been fixed and this
request has been re-proposed for the current release.

Comment 11 RHEL Program Management 2011-05-31 13:42:28 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 16 errata-xmlrpc 2011-11-28 14:43:10 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1490.html