Bug #30093
Updated by Ondřej Ezr over 3 years ago
when running playbook on 298 hosts, I see warnings in the playbook output: [WARNING]: Could not match supplied host pattern, ignoring: <some_hostname>
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1825145
*Description of problem:*
When running remediation playbook on 298 hosts, I see lots of warnings in the playbook output:
[WARNING]: Could not match supplied host pattern, ignoring: <some_hostname>
*Version-Release number of selected component (if applicable):*
satellite-6.7.0-7.el7sat.noarch
*How reproducible:*
always
*Steps to Reproduce:*
1. Schedule a remediation playbook on >100 hosts via FiFi. I'll attach mine playbook as it looks like FiFi/Receptor are not important to reproduce
2. Check output of individual host on Satellite: Monitor -> Jobs -> Ansible - run playbook... -> some host
*Actual results:*
There is lots of these warnings:
1:
[WARNING]: Could not match supplied host pattern, ignoring:
2:
gprfc016-01container20.contperf67.local
3:
[WARNING]: Could not match supplied host pattern, ignoring:
4:
gprfc016-01container208.contperf67.local
5:
[WARNING]: Could not match supplied host pattern, ignoring:
6:
gprfc016-01container209.contperf67.local
[...]
*Expected results:*
No warnings
*Additional info:*
Adam Ruzicka explained me reason for these: Foreman obtains a playbook for all the hosts at once. These hosts are all namely listed in "hosts:" directive of the playbook. Then Foreman starts the same playbook multiple times for subsets of 100 hosts - that makes ansible to report 298 - 100 hosts are missing in the inventory and print the warning.