Bug 2038577

Description of problem:

In certain scenarios, when a satellite is being upgraded from 6,6 -> 6.7 -> 6.8 -> 6.9 -> 6.10, In a few scenario's, The installer executed in prior upgrades were not able to get rid of existing apache configurations referring to mod_passenger.so or mod_wsgi.so and in such scenarios, at the end of the upgrade process to 6.10, httpd fails to get started due to having either of those libraries missing from the satellite.

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

Satellite 6.10.1


How reproducible:

Under a specific scenario where older apache configurations somehow are present in the Satellite server which should not be present since Satellite 6.9

Steps to Reproduce:
1.
2.
3.

Actual results:

The first failure happens at the end of the satellite-installer execution during "satellite-maintain upgrade run --target-version=6.10" and httpd fails to start.

~~
Jan  4 21:34:18 lmpsatellite01 systemd: Stopped The Apache HTTP Server.
Jan  4 21:34:18 lmpsatellite01 systemd: Starting The Apache HTTP Server...
Jan  4 21:34:18 lmpsatellite01 httpd: httpd: Syntax error on line 40 of /etc/httpd/conf/httpd.conf: Syntax error on line 1 of /etc/httpd/conf.modules.d/zpassenger.load: Cannot load modules/mod_passenger.so into server: /etc/httpd/modules/mod_passenger.so: cannot open shared object file: No such file or directory
Jan  4 21:34:18 lmpsatellite01 systemd: httpd.service: main process exited, code=exited, status=1/FAILURE
Jan  4 21:34:18 lmpsatellite01 systemd: Failed to start The Apache HTTP Server.
Jan  4 21:34:18 lmpsatellite01 systemd: Unit httpd.service entered failed state.
~~

Now, if we edit the file "/etc/httpd/conf.modules.d/zpassenger.load", comment out the entry in that file 
or, if we install back the mod_passenger package from https://access.redhat.com/downloads/content/mod_passenger/4.0.18-24.el7sat/x86_64/fd431d51/package and re-run the upgrade everything will go smooth.


Again, as soon as we will proceed for "satellite-maintain content remove-pulp2" , It will remove mod_wsgi package as a part of it but since the older apache config still asks to load it, at the end of the cleanup, if the services will be restarted, the httpd process will fail to get started again.

~~
Jan  4 22:08:21 lmpsatellite01 httpd: httpd: Syntax error on line 40 of /etc/httpd/conf/httpd.conf: Syntax error on line 1 of /etc/httpd/conf.modules.d/wsgi.load: Cannot load modules/mod_wsgi.so into server: /etc/httpd/modules/mod_wsgi.so: cannot open shared object file: No such file or directory
Jan  4 22:08:21 lmpsatellite01 systemd: httpd.service: main process exited, code=exited, status=1/FAILURE
~~

So either have the mod_wsgi package installed back in satellite from https://access.redhat.com/downloads/content/mod_wsgi/3.4-18.el7/x86_64/fd431d51/package or else just comment out all entries in "/etc/httpd/conf.modules.d/wsgi.load" and that will allow httpd to get started.


Additionally, The final cleanup needs to be done this way to get rid of both mod_passenger and mod_wsgi rpms and those old configuration files from Satellite 6.10

####################
* Stop all services

* Take a tar of /etc/httpd  and /usr/lib64/httpd/modules


*  Remove the rpms:

# rpm -ev --nodeps mod_wsgi mod_passenger


* If any of these files are present get rid of them.

Under '/etc/httpd/conf.modules.d':
10-wsgi.conf
passenger.conf
passenger_extra.conf
wsgi.conf
wsgi.load
zpassenger.load

Under '/etc/httpd/conf.d':
01-status.conf
03-crane.conf
05-foreman_proxy_content.conf
10-pulp.conf
pulp_iso.conf


* Start back httpd and see if it is working.

* If yes, start back all services.
####################



Expected results:

Satellite 6.10 upgrade process should be able to take care of these manual cleanup process 



Additional info:

NA