Bug 1317951

Summary: hammer Sync plan works incorrectly when admin user is in a different timezone than satellite
Product: Red Hat Satellite Reporter: sthirugn <sthirugn>
Component: Content ManagementAssignee: Walden Raines <walden>
Status: CLOSED DUPLICATE QA Contact: sthirugn <sthirugn>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bbuckingham, sthirugn
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-12 15:02:17 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:

Description sthirugn@redhat.com 2016-03-15 15:20:37 UTC 
Description of problem:
Hammer 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. Create a sync plan using hammer and list it:
hammer> sync-plan create --name=testsyncplanclitest --interval=hourly --sync-date='2016-03-15  20:50:00' --organization-id=1 --enabled=true
Sync plan created

hammer> sync-plan list --name=testsyncplanclitest --organization-id=1
---|---------------------|---------------------|----------|--------
ID | NAME                | START DATE          | INTERVAL | ENABLED
---|---------------------|---------------------|----------|--------
5  | testsyncplanclitest | 2016/03/16 02:20:00 | hourly   | yes    
---|---------------------|---------------------|----------|--------

4. Go back to UI to chec

Actual results:
Notice that Start date is set using Satellite server's time and not according to user's timezone settings

Expected results:
The Start Date should be set using user's timezone settings

Additional info:
Comment 2 Brad Buckingham 2016-03-16 14:28:58 UTC 
Suresh, I believe this is a duplicate of bug 1317675.  The BZs are UI vs CLI; however, they both use the same underlying API and server-side logic.  Would it be Ok to close this one as a dupe?
Comment 3 Brad Buckingham 2016-03-17 14:06:04 UTC 
The bug should be worked with bug 1317675.  If the fix for either is server-side, the second bug can be closed as a duplicate; however, if it is client-side (ui/cli) then the 2 bugs remain separate.
Comment 4 sthirugn@redhat.com 2016-03-17 14:11:35 UTC 
Thanks Brad.  Lets keep both open as I suspect this is a client side fix.
Comment 5 Walden Raines 2016-05-12 15:02:17 UTC 

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