From 7bf8d77207b24ef5a6edfdfa44f6a97fd209b45d Mon Sep 17 00:00:00 2001 From: Luca Miccini Date: Mon, 1 Jun 2020 09:28:03 +0200 Subject: [PATCH] Ensure net.ipv6.conf.lo.disable_ipv6=0 Along the same lines as https://review.opendev.org/#/c/580460/. Currently, the Erlang Port Mapper Daemon requires that the loopback interface supports IPv6 in order to initialize properly. Without that, rabbitmq-server cannot start and deployment fails at step 2. Until the startup behaviour of epmd is amended, do not disable inet6 support on loopback device to workaround the problem. Change-Id: Ia747103aca99f3f45d7705248c6c1ef19aa93d71 --- deployment/kernel/kernel-baremetal-ansible.yaml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/deployment/kernel/kernel-baremetal-ansible.yaml b/deployment/kernel/kernel-baremetal-ansible.yaml index 4a654f735f..9b9c4f042e 100644 --- a/deployment/kernel/kernel-baremetal-ansible.yaml +++ b/deployment/kernel/kernel-baremetal-ansible.yaml @@ -162,6 +162,8 @@ outputs: value: {get_param: KernelDisableIPv6} net.ipv6.conf.all.disable_ipv6: value: {get_param: KernelDisableIPv6} + net.ipv6.conf.lo.disable_ipv6: + value: 0 net.ipv4.ip_forward: value: {get_param: KernelIpForward} net.ipv4.ip_nonlocal_bind: