Bug 1263696

Summary: Memcached not built with SASL support
Product: Red Hat Enterprise Linux 7 Reporter: Yanis Guenane <yguenane>
Component: memcachedAssignee: Miroslav Lichvar <mlichvar>
Status: CLOSED ERRATA QA Contact: Leos Pol <lpol>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: hbrock, jscotka, lars, lmiksik, markmc, ovasik, srevivo
Target Milestone: pre-dev-freeze   
Target Release: 7.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: memcached-1.4.15-10.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1304473 (view as bug list) Environment:
Last Closed: 2016-11-04 00:35:27 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:
Bug Depends On:    
Bug Blocks: 1252087, 1304473, 1304493    

Description Yanis Guenane 2015-09-16 12:36:20 UTC 
Description of problem:

Currently memcached in base is not build with SASL support preventing to secure the memcached instance.


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

memcached-1.4.15-9.el7.x86_64


How reproducible:

always


Steps to Reproduce:
1. Spawn a C7 node
2. yum install memcached
3. vi /etc/sysconfig/memcached (add '-S' in OPTIONS="")
4. start memcached 

Actual results:

Service fails to start with error message :

memcached[18804]: This server is not built with SASL support.


Expected results:

Service should start manually

Additional info:
Comment 1 Lars Kellogg-Stedman 2015-09-16 13:18:40 UTC 
Should this be against RHEL rather than RDO?  That's where the memcache package lives.
Comment 2 Hugh Brock 2016-02-03 17:11:57 UTC 
We'll need this package rebuilt for secure memcached support in RHELOSP 8.
Comment 13 errata-xmlrpc 2016-11-04 00:35:27 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://rhn.redhat.com/errata/RHBA-2016-2213.html