Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1628407 - [3.11] Fluentd pods failed to start after an update to 3.9.41 when deny_execmem=1 on nodes
[3.11] Fluentd pods failed to start after an update to 3.9.41 when deny_execm...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging (Show other bugs)
3.11.0
All Linux
unspecified Severity urgent
: ---
: 3.11.0
Assigned To: Jeff Cantrill
Anping Li
:
Depends On: 1628371 1628405
Blocks:
  Show dependency treegraph
 
Reported: 2018-09-12 19:24 EDT by Rich Megginson
Modified: 2018-10-11 03:26 EDT (History)
5 users (show)

See Also:
Fixed In Version: openshift3/ose-logging-fluentd:v3.11.3-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
Story Points: ---
Clone Of: 1628405
Environment:
Last Closed: 2018-10-11 03:25:56 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2652 None None None 2018-10-11 03:26 EDT

  None (edit)
Comment 1 Rich Megginson 2018-09-12 19:29:05 EDT
build has been tagged into rhaos-3.11-rhel-7-candidate
Comment 4 Anping Li 2018-09-17 02:31:56 EDT
The fluend pod can be started when deny_execmem is enabled with openshift3/ose-logging-fluentd/images/v3.11.6-1
Comment 6 errata-xmlrpc 2018-10-11 03:25:56 EDT
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-2018:2652

Note You need to log in before you can comment on or make changes to this bug.