Bug 1384722 - miq logo on 404 error page
Summary: miq logo on 404 error page
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - Service
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: cfme-future
Assignee: Allen W
QA Contact: Shveta
URL:
Whiteboard: ssui
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-14 01:20 UTC by Dave Johnson
Modified: 2016-10-28 14:15 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-28 14:15:02 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot (30.50 KB, image/png)
2016-10-14 01:20 UTC, Dave Johnson
no flags Details

Description Dave Johnson 2016-10-14 01:20:32 UTC
Created attachment 1210289 [details]
screenshot

Description of problem:
============================
Typed the wrong url in for the ssui and found that it renders the MIQ logo. 



Version-Release number of selected component (if applicable):  
=============================================================
5.6.2 and 5.7.0.4



How reproducible:
=====================
  100%


Steps to Reproduce:
===============================
1.  https://host/self_service/dave
2.  https://host/self_service_ui
3.


Additional info:
====================================
It take 5-10 seconds to figure out that the page doesn't exist which seemed a little weird.

Comment 1 Allen W 2016-10-26 18:28:32 UTC
Gotta ask the silly question, what logo should be displayed? No logo? Ultimately, what is the desired behavior?

Comment 2 Dave Johnson 2016-10-27 02:28:12 UTC
CloudForms logo or nothing is better than MIQ logo.

Comment 3 Allen W 2016-10-28 14:15:02 UTC
I checked with the powers that are 🤔 confirmed that miq logo is the correct logo to be used here.  Time to fail is a not🐛so gonna close this bz.


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