Modify plugin so that it does not depend on ActionDipatch:Static middleware. Due to configuration changes in Core, this will no longer work as per email below: Hi Lindani, Satoe is in the process of building nightly builds for downstream in preparation for the upcoming CloudForms 4.1 release. During her investigations, she found that the redhat_access_cfme gem is blowing up during application initialization with No such middleware to insert before: ActionDispatch::Static Note that we have changed the configuration to no longer server static assets from Rails (i.e. config.server_static_assets = false), so the check that the gem is doing to find the ActionDispatch::Static middleware may no longer be valid. I'm not sure if you were piggybacking that middleware because it was in a convenient spot in the Rack stack, or if you actually needed to come before that specific one because you were relying on assets being served statically. For now, Satoe has commented out installing the rpm in order to get a build working, and we now have one that you could use for debugging the problem. Thanks, Jason
RPM updated to remove dependency: http://download.devel.redhat.com/brewroot/packages/rh-ruby22-rubygem-redhat_access_cfme/1.0.1/1.el7cf/noarch/rh-ruby22-rubygem-redhat_access_cfme-1.0.1-1.el7cf.noarch.rpm
Please add verification steps
Verify that the CFME appliance starts correctly and that the "Red Hat Insights" UI screens render correctly without any HTTP 404 errors when fetching any required images/fonts files from the server.
Verified the CFME appliance starts correctly and that the "Red Hat Insights" UI screens render correctly without any HTTP 404 errors when fetching any required images/fonts files from the server. Verified Version :- 5.6.0.4-beta2.3.20160421172650_719e256
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:1348