Project

General

Profile

Actions

Bug #20303

closed

Sync Plan page not handling browser locale correctly

Added by Partha Aji over 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Sync Plans
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1438845

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.

Actions #1

Updated by Partha Aji over 7 years ago

  • Subject changed from Sync Plan page not handling browser locale correctly to Sync Plan page not handling browser locale correctly
  • Target version set to 202
Actions #2

Updated by The Foreman Bot over 7 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/6872 added
Actions #3

Updated by Brad Buckingham over 7 years ago

  • Target version changed from 202 to 205
Actions #4

Updated by Justin Sherrill over 7 years ago

  • Priority changed from High to Normal
  • Translation missing: en.field_release set to 281
Actions #5

Updated by Partha Aji over 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF