RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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:
While generating sos-collector, the process fails with error:

<hostname>  : Unable to connect: not a valid RSA private key file

Though the correct keys are installed. https://access.redhat.com/solutions/9194


Version-Release number of selected component (if applicable):
RHEL 8 Beta

How reproducible:
Always

Steps to Reproduce:
1. Configure ssh keys from RHEL8 to other nodes.
2. try to generate sos-collector without password
3.

Actual results:
sos-collector fails to generate with error:
: Unable to connect: not a valid RSA private key file

Expected results:
the process should pass.

Additional info:

Reassigning to Jake as maintainer of sos-collector.

Jake, could you pls. ask for sos-collector component in RHEL8? I see the component in RHEL7 product only, but not in RHEL8. (and I dont know where to raise such requests :( ).

For sos-collector-1.5 you need to have the key loaded by an agent, e.g. ssh-agent.

However, this exact behavior is why we transitioned sos-collector away from paramiko as the transport since this error comes directly from paramiko not supporting the default key types in RHEL 8.

This is fixed in sos-collector-1.6

Closing as this is resolved in sos-collector-1.6 in RHEL 8, but did not make it in time for the Beta.