Bug 2153727

Summary:	Ansible Command ignores advance field
Product:	Red Hat Satellite	Reporter:	Jan Jansky <jjansky>
Component:	Ansible - Configuration Management	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.12.0	CC:	ahumbe, amasolov, jbhatia, nalfassi, rlavi, saydas
Target Milestone:	Unspecified	Keywords:	MigratedToJIRA, Triaged, UserExperience
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 12:56:35 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.