vRA Upgrade fails with Error: Invalid kube-config file. No configuration found

Products

• VMware Aria Suite

Issue/Introduction

• To ensure the vRA is upgraded successfully.

Symptoms:

• kubelet Service is in stopped state
• vracli get nodes returns:

The connection to the server localhost:8080 was refused - did you specify the right host or port

• deploy.sh fails with exit code 1.
• The vRA postupdate.log shows the below error : 

Running check single-aptr

make: *** [/opt/health/Makefile:38: single-aptr] Error 1

make: Target 'firstboot' not remade because of errors.

Running check eth0-ip

Running check non-default-hostname

Running check single-aptr

make: *** [/opt/health/Makefile:38: single-aptr] Error 1

make: Target 'firstboot' not remade because of errors.

Error setting up Kubernetes. Retrying.

2023-04-18 19:34:30Z Script /etc/bootstrap/postupdate.d/03-10-setup-k8s.sh failed, error status 1

Environment

VMware vRealize Automation 8.x

Cause

• This is caused by missing PTR records for the vRA appliances. 
• vRA requires a valid PTR dns record to work.

Resolution

Adding the missing PTR record should resolve the issue and the upgrade should be successful.

Steps: 

1. Login to the vRA appliance as root.
2. Run the following commands to confirm the PTR Record exists on the vRA appliances from CLI: 

host $( iface-ip eth0 ) # if this returns a single line, but
/usr/bin/dig +noall +answer -x $( iface-ip eth0 ) # this contains no ANSWER section, and
/usr/bin/dig +noall +answer +noedns -x $( iface-ip eth0 ) # this also returns the corrrect line, then EDNS is probably broken.

3. if none of the above commands returns an answer successfully, then set up a PTR record for the vRA IP address in the DNS.
4. Retry the upgrade.