Bug 1485889

Summary: Horizon won't load with OSP11 - Script timed out before returning headers: django.wsgi
Product: Red Hat OpenStack Reporter: Radomir Dopieralski <rdopiera>
Component: openstack-puppet-modulesAssignee: Radomir Dopieralski <rdopiera>
Status: CLOSED ERRATA QA Contact: Arik Chernetsky <achernet>
Severity: medium Docs Contact:
Priority: high    
Version: 8.0 (Liberty)CC: achernet, aortega, apannu, asimonel, athomas, beth.white, cchen, ccollett, gcharot, iovadia, jjoyce, jschluet, mburns, mrunge, nlevinki, opavlenk, rdopiera, rhos-maint, roxenham, sclewis, slinaber, srevivo, tvignaud
Target Milestone: zstreamKeywords: Triaged, ZStream
Target Release: 8.0 (Liberty)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-puppet-modules-7.1.5-7.el7ost Doc Type: Bug Fix
Doc Text:
Previously, some binary Python modules used by Horizon were compiled with a flag that requires them to use the simplified GIL state API. Since mod_wsgi uses sub-interpreters and the simplified GIL state API is not reentrant, it results in the mod_wsgi locking up. Consequently the dashboard is unavailable. With this update, the mod_wsgi configuration was changed, forcing mod_wsgi to use the main interpreter instead of sub-interpreters. As a result, mod_wsgi works correctly.
Story Points: ---
Clone Of: 1481774
: 1485890 (view as bug list) Environment:
Last Closed: 2017-11-29 15:57:09 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:
Bug Depends On: 1478042, 1478870, 1479051, 1479055, 1479056, 1479057, 1479058, 1479732, 1481774, 1496173    
Bug Blocks: 1485890, 1485894    

Comment 1 Radomir Dopieralski 2017-09-22 23:18:51 UTC
Installed OSP8 with openstack-puppet-modules-7.1.5-7.el7ost from brew. Verified that it works and that the /etc/httpd/conf.d/15-horizon_vhost.conf file contains the line WSGIApplicationGroup %{GLOBAL}.

Comment 5 errata-xmlrpc 2017-11-29 15:57:09 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/RHBA-2017:3287