To resolve this issue, perform the following:

1. Describe primary pod using the following command:

   kubectl describe <name of primary server pod> -n <namespace>

2. Depending on the following appropriate scenario, fix the error from the output under the Event section:

   • If the event log has an error related to incorrect EFS ID or incorrect format, then update the environment.yaml file with the correct EFS ID and perform the below steps.

     Or

   • If the event log has an error other than the error related to incorrect EFS ID, then analyze and fix the error and perform the below steps.

3. After fixing the error, clean the environment using the following command:

   kubectl delete -k operator/

4. Delete PV and PVC created for primary server only by using the following command:

   kubectl delete envrionment <envrionmentCR-name> -n <namespace>

   Describe the PVC for primary server which has the following format and obtain the corresponding PV name:

   catalog-<resource name prefix of primary>-primary-0
   data-<resource name prefix of primary>-primary-0
   logs-<resource name prefix of primary>-primary-0

   Delete PVC and PV names using the following commands: For PVC: kubectl delete pvc <pvc name> -n <namespace> For PV: kubectl delete pv <pv name>

   • PVC: kubectl delete pvc <pvc name> -n <namespace>

   • PV: kubectl delete pv <pv name>

5. Deploy NetBackup operator again and then apply the environment.yaml file.