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.

This bug was initially created as a copy of Bug #2157663

Description of problem:
Due to bug #2140646, 'systemd-stub' was enabled. This leads to various systemd-boot related files in the systemd-udev package.

From my point of understanding, the 'systemd-stub' is only required for Azure Confidential VMs - and not because Red Hat is really interested in maintaining systemd-boot in RHEL (for e.g. booting RHEL using systemd-boot instead of grub2-efi).

Given I maintain systemd-boot via systemd-extras in EPEL (to actually boot RHEL using systemd-boot instead of grub2-efi), I would like to see Red Hat moving 'systemd-stub' (and all other systemd-boot components) to a separate buildroot-only subpackage - if Red Hat does not plan to fully support systemd-boot itself in RHEL as a first-class citizen (= to actually boot RHEL using systemd-boot instead of grub2-efi).

Version-Release number of selected component (if applicable):
systemd-252-2.el9

Actual results:
Package systemd-udev with 'systemd-stub' and other systemd-boot related files.

Expected results:
All systemd-boot related files in a separate buildroot-only subpackage, to leave space for systemd-boot from systemd-extras from EPEL.

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 (systemd bug fix and enhancement update), 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-2023:6640