timeutils.utcnow use in oslo-incubator and oslo.utils

Bug #1354521 reported by Brant Knudson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
oslo-incubator
Fix Released
High
Davanum Srinivas (DIMS)

Bug Description

There's a oslo.utils.timeutils.utcnow to take the place of oslo-incubator timeutils.utcnow.

When migrating from oslo-incubator to oslo.utils, there's a lot of tests that mock utcnow, so these are now mocking oslo.utils.utcnow.

The memorycache module is using utcnow from oslo-incubator. So mocking oslo.utils.utcnow isn't going to mock osl-incubator's

There's a lot of tests in keystoneclient and keystonemiddleware for the auth_token middleware that mock utcnow, and because some use memorycache these tests fail.

Revision history for this message
Brant Knudson (blk-u) wrote :

I don't know what the fix would be... maybe change memorycache to use oslo.utils.

description: updated
Ben Nemec (bnemec)
Changed in oslo:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote :

Nova is running into this problem as well

Changed in oslo:
assignee: nobody → Davanum Srinivas (DIMS) (dims-v)
status: Triaged → In Progress
Changed in oslo-incubator:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in oslo-incubator:
milestone: none → kilo-1
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in oslo-incubator:
milestone: kilo-1 → 2015.1.0
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.