Bug 1351052

Summary: certmonger build for RHEL 7.3 failure
Product: Red Hat Enterprise Linux 7 Reporter: Jan Cholasta <jcholast>
Component: certmongerAssignee: Jan Cholasta <jcholast>
Status: CLOSED ERRATA QA Contact: Kaleem <ksiddiqu>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: dkupka, jcholast, mkosek, nalin
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: certmonger-0.78.4-2.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 07:50:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
console output with verification steps none

Description Jan Cholasta 2016-06-29 06:26:07 UTC
Description of problem:

certmonger build for RHEL 7.3 fails in the check phase. The tests fail because support for 512 bit RSA has been disabled in RHEL. There may also be other failures.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Try to rebuild certmonger-0.78.4-1.el7

Actual results:
The build fails.

Expected results:
The build succeeds.

Additional info:

Comment 3 Kaleem 2016-08-29 10:40:48 UTC
Please provide steps to verify this.

Comment 4 Jan Cholasta 2016-08-30 05:27:16 UTC
1. Build certmonger-0.78.4-2.el7 RPM, the build must be successful.

Comment 5 Kaleem 2016-09-20 11:00:21 UTC

Certmonger version:

Please find the attached rpmbuild console outout

Comment 6 Kaleem 2016-09-20 11:03:11 UTC
Created attachment 1202852 [details]
console output with verification steps

Comment 8 errata-xmlrpc 2016-11-04 07:50:55 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.