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 2137377 - There are some Systemd failed condition check messages that occur in dmesg on RHEL 9.0.
Summary: There are some Systemd failed condition check messages that occur in dmesg on...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: systemd
Version: 9.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: Frantisek Sumsal
URL:
Whiteboard:
: 2139139 (view as bug list)
Depends On: 2138081
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-24 16:56 UTC by lei1.jiang@intel.com
Modified: 2023-05-09 10:33 UTC (History)
6 users (show)

Fixed In Version: systemd-252-3.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-09 08:21:58 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
8901D03_DNP_RHEL9.0_dmesg_fail (1.23 KB, text/plain)
2022-10-24 16:56 UTC, lei1.jiang@intel.com 		no flags Details
8901D03_FCP_RHEL9.0_dmesg_fail (824 bytes, text/plain)
2022-10-24 16:57 UTC, lei1.jiang@intel.com 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github systemd systemd pull 24523 0 None Merged tree-wide: Use "unmet" for condition checks, not "failed" 2022-10-25 11:10:34 UTC
Red Hat Issue Tracker PLMCORE-4252 0 None None None 2022-11-02 11:42:04 UTC
Red Hat Issue Tracker RHELPLAN-137457 0 None None None 2022-10-24 17:00:02 UTC
Red Hat Product Errata RHBA-2023:2531 0 None None None 2023-05-09 08:23:17 UTC

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
Note You need to log in before you can comment on or make changes to this bug.