Bug 1539980

Summary:	[OSP12] Undercloud installer fails with ERROR: epmd error
Product:	Red Hat OpenStack	Reporter:	Benjamin Schmaus <bschmaus>
Component:	instack-undercloud	Assignee:	Michele Baldessari <michele>
Status:	CLOSED ERRATA	QA Contact:	Arik Chernetsky <achernet>
Severity:	high	Docs Contact:
Priority:	medium
Version:	12.0 (Pike)	CC:	amcleod, apevec, bschmaus, jeckersb, lhh, mburns, michele, mkrcmari, pkomarov, plemenko, srevivo
Target Milestone:	z4	Keywords:	Triaged, ZStream
Target Release:	12.0 (Pike)
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	instack-undercloud-7.4.12-3.el7ost	Doc Type:	Bug Fix
Doc Text:	Previously, undercloud installations with SSL enabled could fail with the error `ERROR: epmd error`. This failure occurred because the VIP that matched the hostname was configured by keepalived after rabbitmq. With this update, keepalived is configured before rabbitmq, and undercloud installation succeeds.	Story Points:	---
Clone Of:
Clones:	1608173 (view as bug list)		Environment:
Last Closed:	2018-12-05 18:52:40 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:	1608173

Description Benjamin Schmaus 2018-01-30 00:44:35 UTC

Description of problem:
When running a new OSP 12 undercloud installation, the undercloud installer fails. Running `systemctl list-units | grep fail` reveals that the epmd.socket and rabbitmq-server service has failed to start.

Restarting the rabbitmq-server service appears to resolve the issue and re-running the undercloud installer then completes without error.

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

How reproducible:


Steps to Reproduce:
1.Fresh install of undercloud
2.
3.

Actual results:


Expected results:


Additional info:

Comment 4 Peter Lemenkov 2018-02-19 15:00:42 UTC

I've looked at the systemd logs and found that both epmd.socket and epmd.0.0.socket are enabled. Looks like someone enabled it accidentally.

Could you please just type

# systemctl disable epmd.socket

it should fix that issue.

Comment 22 errata-xmlrpc 2018-12-05 18:52:40 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://access.redhat.com/errata/RHBA-2018:3789