PowerProtect Data Manager 19.15 Kubernetes User Guide

PowerProtect Data Manager uses the OADP operator to deploy Velero on OpenShift.

Perform the following steps to diagnose the problem.

1. Verify that the OADP operator pod is running in the velero-ppdm namespace by running the command oc get pod -n velero-ppdm -l name=oadp-operator.
   1. If no pods are listed, verify that the cluster role bound to the service account used by the powerprotect-controller has all of the required privileges for operators.coreos.com, oadp.openshift.io and konveyor.openshift.io API groups. Use the command oc get clusterrolebinding powerprotect:cluster-role-binding to identify the cluster role being used.
   2. Review the logs of the Powerprotect controller pod by running the command oc logs <poweprotect-controller pod name> -n powerprotect
   3. Review the events in the velero-ppdm namespace by running the command oc get events -n velero-ppdm
2. Verify that the operator group oadp-operator was created properly in the velero-ppdm namespace by running the command oc get operatorgroup -n velero-ppdm -o yaml
3. Verify that the subscription oadp-operator was created properly in the velero-ppdm namespace by running the command oc get subscription -n velero-ppdm -o yaml
4. Verify that the install plan of OADP version 0.4.2 was approved properly in the velero-ppdm namespace by running the command oc get ip -n velero-ppdm.
   NOTE:The APPROVED field of the CVS oadp-operator.v0.4.2 should be set to true. If an install plan from a later version appears, the APPROVED field for these versions should be set to false.
5. Verify that the Velero pod is running in the velero-ppdm namespace by running the command oc get pod -n velero-ppdm -l component=velero, and review the events in the velero-ppdm namespace by running the command oc get events -n velero-ppdm .