Bug #39294
Updated by Lenz Grimmer about 5 years ago
As I searched for similar issues like #23858, I found a few. view. h2. 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. h2. How to change the timezone To change the timezone in openSUSE or most other Linux distributions do the following: <pre> cd /etc ln -sf ../usr/share/zoneinfo/America/Chicago localtime </pre> h2. 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. h2. 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