Project

General

Profile

Bug #39294

mgr/dashboard: Time handling

Added by Stephan Müller 8 months ago. Updated 5 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
dashboard/usability
Target version:
% Done:

71%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature:

Description

As I searched for similar issues like #23858, I found a few.

My setup

As my local time is set to Germany (2h) and my docker container as default is set to UTC (/- 0h), I decided to move the timezone of it to Chicago (-5h), in order to determine if the backend correctly only gives out UTC times that can easily be converted into the local time in the frontend.

How to change the timezone

To change the timezone in openSUSE or most other Linux distributions do the following:

cd /etc
ln -sf ../usr/share/zoneinfo/America/Chicago localtime

Found Issues

  • #39300
    With the time difference of -7h to the backend, I couldn't log in. The log throw the error `AMT: user info changed after token was issued, iat=%s lastUpdate=%s` which can be found in line 150 in `dashboard/services/auth.py`. I removed as a quick fix line 146 in the same document which said that `user.lastUpdate <= token['iat']` has to be true in order to login.
  • #39299
    Pool -> details -> 'create_time' attribute will provide the local server time instead UTC time
  • #39298
    Monitors 'monmap modified' attribute will provide the local server time instead UTC time
  • #39297
    Log timestamps will provide the local server time instead UTC time
  • #39296
    Alert -> details -> 'endsAt' and 'startsAt' attributes provide a UTC time but are not converted into local time in the frontend
  • #39295
    RGW -> Bucket -> details -> 'modification time' attribute will provide the local server time instead UTC time
  • #23858
    The RBD snapshot creation modal will append a UTC timestamp to the name - but it's more convenient to use a local timestamp with TZ prefix instead.

Working Dates

  • RBD snapshot creation time column provide a UTC timestamp which is converted to local time in the frontend
  • RBD detail view "Created" attribute provide a UTC timestamp which is converted to local time in the frontend

Subtasks

Subtask #23858: mgr/dashboard: New RBD snapshot names should be prefix with a local time bound ISO timestamp not UTCResolvedStephan Müller

Bug #39295: mgr/dashboard: RGW Bucket API should provide times in UTC that will be converted into local time by AngularResolvedAlfonso MH

Bug #39296: mgr/dashboard: Alert details UTC times should be converted into local time by AngularResolvedStephan Müller

Bug #39297: mgr/dashboard: Logs provided by the API should provide timestamps in UTC in ISO 8601 format that will be converted into local time by AngularResolvedKanika Murarka

Bug #39298: mgr/dashboard: Monitors API should provide times in UTC that will be converted into local time by AngularNew

Bug #39299: mgr/dashboard: Pools API should provide times in UTC that will be converted into local time by AngularNew

Bug #39300: mgr/dashboard: Can't login with a bigger time difference between user and server or make auth token work with UTC times onlyResolvedRicardo Dias

History

#1 Updated by Stephan Müller 8 months ago

  • Related to Subtask #23858: mgr/dashboard: New RBD snapshot names should be prefix with a local time bound ISO timestamp not UTC added

#2 Updated by Stephan Müller 8 months ago

  • Description updated (diff)

#3 Updated by Lenz Grimmer 8 months ago

  • Description updated (diff)
  • Target version set to v15.0.0

Also available in: Atom PDF