Bug 1842943

Summary:	~foreman-proxy/.ssh is a symlink to /usr/com/foreman-proxy/ssh/
Product:	Red Hat Satellite	Reporter:	Adam Ruzicka <aruzicka>
Component:	Packaging	Assignee:	Adam Ruzicka <aruzicka>
Status:	CLOSED ERRATA	QA Contact:	Lukas Pramuk <lpramuk>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.8.0	CC:	egolov, lhellebr
Target Milestone:	6.8.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-smart_proxy_openscap-0.7.2-6	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 13:03:08 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 Adam Ruzicka 2020-06-02 12:33:40 UTC

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

Comment 1 Adam Ruzicka 2020-06-02 12:34:35 UTC

This is already fixed in upstream, moving to POST

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

Comment 2 Adam Ruzicka 2020-06-08 14:29:45 UTC

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

Comment 3 Lukas Pramuk 2020-07-14 13:01:37 UTC

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

Comment 6 errata-xmlrpc 2020-10-27 13:03:08 UTC

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