Usage timestamp may not be generated w/ correct timezone data
Bug #927974 reported by
Gabriel Hurley
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Fix Released
|
Low
|
Gabriel Hurley |
Bug Description
Mismatches between the timezone for the python process running the Horizon code and the Nova API code can cause instances created recently to be inappropriately excluded from the results.
Changed in horizon: | |
importance: | Undecided → Low |
milestone: | none → essex-4 |
status: | New → Confirmed |
Changed in horizon: | |
milestone: | essex-4 → none |
Changed in horizon: | |
milestone: | none → folsom-2 |
status: | Fix Committed → Fix Released |
Changed in horizon: | |
milestone: | folsom-2 → 2012.2 |
To post a comment you must log in.
This is an extremely minor issue, and may be aided when Django 1.4 is released (better timezone handling included). Thereby bumping it out of E4.