Bug 1654506

Summary:	Overcloud deployment failed because the ping tests doesn't work due to network security policy
Product:	Red Hat OpenStack	Reporter:	Cristian Muresanu <cmuresan>
Component:	openstack-tripleo-heat-templates	Assignee:	Emilien Macchi <emacchi>
Status:	CLOSED ERRATA	QA Contact:	Sasha Smolyak <ssmolyak>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	13.0 (Queens)	CC:	akaris, emacchi, mburns, mmagr, ramishra
Target Milestone:	---	Keywords:	Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	All
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-8.2.0-22.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-04-30 17:27:36 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:

Description Cristian Muresanu 2018-11-28 22:23:47 UTC

Description of problem:
OpenStack Director uses ICMP packets during deployment to test if overcloud nodes and the gateway are up. This may be an issue in specific environments where ICMP packets are filtered by (transparent) firewalls or the gateway.

Is it possible to disable all those ping tests or change them to actual tests which would check service reachability? For example telnet or netcat to verify if specific services are listening?

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
Overcloud deployment failing

Expected results:
Overcloud deployment OK

Additional info:

 Workaround: https://access.redhat.com/solutions/3719351

Comment 8 errata-xmlrpc 2019-04-30 17:27:36 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-2019:0939