This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2153727 - Ansible Command ignores advance field
Summary: Ansible Command ignores advance field
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Ansible - Configuration Management
Version: 6.12.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
: 2203239 2214194 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-15 10:15 UTC by Jan Jansky
Modified: 2024-06-06 12:56 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 12:56:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36448 0 High New Ansible Command ignores advance field 2023-06-27 12:38:42 UTC
Red Hat Issue Tracker   SAT-18270 0 None Migrated None 2024-06-06 12:56:33 UTC
Red Hat Knowledge Base (Solution) 7030536 0 None None None 2023-08-25 10:44:26 UTC

Description Jan Jansky 2022-12-15 10:15:59 UTC 
Description of problem:
(Not sure if component should be Ansible or Remote Execution, if its not correct please adjust)


Version-Release number of selected component (if applicable):
Satellite 6.10
Satellite 6.11
Satellite 6.12
maybe olders


How reproducible:
Always


Steps to Reproduce:
1. Monitor -> Jobs -> Run Job
2. Details:
Job Category: Ansible Commands
fill search query and command

Advanced fields:
Effective user: root
fill "Password" and "Effective user password"

3. Execute

Actual results:
Permission Denied

or with usage of ssh key

Missing sudo password

Expected results:
Successfully executed task with results.


Additional info:
Only global setting values or host parameters are respected, setting on job execution is ignored completely.
Comment 6 Sayan Das 2023-05-23 08:44:26 UTC 
*** Bug 2203239 has been marked as a duplicate of this bug. ***
Comment 7 nalfassi 2023-05-29 10:04:31 UTC 
Created redmine issue https://projects.theforeman.org/issues/36448 from this bug
Comment 8 Adam Ruzicka 2023-06-12 09:40:15 UTC 
*** Bug 2214194 has been marked as a duplicate of this bug. ***
Comment 11 Eric Helms 2024-06-06 12:56:35 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.