Bug 1654506 - Overcloud deployment failed because the ping tests doesn't work due to network security policy
Summary: Overcloud deployment failed because the ping tests doesn't work due to networ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 13.0 (Queens)
Hardware: All
OS: Unspecified
medium
medium
Target Milestone: ---
: 13.0 (Queens)
Assignee: Emilien Macchi
QA Contact: Sasha Smolyak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-28 22:23 UTC by Cristian Muresanu
Modified: 2021-12-10 18:28 UTC (History)
5 users (show)

Fixed In Version: openstack-tripleo-heat-templates-8.2.0-22.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-30 17:27:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1805703 0 None None None 2018-11-28 22:32:31 UTC
OpenStack gerrit 644299 0 None MERGED Optional ICMP validation of controllers and gateways 2021-02-20 20:01:40 UTC
Red Hat Issue Tracker OSP-11758 0 None None None 2021-12-10 18:28:49 UTC
Red Hat Product Errata RHBA-2019:0939 0 None None None 2019-04-30 17:27:54 UTC

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
Note You need to log in before you can comment on or make changes to this bug.