Description of problem: Now there is no validation whether Gluster network using FQDN or not before gluster deployment. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The dependent bug is ON_QA, moving this bug too
Verified with gluster-ansible-features-1.0.4-3 with the following tests 1. Using IPs for hostnames and the deployment failed 2. Use the non-resolvable hostnames and also the deployment fails
*** Bug 1636373 has been marked as a duplicate of this bug. ***
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/RHEA-2019:1121
*** Bug 1636334 has been marked as a duplicate of this bug. ***