Wrong EFS ID is provided in environment.yaml file
Following error message is displayed when wrong EFS ID is provided in
environment.yamlfile:
"samples/environment.yaml": admission webhook "environment2-validating-webhook.netbackup.veritas.com" denied the request: Environment change rejected by validating webhook: EFS ID provided for Catalog storage is not matching with EFS ID of already created persistent volume for Primary servers Catalog volume. Old EFS ID fs-0bf084568203f1c27 : New EFS ID fs-0bf084568203f1c29
Above error can appear due to the following reasons:
During upgrade, if EFS ID provided is different from the EFS ID used in the previous version deployment.
During fresh deployment, if user manually creates PV and PVC with EFS ID and provides different EFS ID in
environment.yamlfile.
To resolve this issue, perform the following:
- Identify the correct EFS ID used for PV and PVC.
Previously used EFS ID can be retrieved from PV and PVC by using the following steps:
kubectl get pvc -n <namespace>
From the output, copy the name of catalog PVC which is of the following format:
catalog-<resource name prefix>-primary-0
Describe catalog PVC using the following command:
kubectl describe pvc <pvc name> -n <namespace>
Note down the value of Volume field from the output.
Obtain the PV name using the following command:
kubectl get pv -n <namespace>
Describe PV using the following command:
kubectl describe pv <value of Volume obtained from above step>
Note down the value of VolumeHandle field from the output. This is the EFS ID used previously.
- Provide correct EFS ID in the
environment.yamlfile and apply theenvironment.yamlusing the following command:kubectl apply -f environment.yaml