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 1158801

Summary: [firstboot] No firstboot progress after fresh install the RHEL7.1
Product: Red Hat Enterprise Linux 7 Reporter: xingge <gxing>
Component: firstbootAssignee: Martin Kolman <mkolman>
Status: CLOSED CURRENTRELEASE QA Contact: Release Test Team <release-test-team-automation>
Severity: high Docs Contact:
Priority: high    
Version: 7.1CC: gxing, ldai, liliu, mkolman, qianzhan, wpoteat
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-04 16:56:51 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: 1005618    

Description xingge 2014-10-30 09:28:08 UTC
Description of problem:
No firstboot progress after fresh install the RHEL7.1

Version-Release number of selected component (if applicable):
subscription-manager-gui-1.13.6-1.el7.x86_64
subscription-manager-firstboot-1.13.6-1.el7.x86_64
subscription-manager-1.13.6-1.el7.x86_64
python-rhsm-1.13.6-1.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1.Fresh install the RHEL7.1 20141029.0 build
2.After installation complete click the reboot button


Actual results:
After reboot the system shows the login page.

Expected results:
After reboot the system should show the firstboot progress first.

Additional info:
After log in the system, I can run cmd "firstboot" in the CLI to start the firstboot progress.

Comment 1 William Poteat 2015-01-16 16:09:23 UTC
subscription manager does not control the launch of firstboot after anaconda installs a new system

Comment 2 Martin Kolman 2015-01-16 16:56:16 UTC
Please add all the installation log files from /var/log/anaconda as separate text/plain attachments so that we can check what went wrong.

Comment 3 xingge 2015-02-03 02:31:45 UTC
Hi
  The Build after 20141029.0 are all have firstboot progress,should I still offer the log or just close the bug as verified?

Comment 4 Martin Kolman 2015-02-04 16:56:51 UTC
If it works correctly now then we can close this.