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.
Description of problem:
During automatic kickstart installation in graphical mode the installation stops with Storage Spoke incomplete. After visiting the spoke and clicking Done the installation proceeds.
This is caused by a race condition:
Right before storage checking thread finishes, it updates status of the storage spoke to status ready sending message to the main thread. The main thread as a part of the ready message processing updates summary hub completeness based on checking the completeness of the storage spoke which is evaulated based on the storage checking thread, which in case of the race condition hasn't finished yet.
Note the minimal time interval between the thread and the spoke ready status reported (from anaconda.log).
05:13:43,559 DEBUG anaconda: Storage check finished with success.
05:13:43,560 INFO anaconda: Thread Done: AnaCheckStorageThread (139735677433600)
05:13:43,563 INFO anaconda: spoke is ready: StorageSpoke
Version-Release number of selected component (if applicable):
RHEL 7.4
nightlies of RHEL 7.5
How reproducible:
Not easy, I was hitting it consistently when running kickstart tests in kvm. Batch of ~20 tests, running 4 tests in parallel. Every ~2nd batch hit the problem. Another reproducer was reported here:
https://github.com/rhinstaller/anaconda/pull/1194
Steps to Reproduce:
1. Run fully automatic kickstart installation with GUI (I was using vnc).
2. Hit the race (or not)
Actual results:
The installation hangs in summary hub.
Expected results:
The installation completes automatically.
Additional info:
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://access.redhat.com/errata/RHBA-2018:0671