+++ This bug was initially created as a clone of Bug #1019587 +++ Description of problem: Check the favicon of ose console, it should not be a circle, and the title is "Welcome to OpenShift | OpenShift Origin", it should indicate openshift enterprise. Details see in screenshot please. Version-Release number of selected component (if applicable): 2.0/2013-10-15.2 How reproducible: always Steps to Reproduce: 1.Check the favicon and title of ose console 2. 3. Actual results: The favicon is just a circle and the title is "Welcome to OpenShift | OpenShift Origin". Expected results: The favicon should be openshift logo and the title should indicate openshift enterprise. Additional info: --- Additional comment from RHEL Product and Program Management on 2013-10-16 02:49:03 EDT --- Since this issue was entered in bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release. --- Additional comment from Tian Feng on 2013-11-18 05:39:14 EST --- Test on 2.0/2013-11-15.1, the favicon can't display on IE9 & IE10. --- Additional comment from Brenton Leanhardt on 2014-03-21 14:55:01 EDT --- Not urgent, but could someone retest and see if the favicon's are showing up in the 2.1 rebase? I verified the title is correct and that the favicon was showing up in Firefox on Fedora. http://etherpad.corp.redhat.com/puddle-2-1-2014-03-21 --- Additional comment from Tian Feng on 2014-03-23 23:24:09 EDT --- Test on puddle-2-1-2014-03-21. Favicon can't show up on IE9 & IE10 & Safari7. It can show up on Firefox28, Chrome33 successfully. Could you pls check it? Thanks! --- Additional comment from Tian Feng on 2014-03-23 23:24:32 EDT --- --- Additional comment from Tian Feng on 2014-03-23 23:25:00 EDT --- --- Additional comment from Tian Feng on 2014-03-23 23:25:23 EDT ---
Favicon fixed in https://github.com/openshift/origin/pull/2563
Nm, this is against 2.x, reopening
I have tested the issue on IE8 and IE11 (I couldn't find VMs with IE9 and 10) and the web console displays correct OpenShift Enterprise logo. So this issue has been fixed already. Thanks, Vu