Bug 1131661

Summary: sync plan start time is incorrectly claiming that is accepts GMT
Product: Red Hat Satellite Reporter: sthirugn <sthirugn>
Component: WebUIAssignee: Walden Raines <walden>
WebUI sub component: Katello QA Contact: sthirugn <sthirugn>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: unspecified CC: bbuckingham, jnikolak, mmurray, xdmoon
Version: 6.0.3Keywords: Triaged
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/7270
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-12 05:14:49 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
Sync plan claiming GMT none

Description sthirugn@redhat.com 2014-08-19 19:08:38 UTC 
Description of problem:
sync plan start time is incorrectly claiming that is accepts GMT

Version-Release number of selected component (if applicable):
GA Snap 5 - Satellite-6.0.4-RHEL-6-20140813.2

* apr-util-ldap-1.3.9-3.el6_0.1.x86_64
* candlepin-0.9.23-1.el6_5.noarch
* candlepin-common-1.0.1-1.el6_5.noarch
* candlepin-scl-1-5.el6_4.noarch
* candlepin-scl-quartz-2.1.5-5.el6_4.noarch
* candlepin-scl-rhino-1.7R3-1.el6_4.noarch
* candlepin-scl-runtime-1-5.el6_4.noarch
* candlepin-selinux-0.9.23-1.el6_5.noarch
* candlepin-tomcat6-0.9.23-1.el6_5.noarch
* elasticsearch-0.90.10-4.el6sat.noarch
* foreman-1.6.0.40-1.el6sat.noarch
* foreman-compute-1.6.0.40-1.el6sat.noarch
* foreman-gce-1.6.0.40-1.el6sat.noarch
* foreman-libvirt-1.6.0.40-1.el6sat.noarch
* foreman-ovirt-1.6.0.40-1.el6sat.noarch
* foreman-postgresql-1.6.0.40-1.el6sat.noarch
* foreman-proxy-1.6.0.27-1.el6sat.noarch
* foreman-selinux-1.6.0.6-1.el6sat.noarch
* foreman-vmware-1.6.0.40-1.el6sat.noarch
* katello-1.5.0-28.el6sat.noarch
* katello-ca-1.0-1.noarch
* katello-certs-tools-1.5.6-1.el6sat.noarch
* katello-installer-0.0.59-1.el6sat.noarch
* openldap-2.4.23-34.el6_5.1.x86_64
* openldap-devel-2.4.23-34.el6_5.1.x86_64
* pulp-katello-0.3-3.el6sat.noarch
* pulp-nodes-common-2.4.0-0.30.beta.el6sat.noarch
* pulp-nodes-parent-2.4.0-0.30.beta.el6sat.noarch
* pulp-puppet-plugins-2.4.0-0.30.beta.el6sat.noarch
* pulp-puppet-tools-2.4.0-0.30.beta.el6sat.noarch
* pulp-rpm-plugins-2.4.0-0.30.beta.el6sat.noarch
* pulp-selinux-2.4.0-0.30.beta.el6sat.noarch
* pulp-server-2.4.0-0.30.beta.el6sat.noarch
* python-ldap-2.3.10-1.el6.x86_64
* ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch
* ruby193-rubygem-runcible-1.1.0-2.el6sat.noarch

How reproducible:


Steps to Reproduce:
1. The sync plan start time says "Start Time ( GMT)" (see screenshot) but it accepts and processes my time as EDT

Actual results:
The UI says it accepts the time as GMT but it really processes my time as EDT

Expected results:
Perhaps remove (GMT) from UI?

Additional info:
Comment 1 sthirugn@redhat.com 2014-08-19 19:10:49 UTC 
Created attachment 928491 [details]
Sync plan claiming GMT
Comment 2 sthirugn@redhat.com 2014-08-19 19:15:05 UTC 
Perhaps honor GMT in user input and for storing it.
Comment 4 Walden Raines 2014-08-26 19:30:13 UTC 
Created redmine issue http://projects.theforeman.org/issues/7270 from this bug
Comment 5 Walden Raines 2014-08-26 19:33:26 UTC 
PR: https://github.com/Katello/katello/pull/4614
Comment 6 Bryan Kearney 2014-08-27 14:04:06 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/7270 has been closed
-------------
Walden Raines
Applied in changeset commit:katello|275c9fc986e8dc3e38e89cffb8f0c04520b02fb6.
Comment 10 sthirugn@redhat.com 2015-03-17 17:51:52 UTC 
Verified.  Now there is no mention about GMT.  Sync time corresponds to the sat6 server time.

Satellite-6.1.0-RHEL-6-20150311.1
Comment 13 Bryan Kearney 2015-08-11 13:20:46 UTC 
This bug is slated to be released with Satellite 6.1.
Comment 14 errata-xmlrpc 2015-08-12 05:14:49 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.

https://access.redhat.com/errata/RHSA-2015:1592