Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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:
When performing oscap-chroot on not complete chrooted filesystem, there are big walls of errors. I consider it usability issue on par with tracebacks - we don't want user to read tracebacks.
Version-Release number of selected component (if applicable):
openscap-1.2.14-1.el7.x86_64
How reproducible:
reliably
Steps to Reproduce:
1. oscap-chroot ./empty_dir oval eval /usr/share/xml/scap/ssg/content/ssg-rhel7-oval.xml
2.
3.
Actual results:
lots of errors, some blocks are more than 100 lines long
Expected results:
warning or error is compact, and useful to the user
Additional info:
See also Bug 1447341 which deals with the same area.
As the reason for this bug is change of default verbosity, I am marking this as a duplicate of Bug 1447341.
*** This bug has been marked as a duplicate of bug 1447341 ***