Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1902314 - [RFE] Introduce check-only or dry-run feature for any kind of Ansible based job execution from Satellite 6
Summary: [RFE] Introduce check-only or dry-run feature for any kind of Ansible based j...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Ansible - Configuration Management
Version: 6.7.0
Hardware: All
OS: All
unspecified
medium
Target Milestone: 6.11.0
Assignee: satellite6-bugs
QA Contact: Sam Bible
URL:
Whiteboard:
: 1683300 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-27 17:09 UTC by Sayan Das
Modified: 2023-12-15 20:09 UTC (History)
7 users (show)

Fixed In Version: tfm-rubygem-smart_proxy_ansible-3.3.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-05 14:28:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 31710 0 Normal Closed Enable Ansible jobs to run with check-only or dry-run 2021-07-28 17:19:02 UTC
Foreman Issue Tracker 33218 0 Normal Closed Only ansible config jobs should run in check mode 2022-01-17 14:09:27 UTC
Red Hat Knowledge Base (Solution) 5884141 0 None None None 2021-03-15 16:44:27 UTC
Red Hat Product Errata RHSA-2022:5498 0 None None None 2022-07-05 14:28:45 UTC

Description Sayan Das 2020-11-27 17:09:20 UTC 
1. Proposed title of this feature request

Allow ability to execute dry-run for any kind of ansible based remote execution jobs or insights remediation playbook when executing from Satellite

2. What is the nature and description of the request?

Customer relies on the Remote execution of Satellite so that they can run ansible roles\playbooks\commands on the target hosts. As satellite does not have check-only or dry-run option available, Customer will first need to test the playbook or locally and then only they can execute the same from satellite.

3. Why does the customer need this? (List the business requirements here)

Allows them to test before applying possibly disruptive configuration changes.

4. How would the customer like to achieve this? (List the functional requirements here)

A check box or drop down selection in the Job Invokation page to execute as a "dry-run" or "check-only" before they actually execute the playbook\job on the hosts to apply the changes.

A option for hammer as well to execute the job from command line with --chcek-only parameter.

5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

If --check is surfaced through the UI, a tester would create a plan from Ansible playbooks for Insights, then execute the playbook with the dry-run/check-only functionality. Or very simply any ansible based command and seperate ansible based job template execution can be tested with the with the dry-run/check-only functionality

6. Is there already an existing RFE upstream or in Red Hat Bugzilla?

similar upstream issue https://projects.theforeman.org/issues/27034

7. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?

No specific time requirement.

8. Is the sales team involved in this request and do they have any additional input?

NA

9. List any affected packages or components.

Satellite, Insights, Ansible, Remote execution, hammer Web UI 

10. Would the customer be able to assist in testing this functionality if implemented?

Yes.
Comment 2 Bryan Kearney 2021-02-23 16:03:33 UTC 
Upstream bug assigned to ymakias
Comment 3 Bryan Kearney 2021-02-23 16:03:35 UTC 
Upstream bug assigned to ymakias
Comment 4 Bryan Kearney 2021-03-16 16:03:30 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/31710 has been resolved.
Comment 5 Ondřej Ezr 2021-04-28 09:20:26 UTC 
*** Bug 1683300 has been marked as a duplicate of this bug. ***
Comment 10 Sam Bible 2022-04-25 18:54:50 UTC 
Verified on Satellite 6.11 - 16

Steps to Test:
1. Register a RHEL 7 host to Satellite 6.10 and assign an Ansible role.
2. In the Satellite webUI, navigate to Hosts > All Hosts > [hostname] > Edit > Parameters tab.
3. In the "Global Parameters" section, click the "Override" button in the "Actions" column for the "ansible_roles_check_mode" parameter.
4. In the "Host Parameters" section, change the value of the "Value" field from "false" to "true" for the "ansible_roles_check_mode" parameter.
5. Select the "Run Ansible roles" option.

Expected Results:
No changes are made when the Ansible role is run on the host

Actual Results: 
No changes are made when the Ansible role is run on the host, and when viewing the config report for the Host, it is indicated that the host is in "check mode"
Comment 14 errata-xmlrpc 2022-07-05 14:28:38 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Satellite 6.11 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:5498
Note You need to log in before you can comment on or make changes to this bug.