Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-23067

vSphere problem detector showing errors related to vsphere objects from another zone

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • 4.15.0
    • 4.13.z
    • Storage
    • None
    • No
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      vSphere problem detector is showing below messages when storage co is checked: 
      ~~~
        - lastTransitionTime: "2023-10-17T23:37:35Z"
          message: |-
            DefaultStorageClassControllerAvailable: StorageClass provided by supplied CSI Driver instead of the cluster-storage-operator
            VSphereProblemDetectorControllerAvailable: [unable to find VM by UUID 4233d613-8b46-3a74-fdbf-8433e3268730, unable to find VM by UUID 42338985-417b-bf02-17c2-ca16d0b98a0d, unable to find VM by UUID 42337e47-560b-d04d-cccd-a697e69781dd, unable to find VM by UUID 4233eedf-48bb-73b3-2036-3584abda0058, StorageClass sc-av15: couldn't find Datastore given URL "ds:///vmfs/volumes/645ceaee-a-a-72262220002a/";
            VSphereProblemDetectorControllerAvailable: StorageClass thin-csi: storage policy openshift-storage-policy-a-openshift-zj4m6: failed to access datastore A_Openshift: datastore 'A_Openshift' not found]
            VSphereCSIDriverOperatorCRAvailable: All is well
          reason: AsExpected
          status: "True"
          type: Available
      ~~~
      
      CheckNodeDiskUUID check is passed only for the VMs present in datacenter where vsphere-problem-detector pod is scheduled. 
      The UUIDs are matching with config files actually present on VMs. 
      Also, the datastore check is failed for the datastore from another datacenter configured in different zone.
      vSphere user configured at OCP has access to datastore, VMs for which errors are shown.  

      Version-Release number of selected component (if applicable):

      OCP 4.13.17

      How reproducible:

       

      Steps to Reproduce:

      1.
      2.
      3.
      

      Actual results:

      Errors from vsphere problem detector pod are generated. 

      Expected results:

      vsphere problem detector should pass the checks for the objects from different zone configured.

      Additional info:

       

              hekumar@redhat.com Hemant Kumar
              rhn-support-adeshpan Aditya Deshpande
              Wei Duan Wei Duan
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: