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.

Description of problem:
The ssh keypair of foreman-proxy is not created on Satellite installation, even when parameter '--foreman-proxy-plugin-remote-execution-ssh-install-key' is used. Consequently, Satellite can't ReX against itself.

Version-Release number of selected component (if applicable):
Sat 6.8 snap 2.1

How reproducible:
Deterministic

Steps to Reproduce:
1. # satellite-installer --foreman-proxy-plugin-remote-execution-ssh-install-key

Actual results:
Can't SSH to root@<satellite> because:
```
Failed to connect to the host via ssh: Warning: Permanently added 'dhcp-2-205.vms.sat.rdu2.redhat.com,10.1.2.205' (ECDSA) to the list of known hosts.\r\nno such identity: /usr/share/foreman-proxy/.ssh/id_rsa_foreman_proxy: No such file or directory\r\nPermission denied (publickey,gssapi-keyex,gssapi-with-mic,password).
```

Expected results:
SSH keypair created, copied to root's authorized_keys

This is a side effect of https://bugzilla.redhat.com/show_bug.cgi?id=1842943. The key gets generated into /var/lib/foreman-proxy/ssh, however packaging deploys ~foreman-proxy/.ssh as a symlink to /usr/com/something.

Hi Adam,

Are you saying bug 1842943 will solve this one?  If so, shall we close:dupe this one?

I believe it should, let's close this one.

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