Bug 1790992 - Scap hardeding fails
Summary: Scap hardeding fails
Keywords:
Status: CLOSED DUPLICATE of bug 1784556
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.11.2
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: GA
: cfme-future
Assignee: Gregg Tanzillo
QA Contact: Jaroslav Henner
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-14 16:22 UTC by Jaroslav Henner
Modified: 2020-07-15 14:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-14 17:03:35 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jaroslav Henner 2020-01-14 16:22:07 UTC
Description of problem:
After selecting the option
15) Harden Appliance Using SCAP Configuration

The error appears on the console:
Harden Appliance Using SCAP Configuration

Locking down the appliance for SCAP...
Configuration failed: undefined method `add_next_sibling' for nil:NilClass

Press any key to continue.



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

How reproducible:
2/2

Steps to Reproduce:
1. ap
2. 15
3.

Actual results:
error on console

Expected results:
no error

Additional info:
I found no error in evm, appliance_console nor production log

Comment 2 Jaroslav Henner 2020-01-14 16:29:26 UTC
Note I have also noticed this upon the start of the appliance_console:

[root@dhcp-8-196-188 ~]# ap
/opt/rh/cfme-gemset/gems/manageiq-appliance_console-5.3.0/bin/appliance_console:22: warning: already initialized constant SCAP_RULES_DIR
/opt/rh/cfme-gemset/gems/manageiq-appliance_console-5.3.0/lib/manageiq/appliance_console/cli.rb:12: warning: previous definition of SCAP_RULES_DIR was here

Comment 3 Jaroslav Henner 2020-01-14 17:03:35 UTC

*** This bug has been marked as a duplicate of bug 1784556 ***


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