Bug 1317675 - Sync plan works incorrectly when admin user is in a different timezone than satellite
Summary: Sync plan works incorrectly when admin user is in a different timezone than s...
Keywords:
Status: CLOSED DUPLICATE of bug 1335133
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: Unspecified
Assignee: Walden Raines
QA Contact: sthirugn@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-14 20:31 UTC by sthirugn@redhat.com
Modified: 2016-05-12 21:21 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-12 15:02:31 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description sthirugn@redhat.com 2016-03-14 20:31:11 UTC
Description of problem:
Sync plan works incorrectly when admin user is in a different timezone than satellite

Version-Release number of selected component (if applicable):
Satellite 6.2.0-beta-snap3.1

How reproducible:
Always

Steps to Reproduce:
1. Login to Satellite Web UI as admin user
2. Navigate to Admin User -> My Account -> Timezone -> Select a different timezone than the Satellite server. Save.
3. Navigate to Content -> Sync Plan -> New Sync Plan

Actual results:
Notice that Start Date and Start Time show Satellite server's current date/time.

Expected results:
The Start Date and Start Time should be shown as current user timezone date/time.

Additional info:
This is very important because the input Start date/ Start Time is actually converted to Satellite server time internally before getting stored.  So this scenario is like half fixed and this creates confusion.

Comment 2 Brad Buckingham 2016-03-17 14:07:19 UTC
This bug is very similar to bug 1317951.

Refer to https://bugzilla.redhat.com/show_bug.cgi?id=1317951#c3 regarding resolution.

Comment 3 Walden Raines 2016-05-12 15:02:31 UTC

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


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