Bug 1980074 - Provisioning Azure fails in Kickstart default finish when using Ansible Callback
Summary: Provisioning Azure fails in Kickstart default finish when using Ansible Callback
Keywords:
Status: CLOSED DUPLICATE of bug 1956124
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning Templates
Version: 6.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Ondrej Gajdusek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-07 17:20 UTC by Paul Armstrong
Modified: 2021-12-01 13:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-12-01 13:29:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Paul Armstrong 2021-07-07 17:20:56 UTC
Description of problem:
Provisioning Azure fails in Kickstart default finish when using Ansible Callback - the script /root/ansible_provisioning_call.sh is not executable

Version-Release number of selected component (if applicable):
6.9.3

How reproducible:
Always

Steps to Reproduce:
1. Configure Capsule and Tower for callback and Azure provisioning
2. Configure Host group for callback
3. Deploy new system to azure 

Actual results:
Kickstart default finish fails with permission denied on /root/ansible_provisioning_call.sh

Expected results:
Success

Additional info:
Modifying the section to the example below corrects the issue.

<% if host_param_true?('ansible_tower_provisioning') -%>
<%= save_to_file('/root/ansible_provisioning_call.sh', snippet('ansible_tower_callback_script')) %>
sudo chmod +x /root/ansible_provisioning_call.sh
sudo /root/ansible_provisioning_call.sh
<% end -%>

Comment 1 Tomer Brisker 2021-12-01 13:29:43 UTC

*** This bug has been marked as a duplicate of bug 1956124 ***


Note You need to log in before you can comment on or make changes to this bug.