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
-
App data management operations fail with Internal Service Error (500) when Astra Trident is offline
-
In-place restore operations to ontap-nas-economy storage classes fail
-
Restoring from a backup when using Kerberos in-flight encryption can fail
-
Backup data remains in bucket after deletion for buckets with expired retention policy
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.
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.
In-place restore operations to ontap-nas-economy storage classes fail
If you perform an in-place restore of an application (restore the app to its original namespace), and the app's storage class uses the ontap-nas-economy driver, the restore operation can fail if the snapshot directory is not hidden. Before restoring in-place, follow the instructions in Enable backup and restore for ontap-nas-economy operations to hide the snapshot directory.
Restoring from a backup when using Kerberos in-flight encryption can fail
When you restore an application from a backup to a storage backend that is using Kerberos in-flight encryption, the restore operation can fail. This issue does not affect restoring from a snapshot or replicating the application data using NetApp SnapMirror.
|
When using Kerberos in-flight encryption with NFSv4 volumes, ensure that the NFSv4 volumes are using the correct settings. Refer to the NetApp NFSv4 Domain Configuration section (page 13) of the NetApp NFSv4 Enhancements and Best Practices Guide. |
Backup data remains in bucket after deletion for buckets with expired retention policy
If you delete an app's immutable backup after the bucket's retention policy has expired, the backup is deleted from Astra Control but not from the bucket. This issue will be fixed in an upcoming release.