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.
Created attachment 1018536[details]
patch removing the Initial Setup units from the preset file
Description of problem:
The Initial Setup units (TUI and GUI) are marked as enabled in the in the service preset file (/usr/lib/systemd/system-preset/90-default.preset), so they are always enabled once the package containing the unit is installed.
This is an issue when the Initial Setup package is not installed by Anaconda during the initial OS installation but gets installed later, for example as part of a package group. This results in the IS UI interrupting the boot process and waiting for user input.
Therefore the Initial Setup unit files (initial-setup-graphical.service
and initial-setup-text.service) should be removed from the preset file to prevent this from happening.
NOTE: Removal of the preset won't break cases where the package is installed during the OS installation, because Anaconda makes sure to enable the appropriate IS services.
Version-Release number of selected component (if applicable):
219-12.fc23
How reproducible:
always
Steps to Reproduce:
1. install the "minimal install" environment and don't create a user
2. reboot and check that Initial Setup is not running
3. install the KDE Desktop package group (or any other group that pulls in Initial Setup)
4. reboot
Actual results:
The boot process is interrupted by Initial Setup waiting for user input.
Expected results:
Boot is not interrupted by Initial Setup and it's services are not enabled.
Additional info:
A patch removing the Initial Setup units from the preset file is attached.
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://rhn.redhat.com/errata/RHEA-2015-2107.html
Created attachment 1018536 [details] patch removing the Initial Setup units from the preset file Description of problem: The Initial Setup units (TUI and GUI) are marked as enabled in the in the service preset file (/usr/lib/systemd/system-preset/90-default.preset), so they are always enabled once the package containing the unit is installed. This is an issue when the Initial Setup package is not installed by Anaconda during the initial OS installation but gets installed later, for example as part of a package group. This results in the IS UI interrupting the boot process and waiting for user input. Therefore the Initial Setup unit files (initial-setup-graphical.service and initial-setup-text.service) should be removed from the preset file to prevent this from happening. NOTE: Removal of the preset won't break cases where the package is installed during the OS installation, because Anaconda makes sure to enable the appropriate IS services. Version-Release number of selected component (if applicable): 219-12.fc23 How reproducible: always Steps to Reproduce: 1. install the "minimal install" environment and don't create a user 2. reboot and check that Initial Setup is not running 3. install the KDE Desktop package group (or any other group that pulls in Initial Setup) 4. reboot Actual results: The boot process is interrupted by Initial Setup waiting for user input. Expected results: Boot is not interrupted by Initial Setup and it's services are not enabled. Additional info: A patch removing the Initial Setup units from the preset file is attached.