Bug 1513723

Summary: upgrade to satellite 6.3 beta wont work if ssl.conf is missing
Product: Red Hat Satellite Reporter: Chris Roberts <chrobert>
Component: UpgradesAssignee: Chris Roberts <chrobert>
Status: CLOSED ERRATA QA Contact: Sachin Ghai <sghai>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: bbuckingham, cdonnell, cwelton, egolov, inecas, mbacovsk, mmccune, pcreech, sghai
Target Milestone: UnspecifiedKeywords: PrioBumpGSS, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
URL: http://projects.theforeman.org/issues/21708
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-21 16:54:37 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 Roberts 2017-11-15 20:49:51 UTC 
Description of problem:
if there is an update to the modssl/httpd package and you upgrade to 6.3 and ssl.conf is not present the upgrade will fail with httpd not being able to start.

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


How reproducible:


Steps to Reproduce:
1. install satellite 6.2
2. rm -rf ssl.conf file in http conf dir
3. upgrade to 6.3 with an upgrade to httpd/modssl
4. run upgrade

Actual results:

httpd wont start since dual listen 443 in ssl.conf and ports.conf

Expected results:

upgrade to go through

Additional info:
Comment 3 Sachin Ghai 2017-12-13 10:19:34 UTC 
To test the fix, performed upgrade from 6.2.z to satellite 6.3 snap28 using a customer db.

since httpd and mod_ssl needs to be updated along with upgrade, so I just downgraded both rpms before upgrade and removed the ssl.conf from /etc/httpd/conf.d directory and ran upgrade w/ 6.3 snap28 build. Upgrade was completed successfully.
Comment 6 Satellite Program 2018-02-21 16:54:37 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.
> > 
> > https://access.redhat.com/errata/RHSA-2018:0336