Bug 2228246

Summary:	openscap scanner (oscap) runs out of memory
Product:	Red Hat Enterprise Linux 8	Reporter:	Paulo Andrade <pandrade>
Component:	openscap	Assignee:	Jan Černý <jcerny>
Status:	CLOSED MIGRATED	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.6	CC:	ekolesni, jcerny, matyc, mhaicman, mmarhefk
Target Milestone:	rc	Keywords:	MigratedToJIRA, Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-08-17 14:27:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.

Comment 7 Red Hat Bugzilla 2024-01-27 04:25:36 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days