Aria Automation Orchestrator service is unreachable after a fresh installation

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

• You just deployed Aria Automation Orchestrator
• Attempt to list pods using command kubectl -n prelude get pods  fails with an error:

The connection to the server vra-k8s.local:6443 was refused - did you specify the right host or port?

• In /var/log/bootstrap/firstboot.log you see entries similar to:

[preflight] Running pre-flight checks
       [WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/
       [WARNING Hostname]: hostname "vro-01" could not be reached
       [WARNING Hostname]: hostname "vro-01": lookup vro-01 on 192.168.xxx.xx no such host
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
+ kubeadm init phase certs all --config /tmp/kubeadm.config
W0601 12:32:45.566214   2889 utils.go:69] The recommended value for "resolvConf" in "KubeletConfiguration" is: /run/systemd/resolve/resolv.conf; the provided value is: /etc/resolv.conf
...
...
Wrote static etcd manifest to /etc/kubernetes/manifests/etcd.yaml
+ /opt/scripts/wait-k8s-up -t 300 kube-apiserver
Waiting for kube-apiserver timed out: The connection to the server vra-k8s.local:6443 was refused - did you specify the right host or port?
+ res=1
+ echo 'Script /etc/bootstrap/firstboot.d/02-setup-kubernetes failed, error status 1'
Script /etc/bootstrap/firstboot.d/02-setup-kubernetes failed, error status 1

Cause

This issue occurs due to vami.hostname property entered as short name.

Resolution

Redeploy the appliance from OVA and specify a fully qualified domain name (FQDN) for the hostname. For more information, see Download and Deploy the vRealize Orchestrator Appliance.