Bug 1485894
| 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-modules | Assignee: | Radomir Dopieralski <rdopiera> |
| Status: | CLOSED ERRATA | QA Contact: | Udi Kalifon <ukalifon> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.0 (Juno) | CC: | achernet, aortega, apannu, asimonel, athomas, beth.white, cchen, dmacpher, gcharot, iovadia, jjoyce, jschluet, mburns, mrunge, nlevinki, rdopiera, rhos-maint, roxenham, sclewis, slinaber, srevivo, tvignaud |
| Target Milestone: | zstream | Keywords: | Triaged, ZStream |
| Target Release: | 6.0 (Juno) | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | 1485890 | Environment: | |
| Last Closed: | 2017-10-19 19:22:24 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, 1485889, 1485890, 1496173 | ||
| Bug Blocks: | |||
|
Comment 3
Udi Kalifon
2017-10-19 07:40:26 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 |