Hide Forgot
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:
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?
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.
Thanks Brad. Lets keep both open as I suspect this is a client side fix.
*** This bug has been marked as a duplicate of bug 1335133 ***