Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1479057

Summary: Horizon won't load with OSP11 - Script timed out before returning headers: django.wsgi
Product: Red Hat OpenStack Reporter: Radomir Dopieralski <rdopiera>
Component: python-django-horizonAssignee: Radomir Dopieralski <rdopiera>
Status: CLOSED ERRATA QA Contact: Ido Ovadia <iovadia>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0 (Kilo)CC: aortega, apannu, asimonel, athomas, beth.white, cchen, ccollett, gcharot, iovadia, ksavich, lbezdick, mburns, mrunge, rdopiera, roxenham, srevivo
Target Milestone: zstreamKeywords: Triaged, ZStream
Target Release: 7.0 (Kilo)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: python-django-horizon-2015.1.4-3.el7ost Doc Type: Bug Fix
Doc Text:
Previously, mod_wsgi used sub-interpreters, and the simplified GIL state API is not re-entrant. Horizon uses some binary modules compiled with a flag that makes them use the simplified GIL state API. Consequently, mod_wsgi would lock up and hang, making the dashboard unavailable. This update adds "WSGIApplicationGroup %{GLOBAL}" to mod_wsgi configuration, forcing it to always use the main interpreter instead of sub-interpreters. As a result, mod_wsgi works correctly, regardless of the options used to compile the binary python modules. The slight performance penalty is not noticeable.
 Story Points: ---
Clone Of: 1479056
: 1479058 (view as bug list) Environment:
Last Closed: 2017-09-12 17:23:28 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, 1479051, 1479055, 1479056, 1496173    
Bug Blocks: 1478870, 1479058, 1479732, 1481774, 1485889, 1485890, 1485894    

Comment 5 errata-xmlrpc 2017-09-12 17:23:28 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:2695