Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
(In reply to Jan Houska from comment #16)
> ITM is coming ...
>
> Please be so kind check the bug and switch into ON_QA state. Thank you!
I am afraid this is not fully ready, waiting for upstream. This will need to be postponed probably with some exception.
There are some additional patches upstream for OpenSSL 3.0 support, but there are reported bugs still, as it's work in progress. Furthermore, backporting the additonal patches requires more work, as they're not fully compatible with openssl gem in current Ruby.
Concluding, this will need to be addressed after RHEL9 Beta. I will post full compatibility report after the backport is done.
(In reply to Simo Sorce from comment #28)
I can't see any benefit, but I am not against if it helps others.
BTW I should have mention a few things:
1) I have merged the PR in Fedora and so far, Koschei does not show signs of big issues, with exception of rubygem-net-ssh.
2) I believe that upstream wants to land the OpenSSL 3.0 support for Ruby 3.1, where the target release is on Dec 25th.
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 (new packages: ruby), 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/RHBA-2022:2637