Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 2211721

Summary:	Satellite 6.11 install on a VM with existing Ansible
Product:	Red Hat Satellite	Reporter:	Glenn Eaton <glenn.eaton>
Component:	Installation	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.11.5	CC:	egolov, ehelms, nalfassi, rlavi
Target Milestone:	Unspecified	Keywords:	MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 16:15:12 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 Glenn Eaton 2023-06-01 16:43:02 UTC

Description of problem:
Satellite is almost never the first Ansible capable tool to arrive in an environment. The existing configuration methodology for a fresh Sat6 implementation, in effect, forces the user to create a new set of Ansible credentials which is likely to be redundant as many, if not most, customers will already have some form of Ansible or credential authorized automation in place. This is our problem here at Fiserv!

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

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Evgeni Golov 2023-06-15 12:52:14 UTC

I am not sure we understand your request correctly. Are you requesting a feature where Satellite can reuse existing credentials (username/password, ssh key, etc) for the Ansible/REX feature instead of creating an own key and having you the user enroll that key on all the machines?

Comment 3 Glenn Eaton 2023-06-15 14:22:30 UTC

(In reply to Evgeni Golov from comment #2)
> I am not sure we understand your request correctly. Are you requesting a
> feature where Satellite can reuse existing credentials (username/password,
> ssh key, etc) for the Ansible/REX feature instead of creating an own key and
> having you the user enroll that key on all the machines?

Yes,  this is what I would like to see.  I don't want to redo alot of work that is already done with the original/Legacy Ansible ID/Account.

Comment 4 Evgeni Golov 2023-06-16 12:03:01 UTC

You can stop Satellite from generating an SSH key by using `--foreman-proxy-plugin-remote-execution-script-generate-keys false` during installation.
Then you can provide an own SSH key in `/var/lib/foreman-proxy/ssh/id_rsa_foreman_proxy(.pub)` yourself (or even change the location with --foreman-proxy-plugin-remote-execution-script-ssh-identity-dir/--foreman-proxy-plugin-remote-execution-script-ssh-identity-file).
If you also need to alter the username used for SSH, there is the remote_execution_ssh_user setting, which can be either set globally or as a parameter for a host or hostgroup.

Would that suit your needs?

Comment 5 Glenn Eaton 2023-07-31 14:41:56 UTC

we will test this out and let you know.

Comment 6 Eric Helms 2024-06-06 16:15:12 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.