Hide Forgot
Description of problem: While running multiple host installs in parallel on RHEV-M 3.0, the certs database became corrupted. There was a trailing blank line and the serial file was off by one. This corruption made it impossible to create new certs and hence add more hosts. Version-Release number of selected component (if applicable): RHEL6.1 ca-certificates.noarch 2010.63-3.el6 How reproducible: Was not able to reproduce a second time, will keep trying... Steps to Reproduce: 1.Use RHEV-M 2.Create a REST script to install 100 hosts 3.run the script Actual results: /etc/pki/rhevm/database.txt had a blank line The value in /etc/pki/rhevm/serial.txt matched the last entry in th database file. I was unable to create any more certs until the files were fixed by hand. Expected results: It should all "just work" Additional info:
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
Hi, Changing the BZ to openssl, and adding some information; We use OpenSSL for CA functionality in RHEV-M. It seems that we hit a concurrency issue when we try to sign several certificates. The effect was corrupted database file (had an extra empty line) and serial file wasn't increased. What we need is some basic locking mechanism, so when we use "openssl ca" it'll block other calls until it ends the current task. I saw other places implementing it with a simple lock file, similar to what National US laboratories implemented: http://bugzilla.mcs.anl.gov/globus/show_bug.cgi?id=6528
I'm sorry but the openssl ca was never meant to be a full Certificate Authority solution but rather a proof of a concept implementation using OpenSSL. It should not be used as a production tool in an environment such as yours. You will have to add the locking mechanism above it or - what I would suggest as a more appropriate - to use the Red Hat Certificate System http://www.redhat.com/certificate_system/ as the authority.