In case of Exhibitor starting up with a static backend configured, if the IP returned by the ip-detect script is not contained in the configured master list in config.yaml, the cluster will fail to come up. This is because the IP returned by ip-detect is used for the Exhibitor --hostname command line parameter that identifies the given Exhibitor instance. If an Exhibitor instance wrongly identifies as being different from the the expected master list it will not be included once the cluster transitions to the multi-node Exhibitor config.
In case of a static backend we know beforehand which Exhibitor instances identified by master IPs are expected to start up, therefore we can check if the ip-detect invocation caused any problems.
The ticket tracks the creation of a check in the bootstrap code that terminates the bootstrap if the ip-detect script returns an unexpected IP address.