Bug 1284133 - Redis fails to restart in HA setup due to SELinux
Redis fails to restart in HA setup due to SELinux
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-selinux (Show other bugs)
8.0 (Liberty)
Unspecified Unspecified
high Severity high
: beta
: 8.0 (Liberty)
Assigned To: Ryan Hallisey
Marius Cornea
: AutomationBlocker
Depends On:
Blocks: 1284436
  Show dependency treegraph
Reported: 2015-11-20 18:56 EST by Marius Cornea
Modified: 2016-04-07 17:13 EDT (History)
9 users (show)

See Also:
Fixed In Version: openstack-selinux-0.6.46-1.el7ost
Doc Type: Bug Fix
Doc Text:
Previously, SELinux prevented redis from connecting to its own port, resulting in redis failing at restart. With this update, redis has the permission to connect to the 'redis' labeled port. As a result, redis runs properly and resource restart is successful.
Story Points: ---
Clone Of:
: 1284436 (view as bug list)
Last Closed: 2016-04-07 17:13:15 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Marius Cornea 2015-11-20 18:56:15 EST
Description of problem:
Redis fails to restart in HA setup with 3 controllers due to SELinux 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Deploy environment with 3 controllers
2. On one of the controllers run pcs resource restart redis-master
3. Watch the /var/log/audit/audit.log

Actual results:
type=AVC msg=audit(1448063445.338:2728): avc:  denied  { name_connect } for  pid=30202 comm="redis-server" dest=6379 scontext=system_u:system_r:redis_t:s0 tcontext=system_u:object_r:redis_port_t:s0 tclass=tcp_socket

The resouce fails to restart:
Error: Could not complete shutdown of redis-master, 1 resources remaining
Error performing operation: Timer expired

Expected results:
The resource is restarted.

Additional info:
Comment 4 Marius Cornea 2016-02-02 06:09:54 EST
Comment 5 errata-xmlrpc 2016-04-07 17:13:15 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.


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