After upgrading to any version of VMware Aria Automation / Orchestrator, deploy.sh fails with /opt/health/Makefile:38: single-aptr] Error 1

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

• The Upgrade summary report will report similar to the below excerpt:

Upgrade Report

Summary -------------------------------------------------------------------------------------

Date: <Date & timestamp>
Duration: 41 minutes
Result: Upgrade Failure

Description: Upgrade failed and left the system in non-working state. Check the error report below to correct the problem. Once addressed, you can continue the upgrade by running 'vracli upgrade exec --resume'

Reference

-------------------------------------------------------------------------------------

Logs: /var/log/vmware/prelude
Backup: /data/restorepoint
Runtime: /var/vmware/prelude/upgrade

Some directories might not exist.

Errors
-------------------------------------------------------------------------------------
[ERROR][2022-05-12 15:25:01][<Appliance FQDN>] Upgrade failed on this node. Monitoring on this node will be deactivated.

• The /var/log/bootstrap/postupdate.log contains the following message indicating a failure during reverse lookup against the hostname:

  + /etc/bootstrap/firstboot.d/02-setup-kubernetes 
  + export -f wait_health 
  + timeout 300s bash -c wait_health 
  Running check non-default-hostname 
  Running check eth0-ip 
  Running check single-aptr 
  make: *** [/opt/health/Makefile:38: single-aptr] Error 1

Cause

A health check is performed during upgrade for both forward and reverse DNS lookups. This error can occur when the PTR record is missing in DNS for the Aria Automation or Aria Automation Orchestrator appliances.

Resolution

To resolve the issue, confirm the reverse lookup PTR record is created in DNS for the Aria Automation or Aria Orchestrator hostname.

VMware Aria Automation/VMware Aria Automation Orchestrator 8.7 and later use the dig command instead of host in order to validate the DNS service in the script /opt/health/Makefile "single-aptr".

• Version 8.6.2 and below

single-aptr: eth0-ip 
$(begin_check) 
echo Check the ip address if eth0 resolves only to a single hostname 
[ 1 -eq $$( host $$( host $$( iface-ip eth0 ) | wc -l ) ] $(end_check)

• Version 8.7 onwards

single-aptr: eth0-ip
 $(begin_check) 
echo Check the ip address if eth0 resolves only to a single hostname [ 1 -eq $$(/usr/bin/dig +noall +answer -x $$( iface-ip eth0 ) | grep "PTR" | wc - l ) ] 
$(end_check)

Therefore, for these versions it is recommended to run the following commands:

/usr/bin/dig +noall +answer +nocookie -x $( iface-ip eth0 )
/usr/bin/dig +noall +answer +noedns -x $( iface-ip eth0 )
/usr/bin/dig +noall +answer -x $( iface-ip eth0 )

Scenarios:

• If the answers are blank, it is required to create a PTR record.

• If only the last command succeeds and a Microsoft AD DNS server is being used, please review this Microsoft Article Some DNS name queries are unsuccessful after you deploy a Windows-based DNS server.

Note

Successful execution returns the associated PTR reverse lookup record similar to the below output.

root@vra-01 [ ~ ]# /usr/bin/dig +noall +answer +nocookie -x $( iface-ip eth0 )
21.110.168.192.in-addr.arpa. 3600 IN    PTR     vra-01.vcloud.local.

root@vra-01 [ ~ ]# /usr/bin/dig +noall +answer +noedns -x $( iface-ip eth0 )
21.110.168.192.in-addr.arpa. 3600 IN    PTR     vra-01.vcloud.local.

root@vra-01 [ ~ ]# /usr/bin/dig +noall +answer -x $( iface-ip eth0 )
21.110.168.192.in-addr.arpa. 3600 IN    PTR     vra-01.vcloud.local.

Additional Information

See Troubleshooting VMware Aria Automation 8.x (formerly vRealize Automation 8.x) upgrades and Troubleshooting VMware Aria Automation cloud proxies and On-Premises appliance deployments for additional troubleshooting guidance.