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.

Bug 1394391

Summary: [RFE] bootstrap.py: backport --rex to Satellite 6.2.x
Product: Red Hat Satellite Reporter: Bryan Kearney <bkearney>
Component: BootstrapAssignee: Rich Jerrido <rjerrido>
Status: CLOSED ERRATA QA Contact: Evgeni Golov <egolov>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.3CC: bbuckingham, egolov, ehelms, fcami, greartes, jcallaha, sjagtap
Target Milestone: UnspecifiedKeywords: FutureFeature, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1380783 Environment:
Last Closed: 2018-02-21 16:46:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1380783    
Bug Blocks:    

Description Bryan Kearney 2016-11-11 20:21:01 UTC
+++ This bug was initially created as a clone of Bug #1380783 +++

Description of problem:
bootstrap.py does not install Foreman's SSH remote execution key.

Version-Release number of selected component (if applicable):
katello-client-bootstrap-1.1.0-2.el7sat

How reproducible:
Always

Steps to Reproduce:
1. register a client with bootstrap.py


Actual results:
No key in /root/.ssh/authorized_keys

Expected results:
Foreman's key there


Additional info:
upstream commit:
https://github.com/Katello/katello-client-bootstrap/commit/564dede32d8baa3c7b8647dcecbb52c060682adf

--- Additional comment from rjerrido on 20161031T17:38:59

Moving to POST as patch is available upstream.

Comment 2 Evgeni Golov 2017-08-30 09:43:28 UTC
VERIFIED

Version tested:
Satellite 6.3 Snap 13
katello-client-bootstrap-1.4.0-1.el7sat.noarch

[root@rhel7 ~]# cat ~/.ssh/authorized_keys
cat: /root/.ssh/authorized_keys: No such file or directory
[root@rhel7 ~]# python bootstrap.py -s sat63-qa-rhel7.kangae.example.com -l admin -p changeme -a rhel7 -o "Default Organization" -L "Default Location" -g rhel --rex --force
…
[NOTIFICATION], [2017-08-30 09:41:12], [Foreman's SSH key was added to /root/.ssh/authorized_keys] 
[root@rhel7 ~]# cat ~/.ssh/authorized_keys
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC3A5rp8s/NSpFYwyCnMw6BItkpF9ve5I5XGdmW1JUMGDmmzey/EOekk/VmHKoUDdcRtwWPrxiqy5BaYa0EUrxg7W5Xy+hDN47d12f5cDzDsGzgQkUQYexrXsBJLD+mpqh7M9rCg03HvMDZ/aIlEXw60WGhSd9/oTx7cFYfxrEG/Z3TmtdL/e9gRqDUDD1FjjUIlLWhgy6/wuFEQvPPrKF2F7mYzO8rFVFyQjhxsmKgTsa9TJk8wIFYjkf+Zm0me+YOIksvG69Rn4qgHcAAl4LEv3gOI9h7r82IwuiM966mV4U0HTaHSf0gqkCXSmui2MH/r1QDqK8s/Tb70GNmZINt foreman-proxy.example.com

Comment 3 Bryan Kearney 2018-02-21 16:42:22 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:0336

Comment 4 Bryan Kearney 2018-02-21 16:46:25 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:0336

Comment 5 Satellite Program 2018-02-21 16:51:07 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:0336