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:
Running 6.2 beta on RHEL7.2, got the mod_ssl-2.4.6-40.el7_2.1.x86_64 update yesterday. After deploying it, httpd won't start as there are now two "Listen 443" directives:
[root@sat62 ~]# grep -r "Listen.*443" /etc/httpd/
/etc/httpd/conf.d/ssl.conf:Listen 443 https
/etc/httpd/conf/ports.conf:Listen 443
and these lead to
httpd[10568]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:443
When the parser hits the second one.

Version-Release number of selected component (if applicable):
satellite-6.2.0-9.0.beta.el7sat.noarch

How reproducible:
didn't try.

Steps to Reproduce:
1. install satellite before the mod_ssl update
2. update mod_ssl
3. restart httpd

Actual results:
httpd[10568]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:443

Expected results:
httpd starts

Additional info:

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