-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with AWX Callback and Host Matching Error #15166
Comments
hey @analissec are you able to reproduce this on the latest version of awx? |
I am running v24.4.0 and am having this same issue. $ curl -k -H 'Content-Type: application/json' -d '{"host_config_key": "test-awx-callback"}' https://[AWX Server]/api/v2/job_templates/15/callback/
{"msg":"No matching host could be found!"} Like @analissec, I, too, am importing hosts from Red Hat Satellite using the Satellite inventory plugin. However, I can successfully run a job template directly against the client without issue. |
@analissec @tonythell are ya'll using the It can cause the headers listed in |
@chrismeyersfsu The |
https://[AWX Server]/api/v2/job_templates/15/callback/ <-- issue a GET request with
|
Could you please clarify the |
AWX setting |
Thank you for your help @chrismeyersfsu. I found that my issue wasn't an actual AWX issue. I'm running awx-operator in a single-node k3s cluster and found that I was missing an additional Traefik config to allow Essentially, I followed the instructions found here (https://github.com/kurokobo/awx-on-k3s/blob/main/tips/troubleshooting.md#provisioning-callback-does-not-work). After that change, provisioning callbacks started working for me. |
Please confirm the following
security@ansible.com
instead.)Bug Summary
I'm encountering a problem with the AWX callback command and host matching. When I run the Ansible callback command:
/usr/bin/curl -k --data "host_config_key=test-ansible-host" https://[AWX_SERVER]/api/v2/job_templates/1527/callback/
I receive the following response:
{"msg":"No matching host could be found!"}
Here's some additional context:
Any insights or assistance on resolving this issue would be greatly appreciated!
AWX version
22.3.0
Select the relevant components
Installation method
N/A
Modifications
no
Ansible version
No response
Operating system
No response
Web browser
No response
Steps to reproduce
Expected results
Upon running the Ansible callback command, the system should successfully identify and match the host in the AWX dynamic inventory. The command should then trigger the specified job template on the identified host without encountering any errors. Additionally, the callback should execute any associated tasks or actions as intended.
Actual results
Upon running the Ansible callback command, the system fails to identify and match the host specified in the AWX dynamic inventory. Instead, it returns an error message stating "No matching host could be found!" despite the host being present in the inventory.
Additional information
No response
The text was updated successfully, but these errors were encountered: