Project

General

Profile

Bug #7714

NTP Widget Time Display

Added by Ben Montour about 1 year ago. Updated 11 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
NTPD
Target version:
Start date:
07/21/2017
Due date:
% Done:

100%

Estimated time:
Affected Version:
Affected Architecture:

Description

NTP Widget on 2.3.4-RELEASE-p1 is showing a time other than the received NTP time. Timezone is set to Etc/UTC as per default. Time displayed on main dashboard widget shows correct UTC time. Time displayed on NTP Widget shows time corresponding to my local time.

Associated revisions

Revision 893b6091 (diff)
Added by Steve Beaver 11 months ago

Fixed #7714
Added JS code to formate the date/time for UCT

Revision 7f9b448f (diff)
Added by Steve Beaver 11 months ago

Fixed #7714
Added JS code to formate the date/time for UCT

(cherry picked from commit 893b609111be502233a7a4ad6804fff1e4779a03)

Revision fe814d92 (diff)
Added by Stephen Jones 11 months ago

Fixed #7714 Edited it to show correct timezone

Revision cc0e8de2 (diff)
Added by Stephen Jones 11 months ago

Fixed #7714 Edited it to show correct timezone

(cherry picked from commit fe814d92aae5c53305d484480fa403299a39541a)

History

#1 Updated by Jim Pingle about 1 year ago

  • Category set to NTPD
  • Status changed from New to Confirmed
  • Target version set to 2.4.1

Note: The time itself is correctly fetched from the firewall, but is being adjusted to the wrong time zone when displayed. It is not taking the minutes/seconds/etc from the client like #7245.

#2 Updated by Jim Pingle 12 months ago

  • Target version changed from 2.4.1 to 2.4.2

Moving target to 2.4.2 as we need 2.4.1 sooner than anticipated.

#3 Updated by Steve Beaver 12 months ago

  • Assignee set to Stephen Jones

#4 Updated by Steve Beaver 11 months ago

  • Status changed from Confirmed to Feedback
  • % Done changed from 0 to 100

#5 Updated by Steve Beaver 11 months ago

  • % Done changed from 100 to 0

#6 Updated by Steve Beaver 11 months ago

  • % Done changed from 0 to 100

#7 Updated by Jim Pingle 11 months ago

  • Status changed from Feedback to Resolved
  • Target version changed from 2.4.2 to 2.4.1

This has already been fixed on 2.4.1

Also available in: Atom PDF