Red Hat Bugzilla – Bug 1298603
Memcached fails to start in ipv6 environment
Last modified: 2016-11-03 20:35:46 EDT
+++ This bug was initially created as a clone of Bug #1298401 +++
Description of problem:
Memcached fails to start in ipv6 environment:
overcloud-controller-0 systemd: Starting Cluster Controlled memcached...
overcloud-controller-0 memcached: Invalid port number: "fd00:fd00:2000:f816:3eff:feae:9393"failed to listen on TCP port 11211: Success
overcloud-controller-0 systemd: memcached.service: main process exited, code=exited, status=71/n/a
overcloud-controller-0 systemd: Unit memcached.service entered failed state.
Version-Release number of selected component (if applicable):
I'm doing the test following the instructions in:
and enabling pacemaker by passing an additional $THT/environments/puppet-pacemaker.yaml environment file
Steps to Reproduce:
1. Apply workarounds for BZ#1295986 and BZ#1297850
2. Deploy ipv6 enabled overcloud
systemd: Starting Cluster Controlled memcached...
memcached: Invalid port number: "fd00:fd00:2000:f816:3eff:feae:9393"failed to listen on TCP port 11211: Success
memcached gets started
[root@overcloud-controller-0 ~]# cat /etc/sysconfig/memcached
OPTIONS="-l fd00:fd00:fd00:2000:f816:3eff:feae:9393 -U 11211 -t 4 >> /var/log/memcached.log 2>&1"
--- Additional comment from Emilien Macchi on 2016-01-13 23:31:57 EST ---
Assigned to OPM because I think it's a bug in puppet-memcached. We're looking at it.
--- Additional comment from Marius Cornea on 2016-01-14 06:09:46 EST ---
The issue has been reported here:
and it appears to have been solved in release 1.4.25:
The version installed on my system is memcached-1.4.15-9.el7.x86_64
Effectively, OpenStack can't be deployed on RHEL 7.2 using ipv6.
The upstream patch applies cleanly to 1.4.15 and seems to work as expected.
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.