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.
Description of problem:
The foreman-proxy is copied 3 times on the provisioned machine in /root/.ssh/authorized_keys when the remote execution is available.
By previewing the remote_execution_ssh_keys snippet , it shows the foreman-proxy keys of the satellite and the capsule 3 times
Version-Release number of selected component (if applicable):
Red Hat satellite 6.7
How reproducible:
100%
Steps to Reproduce:
1. Provision a new machine.
2. Check file /root/.ssh/authorized_keys
3. Also by previewing remote_execution_ssh_keys snippet.
Actual results:
The ssh key is replicated 3 times
Expected results:
The ssh key has only one entry for the satellite and one for the capsule if existing.
VERIFIED
on sat6.9.0-14.0
the snippet now works correctly and the provisioned host ends up with a single occurrence of the key in authorized_keys file of root user:
```
[root@abel-frames ~]# cat ~/.ssh/authorized_keys
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCes4pAjGQ62TWSC2E6k0YcxCPV1nWKOfNjBtcVuOIqnC/kQ4Nh3JxAcRbaj9/zn4zWYXyYO4bS9AtvAweHf1C1fuzUopr73Rs822GlaktlA6UdwyGEv9gO2+INvNEyG167kAIa9qxygbqfiDnpjBCTdDE4iIlEkAvIdDv4sFEUOi4zmV5aBTRh0S3/UbtqH5Yescp2mRzpbz7AA4dEpjDu5mnVZXtsv8omhvukPgf9UNol6v4fMPHlPNvL8zZ8CXe51JAWcFzVS2rwKqt6R7nwhb6XEuVkNFNc8VgF52njoFQVUOia/XYcjzJmZI7kib2omcVfTxwIM/zgA38rjtdb foreman-proxy@<redacted>.com
[root@abel-frames ~]#
```
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.9 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-2021:1313