Bug 1485894 - Horizon won't load with OSP11 - Script timed out before returning headers: django.wsgi
Summary: Horizon won't load with OSP11 - Script timed out before returning headers: dj...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-puppet-modules
Version: 6.0 (Juno)
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: zstream
: 6.0 (Juno)
Assignee: Radomir Dopieralski
QA Contact: Udi Kalifon
URL:
Whiteboard:
Depends On: 1478042 1478870 1479051 1479055 1479056 1479057 1479058 1479732 1481774 1485889 1485890 1496173
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-28 11:38 UTC by Radomir Dopieralski
Modified: 2020-12-14 09:44 UTC (History)
22 users (show)

Fixed In Version: openstack-puppet-modules-2014.2.15-9.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.
Clone Of: 1485890
Environment:
Last Closed: 2017-10-19 19:22:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1573488 0 None None None 2017-08-28 11:38:02 UTC
Launchpad 1708655 0 None None None 2017-08-28 11:38:02 UTC
OpenStack gerrit 491459 0 None None None 2017-08-28 11:38:02 UTC
Red Hat Product Errata RHBA-2017:2992 0 normal SHIPPED_LIVE openstack-packstack and openstack-puppet-modules bug fix advisory 2017-10-19 23:22:10 UTC

Comment 3 Udi Kalifon 2017-10-19 07:40:26 UTC 
Horizon worked after a packstack all-in-one install: 2017-09-25.1
Comment 5 errata-xmlrpc 2017-10-19 19:22:24 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:2992
Note You need to log in before you can comment on or make changes to this bug.