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.
When installing af RHEL 7.2 in a fresh Virtualbox environment and doing yum update, it will hang in cleanup of init-setup-0.3.0.30-1.el7.x86_64.
Version-Release number of selected component (if applicable): yum-3.4.3-132 and -150.el7.noarch, kernels: kernel-3.10.0-327 and -514.el7.x86_64.
How reproducible:
100% when certain certain packages selected during install.
Steps to Reproduce:
1. Create a new virtualbox image with 8Gb RAM and 16Gb virtual disk
2. Add the rhel-server-7.2-x86_64-dvd.iso as optical disk
3. Start installation and activate network support.
4. Use danish keyboard and language.
5. Select GUI configuration and the check the following options: Java platform, NFS client, Virtualization Client, Hypervisor and Tools.
6. Create regular user with admin rights.
7. Complete installation and reboot.
8. Accept license
9. Login as regular user and register and attach site using GUI.
10. Open Terminal window and login as root
11. Type yum update
12. Accept prompts for importing keys.
Actual results:
During cleanup - around line 680 - cleanup - progress stops at the initial-setup and hangs forever.
Rebooting gives kernel panic with a corrupt disk.
Expected results:
Yum completes and a reboot will run with a system updated to 7.3.
Additional info:
The packages selected during installation is important. If no additional packages is selected and default english language is used (but still with danish keyboard) yum updates completes and system is useable.
This is particular critical at the moment, as the RHEL 7.2 image is still present on developer.redhat.com.
A simple workaround is download a 7.3 image from the main Red Hat site.
First observed on 2016-11-29 (first attempt) - latest on 2016-12-02.
There is some systemctl command running
systemctl try-restart initial-setup-text.service
if you kill the process with the "kill" command the yum cleanup continues...
Cleanup : initial-setup-0.3.9.30-1.el7.x86_64 1239/1854
/var/tmp/rpm-tmp.G6HJ6m: line 6: 25160 Killed systemctl try-restart initial-setup-text.service > /dev/null 2>&1
Cleanup : anaconda-core-21.48.22.56-1.el7.x86_64 1240/1854
Cleanup : anaconda-tui-21.48.22.56-1.el7.x86_64 1241/1854
Cleanup : 1:python-blivet-0.61.15.37-1.el7.noarch 1242/1854
Comment 7RHEL Program Management
2021-01-15 07:28:56 UTC
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.
