Bug 1547643

Summary: intermittent install failure, httpd does not start
Product: Red Hat Satellite Reporter: Chris Duryee <cduryee>
Component: InstallationAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.2.14Keywords: Triaged
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-19 15:17:32 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:
Embargoed:

Description Chris Duryee 2018-02-21 16:37:49 UTC 
Description of problem:

When provisioning a fresh satellite host on a hypervisor with flaky DNS, httpd will occasionally not start up. I have to run through the steps in https://access.redhat.com/solutions/1519933 to fix things.

from the puppet httpd error log:

[Wed Feb 21 15:29:04.837896 2018] [ssl:emerg] [pid 28744] AH02238: Unable to configure RSA server private key                                
[Wed Feb 21 15:29:04.837914 2018] [ssl:emerg] [pid 28744] SSL Library Error: error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch            

I am not sure how to repro this or if DNS is related.


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


How reproducible: intermittent
Comment 1 Chris Duryee 2018-02-21 16:38:48 UTC 
package versions:

foreman-installer-1.11.0.18-1.el7sat.noarch
foreman-installer-katello-3.0.0.101-1.el7sat.noarch
katello-installer-base-3.0.0.101-1.el7sat.noarch
satellite-installer-6.2.0.13-1.el7sat.noarch

satellite-6.2.14-4.0.el7sat.noarch
Comment 3 Chris Duryee 2018-02-22 16:36:59 UTC 
I hit this on a capsule install as well.
Comment 6 Chris Duryee 2018-03-19 15:17:32 UTC 

*** This bug has been marked as a duplicate of bug 1557545 ***