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.
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 (Moderate: python38:3.8 and python38-devel:3.8 security 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/RHSA-2023:7050
Description of problem: When rebulding python38 module for RHEL 8, numpy fails to build from source with: =================================== FAILURES =================================== ______________________________ TestCond.test_nan _______________________________ self = <numpy.linalg.tests.test_linalg.TestCond object at 0x7fffa7e705b0> def test_nan(self): # nans should be passed through, not converted to infs ps = [None, 1, -1, 2, -2, 'fro'] p_pos = [None, 1, 2, 'fro'] A = np.ones((2, 2)) A[0,1] = np.nan for p in ps: > c = linalg.cond(A, p) A = array([[ 1., nan], [ 1., 1.]]) p = None p_pos = [None, 1, 2, 'fro'] ps = [None, 1, -1, 2, -2, 'fro'] self = <numpy.linalg.tests.test_linalg.TestCond object at 0x7fffa7e705b0> numpy/linalg/tests/test_linalg.py:770: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ <__array_function__ internals>:5: in cond ??? numpy/linalg/linalg.py:1740: in cond s = svd(x, compute_uv=False) <__array_function__ internals>:5: in svd ??? numpy/linalg/linalg.py:1648: in svd s = gufunc(a, signature=signature, extobj=extobj) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ err = 'invalid value', flag = 8 def _raise_linalgerror_svd_nonconvergence(err, flag): > raise LinAlgError("SVD did not converge") E numpy.linalg.LinAlgError: SVD did not converge err = 'invalid value' flag = 8 numpy/linalg/linalg.py:106: LinAlgError = 1 failed, 10151 passed, 69 skipped, 173 deselected, 18 xfailed, 1 xpassed in 73.21 seconds = Version-Release number of selected component (if applicable): numpy-1.17.3-6 Steps to Reproduce: 1. Scratch build python38 module for RHEL 8. Additional info: We need to rebuild the module to be able to ship a CVE fix in one of its components so this is kinda important for us.