Release notes
Known issues
Suggest changes
PDFs
Known issues identify problems that might prevent you from using this release of the product successfully.
The following known issues affect the current release:
App backups and snapshots fail if the volumesnapshotclass is added after a cluster is managed
Backups and snapshots fail with a UI 500 error in this scenario. As a workaround, refresh the app list.
App clones fail after an application is deployed with a set storage class
After an application is deployed with a storage class explicitly set (for example, helm install …-set global.storageClass=netapp-cvs-perf-extreme), subsequent attempts to clone the application require that the target cluster have the originally specified storage class.
Cloning an application with an explicitly set storage class to a cluster that does not have the same storage class will fail. There are no recovery steps in this scenario.
Managing a cluster with Astra Control Center fails when kubeconfig file contains more than one context
You cannot use a kubeconfig with more than one cluster and context in it. See the knowledgebase article for more information.
A monitoring pod can crash in Istio environments
If you pair Astra Control Center with Cloud Insights in an Istio environment, the telegraf-rs pod can crash. As a workaround, perform the following steps:
-
Find the crashed pod:
kubectl -n netapp-monitoring get pod | grep Error
You should see output similar to the following:
NAME READY STATUS RESTARTS AGE telegraf-rs-fhhrh 1/2 Error 2 (26s ago) 32s
-
Restart the crashed pod, replacing
<pod_name_from_output>with the name of the affected pod:kubectl -n netapp-monitoring delete pod <pod_name_from_output>
You should see output similar to the following:
pod "telegraf-rs-fhhrh" deleted
-
Verify that the pod has restarted, and is not in an Error state:
kubectl -n netapp-monitoring get pod
You should see output similar to the following:
NAME READY STATUS RESTARTS AGE telegraf-rs-rrnsb 2/2 Running 0 11s
App data management operations fail with Internal Service Error (500) when Astra Trident is offline
If Astra Trident on an app cluster goes offline (and is brought back online) and 500 internal service errors are encountered when attempting app data management, restart all of the Kubernetes nodes in the app cluster to restore functionality.