Bug 2213320

Summary:	"Error in GnuTLS initialization: Error while performing self checks" in FIPS mode
Product:	Red Hat Enterprise Linux 8	Reporter:	Andrew Mike <amike>
Component:	gnutls	Assignee:	Daiki Ueno <dueno>
Status:	CLOSED MIGRATED	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.8	CC:	asosedki, brclark
Target Milestone:	rc	Keywords:	MigratedToJIRA, Triaged
Target Release:	---	Flags:	amike: needinfo- pm-rhel: mirror+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-20 00:24:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Andrew Mike 2023-06-07 19:48:27 UTC

Description of problem: When using GnuTLS in FIPS mode, it fails its self check suite upon bootup.

Version-Release number of selected component (if applicable):
3.6.16-6.el8_7.x86_64

How reproducible: Consistent.

Steps to Reproduce:
1. Enable FIPS mode on a system.
2. Reboot the system.

Actual results: 
A message appepars in the journald log from dracut-cmdline: "Error in GnuTLS initialization: Error while performing self checks."

Expected results:
GnuTLS passes self-checks for FIPS.

Additional info:
This appears to be a regression from Bugzilla 1665061, which was fixed in gnutls-3.6.5-2.el8.

Comment 9 RHEL Program Management 2023-09-20 00:23:14 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 10 RHEL Program Management 2023-09-20 00:24:09 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.