enderm
commented
3 years ago you didn't provide enough information here. Please share at least the contents of your ansible vars settings, and information about how you created the k8s environment.
You are asking whether you need to open port 22 manually on "that server", which, I assume means the jump VM. I agree that a closed network port is a likely cause here. You are free to open that port manually (or programmatically) and see if that helps.
There are also ways to set up the viya4-iac-* and viya4-deployment parameters so that you do not need to do that extra step.
Some points to check:
If you used one of the viya4-iac-* projects to create your k8s cluster, double-check that you set the correct CIDR range) for client access (https://github.com/sassoftware/viya4-iac-azure/blob/main/docs/CONFIG-VARS.md#admin-access). You can verify that by trying to log into your jump host by using ssh from the same client where your are running your ansible playbook.
Once the ssh login works, make sure that you specified the correct ssh key for your ansible play. It should be same one you specified as "ssh_public_key" when you created your cluster (https://github.com/sassoftware/viya4-iac-azure/blob/main/docs/CONFIG-VARS.md#required-variables), and also the one you used when trying to login to your jump VM via ssh (the JUMP_SVR_PRIVATE_KEY setting: https://github.com/sassoftware/viya4-deployment/blob/main/docs/CONFIG-VARS.md#jump-server)
venu-ibex-9
I am getting this below issue , do i need to open port 22 manually on that server?
Failed to connect to the host via ssh: ssh: connect to host 50.16.214.175 port 22: Operation timed out
TASK [jump-server : jump-server - lookup groups] *** fatal: [localhost -> 50.16.214.175]: FAILED! => {"msg": "Timeout (12s) waiting for privilege escalation prompt: "}
PLAY RECAP ***** localhost : ok=21 changed=3 unreachable=0 failed=1 skipped=31 rescued=0 ignored=0