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.
Description of problem:
Currently the Initial Setup systemd units are enabled by in the default systemd preset (/usr/lib/systemd/system-preset/90-default.preset). This has the unfortunate side effect that if the Initial Setup package is not installed during the installation, Initial Setup won't launch after the first reboot (which is perfectly fine if the package was left-out on purpose cause this) but **will start at a later date if its package gets installed**.
This can be quite problematic, as Initial Setup by design interrupts normal boot and waits for user input, which can potentially cause serious issues, especially on headless and unattended machines.
How reproducible:
always
Steps to Reproduce:
1. perform minimal install of RHEL7 server
2. after the reboot note that IS is not running (this is expected behavior for minimal install)
3. install the "Server with GUI" package group with yum groupinstall
Actual results:
Initial Setup is started on next boot, interrupts normal startup and waits for user input.
Expected results:
Initial Setup is not started on next boot.
Additional info:
Anaconda already enables (or disables by default for kickstart & if firstboot --disable is used) the initial-setup services (TUI & GUI).
So provided that this mechanism works correctly for all cases when Initial setup should be enabled, then dropping the initial-setup services from the systemd preset list might be enough to fix this issue.
Bug 1215226 has been fixed and no changes are needed on the Initial Setup side, so duping this on 1215226.
*** This bug has been marked as a duplicate of bug 1215226 ***