Bug 1994035

Summary:	SNO: LSO diskmaker pod using excessive cpu
Product:	OpenShift Container Platform	Reporter:	browsell
Component:	Storage	Assignee:	Rohan CJ <rojoseph>
Storage sub component:	Local Storage Operator	QA Contact:	Chao Yang <chaoyang>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	aos-bugs, hekumar, jsafrane, keyoung, rojoseph
Version:	4.8
Target Milestone:	---
Target Release:	4.9.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Frequency at which Local Storage Operator inspects newly added block devices has been lowered to 60 seconds to lower its CPU consumption.	Story Points:	---
Clone Of:
Clones:	2006698 (view as bug list)		Environment:
Last Closed:	2021-10-18 17:46:26 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:	2006698

Comment 1 Jan Safranek 2021-08-17 14:42:13 UTC

Assigning to Santosh for initial triage. Feel free to assign to another person. In general, LSO should be less noisy and use informers for the API objects and poll local devices less frequently - after startup, a node should be fairly stable and devices don't appear/disappear that often.

Comment 2 Rohan CJ 2021-08-27 10:34:58 UTC

Can watch events based on udevadm monitor instead of polling.

Comment 6 Chao Yang 2021-09-08 09:14:32 UTC

E0908 09:11:36.587306  495048 reconcile.go:520] unable to add disk-id /dev/vg00/pv003 to local disk pool: unable to find device at path /dev/vg00/pv003: lstat /dev/vg00/pv003: no such file or directory
E0908 09:12:36.674129  495048 reconcile.go:520] unable to add disk-id /dev/vg00/pv003 to local disk pool: unable to find device at path /dev/vg00/pv003: lstat /dev/vg00/pv003: no such file or directory

passed with local-storage-operator.4.9.0-202109071344

Comment 8 errata-xmlrpc 2021-10-18 17:46:26 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