Resolving an issue where the Storage class does not exist
The Config-Checker checks if the storage class name given in primary server/media server CR is available in the cluster.
The following error is displayed:
Error: ERROR Storage class with the <storageClassName> name does not exist.
After fixing this error, primary server or media server CR does not require any changes. If you want to reflect the changes and invoke the NetBackup operator reconciler loop immediately, pause the reconciler of the custom resource by changing the paused: false value to paused: true in the primaryServer or mediaServer section by using the following command:
kubectl edit Environment <environment-CR-name> -n <namespace>
Again change the value to paused: false (un pause) in the primaryServer or mediaServer section by using the following command:
kubectl edit Environment <environment-CR-name> -n <namespace>
To resolve an issue where the Storage class does not exist
- Create storage class with the same name given in primary server or media server CR with ReclaimPolicy as Retain in the cluster.
To create storage class, refer to the following link:
Azure Kubernetes Service storage classes
Amazon Elastic Kubernetes Service storage classes
In this scenario, no change in primary server or media server CR is required. As a result, reconciler loop is not invoked immediately.
- To invoke the reconciler loop again, delete the respective CR by changing the paused: false value to paused: true in the primaryServer or mediaServer section in environment CR by using the following command:
kubectl edit Environment <environment-CR-name> -n <namespace>
Save the changes.
Again change the value to paused: false in the primaryServer or mediaServer section by using the following command:
kubectl edit Environment <environment-CR-name> -n <namespace>
Save the changes.