Bug 2137377

Summary: There are some Systemd failed condition check messages that occur in dmesg on RHEL 9.0.
Product: Red Hat Enterprise Linux 9 Reporter: lei1.jiang <lei1.jiang>
Component: systemdAssignee: systemd-maint
Status: CLOSED ERRATA QA Contact: Frantisek Sumsal <fsumsal>
Severity: high Docs Contact:
Priority: unspecified    
Version: 9.0CC: dtardon, fkrska, jamacku, lei1.jiang, pragyansri.pathi, systemd-maint-list
Target Milestone: rcKeywords: Improvement, TestOnly, Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: systemd-252-3.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-09 08:21:58 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:
Bug Depends On: 2138081    
Bug Blocks:    
Attachments:
Description Flags
8901D03_DNP_RHEL9.0_dmesg_fail
none
8901D03_FCP_RHEL9.0_dmesg_fail none

Description lei1.jiang@intel.com 2022-10-24 16:56:50 UTC
Created attachment 1920027 [details]
8901D03_DNP_RHEL9.0_dmesg_fail

Description of problem:
There are some Systemd failed condition check messages that occur in dmesg on RHEL 9.0.

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

How reproducible:


Steps to Reproduce:
1.Installed RHEL 9.0.
2.After installed successfully, Check dmesg with the command “dmesg | grep –i fail.”
Failed. >> There are some Systemd failed condition check messages that occur in dmesg


Actual results:
There are some Systemd failed condition check messages that occur in dmesg on RHEL 9.0.

Expected results:
There without any failed message occur in dmesg on RHEL 9.0.

Additional info:
RHEL 8.6 without this issue.
Reproducibility: 100%

Configuration:
CPU : Intel_Sapphire Rapids_MCC_6458Q_3.1GHZ_S2_350W_28C_Q1VZ (MCC) *2
DIMM :Micron 4800 2Rx8 32G *16 
BIOS: 8901.D03_prd
BMC : 1.30-0-gf45637-3cc10000-pfr-oob
FRU: N/A
ME : 06.00.03.0256.0
PCH :Emmitsburg QS-B1 QYKV 
BMC chip : AST2600-A3
MB : M44241-400 BQDP21700211 (DNP Silver FAB4) 
CPLD : DNP_v3.0(file name: pfr_dnp_10M50-_v3p0.pof)
NVM : 8.7
ISD   2022.2226.0-nda
Cscripts Rev2232-6000-Build2585
KCS mode : Provisioning mode
Linux_qat20.l.0.9.5-00001_v2

CPU : Intel_Sapphire Rapids_MCC_6458Q_3.1GHZ_S2_350W_28C_Q1VZ (MCC) *2
DIMM : Micron 32GB 2Rx8 4800 * 2(CPU0 A1 CPU1 A1)
BIOS: 8901.D03_prd
BMC : 1.30-0-gf45637-3cc10000-pfr-oob
FRU: N/A
ME : 06.00.03.0256.0
PCH: Emmitsburg QS-B1 QYKV 
BMC chip: AST2600-A
MB: M36359-300 BQFX22100011 (FCP Silver L6 8*2.5 2U 2208)
CPLD : FCP_v2.2 file name: pfr_fcp_10M50 _v2p2.bin)
ISD   2022.2226.0-nda
Cscripts Rev2232-6000-Build2585
KCS mode: Provisioning mode
Linux_qat20.l.0.9.5-00001_v2

Comment 1 lei1.jiang@intel.com 2022-10-24 16:57:38 UTC
Created attachment 1920028 [details]
8901D03_FCP_RHEL9.0_dmesg_fail

Comment 2 David Tardon 2022-10-25 11:10:15 UTC
These are not failures. It means the conditions were not satisfied. (That they are not failures is also indicated by the fact that thay are logged at level info.) Anyway, upstream has already changed the wording to avoid false alarms like this.

Comment 3 David Tardon 2022-11-02 07:27:56 UTC
*** Bug 2139139 has been marked as a duplicate of this bug. ***

Comment 4 lei1.jiang@intel.com 2022-11-02 08:04:11 UTC
ok, thanks.
we can close this issue, thanks for your help.

Comment 7 errata-xmlrpc 2023-05-09 08:21:58 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 (systemd bug fix and enhancement 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/RHBA-2023:2531