Deploying telegraf agents fails with message failed to connect to salt master

Products

• VMware Aria Operations 8.x
• VMware Aria Operations (formerly vRealize Operations) 8.x

Issue/Introduction

Deploying telegraf agents fails when there is an existing salt installation on the VM 

Port 4505, 4506, 443 of CP can be reached from endpoint VM. But deploying telegraf agent still fails with "failed to connect to salt Master"

 

ucp-firstboot Log shows the following:

INFO - config-utils - data: {'status': 'FAILED', 'totalstages': 17, 'currentstage': 14, 'action': 'install', 'job': 'install', 'data': [{'stage': '14', 'status': 'FAILED', 'message': 'Failed to Connect 
to Salt Master. null.Verify Agent installation log for more details.'}], 'vc_uuid': 'xxxxx', 'vm_mor': 'vm-20313', 'requestId': '797a244a-9c4f-45a1-9102-da57e482ca73', 'ts': 1737749752}
INFO - config-utils - Sent metrics to the path https:/vrops/arc/control. resp = 202
NFO - config-utils - stage_status: FAILED, stage_mesg: ['install', 'reinstall', '14', 'FAILED', 'Failed to Connect to Salt Master. null. Verify Agent installation log for more details.']

Environment

Aria Operations 8.x

Cause

 The internal ports "tcp_pub_port" and "tcp_pull_port" configured on the salt minion are the same for both instances of salt configuration, only one instance can be using the ports at a time. 

Resolution

To resolve change the configuration of the non aria operations salt minion. By default, the salt-minion configuration will be in /etc/salt/minion 

Modify the following ports from their default values. 

 "tcp_pub_port" Default: 4510

 "tcp_pull_port" Default: 4511