Bug 1318041

Summary:	Plugin asset compilation does not expand SCSS imports of CSS files
Product:	Red Hat Satellite	Reporter:	Eric Helms <ehelms>
Component:	Provisioning	Assignee:	Eric Helms <ehelms>
Status:	CLOSED ERRATA	QA Contact:	sthirugn <sthirugn>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.0.4	CC:	bbuckingham, sthirugn
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/14221
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-27 09:06:45 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1315610

Description Eric Helms 2016-03-15 20:13:48 UTC

The plugin asset rake task is not using the template provided by sass-rails that correctly identifies css imports in SCSS files. This results in either compiled CSS files that have regular css import statements or can throw errors during asset compilation. In the former case, 404s will be seen in the browser in production because the stylesheet will try to import those CSS files from the server (when they should be embedded in the compiled CSS file).

Comment 1 Eric Helms 2016-03-15 20:13:50 UTC

Created from redmine issue http://projects.theforeman.org/issues/14221

Comment 2 Eric Helms 2016-03-15 20:13:53 UTC

Upstream bug assigned to ehelms

Comment 4 Bryan Kearney 2016-03-16 10:01:23 UTC

Moving to POST since upstream bug http://projects.theforeman.org/issues/14221 has been closed
-------------
Eric Helms
Applied in changeset commit:d8520a15230d854e65bb7de012a1a7e4f9806392.

Comment 6 sthirugn@redhat.com 2016-04-22 21:04:58 UTC

So far there are no issues regarding 404 on retrieving various assets.  Moving this verified for Satellite-6.2-beta-snap-9.  This will be reopened if any issue is found in future.

Comment 8 errata-xmlrpc 2016-07-27 09:06:45 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1500