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:
Installation crashes when trying to fetch security policy from a server, while the server address is wrong or if it takes too long to fetch and you press the fetch button too many times, it can be achieved by either clicking too fast or by keeping the enter button pressed.
The url has to be valid, meaning http://xxx.xxx.xxx.xxx/<whatever_imaginery_file>
otherwise it will be rejected as invalid and nothing will happen, we need to enforce it to start looking for the url.

Version-Release number of selected component (if applicable):
It's applicable to every version that uses anaconda and can fetch policies from web server.

How reproducible:
Every time.

Steps to Reproduce:
1. Start installing the VM.
2. Try to fetch profile from remote server.
3. Press fetch fast enough 2-3 times or keep the enter pressed.

Actual results:
It looks likes it's trying to start multiple threads and since they all have the same name anaconda crashes.

This is interesting, as in https://github.com/OpenSCAP/oscap-anaconda-addon/blob/rhel8-branch/org_fedora_oscap/gui/spokes/oscap.py#L370 the _fetch_flag_lock and _fetching property indicate that this shouldn't happen. However, it apparently can happens.
As it is not easy to reproduce the issue, it's probably some nasty corner case.

Moving the BZ to Anaconda, as it looks like that the issue is caused by the thread manager.

The manager doesn't remove the thread explicitly when called with wait(), and it takes time for the thread to remove itself from the manager.

The same problem exists on RHEL-9 as well, reported as bug 2127502.

https://github.com/OpenSCAP/oscap-anaconda-addon/pull/221

A fix has been merged into upstream in https://github.com/OpenSCAP/oscap-anaconda-addon/pull/221

Verified with oscap-anaconda-addon-1.2.1-9.el8, the problem is no longer reproducible.

Marking as Verified:Tested.

Checked that oscap-anaconda-addon-1.2.1-10.el8 is in nightly compose RHEL-8.8.0-20221204.2

Moving to VERIFIED

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 (oscap-anaconda-addon bug fix and enhancement update), 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-2023:2828