Bug 1560479 - custom css file cleared after upgrade/update
Summary: custom css file cleared after upgrade/update
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Build
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.10.0
Assignee: Satoe Imaishi
QA Contact: Jaroslav Henner
URL:
Whiteboard: black:upgrade:migration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-26 09:25 UTC by luke couzens
Modified: 2019-02-07 23:01 UTC (History)
5 users (show)

Fixed In Version: 5.10.0.4
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-07 23:01:18 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:0212 0 None None None 2019-02-07 23:01:24 UTC

Description luke couzens 2018-03-26 09:25:06 UTC 
Description of problem:custom css file cleared after upgrade/update


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


How reproducible:100%


Steps to Reproduce:
1.provision 5.9.1.0 appliance
2.add custom css to vmdb/public/custom.css
3.add latest repos
4.update appliance with webui

Actual results:
custom.css file is over written with fresh file

Expected results:
customization's not lost and continue to work after update.

Additional info:
Comment 3 Jaroslav Henner 2019-01-23 10:47:01 UTC 
I upgraded from CFME 5.9 to 5.10. The file was preserved and customisation were working after the upgrade and migration.
Comment 4 errata-xmlrpc 2019-02-07 23:01:18 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/RHSA-2019:0212
Note You need to log in before you can comment on or make changes to this bug.