-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.14.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
As per RFE-6939 (https://issues.redhat.com/browse/RFE-6939), it was not viable to request a new feature adoption so OCP can identify new log levels so this bug is for csi-provisioner to see how to make it a bit less noisy in terms of logs.
Version-Release number of selected component (if applicable):
OCP 4.14.33
How reproducible:
Many errors observed after 4.14 branch are repeated continuosly E1016 09:51:38.421016 1 controller.go:1007] error syncing volume "pvc-x-1b8f-48fd-94b7-3285167c1a4a": persistentvolume pvc-fcc8d785-1b8f-48fd-94b7-3285167c1a4a is still attached to node x.comE1016 09:51:34.679365 1 controller.go:1512] delete "pvc-x-25fc-430d-89c9-2cfc44041e06": volume deletion failed: persistentvolume pvc-759c3aab-25fc-430d-89c9-2cfc44041e06 is still attached to node x.com Build clusters where with every build couple of PVC gets created and destroyed are the main reason.
Actual results:
Logs are too noisy, should not be repeated constantly if possible.
Expected results:
Logs to not be repeated in a cycle.
Additional info:
Customer has blacklisted whole logs for this project for hundreds of cluster loosing visibility, no filtering allowed.
- is related to
-
RFE-6939 RFE - Add configuration option to control VMware vSphere CSI driver Logging lower levels
-
- Closed
-