Hide Forgot
Description of problem: On RHEL 7.3, initial-setup-graphical.service hangs during startup, which is somehow unexpected behavior compared to RHEL 7.2, where it throws an error (when there's no X server available). We managed to trigger this issue during an upgrade of one of our systems (by some post-install scriptlet, I guess), which had to be fixed manually. In this case, the initial-setup-graphical.service was in 'activating' state for 54 minutes and the upgrade was stuck. Version-Release number of selected component (if applicable): initial-setup-0.3.9.36-1.el7.x86_64 initial-setup-gui-0.3.9.36-1.el7.x86_64 How reproducible: always Steps to Reproduce: # yum -y install initial-setup-gui # systemctl start initial-setup-graphical.service Actual results: # systemctl start initial-setup-graphical.service <... no output ...> ## From another terminal # systemctl status initial-setup-graphical.service ● initial-setup-graphical.service - Initial Setup configuration program graphical interface Loaded: loaded (/usr/lib/systemd/system/initial-setup-graphical.service; disabled; vendor preset: disabled) Active: activating (start) since Fri 2016-11-04 10:51:42 EDT; 28min ago <...> Expected results: ## Output from RHEL 7.2 # rpm -qa | grep initial-setup initial-setup-0.3.9.30-1.el7.x86_64 initial-setup-gui-0.3.9.30-1.el7.x86_64 # systemctl start initial-setup-graphical.service Job for initial-setup-graphical.service failed because the control process exited with error code. See "systemctl status initial-setup-graphical.service" and "journalctl -xe" for details. # systemctl status initial-setup-graphical.service ● initial-setup-graphical.service - Initial Setup configuration program Loaded: loaded (/usr/lib/systemd/system/initial-setup-graphical.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2016-11-04 11:26:49 EDT; 17s ago <...>
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.