Bug #15180
closedUnnecessary date/time transformation for sync plan start date
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1335133
Description of problem:
From first glance, transforming date and time for sync plans to Satellite server values can be treated as a feature, but is unacceptable from user perspective. That is fine to have some logic like this, but somewhere internally on the server, not for public view
API example:
Making HTTP POST request to https://server/katello/api/v2/organizations/1850/sync_plans with options {'verify': False, 'auth': ('admin', 'changeme'), 'headers': {'content-type': 'application/json'}} and data {"interval": "hourly", "enabled": false, "organization_id": 1850, "sync_date": "06/07/2372 04:18", "name": "name"}.
Received HTTP 200 response: {"id":132,"organization_id":1850,"name":"name","description":null,"interval":"hourly","next_sync":null,"created_at":"2016-05-11 10:48:20 UTC","updated_at":"2016-05-11 10:48:20 UTC","enabled":false,"products":[],"permissions":{"view_sync_plans":true,"edit_sync_plans":true,"destroy_sync_plans":true},"sync_date":"07/06/2372 12:18:AM"}
UI example:
Created with '2016-05-11' and '15:09'
and received:
'05/11/2016 08:09:AM'
If API part has not so serious impact, but UI behaviour should be definitely treated as severe issue as for user it is complete mess why his data is transformed in that way.
Version-Release number of selected component (if applicable):
6.2 SNAP 10
How reproducible:
Always
Steps to Reproduce:
1. Create new sync plan with specific start data and time
2. Read the entity back and check the values returned
3.
Actual results:
Data and time is transformed to system time taken from the server where application is deployed
Expected results:
Data and time should be shown in the same format and values as user inputted them
Additional info:
'Start Date' is transformed, but not the 'Next Sync' information that is add even more chaos in sync process