Troubleshooting CLI Issues

Here’s a list of various reasons your CLI might fail.

Networking issues

If your nodes are deployed on an internal network, (eg an node deployed on any of the following: AWS or Azure private network, OpenStack tenant network, VMware NSX tenant/private network) you must specify the internal IP of the node as a parameter to the CLI.

If in doubt, run ifconfig on the node, then see what IP address gets reported and specify that IP. Your external IP will not get reported by ifconfig as that is configured external to the node.

PMK Tenant or Region Different From Default

Current version of the CLI assumes RegionOne as region and service as tenant for your PMK environment. If you wish to override these (eg because you wish to create a cluster in a different tenant), you can do that by

Also see Node Failure Issues for various reasons why your node might run into failures.