# \[WARNING\]: Could not match supplied host pattern, ignoring:

**URL:** <https://forum.ansible.com/t/warning-could-not-match-supplied-host-pattern-ignoring/36364>\
**Category:** AWX Project\
**Tags:** awx\
**Created:** [February 24, 2022, 11:38am UTC](https://forum.ansible.com/t/warning-could-not-match-supplied-host-pattern-ignoring/36364 "2022-02-24T11:38:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![K11](https://avatars.discourse-cdn.com/v4/letter/k/8dc957/32.png) [@K11](https://forum.ansible.com/u/K11)\
**Post date:** [February 24, 2022, 11:38am UTC](https://forum.ansible.com/t/warning-could-not-match-supplied-host-pattern-ignoring/36364/1 "2022-02-24T11:38:19Z")

</div>

Hey All

I am a complete newbie to this so do excuse me on this.  
Managed to set up Ansible AWX following this[guide](https://computingforgeeks.com/install-and-configure-ansible-awx-on-centos/)

Got Git integrated  
Created SSH Keys

All hosts added vi IP address and copied the SSH Keys as per the document  
Put the hosts in a test inventory  
I put this playbook in Git and found seen in my AWX instance

---

<div class="post-metadata">

**Author:** ![jowestco](https://avatars.discourse-cdn.com/v4/letter/j/85f322/32.png) [@jowestco](https://forum.ansible.com/u/jowestco)\
**Post date:** [March 2, 2022, 8:51pm UTC](https://forum.ansible.com/t/warning-could-not-match-supplied-host-pattern-ignoring/36364/2 "2022-03-02T20:51:50Z")

</div>

The line `hosts: UbuntuTest` is telling ansible that it should look into your inventory for a group (or a host) named UbuntuTest. The error you are getting is indicating that you have no such group or host within your inventory.

My recommendation would be to double check your awx inventory tied to your job template to see if has a group or host with that name. If not, add one and try again and see if it works.

Also, I would recommend changing your playbook to say `hosts: all` and then set a limit in the job template inside AWX. That way, if you wanted to have multiple job templates that pointed to different hosts they could all use the same playbook (applying the limit from the job template itself).

-John