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. In this case, NetBackup operator reconciler loop is invoked after every 10 hours. If you want to reflect the changes and invoke the NetBackup operator reconciler loop immediately, delete and reapply the primary server or media server CR.
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:
https://docs.microsoft.com/en-us/azure/aks/concepts-storage#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.
If it is primary server CR, use the kubectl delete -f <environment.yaml> command, or if it is media server CR, edit the Environment CR by removing the media server section in the
environment.yaml.Note:
To reuse the mediaServer section information, you must save it and apply the yaml again with the new changes using the kubectl apply -f <environment.yaml> command.
- Apply the CR again.
If it is primary server CR then reapply it using the kubectl apply -f <environment.yaml> command or if it is media server CR, add mediaServer section that was deleted earlier with required data in
environment.yamland reapply it using the kubectl apply -f <environment.yaml> command.