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 1316553 - at does not post a job with the correct time when the UTC timezone is specified
Summary: at does not post a job with the correct time when the UTC timezone is specified
Keywords:
Status: CLOSED DUPLICATE of bug 1320322
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: at
Version: 6.9
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Tomas Mraz
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-10 13:09 UTC by Stuart Newman
Modified: 2016-03-29 09:08 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-29 09:08:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Stuart Newman 2016-03-10 13:09:31 UTC
Description of problem: The system clock is configured for UTC.  When an at request is made using the form 

    at 16:00 UTC,

the time displayed is is 15:00 rather than 16:00


Version-Release number of selected component (if applicable):3.1.10-48.el6


How reproducible: always


Steps to Reproduce:
1.Configure the system clock for UTC
2.Key in at 16:00 UTC
3.Key in atq to display the at queue

Actual results:
5	2016-03-10 15:00 a root

Expected results:
5	2016-03-10 16:00 a root

Additional info:

Comment 2 Tomas Mraz 2016-03-14 10:55:27 UTC
Please use the regular Red Hat support channels https://www.redhat.com/support to help to prioritize the bug fix appropriately.

Comment 3 Stuart Newman 2016-03-25 14:50:42 UTC
The problem is caused by code in the parsetime subprogram in parsetime.y . exectm is moved to currtm after exectm.tm_isdst is set to -1. Nothing ever resets currtm.tm_isdst to either 0 or 1. When execution reaches line 508, currtm.tm_isdst is still -1, causing the test to pass, reducing the scheduled time by one hour. The proposed fix moves exectm to currtm before exectm.tm_isdst is set to -1. The proposed fix (based on line numbers in at-3.1.10-48.el6.i686 is 479a480 > memcpy(&currtm,&exectm,sizeof(currtm)); 482d482 < memcpy(&currtm,&exectm,sizeof(currtm));

Comment 4 Tomas Mraz 2016-03-29 09:05:02 UTC
I do not think this is proper fix either. The dst correction is incorrect. I committed the proper fix to the current Fedora rawhide package.

I am sorry that I have to repeat that if you need the fix in the RHEL package, please report it via regular Red Hat support channels so it can be properly prioritized.

Comment 5 Tomas Mraz 2016-03-29 09:08:58 UTC
Ah I see there is already such report. If it was not you who opened it, please open it too so the priority is raised.

*** This bug has been marked as a duplicate of bug 1320322 ***


Note You need to log in before you can comment on or make changes to this bug.