Bug 725571

Summary:	Running multiple RHEV-M installs corrupted certs database
Product:	Red Hat Enterprise Linux 6	Reporter:	Mark Wagner <mwagner>
Component:	openssl	Assignee:	Tomas Mraz <tmraz>
Status:	CLOSED WONTFIX	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.1	CC:	dfediuck, dpal, iheim, perfbz
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	6.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:
Clones:	725732 (view as bug list)		Environment:
Last Closed:	2011-07-26 09:09:45 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Mark Wagner 2011-07-25 21:11:59 UTC

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:

Comment 3 RHEL Program Management 2011-07-25 21:39:06 UTC

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.

Comment 6 Doron Fediuck 2011-07-26 08:58:28 UTC

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

Comment 7 Tomas Mraz 2011-07-26 09:09:45 UTC

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.