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:
Due to a wrong expansion of a macro, ~foreman-proxy/.ssh points into somewhere in /usr/com. It should point to /var/lib/foreman-proxy/

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


How reproducible:


Steps to Reproduce:
1. Run ls -lad ~foreman-proxy/.ssh

Actual results:
It is a symlink to somewhere under /usr/com/


Expected results:
It should point to /var/lib/foreman-proxy/ssh

This is already fixed in upstream, moving to POST

Fix in upstream: https://github.com/theforeman/foreman-packaging/pull/5293

*** Bug 1842957 has been marked as a duplicate of this bug. ***

VERIFIED.

@Satellite 6.8.0 Snap8
tfm-rubygem-smart_proxy_remote_execution_ssh-0.3.0-3.el7sat.noarch

# ls -lad ~foreman-proxy/.ssh
lrwxrwxrwx. 1 root root 26 Jul 13 10:20 /usr/share/foreman-proxy/.ssh -> /var/lib/foreman-proxy/ssh

>>> ~foreman-proxy/.ssh points to correct place /var/lib/foreman-proxy/ssh

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 (Important: Satellite 6.8 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-2020:4366