deploy.sh fails with /opt/health/Makefile:38: single-aptr] Error 1

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Output of deploy.sh contains the following error:

Running check non-default-hostname 
Running check eth0-ip 
Running check single-aptr 
make: *** [/opt/health/Makefile:38: single-aptr] Error 1

an Aria Automation 8.x upgrade can fail:

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

Aria Automation Upgrade fails with the error code LCMVRAVACONFIG590095 in Aria Suite Lifecycle

Error Code: LCMVRAVACONFIG590095
Failed to check VMware Aria Automation nodes health status. Ensure VMware Aria Automation node is up and services are running

a VCF Automation 9 upgrade can fail

Reviewing the upgrade script kubectl logs vcfa-upgrade-80-entrypoint-#####-execute-script-########## -n prelude shows:

2026-09-17 13:23:33 [DEBUG] SSH stderr: Warning: Permanently added 'vcfa.example.com' (ED25519) to the list of known hosts.
Welcome to VMware Aria Automation Appliance 8.18.1
+ echo 'Triggering graceful shutdown of all services ...'
+ /opt/scripts/deploy.sh --shutdown --quick
2026-09-17 13:23:33 [WARNING] SSH operation timed out after 1800s (attempt 3/3)
2026-09-17 13:23:33 [ERROR] SSH connection to vcfa.example.com failed after 3 attempts
2026-09-17 13:23:33 [ERROR] Remote command execution failed on vcfa.example.com with exit code 124
2026-09-17 13:23:33 [DEBUG] Command output: Warning: Permanently added 'vcfa.example.com' (ED25519) to the list of known hosts.
Welcome to VMware Aria Automation Appliance 8.18.1
+ echo 'Triggering graceful shutdown of all services ...'
+ /opt/scripts/deploy.sh --shutdown --quick
Warning: Permanently added 'vcfa.example.com' (ED25519) to the list of known hosts.
Welcome to VMware Aria Automation Appliance 8.18.1
+ echo 'Triggering graceful shutdown of all services ...'
+ /opt/scripts/deploy.sh --shutdown --quick
2026/09/17 13:23:33 ERROR : ########################## Script exited unexpectedly at line 1 with exit code 124
2026/09/17 13:23:33 INFO : ########################## Workflow stage:
2026/09/17 13:23:33 INFO : ########################## Calling get_message_count...
2026/09/17 13:23:33 INFO : ########################## get_message_count returned: 0, output: ''
2026/09/17 13:23:33 ERROR : ########################## get_message_count returned empty, defaulting to 0
2026/09/17 13:23:33 INFO : ########################## Existing messages: 0
2026/09/17 13:23:33 INFO : ########################## Creating generic error message
time="2026-09-17T13:23:34.313Z" level=info msg="sub-process exited" argo=true error="<nil>"
time="2026-09-17T13:23:34.314Z" level=info msg="no need to save parameter - on overlapping volume: /tmp/output.txt" argo=true
time="2026-09-17T13:23:34.314Z" level=info msg="no need to save parameter - on overlapping volume: /tmp/error.txt" argo=true
Error: exit status 124

/var/log/deploy.log on Aria Automation 8.x shows:

=========================
[2026-09-17 13:17:52.304+0000] Waiting for deploy healthcheck
=========================
+ timeout 300s bash -c wait_deploy_health
Running check eth0-ip
Running check non-default-hostname
Running check node-name
Running check single-aptr
make: *** [/opt/health/Makefile:38: single-aptr] Error 1
Running check nodes-ready
Running check nodes-count
Running check fips
make: Target 'deploy' not remade because of errors.

Environment

Aria Automation 8.x

Aria Automation Orchestrator 8.x

Cause

A health check is performed during service start 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. This issue can occur if there are duplicate PTR record entry for the appliance nodes and load balancer.

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 existing DNS are needs to be updated, Please Update the DNS server with following Document - Update the DNS assignment for VMware Aria Automation
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.
Also check if there are duplicate IP adderesses in the DNS table and correct it, by using an unused IP address.

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 )
X.X.X.X.in-addr.arpa. 3600 IN    PTR     vra-01.X.X.

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

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

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.