Description of problem: RHEV Admin Portal Unreachable After Upgrading to 3.4 due to mod_proxy_ajp not loading Version-Release number of selected component (if applicable): Red Hat Enterprise Virtualization 3.4 (immediately after running ovirt-engine-upgrade) How reproducible: Unknown Steps to Reproduce: 1. Upgrade to RHEV 3.4 2. Upgrade appears successful until attempting to visit Admin Portal 3. Browser returns: Not Found The requested URL /ovirt-engine/ was not found on this server. Actual results: 1. RHEV-M Admin Portal fails to start mod_proxy_ajp after upgrade, 2. service httpd restart returns Starting httpd: Warning: DocumentRoot [/var/www/does/not/exist] does not exist Expected results: RHEV-M Admin Portal works as expected Additional info: Issue is resolved via the following workaround In httpd config, Apache was unable to proxy pass the requests from :443 to ovirt-engine, simply because the proxy_ajp_module didn't load. (/etc/httpd/conf.d/proxy_ajp.conf) <IfModule mod_proxy_ajp.c> LoadModule proxy_ajp_module modules/mod_proxy_ajp.so </IfModule> For some reason, ifModule mod_proxy_ajp.c failed, thus LoadModule was skipped. When the if clause is commented out, everything works.
To summarize an internal investigation: 1. The file /etc/httpd/conf.d/proxy_ajp.conf had bad content due to an internal error, and not due to any known (to me) bug in a released product (rhev or other). 2. I posted a fix to prevent such an error in future similar cases, although I am not sure we really need it. As always, we can't fix everything - if a user somehow unloaded the ajp proxy module, merely adding LoadModule might not be enough - e.g. the user can also remove the actual module file. nvm.
moving to Modified, as the patch was merged to upstream master. Can quite easily be cloned and backported to older releases, not that important imo.
Can you please add a updated steps to reproduce ?
(In reply to Yaniv Dary from comment #11) > Can you please add a updated steps to reproduce ? Something like that should do: 1. On a clean system (el or fedora), yum install httpd 2. Find in /etc/httpd all lines with 'LoadModule proxy_ajp_module' and deactivate them (remove or comment out). 3. install and setup engine. 4. Try opening the web interface with a web browser. To reproduce, install and setup a version without the fix (say, 3.5.z), it will fail. To verify, install and setup a fixed version (current master/3.6+), it should work. For extra points, find and disable mod_proxy_ajp.so (by renaming or removing it) and restart httpd. The fixed version will hopefully cause apache to write to the error log a line which will point you to our conf file, which will have somewhat-helpful comment.
ok, rhevm-3.6.0.2-0.1.el6.noarch so, if anything was broken while loading the module via other files it will be caught by "last" conf file - ie. _z_ -ovirt-engine-proxy.conf ('z-' to be loaded last) and this conf file tries its best to load the module... # grep -vE '^[ \t]*#|^$' /etc/httpd/conf.d/z-ovirt-engine-proxy.conf <IfModule !proxy_ajp_module> LoadModule proxy_ajp_module modules/mod_proxy_ajp.so </IfModule> <IfModule proxy_ajp_module> <IfModule headers_module> RequestHeader unset Expect early </IfModule> <LocationMatch ^/(ovirt-engine($|/)|api($|/)|RHEVManagerWeb/|OvirtEngineWeb/|ca.crt$|engine.ssh.key.txt$|rhevm.ssh.key.txt$)> ProxyPassMatch ajp://127.0.0.1:8702 timeout=3600 retry=5 <IfModule deflate_module> AddOutputFilterByType DEFLATE text/javascript text/css text/html text/xml text/json application/xml application/json application/x-yaml </IfModule> </LocationMatch> </IfModule>
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://rhn.redhat.com/errata/RHEA-2016-0376.html