Bug 1438845

Summary: Sync Plan page not handling browser locale correctly
Product: Red Hat Satellite Reporter: Partha Aji <paji>
Component: Sync PlansAssignee: Partha Aji <paji>
Status: CLOSED ERRATA QA Contact: Peter Ondrejka <pondrejk>
Severity: high Docs Contact:
Priority: high    
Version: 6.3.0CC: aagrawal, bbuckingham, daniele, jcallaha, ktordeur, nshaik
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-katello-3.4.4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-21 16:54:37 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:

Description Partha Aji 2017-04-04 14:12:50 UTC
1) Make sure your User preference has the following set. (Admin -> My Accounts)
Language: Browser Locale
Timezone: Browser Timezone 


2) Change your locale location to Prague or of the other EU time zone cities
3) Create sync plan
4) Note that the sync date shows up in the local time zone ("2017/04/04 07:18:00 CEST")

Open the Browser JS console and notice the following error
 "Timepicker directive: "ng-model" value must be a Date object, a number of milliseconds since 01.01.1970 or a string representing an RFC2822 or ISO 8601 date."

A side effect of this is that you will not be able to save/update any sync plan changes including enabled/disabled via the UI.

Temporary Workaround.
 Change the Language in User Preferences to "English(United States)" and notice that now it prints the date in UTC and works correctly.

Comment 1 Partha Aji 2017-04-04 14:32:24 UTC
Easier reproducer 

Change the timezone in User Preferences to one of GMT -4 -3 -2 -1 0, +1  (I chose Prague GMT +1) and you will hit this error.
 

Temporary work around is change the time zone preferences to use UTC.

Comment 3 Brad Buckingham 2017-05-16 20:49:24 UTC
*** Bug 1412568 has been marked as a duplicate of this bug. ***

Comment 4 Partha Aji 2017-07-13 23:15:03 UTC
Created redmine issue http://projects.theforeman.org/issues/20303 from this bug

Comment 5 Satellite Program 2017-07-24 22:04:59 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20303 has been resolved.

Comment 6 Satellite Program 2017-08-03 22:06:12 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20303 has been resolved.

Comment 7 Peter Ondrejka 2017-10-04 13:20:44 UTC
Verified in satellite-6.3.0-19.0.beta.el7sat.noarch

Comment 8 Satellite Program 2018-02-21 16:54:37 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-2018:0336