Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 806969 - sync_plan creation is setting time 1 hour behind the chosen time
Summary: sync_plan creation is setting time 1 hour behind the chosen time
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hammer
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: Unspecified
Assignee: Ivan Necas
QA Contact: Sachin Ghai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-26 16:15 UTC by Og Maciel
Modified: 2019-09-26 17:45 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
In CloudForms System Engine, when creating a content synchronization plan, the actual sync time might be off by one hour from the sync time entered. The problem appears when the system clock has a negative timezone shift (e.g. EDT "-04:00"). This fix corrects this issue and sync plans can now be properly scheduled for EDT and other negative timezones.
Clone Of:
Environment:
Last Closed: 2012-12-04 19:43:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1543 0 normal SHIPPED_LIVE Important: CloudForms System Engine 1.1 update 2012-12-05 00:39:57 UTC

Description Og Maciel 2012-03-26 16:15:11 UTC 
Description of problem:

Seems that creating a sync plan via the cli and defining the start time will actually set it to 1 hour behind the chosen time. i.e. if you set it to start at 10:00 am, the task will be set to start at 09:00 am instead.

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

katello-cli-0.1.107-1.el6.noarch

How reproducible:


Steps to Reproduce:
1. Use the following script:

#!/bin/env bash

function kk() {
  KATELLO_PATH=/usr/bin/katello
  $KATELLO_PATH -u admin -p admin "$@"
}

kk org create --name Trenton
kk environment create --org Trenton --name Dev1 --prior Library
kk environment create --org Trenton --name QA1 --prior Dev1
kk environment create --org Trenton --name GA1 --prior QA1

# Switch to Trenton Org
kk client remember --option org --value Trenton
kk client remember --option env --value Dev1

# Custom provider
kk provider create --name="Automated Builds"
kk product create --name="SystemEngine" --provider="Automated Builds"
kk repo create --name="Agent" --product="SystemEngine" --org="Trenton" --url=http://lzap.fedorapeople.org/fakerepos/zoo5/

# Sync plans
kk sync_plan create --org "Trenton" --interval hourly --date `date +"%Y-%m-%d"` --time `date -d "+20 minute" +"%H:%M:%S"` --name "Hourly"
kk product set_plan --org Trenton --name SystemEngine --plan Hourly
  
Actual results:

kk sync_plan info --name Hourly --org Trenton shows the task scheduled 1 hour in the past.


Expected results:

kk sync_plan info --name Hourly --org Trenton should show the task scheduled to start 20 minutes from now.


Additional info:
Comment 1 Ivan Necas 2012-03-26 16:44:35 UTC 
Fixed in commit 7aab89cbf86208a0a315853c4574d3d302fd5000
Comment 2 Ivan Necas 2012-03-26 16:52:08 UTC 
Note: this issue occurs only on machines with negative time-zone shift, e.g. EDT "-04:00"
Comment 3 James Laska 2012-04-18 14:09:27 UTC 
The impact seems low and the problem document-able.

If anyone considers this to be a 1.0 release blocker, please feel free to set the appropriate flags.  Otherwise, I'm requesting a release note, and requesting resolution in the next release.
Comment 4 James Laska 2012-04-18 14:09:28 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
In CloudForms System Engine, when creating a content synchronization plan, the actual sync time may be off by one hour from the sync time entered.  The problem appears to only manifest when the system clock has a negative time-zone shift (e.g. EDT "-04:00").  To workaround this problem, adjust the synchronization plan time accordingly, or set your system clock to use UTC.

The problem has been fixed upstream, and will be included in a future CloudForms System Engine release.
Comment 5 Shikha 2012-05-09 01:52:45 UTC 
Release Note added. Link:
http://documentation-stage.bne.redhat.com/docs/en-US/CloudForms/1.0/html-single/Release_Notes/index.html#sect-Release_Notes-System_Engine-System_Engine_Considerations-known_issues_11

Regards,
Shikha
Comment 8 Sachin Ghai 2012-10-01 06:44:59 UTC 
verified this defect with following build:

katello-glue-pulp-1.1.12-9.el6cf.noarch
katello-1.1.12-9.el6cf.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
katello-certs-tools-1.1.8-1.el6cf.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
katello-cli-1.1.8-5.el6cf.noarch
katello-qpid-client-key-pair-1.0-1.noarch
katello-cli-common-1.1.8-5.el6cf.noarch
katello-common-1.1.12-9.el6cf.noarch
katello-configure-1.1.9-4.el6cf.noarch
katello-all-1.1.12-9.el6cf.noarch
katello-glue-candlepin-1.1.12-9.el6cf.noarch
katello-selinux-1.1.1-1.el6cf.noarch


now sync plan is properly schedules for EDT timezone. As per the script in defect description the task should be scheduled after 20 min from current time.

katello> sync_plan info --name Hourly --org Trenton
--------------------------------------------------------------------------------
                                Sync Plan Info
--------------------------------------------------------------------------------

Id:          1
Name:        Hourly
Description:
    None
Start date:  2012/10/01 00:48:00
Interval:    hourly

katello> quit
[root@shark ~]# date
Mon Oct  1 00:29:15 EDT 2012
[root@shark ~]#
Comment 11 errata-xmlrpc 2012-12-04 19:43:53 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/RHSA-2012-1543.html
Comment 12 Mike McCune 2013-08-16 18:04:09 UTC 
getting rid of 6.0.0 version since that doesn't exist
Note You need to log in before you can comment on or make changes to this bug.