Bug 1538448

Summary:	[RFE] Need to back up SSH keys for remote execution by katello-backup\|restore
Product:	Red Hat Satellite	Reporter:	Shivdutt Bharadwaj <shbharad>
Component:	Backup & Restore	Assignee:	Chris Roberts <chrobert>
Status:	CLOSED ERRATA	QA Contact:	Ales Dujicek <adujicek>
Severity:	medium	Docs Contact:
Priority:	high
Version:	6.2.12	CC:	adujicek, chrobert, cmarinea, hshukla
Target Milestone:	6.4.0	Keywords:	EasyFix, FutureFeature, PrioBumpPM, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	https://projects.theforeman.org/issues/22607
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-16 15:30: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 Shivdutt Bharadwaj 2018-01-25 06:43:16 UTC

Description of problem:
During the trial run of backup and recovery of Satellite server by (katello-backup|restore), system could NOT recover the Remote Execution function 
because the ssh private key (/usr/share/foreman-proxy/.ssh/id_rsa_foreman_proxy) was not backed up.


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

How reproducible:
Always

Steps to Reproduce:
1. Run katello-backup
2. Try to restore from the back up
3. Rex will not work on restored system as ssh-keys were not backed up 

Actual results:
ssh-key not available in backup in katello-backup

Expected results:
ssh-key should be backed up in katello-backup or there should be some option to enable it

Additional info:

Comment 2 Satellite Program 2018-02-22 11:01:09 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/22607 has been resolved.

Comment 6 errata-xmlrpc 2018-10-16 15:30: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, 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-2018:2927