-
Bug
-
Resolution: Done
-
Normal
-
4.18
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
In Progress
-
Release Note Not Required
-
N/A
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-60784. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-60535. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-59319. The following is the description of the original issue:
—
Description of problem:
vsphere problem detector fails with: VSphereProblemDetectorControllerAvailable: [failed to find VM for node soca-j27gj-gv2-infra-x5zg9: unable to determine vcenter for node abcd-j27gj-123-infra-x5zg9...
Version-Release number of selected component (if applicable):
4.18.10
How reproducible:
All the time in user environment
Steps to Reproduce:
1.
Actual results:
vsphere-problem-detector failing and showing errors in clusteroperator for storage
Expected results:
vsphere-problem-detector showing no errors.
Additional info:
- clones
-
OCPBUGS-60784 [4.18] vSphere Problem Detector: Unable to determine vCenter for VM
-
- Closed
-
- is blocked by
-
OCPBUGS-60784 [4.18] vSphere Problem Detector: Unable to determine vCenter for VM
-
- Closed
-
- is duplicated by
-
OCPBUGS-60072 vSphere Problem Detector: Unable to determine vCenter for VM
-
- Closed
-
- links to