Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem: "hammer scap-content create" command is failing with error
"Error: No such file or directory"
Version-Release number of selected component (if applicable):
6.14.0 Snap 8
How reproducible:
Always
Steps to Reproduce:
1. On Satellite terminal, try to create scap-content using Hammer CLI command
# hammer scap-content create --scap-file="/usr/share/xml/scap/ssg/content/ssg-rhel7-ds.xml --title="test"
Actual results:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Failed to create SCAP content:
Error: No such file or directory @ rb_sysopen - /usr/share/xml/scap/ssg/content/ssg-rhel7-ds.xml --title=test
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Expected results:
SCAP content should be created
Additional info:
1. Upon failure of "scap-content create" command system call function name "rb_sysopen" is displayed which is not expected.
2. SCAP packages available on satellite
# rpm -qa | grep openscap
openscap-1.3.7-1.el8.x86_64
rubygem-openscap_parser-1.0.2-2.el8sat.noarch
rubygem-smart_proxy_openscap-0.9.2-1.el8sat.noarch
rubygem-openscap-0.4.9-9.el8sat.noarch
rubygem-hammer_cli_foreman_openscap-0.1.13-2.el8sat.noarch
rubygem-foreman_openscap-7.0.0-1.el8sat.noarch
3. Missing package "scap-security-guide" in 6.14.0 Snap 8
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 (Important: Satellite 6.14 security and bug fix update), 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-2023:6818