Overview of the Issue
All of the example scripts use the $hostname variable defined in env.sh as the output of hostname -f when defining host:port values. An exception to that, however, was the vtadmin-up.sh script which used a combination of no host, and localhost. The no host case could end up using IPV6 on some hosts, and localhost could resolve to anything (typically IPV4 127.0.0.1).
This means that the behavior is undefined, as well as being non-uniform. An example of problems this could lead to was discussed in the Vitess slack where the web app is using IPV4 and the API server IPV6 and the two cannot talk.
Reproduction Steps
N/A
Binary Version
Operating System and Environment details
Log Fragments
Overview of the Issue
All of the example scripts use the
$hostnamevariable defined inenv.shas the output ofhostname -fwhen defining host:port values. An exception to that, however, was thevtadmin-up.shscript which used a combination of no host, and localhost. The no host case could end up using IPV6 on some hosts, and localhost could resolve to anything (typically IPV4 127.0.0.1).This means that the behavior is undefined, as well as being non-uniform. An example of problems this could lead to was discussed in the Vitess slack where the web app is using IPV4 and the API server IPV6 and the two cannot talk.
Reproduction Steps
N/A
Binary Version
Operating System and Environment details
Log Fragments