Bug 1877001

Summary:	Suggested backport: avoid excessive volume warnings in logs
Product:	OpenShift Container Platform	Reporter:	Elana Hashman <ehashman>
Component:	Storage	Assignee:	Jan Safranek <jsafrane>
Storage sub component:	Kubernetes	QA Contact:	Qin Ping <piqin>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	unspecified	CC:	aos-bugs, jsafrane
Version:	4.4
Target Milestone:	---
Target Release:	4.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Reduced log noise when changing fsGroup of a small volume.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 16:38:55 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:

Description Elana Hashman 2020-09-08 16:57:25 UTC

This went into upstream Kubernetes but I understand from https://issues.redhat.com/browse/OCPPLAN-4276 that we are not proactively taking upstream backports/patch release fixes.

I have seen this spamming kubelet logs on a number of 4.4.x OCP clusters in production so if it's easy to take the backport I'd suggest integrating it: https://github.com/kubernetes/kubernetes/pull/94432

It will prevent the logs from being spammed with the message "Setting volume ownership for %s and fsGroup set. If the volume has a lot of files then setting volume ownership could be slow, see https://github.com/kubernetes/kubernetes/issues/69699" across many volumes; the log entry will only land if it takes >30s.

Comment 5 Qin Ping 2020-09-15 07:17:39 UTC

Verified with: 4.6.0-0.nightly-2020-09-14-221526

Comment 8 errata-xmlrpc 2020-10-27 16:38:55 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 (OpenShift Container Platform 4.6 GA Images), 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-2020:4196