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.
As mentioned on the MR, systemd-oomd will not be enabled by default in CentOS Stream or RHEL. We can use this bug to add the package to the compose in other ways if it's something we're going to support at all.
For CentOS Stream and RHEL-9 we are planning to put systemd-oomd to a subpackage alongside the default configuration. Package won't be installed by default and whoever wants it will get the daemon together with the default config after installing systemd-oomd subpackage.
In RHEL we want users to have the option to use it but we don't want oomd present in every environment where systemd rpm is installed (e.g. container images). Hence we need to move systemd-oomd daemon binary to a subpackage and then it make sense to also rename current config subpackage to just say systemd-oomd.
Davide, does this plan work for you?