The cms module does not raise an exception if the call fails, but the exit code is zero.

Bug #1071855 reported by Tim Simpson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Identity (keystone)
Fix Released
Undecided
Unassigned

Bug Description

Encountered while running a misconfigured devstack.

OpenSSL does not support CMS in my VM, so when the cms module called openssl, I saw this:

"openssl:Error: 'cms' is an invalid command."

The return code was zero, but the std err indicated an issue. I think that CalledProcessError should be raised if the stderr contains the text "Error."

Revision history for this message
Tim Simpson (tim-simpson) wrote :
Adam Young (ayoung)
Changed in keystone:
status: New → Fix Committed
Thierry Carrez (ttx)
Changed in keystone:
milestone: none → grizzly-1
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in keystone:
milestone: grizzly-1 → 2013.1
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.