Use of now/utcnow inconsistent

Bug #792097 reported by Vish Ishaya
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Wishlist
Vish Ishaya

Bug Description

The codebase is using datetime.now datetime.utcnow and utils.utcnow. We should have one consistent method for getting now. There aren't any specific bugs resulting from this issue, but this an important cleanup for the future.

Related branches

Changed in nova:
status: New → In Progress
importance: Undecided → Wishlist
assignee: nobody → Vish Ishaya (vishvananda)
Thierry Carrez (ttx)
Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
milestone: none → diablo-2
Thierry Carrez (ttx)
Changed in nova:
milestone: diablo-2 → 2011.3
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.