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:

Somehow python-greenlet was associated with sst_openshift.  We do not use that package as best we can tell.  In RHEL 8 it was in CRB and AppStream however 9 currently has it only in CRB.  I would suggest removing it unless an owner is found.

openstack is requiring greenlet >= 1.0.0 to update sqlalchemy. What's the plan for greenlet in CentOS9?, remove it from OS repos, to keep it as is or rebase it?

I'd like to raise this again.

According to Josh Boyer[1], python-greenlet is likely to be removed from RHEL9/CentOS Stream 9, which would let us add it to EPEL9 and update it there. Is there an ETA for a decision, removal? Right now this is blocking inclusion of python-sqlalchemy in EPEL9 because the version of python-greenlet in EL9 is buggy[2].

[1]: https://bugzilla.redhat.com/show_bug.cgi?id=2042779#c17
[2]: https://bugzilla.redhat.com/show_bug.cgi?id=2042779#c8

This has been removed from RHEL 9. The EPEL request for python-greenlet should continue now.