Actions
Feature #38219
closedAAP 2.5 support in Ansible Callback
Status:
Closed
Priority:
Normal
Assignee:
Category:
Unattended installations
Target version:
Difficulty:
Triaged:
Yes
Description
Our kickstart template calls the ansible_provisioning_callback snippet
That ansible_provisioning_callback snippet further calls ansible_tower_callback_service and ansible_tower_callback_script snippets to setup the ansible callback on the deployed systems and perform the callback.
In both of those snippets, we have the `/api/v2/job_templates/` endpoint hardcoded for all satellite\foreman versions.
This used to work fine till AAP 2.4. With AAP 2.5, a gateway was introduced and hence the `/api/v2` endpoints are now `/api/controller/v2` and this will result in failures to complete the ansible callback when end-user uses AAP 2.5.
Updated by The Foreman Bot about 2 months ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/10445 added
Updated by Nofar Alfassi 19 days ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman|2a81d51f7793f82bc5687952789e716b278083ff.
Updated by Ewoud Kohl van Wijngaarden 19 days ago
- Tracker changed from Bug to Feature
- Subject changed from Ansible Callback does not work when using AAP 2.5 to AAP 2.5 support in Ansible Callback
Updated by The Foreman Bot 19 days ago
- Pull request https://github.com/theforeman/foreman/pull/10486 added
Updated by Ewoud Kohl van Wijngaarden 17 days ago
- Category set to Unattended installations
- Triaged changed from No to Yes
- Fixed in Releases deleted (
3.15.0)
Updated by The Foreman Bot 11 days ago
- Pull request https://github.com/theforeman/foreman/pull/10493 added
Updated by Nofar Alfassi 11 days ago
- Related to Bug #38319: Fix Ansible Tower FQDN migration added
Updated by Nofar Alfassi 11 days ago
- Pull request deleted (
https://github.com/theforeman/foreman/pull/10493)
Actions