Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1993444

Summary:	NFD - cstate detection enabled on s390x
Product:	OpenShift Container Platform	Reporter:	jschinta
Component:	Multi-Arch	Assignee:	jschinta
Status:	CLOSED ERRATA	QA Contact:	Douglas Slavens <dslavens>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.9	CC:	danili
Target Milestone:	---
Target Release:	4.9.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-10-18 17:46:20 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:
Bug Blocks:	1980363

Description jschinta 2021-08-13 06:59:00 UTC

Description of problem:
When running NFD on OCP 4.9 you can see in the logs that it is trying and failling to detect cstate on s390x.

I0812 09:08:40.750590       1 nfd-worker.go:422] configuration file "/etc/kubernetes/node-feature-discovery/nfd-worker.conf" parsed
I0812 09:08:40.750646       1 nfd-worker.go:457] worker (re-)configuration successfully completed
I0812 09:08:40.750690       1 nfd-worker.go:468] starting feature discovery...
E0812 09:08:40.750897       1 cpu.go:150] failed to detect cstate: cannot get driver for cpuidle: open /host-sys/devices/system/cpu/cpuidle/current_driver: no such file or directory
I0812 09:08:40.756227       1 nfd-worker.go:480] feature discovery completed
I0812 09:08:40.756258       1 nfd-worker.go:550] sending labeling request to nfd-master

Version-Release number of selected component (if applicable):
OCP 4.9.0-0.nightly-s390x-2021-08-04-204925
NFD 4.9.0-202107210242

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
Trying and failing to detect cstate

Expected results:
Not trying to detect cstate on s390x.

Additional info:

Comment 1 jschinta 2021-08-13 07:43:31 UTC

I created an upstream PR for this one https://github.com/kubernetes-sigs/node-feature-discovery/pull/571

You can assign the bug to me.

Comment 2 Dan Li 2021-08-13 14:55:00 UTC

Setting reviewed-in-sprint flag as the PR is ongoing. Assigning to Jan

Comment 4 Dan Li 2021-08-23 13:44:36 UTC

Hi Jan, could you provide a severity for this bug?

Comment 5 jschinta 2021-08-23 13:55:29 UTC

Downstream PR https://github.com/openshift/node-feature-discovery/pull/51

Comment 6 Dan Li 2021-08-30 16:43:25 UTC

Hi Jan, do you think this bug will be resolved before the end of this sprint (September 4th)? If not, I'd like to set the "reviewed-in-sprint" flag.

Comment 7 jschinta 2021-08-31 12:12:38 UTC

Hi Dan,

Eduardo created the Version bump including the fix for this BZ, so the new PR is https://github.com/openshift/node-feature-discovery/pull/52

I do not know if it will be merged this week or not. I would say set the flag to be safe.

Comment 9 jschinta 2021-09-01 08:17:15 UTC

The PR https://github.com/openshift/node-feature-discovery/pull/52 has been merged.

Comment 11 jschinta 2021-09-09 07:15:24 UTC

Verified with NFD Operator 4.9.0-202109071344

Comment 13 errata-xmlrpc 2021-10-18 17:46: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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security 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/RHSA-2021:3759