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:
When I configured repository with baseurl= being an metalink in RHEL6 in FIPS mode, yum fails to download it.


Version-Release number of selected component (if applicable):
yum-3.2.27-9.el6.noarch
fipscheck-1.2.0-4.1.el6.i686
kernel-2.6.32-28.el6.i686
kernel-2.6.32-33.el6.i686


How reproducible:
always (tested on 1 i386 RHEL6 system)


Steps to Reproduce:
1. # vim /etc/yum.repos.d/fedora-meta.repo
   [fedora-meta]
   name=Fedora 12 i386
   failovermethod=priority
   mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-12&arch=i386
   enabled=1
   metadata_expire=7d
   gpgcheck=1
   gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearch
2. # yum repolist
   Loaded plugins: aliases, changelog, downloadonly, presto, protect-packages, refresh-packagekit, rhnplugin, security, tmprepo,
                 : verify, versionlock
   This system is not registered with RHN.
   RHN support will be disabled.
   fedora-meta/metalink                            |  20 kB     00:00     
   fips.c(152): OpenSSL internal error, assertion failed: FATAL FIPS SELFTEST FAILURE
   Aborted (core dumped)


Actual results:
yum fails to download metalink


Expected results:
should work


Additional info:
This was mentioned in:
  https://bugzilla.redhat.com/show_bug.cgi?id=541974#c5

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Can we get a backtrace ... or access to a fips machine, as I can't see where we are accessing md5.

Hello,
you are right. I have re-checked with these versions:

kernel-2.6.32-44.el6.i686
fipscheck-lib-1.2.0-4.1.el6.i686
fipscheck-1.2.0-4.1.el6.i686
yum-3.2.27-12.el6.noarch

and I do not see the problem any more. Maybe before I have forgot to run `prelink -u -a; rpm -e prelink` before switching to FIPS?

Thank you and sorry for a mess,
Jan