New commit detected on ManageIQ/manageiq-appliance/ivanchuk: https://github.com/ManageIQ/manageiq-appliance/commit/bee5b8f5c1fe9a54c373a5c47f9b287d873ec768 commit bee5b8f5c1fe9a54c373a5c47f9b287d873ec768 Author: Brandon Dunne <bdunne> AuthorDate: Thu Dec 12 17:10:06 2019 -0500 Commit: Brandon Dunne <bdunne> CommitDate: Thu Dec 12 17:10:06 2019 -0500 Merge pull request #267 from carbonin/bump_appliance_console Update manageiq-appliance_console to v5.3.0 (cherry picked from commit 45384f58186d1827d75095d84a9ed12c3344ee0d) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1784556 Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1784557 manageiq-appliance-dependencies.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
*** Bug 1790992 has been marked as a duplicate of this bug. ***
It is just a warning, but I think it should not appear (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
Is the bug fixed as originally reported? The warnings are a separate issue. They were caused by the fix for https://bugzilla.redhat.com/show_bug.cgi?id=1784557 and are resolved in https://github.com/ManageIQ/manageiq-appliance_console/pull/108 Additionally, I don't think the warnings really warrant the blocker flag and severity of this BZ so it should be opened as a separate one.
Verified in 5.11.2.0.20200113212029_18edbd8 Verification steps: 1. SSH to the appliance and run "ap" 2. Hit enter and then 15 3. Verified the following message appeared Harden Appliance Using SCAP Configuration Locking down the appliance for SCAP... Complete Press any key to continue. New Bug was written for the warnings that appeared when starting the appliance console: https://bugzilla.redhat.com/show_bug.cgi?id=1793070
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-2020:0452