Hide Forgot
Description of problem: In Origin - M4. After installing using oo-install. Icons are not populating. getting 404 for woff file https://<host>/assets/openshift-icon-55f8556a7faecb27032125eb2f500911.woff Version-Release number of selected component (if applicable): Origin M4 How reproducible: Install Openshift-origin M4 and if you hit the server url in browser, everything will be working but icons will not be displayed. Steps to Reproduce: 1. Install Openshift origin m4 using sh <(curl -s https://install.openshift.com/origin-m4) 2. open in browser after installation https://<host> 3. You can see icons are not displaying Actual results: Icons should be displaying near to the text or wherever it is placed. Expected results: It is not displaying. Additional info: To fix this: This is the file where path is given wrongly - common-ddb6f0c18956c0219bb83c21326312ca.css In this file instead of url(/console/assets/openshift-icon-55f8556a7faecb27032125eb2f500911.woff) it is given as url(/assets/openshift-icon-55f8556a7faecb27032125eb2f500911.woff) If we correct to url(/console/assets/openshift-icon-55f8556a7faecb27032125eb2f500911.woff) EVerything will be working as expected. Thanks! You all doing a great job, Thanks for your help!
This is not a bug in oo-install for M4, but rather with OpenShift M4 itself. I believe that the CSS url() line referenced above, in its pre-processed state, lives here: https://github.com/openshift/origin-server/blob/master/console/app/assets/stylesheets/_openshift-icon.css.scss#L5 When it is processed by SASS and combined into common.css[1], it is getting the wrong URL path. Re-classifying as a management console bug. [1]: https://github.com/openshift/origin-server/blob/master/console/app/assets/stylesheets/common.css.scss#L84
This is an M4 issue, so directing it to the Online team.
We apologize, however, we do not plan to address this report at this time. The majority of our active development is for the v3 version of OpenShift. If you would like for Red Hat to reconsider this decision, please reach out to your support representative. We are very sorry for any inconvenience this may cause.