cancel
Showing results for 
Search instead for 
Did you mean: 
87924906
Mission Specialist
Mission Specialist
  • 438 Views

Issue using Provisioning Callback during host provisioning

Jump to solution

I am trying to use the provisioning callback feature in Ansible Automation Platform. I created a Job Template with a Provisioning Callback URL and a Host Config Key. The idea is that during host provisioning, the host should call this URL to request a configuration update. I set the callback URL in the Job Template and configured it in the host group, but it is not working as expected. Has anyone else tried this setup or run into the same issue?

Labels (2)
1 Solution

Accepted Solutions
87924906
Mission Specialist
Mission Specialist
  • 334 Views

After updating the "ansible_tower_fqdn" global parameter in satellite to use the hostname instead of the URL, it worked.

Thank you @Chetan_Tiwary_ for your response

View solution in original post

6 Replies
Chetan_Tiwary_
Community Manager
Community Manager
  • 407 Views

@87924906 what exactly are you getting there ? when doing the curl are you getting : No matching host could be found error ? are you using any proxy server ? 

0 Kudos
87924906
Mission Specialist
Mission Specialist
  • 380 Views

the inventory sync with satellite takes beyond the timeout for the callback, so nothing happens. Receiving callback timeout.we have to run it ad-hoc, rather than callback

Chetan_Tiwary_
Community Manager
Community Manager
  • 360 Views

@87924906 did you find anything in the logs ? 

I know that when Automation controller  calls the provisioning callback API, first, it needs to confirm the host is in its inventory. If any of your inventory sources have "Update on Launch" enabled, the controller will run a sync first.

Then, it will perform two DNS lookups. It does a reverse DNS lookup on the host that called the API. That's usually based on the REMOTE_HOST_HEADER. After that, it does a regular DNS lookup for every host listed in its inventory. It's basically trying to match the two to be sure.

I am not sure what exaclty is causing your issue. Did you happen to raise a support case with Ansible support in RH ?

@Waldirio any idea about this ?

0 Kudos
87924906
Mission Specialist
Mission Specialist
  • 335 Views

After updating the "ansible_tower_fqdn" global parameter in satellite to use the hostname instead of the URL, it worked.

Thank you @Chetan_Tiwary_ for your response

Chetan_Tiwary_
Community Manager
Community Manager
  • 328 Views
87924906
Mission Specialist
Mission Specialist
  • 326 Views

Thank you! We are using satellite Version 6.15

Join the discussion
You must log in to join this conversation.