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.
Initial Setup needs to be started before getty as it both needs to use the console to run (in TUI mode) and also as it might change system state and we don't want to do that while a user is potentially logged in.
This is currently done by individually listing all the getty@<console name>.service units in the Before= section of the Initial Setupe service files[0], which is sub-optimal and not very robust:
- it clutters the service file/s quite a bit
- there can be an arbitrary amount of arbitrarily named consoles, especially on more exotic hardware, so it's easy to miss some of them (on Fedora exotic consoles for ARM hardware have to be added regularly)
Based on this feedback from Initial Setup systemd developers have added[1] the new getty-pre.target, which gets triggered before getty has a chance to run on any console. This has a range of benefits compared to the current solution:
- by using the target Initial Setup should never again missing a console when blocking getty (systemd has all the needed information to make sure to run ther target before getty is activated on any console)
- the Initial Setup service files can be greatly cleaned up, with just a single line to use the getty-pre.target replacing many lines listing different consoles
[0] https://github.com/rhinstaller/initial-setup/blob/rhel7-branch/systemd/initial-setup.service#L6
[1] https://github.com/systemd/systemd/pull/6667
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, 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-2018:0795