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.
Description of problem:
Registering RHEL-8 machine with Satellite-6.5 using bootstrap script with --rex and --rex-user parameter fails with error 'TypeError: 'in <string>' requires string as left operand, not bytes'
Version-Release number of selected component (if applicable):
Satellite-6.5
How reproducible:
Always with RHEL-8 client
Steps to Reproduce:
Download the boostrap script for Satellite-6.5 on RHEL-8 client machine and execute it like below.
# /usr/libexec/platform-python bootstrap.py -l admin -s 'satellite.example.com' -o 'redhat' -L 'default_location' -g bootstrap -a Test_AK --rex --rex-user=root --unmanage --force --skip puppet --skip-foreman
Actual results:
The client gets successfully registered but fails at below step while installing Remote Execution SSH key for user
[SUCCESS], [2019-10-21 22:44:22], [/usr/bin/yum -y remove rhn-setup rhn-client-tools yum-rhn-plugin rhnsd rhn-check rhnlib spacewalk-abrt spacewalk-oscap osad 'rh-*-rhui-client' 'candlepin-cert-consumer-*'], completed successfully.
[NOTIFICATION], [2019-10-21 22:44:22], [Fetching Remote Execution SSH key from https://syssat65.gsslab.pnq2.redhat.com:9090/ssh/pubkey]
[NOTIFICATION], [2019-10-21 22:44:23], [Installing Remote Execution SSH key for user root]
Traceback (most recent call last):
File "bootstrap.py", line 1563, in <module>
install_ssh_key_from_url(remote_exec_url)
File "bootstrap.py", line 674, in install_ssh_key_from_url
install_ssh_key_from_string(foreman_ssh_key)
File "bootstrap.py", line 708, in install_ssh_key_from_string
if foreman_ssh_key in open(options.remote_exec_authpath, 'r').read():
TypeError: 'in <string>' requires string as left operand, not bytes
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-2020:1454