This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2228246 - openscap scanner (oscap) runs out of memory [NEEDINFO]
Summary: openscap scanner (oscap) runs out of memory
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: openscap
Version: 8.6
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Jan Černý
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-01 20:00 UTC by Paulo Andrade
Modified: 2023-08-17 14:27 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-17 14:27:08 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pandrade: needinfo? (jcerny)

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-1474 0 None Migrated None 2023-08-17 14:26:59 UTC
Red Hat Issue Tracker RHELPLAN-164073 0 None None None 2023-08-01 20:02:01 UTC

Comment 1 Jan Černý 2023-08-07 12:33:45 UTC 
Hi,

I would like to ask you for as many information as possible because the issues like this are often difficult to investigate.
Which versions of openscap and scap-security-guide packages have been used?
Have you tried this with the latest available versions of the openscap and scap-security-guide packages?
Does any specific rule cause this problem? Did any of the approaches in the linked article helped or mitigated the problem?
Would it be possible to attach the output of oscap with --verbose logs?
Comment 5 RHEL Program Management 2023-08-17 14:12:44 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 6 RHEL Program Management 2023-08-17 14:27:08 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues.
Note You need to log in before you can comment on or make changes to this bug.