So based on logs here - it is very difficult to ascertain what exactly failed. We log sparingly in production and hence it is almost impossible to tell at this point I think. Is customer open to running a different version of binary in a pod with more logs, to track down exact code that is throwing the error?
Hi Hemant, I'll get back to the customer asking if that would be possible and will let you know.
Hi Hemant, The customer got back to us saying they're willing to use the binary on debug mode to help us narrow down their issue. I'll wait for further instructions from your side to do that, feel free to ask for any information needed to troubleshoot it as well. Best regards,
Can you create following pod in openshift-cluster-storage-operator namespace: apiVersion: "v1" kind: "Pod" metadata: name: "debug-pod" labels: name: "debug-pod" spec: containers: - name: "debug-pod" image: "quay.io/gnufied/vsphere-problem-detector:debug-sep23" args: - start - --v=4 serviceAccountName: vsphere-problem-detector-operator And paste me output of logs? feel free to scrub out any vcenter/confidential information .
https://github.com/openshift/vsphere-problem-detector/pull/57
Thanks for the update and your work here, Hemant. I've updated the customer.
Hi, Customer got back to us saying their Datastore does not belong to a Datastore cluster: >The datastores used in the Openshift installation and by the affected storageclass are not inside a datastore cluster. The entity that contains these datastores is the datacenter object of the vcenter. These DS are marked with a label that identifies which DS belong to the storage policy. > >Please, tell me how should I proceed to have correctly configured the storage in vmware. I have followed the official documentation and I do not see that any requirement has been breached. Is there any log where it says the Datastore belongs to a Datastore cluster? Thanks,
Hi @HemantKumar , could you please provide us with further information where the logs said that the datastore belongs to a datastore cluster? Customer mentioned it's not part of a datastore cluster. >The datastores used in the Openshift installation and by the affected storageclass are not inside a datastore cluster. The entity that contains these datastores is the datacenter object of the vcenter. These DS are marked with a label that identifies which DS belong to the storage policy. >Please, tell me how should I proceed to have correctly configured the storage in vmware. I have followed the official documentation and I do not see that any requirement has been breached. Thanks,
Reproduced on 4.9.0-rc.4: I0930 08:09:26.516490 1 datastore.go:107] CheckStorageClasses: thin-copy: ServerFaultCode: InvalidProperty I0930 08:09:26.549516 1 datastore.go:124] CheckStorageClasses checked 3 storage classes, 1 problems found I0930 08:09:26.549546 1 operator.go:241] CheckStorageClasses failed: StorageClass thin-copy: ServerFaultCode: InvalidProperty Verified passed on 4.10.0-0.nightly-2021-09-30-154054, it shows the message which not caused by storageclass. I1001 03:04:22.578305 1 datastore.go:187] unable to list policy datastores: getPolicyDatastores: error listing datastores: ServerFaultCode: InvalidProperty I1001 03:04:22.578334 1 datastore.go:124] CheckStorageClasses checked 3 storage classes, 0 problems found I1001 03:04:22.578343 1 vsphere_check.go:217] CheckStorageClasses passed
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 (Moderate: OpenShift Container Platform 4.10.3 security update), 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/RHSA-2022:0056