timeutils.utcnow use in oslo-incubator and oslo.utils
Bug #1354521 reported by
Brant Knudson
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.
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.
Changed in oslo: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in oslo: | |
assignee: | nobody → Davanum Srinivas (DIMS) (dims-v) |
status: | Triaged → In Progress |
Changed in oslo-incubator: | |
status: | In Progress → Fix Committed |
Changed in oslo-incubator: | |
milestone: | none → kilo-1 |
status: | Fix Committed → Fix Released |
Changed in oslo-incubator: | |
milestone: | kilo-1 → 2015.1.0 |
To post a comment you must log in.
I don't know what the fix would be... maybe change memorycache to use oslo.utils.