-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
4.19
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
None
-
Rejected
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
[vsphere-problem-detector] morbidly logged "VSphereProblemDetectorController reconciliation failed: obj.Name must be provided to Apply"
Version-Release number of selected component (if applicable):
4.19.0-0.nightly-2025-03-20-062111
How reproducible:
Always
Steps to Reproduce:
1. Launch an Openshift cluster on vmware vsphere. 2. Check the vsphere-problem-detector logs under namespace openshift-cluster-storage-operator.
Actual results:
In step2: there's lots of error complain that "VSphereProblemDetectorController reconciliation failed: obj.Name must be provided to Apply" $ oc logs vsphere-problem-detector-operator-f7d744b6c-kzz84|grep 'VSphereProblemDetectorController reconciliation failed: obj.Name must be provided to Apply'|wc -l 6682
Expected results:
In step2: vsphere-problem-detector logs should have no such unexpected errors.
Additional info:
CI logs -> https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/logs/periodic-ci-openshift-release-master-nightly-4.19-e2e-vsphere-ovn-csi/1902607690383757312/artifacts/e2e-vsphere-ovn-csi/gather-extra/artifacts/pods/openshift-cluster-storage-operator_vsphere-problem-detector-operator-ff97c5c9-r6b48_vsphere-problem-detector-operator.log
- duplicates
-
OCPBUGS-53217 logs are being spammed with "E0317 15:28:09.035372 1 base_controller.go:279] "Unhandled Error" err="VSphereProblemDetectorController reconciliation failed: obj.Name must be provided to Apply"
-
- Verified
-
- is duplicated by
-
OCPBUGS-53217 logs are being spammed with "E0317 15:28:09.035372 1 base_controller.go:279] "Unhandled Error" err="VSphereProblemDetectorController reconciliation failed: obj.Name must be provided to Apply"
-
- Verified
-