Chapter 11. Using the vSphere Problem Detector Operator

• The checks run every hour.
• If any check fails, the Operator runs the checks again in intervals of 1 minute, 2 minutes, 4, 8, and so on. The Operator doubles the interval up to a maximum interval of 8 hours.
• When all checks pass, the schedule returns to an hour interval.

Prerequisites

• Access to the cluster as a user with the cluster-admin role.

Procedure

• Scale the Operator to 0:

  $ oc scale deployment/vsphere-problem-detector-operator --replicas=0 \
      -n openshift-cluster-storage-operator

Verification

• Verify that the pods have restarted by running the following command:

  $ oc -n openshift-cluster-storage-operator get pod -l name=vsphere-problem-detector-operator -w

  Example output

  NAME                                                 READY   STATUS    RESTARTS   AGE
  vsphere-problem-detector-operator-77486bd645-9ntpb   1/1     Running   0          11s

  The AGE field must indicate that the pod is restarted.

Procedure

• To view the events by using the command line, run the following command:

  $ oc get event -n openshift-cluster-storage-operator \
      --sort-by={.metadata.creationTimestamp}

  Example output

  16m     Normal    Started             pod/vsphere-problem-detector-operator-xxxxx         Started container vsphere-problem-detector
  16m     Normal    Created             pod/vsphere-problem-detector-operator-xxxxx         Created container vsphere-problem-detector
  16m     Normal    LeaderElection      configmap/vsphere-problem-detector-lock    vsphere-problem-detector-operator-xxxxx became leader

• To view the events by using the OpenShift Container Platform web console, navigate to Home Events and select openshift-cluster-storage-operator from the Project menu.

Procedure

• To view the logs by using the command line, run the following command:

  $ oc logs deployment/vsphere-problem-detector-operator \
      -n openshift-cluster-storage-operator

  Example output

  I0108 08:32:28.445696       1 operator.go:209] ClusterInfo passed
  I0108 08:32:28.451029       1 datastore.go:57] CheckStorageClasses checked 1 storage classes, 0 problems found
  I0108 08:32:28.451047       1 operator.go:209] CheckStorageClasses passed
  I0108 08:32:28.452160       1 operator.go:209] CheckDefaultDatastore passed
  I0108 08:32:28.480648       1 operator.go:271] CheckNodeDiskUUID:<host_name> passed
  I0108 08:32:28.480685       1 operator.go:271] CheckNodeProviderID:<host_name> passed

• To view the Operator logs with the OpenShift Container Platform web console, perform the following steps:

  1. Navigate to Workloads Pods.
  2. Select openshift-cluster-storage-operator from the Projects menu.
  3. Click the link for the vsphere-problem-detector-operator pod.
  4. Click the Logs tab on the Pod details page to view the logs.

• The naming conventions require 205 characters of the 255 character limit.
• The datastore name and the cluster ID are determined from the deployment.
• The datastore name and cluster ID are substituted into the preceding pattern. Then the path is processed with the systemd-escape command to escape special characters. For example, a hyphen character uses four characters after it is escaped. The escaped value is \x2d.
• After processing with systemd-escape to ensure that systemd can access the fully qualified path to the VDMK file, the length of the path must be less than 255 characters.