Bug 1215226

Summary: Initial Setup units should not be enabled in the the default service preset
Product: Red Hat Enterprise Linux 7 Reporter: Martin Kolman <mkolman>
Component: redhat-releaseAssignee: Jan Blazek <jblazek>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.2CC: jblazek, lnykryn, mbanas, mkolman, mkovarik, systemd-maint-list
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 07:42:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1133060, 1169889, 1178588, 1183042, 1199234    
Attachments:
Description Flags
patch removing the Initial Setup units from the preset file none

Description Martin Kolman 2015-04-24 16:21:08 UTC
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.

Comment 2 Lukáš Nykrýn 2015-04-27 07:19:57 UTC
That file is handled by redhat-release on rhel.

Comment 7 Martin Kolman 2015-07-28 12:16:42 UTC
*** Bug 1183042 has been marked as a duplicate of this bug. ***

Comment 10 errata-xmlrpc 2015-11-19 07:42:20 UTC
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