Bug 1483149 - Deploying Horizon in OSP-10z4 Leads to an Inaccessible Horizon
Summary: Deploying Horizon in OSP-10z4 Leads to an Inaccessible Horizon
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-horizon
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z4
: 10.0 (Newton)
Assignee: Radomir Dopieralski
QA Contact: Ido Ovadia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-18 21:37 UTC by Dustin Schoenbrun
Modified: 2017-09-06 17:13 UTC (History)
11 users (show)

Fixed In Version: puppet-horizon-9.5.0-2.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-06 17:13:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1708655 0 None None None 2017-08-21 10:14:39 UTC
OpenStack gerrit 493593 0 None MERGED Horizon SSL handshake errors with apache 2020-08-21 04:31:03 UTC
Red Hat Product Errata RHBA-2017:2654 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 10 director Bug Fix Advisory 2017-09-06 20:55:36 UTC

Description Dustin Schoenbrun 2017-08-18 21:37:26 UTC
Description of problem:
When deploying Horizon using the OSP-10z4 puddle, the login page for Horizon never appears and instead shows either an HTTP 500 or 503 error. 

Version-Release number of selected component (if applicable):
puppet-horizon-9.5.0-1.el7ost.noarch
python-django-horizon-10.0.5-3.el7ost.noarch


How reproducible:
Looks to be always reproducible. This was observed on four different deployments, all using Infrared to deploy.

Steps to Reproduce:
1. Deploy an OSP-10z4 instance using Infrared with at least one controller and one compute node.
2. Attempt to access the Horizon UI through either the controller's IP or through some sort of port forwarding. I used curl and Firefox to attempt to connect.
3. Observe a 500 or 503 error after a long pause and potentially an error showing up in /etc/httpd/horizon_error.log.

Actual results:
Attempting to access the Horizon UI results in a 500 or 503 error after a pause and an error in the /etc/httpd/horizon_error.log file that reads similar to: 
[Fri Aug 18 21:00:43.394750 2017] [core:error] [pid 95394] [client 172.17.1.12:34606] End of script output before headers: django.wsgi

Expected results:
Horizon UI login page should load successfully.

Additional info:
This was observed on four separate deployments all running the OSP-10z4 puddle (2017-08-11.2), all with various configurations and controller/compute node counts.

Comment 1 Raissa Sarmento 2017-08-21 10:17:14 UTC
Fix for this issue was merged and backported to stable/newton upstream (links on the external bug ids list)

Comment 3 Ido Ovadia 2017-09-05 13:37:07 UTC
Verified
========
puppet-horizon-9.5.0-2.el7ost.noarch

Comment 5 errata-xmlrpc 2017-09-06 17:13:14 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:2654


Note You need to log in before you can comment on or make changes to this bug.