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.
Bug 1746565 - [fips] knet transport fails to initialize with OS in fips mode [rhel-8.0.0.z]
Summary: [fips] knet transport fails to initialize with OS in fips mode [rhel-8.0.0.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pcs
Version: 8.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 8.0
Assignee: Tomas Jelinek
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1740218
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-28 19:14 UTC by Oneata Mircea Teodor
Modified: 2020-11-14 07:53 UTC (History)
11 users (show)

Fixed In Version: pcs-0.10.1-4.el8_0.4
Doc Type: Bug Fix
Doc Text:
Cause: Pcs creates 384 bytes long corosync authkey. Consequence: Corosync does not start when FIPS mode is enabled. Fix: Make pcs create 256 bytes long corosync authkey. Result: Corosync starts even when FIPS mode is enabled.
Clone Of: 1740218
Environment:
Last Closed: 2019-09-10 13:13:20 UTC
Type: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
proposed fix (3.58 KB, patch)
2019-08-29 10:04 UTC, Ivan Devat 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2701 0 None None None 2019-09-10 13:13:21 UTC

Comment 1 Ivan Devat 2019-08-29 10:04:30 UTC 
Created attachment 1609327 [details]
proposed fix
Comment 2 Ivan Devat 2019-08-29 12:28:04 UTC 
After Fix
=========

[ant8 ~] $ rpm -q pcs
pcs-0.10.1-4.el8_0.4.x86_64
[ant8 ~] $ fips-mode-setup --check
FIPS mode is enabled.

[ant8 ~] $ pcs cluster setup zoo ant8 bee8
No addresses specified for host 'ant8', using 'ant8'
No addresses specified for host 'bee8', using 'bee8'
Destroying cluster on hosts: 'ant8', 'bee8'...
bee8: Successfully destroyed cluster
ant8: Successfully destroyed cluster
Requesting remove 'pcsd settings' from 'ant8', 'bee8'
ant8: successful removal of the file 'pcsd settings'
bee8: successful removal of the file 'pcsd settings'
Sending 'corosync authkey', 'pacemaker authkey' to 'ant8', 'bee8'
ant8: successful distribution of the file 'corosync authkey'
ant8: successful distribution of the file 'pacemaker authkey'
bee8: successful distribution of the file 'corosync authkey'
bee8: successful distribution of the file 'pacemaker authkey'
Synchronizing pcsd SSL certificates on nodes 'ant8', 'bee8'...
bee8: Success
ant8: Success
Sending 'corosync.conf' to 'ant8', 'bee8'
ant8: successful distribution of the file 'corosync.conf'
bee8: successful distribution of the file 'corosync.conf'
Cluster has been successfully set up.

[ant8 ~] $ ls -l /etc/corosync/authkey
-r--------. 1 root root 256 Aug 29 13:23 /etc/corosync/authkey

[ant8 ~] $ pcs cluster start --all --wait
ant8: Starting Cluster...
bee8: Starting Cluster...
Waiting for node(s) to start...
ant8: Started
bee8: Started

[ant8 ~] $ systemctl status corosync
● corosync.service - Corosync Cluster Engine
   Loaded: loaded (/usr/lib/systemd/system/corosync.service; disabled; vendor preset: disabled)
   Active: active (running) since Thu 2019-08-29 13:24:05 CEST; 28s ago
   ...
Comment 6 errata-xmlrpc 2019-09-10 13:13:20 UTC 
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, 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-2019:2701
Note You need to log in before you can comment on or make changes to this bug.