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):
nightlies of RHEL 7.5
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:
Steps to Reproduce:
1. Run fully automatic kickstart installation with GUI (I was using vnc).
2. Hit the race (or not)
The installation hangs in summary hub.
The installation completes automatically.
Created attachment 1331376 [details]
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.