Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.

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.

*** Bug 1412568 has been marked as a duplicate of this bug. ***

Created redmine issue http://projects.theforeman.org/issues/20303 from this bug

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20303 has been resolved.

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20303 has been resolved.

Verified in satellite-6.3.0-19.0.beta.el7sat.noarch

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