Bug 1655691 - [3.9] Fluentd pods failed to start after an update to 3.9.41 when deny_execmem=1 on nodes
Summary: [3.9] Fluentd pods failed to start after an update to 3.9.41 when deny_execme...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.9.0
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: ---
: 3.9.z
Assignee: Jeff Cantrill
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-03 17:17 UTC by Rich Megginson
Modified: 2022-03-13 16:19 UTC (History)
5 users (show)

Fixed In Version: openshift3/logging-fluentd:v3.9.53-1
Doc Type: Bug Fix
Doc Text:
Cause: rubygem ffi 1.9.25 reverted a patch which allowed it to work on systems with SELinux deny_execmem=1. Consequence: Fluentd crashes. Fix: The fix is to revert the patch reversion. Result: Fluentd does not crash when using SELinux deny_execmem=1.
Clone Of: 1628371
Environment:
Last Closed: 2019-01-10 08:55:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0028 0 None None None 2019-01-10 08:55:28 UTC

Comment 4 Anping Li 2018-12-19 02:32:13 UTC 
Move to verified as comment 2
Comment 6 errata-xmlrpc 2019-01-10 08:55:23 UTC 
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, 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/RHBA-2019:0028
Note You need to log in before you can comment on or make changes to this bug.