Bug 1330554 - HTTP 500 page is not themed
Summary: HTTP 500 page is not themed
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-django-horizon
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: async
: ---
Assignee: Beth White
QA Contact: Ido Ovadia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-26 12:47 UTC by Martin Pavlásek
Modified: 2016-12-13 15:49 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-13 15:49:57 UTC
Target Upstream Version:

Attachments (Terms of Use)
error page vs. common page (100.77 KB, image/png)
2016-04-26 12:47 UTC, Martin Pavlásek 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1478652 0 None None None 2016-06-23 18:24:57 UTC

Description Martin Pavlásek 2016-04-26 12:47:12 UTC 
Created attachment 1150966 [details]
error page vs. common page

Description of problem:
If some link leads to somewhere, that cause HTTP 500 status page, the error page don't use RHOS theme. Let see the attachment.

Version-Release number of selected component (if applicable):
python-django-horizon-2015.1.2-4.el7ost.noarch
RHEL 7.2

How reproducible:
100%

Steps to Reproduce:
1. 
2.
3.

Actual results:
The page looks like from upstream openstack

Expected results:
I'm expecting gray-red color scheme there.

Additional info:
Comment 3 Radomir Dopieralski 2016-11-23 11:20:48 UTC 
I would say that Horizon should never display an Error 500 page, and if it does, that is a bug in Horizon.
Comment 5 Beth White 2016-12-13 15:49:57 UTC 
Since the error pages in Horizon are by necessity static, and the themes are by their nature dynamic, it is impossible to theme the error pages in accordance with user-selected themes without significantly modifying the framework on which Horizon is based.
Note You need to log in before you can comment on or make changes to this bug.