Plugins » Ansible

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1868800

Description of problem:
When trying to install the cloud connector on the Satellite with multiple external Capsule servers, it is possible that the Satellite's host profile is configured in such a way that a external Capsule will be selected to run the job opposed to the Satellite server. This will result in a failure of the installation due to the lookup template used in the /usr/share/ansible/roles/project-receptor.satellite_receptor_installer/templates/receptor.conf.j2:
node_id={{ lookup('file', receptor_config_dir+'/rh_'+sat_account_id+'/uuid') }}

as the lookup module is only used for local files and not run on the remote server.

Version-Release number of selected component (if applicable):
6.7.2

How reproducible:
Everytime

Steps to Reproduce:
1. Get to the step before running the cloud connector playbook
2. Ensure your Satellite host profile is configured in a way that the algorithm used to determine the execution capsule (https://access.redhat.com/documentation/en-us/red_hat_satellite/6.7/html-single/managing_hosts/index#sect-Managing_Hosts-Choosing_a_Satellite_Capsule_for_Remote_Execution) will not be the Satellite server, but a external Capsule
3.

Actual results:
Creation of the '/etc/receptor/rh_*/receptor.conf failes due to the missing uuid file on the external capsule

Expected results:
The playbook should ensure that the playbook can only be executed on the Satellite server from the Satellite server

Additional info: