Dates should be served in a correct UTC format
Bug #1443343 reported by
Nikita Konovalov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Sahara |
Fix Released
|
High
|
Nikita Konovalov | ||
Kilo |
Fix Released
|
Medium
|
Vitalii Gridnev |
Bug Description
The dates returned in created_at and updated_at fields should be presented in valid UTC format. The only consumer of those fields is the event log tab in the cluster UI.
The correct date example looks like this: 2015-04-
However the milliseconds part may sometimes be skipped depending on SQL engine and SQLAlchemy circumstances, so to keep things consistent it's better to remove the milliseconds suffix from all dates.
The final date should look like this: 2015-04-13T09:52:15
Changed in sahara: | |
assignee: | nobody → Nikita Konovalov (nkonovalov) |
description: | updated |
Changed in sahara: | |
status: | New → In Progress |
Changed in sahara: | |
milestone: | none → liberty-1 |
Changed in sahara: | |
importance: | Undecided → High |
Changed in sahara: | |
status: | Fix Committed → Fix Released |
Changed in sahara: | |
milestone: | liberty-1 → 3.0.0 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/170446 /git.openstack. org/cgit/ openstack/ sahara/ commit/ ?id=3b4f17bc18c 34ae4c7ec37e9d4 dff41a32abdc28
Committed: https:/
Submitter: Jenkins
Branch: master
commit 3b4f17bc18c34ae 4c7ec37e9d4dff4 1a32abdc28
Author: Nikita Konovalov <email address hidden>
Date: Fri Apr 3 14:53:35 2015 +0300
Date format set to be correct utc date
As it turned out the format of the date used in Sahara may not be
understood by som JavaScript engines which prevents the dates to be
displayed correctly in UI. The milliseconds part of the time is also
removed as it has never been necessary to access the dates with that
accuracy. However the presence or sometime absence of the .ms suffix
makes it harder to handle dates.
Closes-Bug: #1443343 ba632c1458bba8b d47a0e1a01f
Change-Id: I1f4cc6dc443605