Info: The base_orch repo is fixed: Apache returns 200 OK , and all 10 B servers say base_orch OK . Next, re-run the MOTD update for the B servers only. Run it from the folder you're already in ( /etc/ansible/tricycle_ansible_master ): ansible-playbook site.yml -i inventories/ref_rbb/hosts_ref_rbb.yml --ask-vault-pass -u dbv6admin --tags tcpwrappers --limit 'rbb-ref-b-*:!rbb-ref-b-vlim06' Then check the result on one server: ssh rbb-ref-b-vlim02 cat /etc/motd If the run ends with failed=0 and the MOTD shows the new kernel ( 553.184.1 ), the MOTD step is done. If anything fails, send me the PLAY RECAP. ====================================================== The files are there, but one folder level too deep, so the servers still can't find them. What happened: your update/ folder already had a base_orch_yum_repo-1.1.0 folder inside it. Moving it created this: /var/www/html/base_orch_yum_repo-1.1.0/base_orch_yum_repo-1.1.0/ <- the RPMs are here But the servers...
INFO: Good news: the B side uses os-patch , the same as the A side. inventories/ref_rbb/hosts_ref_rbb.yml sets os_patch_url: "http://{{ ansible_address }}/os-patch/" . os_patch.yml builds the patch repo from that ( baseurl: "{{ os_patch_url }}" ). So the playbook creates the patch repo pointing at os-patch , which is the folder you just fixed. The rhel-8-baseos address only appears in the eden_rbb inventories, which aren't part of this run. One last check. {{ ansible_address }} is the master's IP, filled in for each server. Earlier, vlim04 and vlim05 had the A master's address ( .61 ) in their old rbb-base file. Confirm every B server will use the B master ( .62 ): ansible 'rbb-ref-b-*' -i inventories/ref_rbb/hosts_ref_rbb.yml --ask-vault-pass -m debug -a "msg={{ os_patch_url }}" This doesn't log in to the servers. It just prints the address each one will use. All of them show http://10.212.176.62/os-patch/ : run Step ...