Hide Forgot
+++ 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.
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
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
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