Bug 1186440

Summary: unable to access UI after installing foreman_openscap package
Product: Red Hat Satellite Reporter: Kedar Bidarkar <kbidarka>
Component: WebUIAssignee: Shlomi Zadok <szadok>
WebUI sub component: Foreman QA Contact: Kedar Bidarkar <kbidarka>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: unspecified CC: bbuckingham, bkearney, cwelton, jmontleo, slukasik
Version: NightlyKeywords: Triaged
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-12 05:22:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
oscap failure none

Description Kedar Bidarkar 2015-01-27 16:43:02 UTC
Created attachment 984759 [details]
oscap failure

Description of problem:

Installing "ruby193-rubygem-foreman_openscap" package leads to broken UI.

Version-Release number of selected component (if applicable):
nightly + oscap package from foreman-plugins

How reproducible:
always

Steps to Reproduce:
1. Install oscap packages with "yum install ruby193-rubygem-foreman_openscap"
2. restart katello-service 
3. WEBUI is broken

Actual results:
WebUI is broken after installing 

Expected results:
WebUI should be working with the oscap plugin.

Additional info:

Comment 1 Kedar Bidarkar 2015-01-27 16:44:54 UTC
following are the oscap packages installed on the foreman nightly setup.


(1/5): openscap-1.2.1-0.1.el6.x86_64.rpm                                                                                                                               | 3.2 MB     00:01     
(2/5): ruby193-rubygem-ffi-1.4.0-3.el6.x86_64.rpm                                                                                                                      | 125 kB     00:00     
(3/5): ruby193-rubygem-foreman_openscap-0.2.1-1.el6.noarch.rpm                                                                                                         |  31 kB     00:00     
(4/5): ruby193-rubygem-openscap-0.4.2-2.el6.noarch.rpm                                                                                                                 |  18 kB     00:00     
(5/5): ruby193-rubygem-scaptimony-0.3.0-1.el6.noarch.rpm

Comment 4 Šimon Lukašík 2015-01-28 10:44:09 UTC
This is caused by delayed release of foreman_openscap.

The scaptimony 0.3.0 is requirement of foreman_openscap 0.3.0 and it does not play well with foreman_openscap 0.2.0.

We will release foreman_openscap 0.3.0 shortly and make sure that the future releases of foreman_openscap require the specific version of scaptimony.

Comment 5 Šimon Lukašík 2015-01-29 21:37:30 UTC
Fixed upstream in https://github.com/theforeman/foreman-packaging/pull/509

Comment 9 Kedar Bidarkar 2015-02-13 06:40:51 UTC
We do have the 0.3.0 version in Beta snap2, so will be moving this to verified state.

And The Satellite6 UI is now accesible after installing this package.

Comment 10 Bryan Kearney 2015-08-11 13:37:41 UTC
This bug is slated to be released with Satellite 6.1.

Comment 11 errata-xmlrpc 2015-08-12 05:22:23 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-2015:1592