Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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:

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.

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