Bug 1478870
| Summary: | Horizon won't load with OSP11 - Script timed out before returning headers: django.wsgi | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Radomir Dopieralski <rdopiera> | |
| Component: | puppet-horizon | Assignee: | Radomir Dopieralski <rdopiera> | |
| Status: | CLOSED ERRATA | QA Contact: | Arik Chernetsky <achernet> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 11.0 (Ocata) | CC: | aortega, apannu, asimonel, athomas, beth.white, cchen, gcharot, iovadia, jjoyce, jschluet, mburns, mrunge, rdopiera, roxenham, samccann, slinaber, srevivo, tvignaud | |
| Target Milestone: | z2 | Keywords: | Triaged, ZStream | |
| Target Release: | 11.0 (Ocata) | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | puppet-horizon-10.3.1-2.el7ost | Doc Type: | Bug Fix | |
| Doc Text: |
Some binary python modules used by Horizon were compiled with a flag that makes them use the simplified GIL state API. Since mod_wsgi uses sub-interpreters, and the simplified GIL state API is not re-entrant, this results in the mod_wsgi locking up and hanging, making the dashboard unavailable.
Added "WSGIApplicationGroup %{GLOBAL}" to mod_wsgi configuration, which forces it to always use the main interpreter instead of sub-interpreters. With that option, mod_wsgi works correctly no matter what options were used to compile the binary python modules. The slight performance penalty is not noticeable.
|
Story Points: | --- | |
| Clone Of: | 1478042 | |||
| : | 1479732 (view as bug list) | Environment: | ||
| Last Closed: | 2017-09-13 21:43:17 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, 1479057, 1479058, 1496173 | |||
| Bug Blocks: | 1479732, 1481774, 1485889, 1485890, 1485894 | |||
|
Comment 1
Radomir Dopieralski
2017-08-07 13:56: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:2721 |