nova.crypto.revoke_cert always raises ProjectNotFound
Bug #1376368 reported by
Alex Gaynor
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Critical
|
Russell Bryant | ||
OpenStack Security Advisory |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
(Marked this as a security issue for now, since cert revocation not working is pretty serious)
https:/
os.chdir *always* returns None, which means that path is always taken and the cert is never revoked
Changed in ossa: | |
status: | New → Incomplete |
Changed in nova: | |
assignee: | nobody → Davanum Srinivas (DIMS) (dims-v) |
Changed in nova: | |
milestone: | none → juno-rc2 |
tags: | removed: juno-rc-potential |
Changed in nova: | |
assignee: | Davanum Srinivas (DIMS) (dims-v) → Russell Bryant (russellb) |
milestone: | juno-rc2 → kilo-1 |
Changed in nova: | |
milestone: | kilo-1 → juno-rc2 |
no longer affects: | nova/juno |
Changed in nova: | |
assignee: | Russell Bryant (russellb) → Davanum Srinivas (DIMS) (dims-v) |
Changed in nova: | |
assignee: | Davanum Srinivas (DIMS) (dims-v) → Russell Bryant (russellb) |
Changed in nova: | |
milestone: | juno-rc2 → 2014.2 |
To post a comment you must log in.
Thanks for the report, the OSSA task have been set to incomplete pending additional security reviews.
Well os.chdir will raise an exception if the directory is not existent...
Yet the revocation code seems to be unreachable!