Bug 1386358 - race condition between multiple oscap processes
Summary: race condition between multiple oscap processes
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openscap
Version: 7.4
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Jan Černý
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On: 1368896
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-18 18:06 UTC by Marek Haicman
Modified: 2018-11-07 14:15 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1368896
Environment:
Last Closed: 2018-11-07 14:15:01 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Marek Haicman 2016-10-18 18:06:22 UTC 
+++ This bug was initially created as a clone of Bug #1368896 +++

Description of problem:
Tracking bug for race condition issue in oscap tool.
Please see original bug for description of the issue.




Discussion picked from the original bug:

Brent Baude and I debugged and discussed this issue today. First we suspected it was in openscap-daemon but openscap-daemon runs the right commands with the right paths.

Turns out it is some sort of a race condition between multiple oscap processes being spawned. Using "--jobs 1" or "-j1" when running oscapd-evaluate fixes these issues. My guess is that oscap processes talk to probes that don't belong to them and get the wrong results.
Comment 2 Matus Marhefka 2018-11-07 14:15:01 UTC 
This was worked around for openscap container and there are no other reports for this issue. If the issue is encountered in the future feel free to open a new bug.
Note You need to log in before you can comment on or make changes to this bug.