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.

Bug 1091317

Summary: firstboot-graphical service stays enabled after the firstboot
Product: Red Hat Enterprise Linux 7 Reporter: Vratislav Podzimek <vpodzime>
Component: firstbootAssignee: Martin Kolman <mkolman>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: mbanas
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: firstboot-19.9-2 Doc Type: Bug Fix
Doc Text:
Cause: The Firstboot Systemd service stayed enabled even after Firstboot has been completed. Consequence: The Frstboot service slowed down every boot by about 400 ms. Fix: The Fisrtboot service is now properly disabled once Firstboot is completed. Result: The service is now no longer run once Firstboot has been completed, speeding up boot by about ~400 ms.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-05 09:06:39 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:
Attachments:
Description Flags
patch fixing the issue for both newly installed and existing systems none

Description Vratislav Podzimek 2014-04-25 11:03:50 UTC
Created attachment 889659 [details]
patch fixing the issue for both newly installed and existing systems

Description of problem:
As part of the first boot process, the firstboot-graphical service runs the firstboot utility. However, when it is finished, it just writes out the /etc/sysconfig/firstboot file with the "RUN_FIRSTBOOT=NO" line without disabling the service. As a result, the service runs on every boot of the system just to open that file and find out it should kill itself. That takes ~400ms which is ~10 % of boot time of the freshly installed system.

Version-Release number of selected component (if applicable):
firstboot-19.9-1.el7.noarch

How reproducible:
100 %

Steps to Reproduce:
1. install RHEL 7 with the firstboot utility
2. boot the system and go through the first boot setup
3. reboot the system
4. run 'systemd-analyze blame' to see that the service was run and took ~400ms

Actual results:
the firstboot-graphical service is run again and again only to find out it should kill itself

Expected results:
the firstboot-graphical service is run only once

Additional info:
this can be easily patched (attached) and fixed for both newly installed systems and already installed system

Comment 2 RHEL Program Management 2014-05-03 05:47:43 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 3 Vratislav Podzimek 2014-09-03 09:46:18 UTC
Martin, this is already fixed in Rawhide. We just need to take the patch and apply it to another RHEL 7 firstboot build.

Comment 4 Martin Kolman 2014-09-03 10:52:40 UTC
The patch looks good, thanks & ACK!

Comment 6 Alexander Todorov 2014-10-30 12:37:02 UTC
After the reboot:

# systemd-analyze blame
         17.716s boot.mount
          8.984s initial-setup-text.service
          4.671s firewalld.service
          3.578s tuned.service
          2.812s kdump.service
          2.527s postfix.service
          2.323s network.service
          2.316s accounts-daemon.service
          2.147s ModemManager.service
          1.917s avahi-daemon.service
          1.473s systemd-logind.service
          1.442s libvirtd.service
          1.361s rtkit-daemon.service
          1.288s sysstat.service
          1.049s abrt-ccpp.service
           902ms lvm2-monitor.service
           889ms systemd-udev-settle.service
           747ms NetworkManager.service
           590ms rhel-dmesg.service
           568ms chronyd.service
           565ms polkit.service
           546ms rsyslog.service
           540ms rhel-loadmodules.service
           527ms ksm.service
           498ms ksmtuned.service
           383ms gdm.service
           332ms systemd-tmpfiles-setup-dev.service
           311ms rhel-import-state.service
           285ms dmraid-activation.service
           226ms systemd-vconsole-setup.service
           219ms rhel-readonly.service
           211ms kmod-static-nodes.service
           201ms systemd-udev-trigger.service
           187ms auditd.service
           178ms sys-kernel-debug.mount
           163ms systemd-tmpfiles-setup.service
           162ms dev-mqueue.mount
           162ms dev-hugepages.mount
           134ms colord.service
           123ms systemd-remount-fs.service
           115ms plymouth-read-write.service
           102ms rhsmcertd.service
            96ms systemd-user-sessions.service
            93ms rhnsd.service
            89ms systemd-sysctl.service
            87ms dev-mapper-rhel\x2dswap.swap
            81ms systemd-localed.service
            76ms lvm2-pvscan@252:2.service
            67ms upower.service
            65ms plymouth-start.service
            49ms systemd-update-utmp.service
            39ms systemd-journal-flush.service
            33ms systemd-udevd.service
            28ms systemd-random-seed.service
            12ms systemd-update-utmp-runlevel.service
             8ms sys-kernel-config.mount

Comment 8 errata-xmlrpc 2015-03-05 09:06:39 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/RHBA-2015-0394.html