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 installation of RHEL 7.3 beta 1, if you select a STIG to be applied as the security policy, the installation fails with an error. Furthermore, if you switch to a text console then back to the graphical installer, the error dialog box becomes just a plain white box, and the graphical interface is completely unresponsive.


Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. Install RHEL 7.3 beta 1 with a STIG security policy selected
2.
3.

Actual results: Installation fails with a Python traceback.


Expected results: Installation succeeds.


Additional info:

Do you think, it is duplicate of
https://github.com/OpenSCAP/oscap-anaconda-addon/issues/8 (see screenshots)~ https://bugzilla.redhat.com/show_bug.cgi?id=1360765 ?

(In reply to Zbynek Moravec from comment #2)
> Do you think, it is duplicate of
> https://github.com/OpenSCAP/oscap-anaconda-addon/issues/8 (see screenshots)~
> https://bugzilla.redhat.com/show_bug.cgi?id=1360765 ?

Yes, that github issue is what I observed.

Fixed in upstream:
https://github.com/OpenSCAP/oscap-anaconda-addon/commit/fb9c485418e59cfead3ab28d8ff8cfb7a19bba48

(In reply to Zbynek Moravec from comment #4)
> Fixed in upstream:
> https://github.com/OpenSCAP/oscap-anaconda-addon/commit/
> fb9c485418e59cfead3ab28d8ff8cfb7a19bba48

This patch is already in RHEL-7.4 (oscap-anaconda-addon-0.7-15.el7), so I'm closing this bug as a duplicate of bug 1360765 based on previous comments.

*** This bug has been marked as a duplicate of bug 1360765 ***