Bug 1452396 - SSUI shows Manage IQ productization
Summary: SSUI shows Manage IQ productization
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - Service
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.9.0
Assignee: Allen W
QA Contact: Dave Johnson
URL:
Whiteboard: ssui:
: 1501043 (view as bug list)
Depends On:
Blocks: 1460755
TreeView+ depends on / blocked
 
Reported: 2017-05-18 21:08 UTC by Matt Pusateri
Modified: 2019-08-06 20:05 UTC (History)
9 users (show)

Fixed In Version: 5.9.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1460755 (view as bug list)
Environment:
Last Closed: 2018-03-06 15:07:14 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
login screen (112.88 KB, image/png)
2017-05-18 21:14 UTC, Matt Pusateri
no flags Details
Header bar (20.41 KB, image/png)
2017-05-18 21:15 UTC, Matt Pusateri
no flags Details

Description Matt Pusateri 2017-05-18 21:08:10 UTC
Description of problem:
SSUI has MIQ productization in various places instead of RH productization See screenshots. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Login screen, Header bar, about modal.  Maybe more I don't know what all get's changed.

Comment 2 Matt Pusateri 2017-05-18 21:14:32 UTC
Created attachment 1280244 [details]
login screen

Comment 3 Matt Pusateri 2017-05-18 21:15:18 UTC
Created attachment 1280245 [details]
Header bar

Comment 4 Matt Pusateri 2017-05-18 21:17:08 UTC
Version 5.8.0.15

Comment 5 Chris Kacerguis 2017-05-18 21:51:00 UTC
Just looking at the bg-login.png file (that's a good one to look at) it seems that all instances of that file (there are 3) are correct.  However, looking at where webpack puts things, there is a file that is the incorrect image.  

This leads me to think that yard build is getting run before the productization files are in place.

Comment 7 Chris Kacerguis 2017-05-19 13:10:31 UTC
Issue is here:

https://github.com/ManageIQ/manageiq-ui-service/blob/105db14ae4f50df057b5c41c2d834861661df74b/config/webpack.dev.js#L99

If the file is small, and not present before we build, it doesn’t matter what’s in the skin folder, we serve a small URI encoded file.

PR incoming.

Comment 8 Allen W 2017-05-19 19:25:09 UTC
sooooooo after a long day of bagging the head against the keyboard… our core issue with skinning is this.  Some assets work and some assets don’t because the assets declarations are different. Declarations from the html with `src` refer to the images folder, which is fine because at the tail end of webpacking that is populated (in miq/public) with the desired skinned contents.  Declarations from the sass files however get processed, which happens *before* the skinned assets are copied (but also, these assets look for images in the `client/app/assets/images` folder rather than the `/client/skinned` folder)

SO I propose that we reconfigure the symlink to link the `sample-skin/images` folder to the ‘client/app/assets/images` folder in addition to `client/skinned`this will ensure compiled assets used skinned versions.

Comment 9 Chris Kacerguis 2017-05-19 19:39:50 UTC
@Satoe - Thoughts on Allen's idea (Comment 8)?

Comment 10 Satoe Imaishi 2017-05-19 19:52:59 UTC
Works for me - once needed change is done on SUI side (change to link.sh?), please assign this BZ to me so I can ensure downstream build makes use of the change.

Comment 11 Allen W 2017-05-24 21:27:37 UTC
https://github.com/ManageIQ/manageiq-ui-service/pull/790

Satoe, good news, you got nothing to do here, nothing changed with link.sh, essentially reconfigured webpack so that we're now dynamically setting asset urls in sass based on deployment environment, so when we're in production, we'll use the appropriate /images folder assets

Comment 13 Matt Pusateri 2017-10-12 21:29:09 UTC
Verified in 5.9.0.2

Comment 14 Chris Kacerguis 2017-10-12 22:02:45 UTC
*** Bug 1501043 has been marked as a duplicate of this bug. ***


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