name resolution fails with custom DNS #21
Description
In what area(s)?
/area azlustre
Expected Behavior
OSS and RBH try to register to MDS by resolving the hostname (ie. default = lustre).
Actual Behavior
In an environment with custom DNS without autoregistration the name resolution of lustre does not work. The OSS and RBH nodes fail to resolve MDS and timeout without completing install. Adding an /etc/hosts entry for lustre on each node was a workaround.
Steps to Reproduce the Problem
Run setup on a VNET with a custom DNS that doesn't use autoregistration.