ONTAP Operating System Issues
ONTAP Operating System Issues
Highest rated
(rating)- CONTAP-108899: Upgrade stopped due to an NVRAM log not synchronized
- CONTAP-122618: vifmgr.clusterBD.Partition EMS event observed on switchless cluster
- CONTAP-248510: Vserver delete fails with "Internal error. Failed to delete network configurations for Vserver"
- CONTAP-258788: Scheduled configuration backup upload fails via PUT over HTTPS
- CONTAP-208827: Performance degradation is occurring due to high utilization of the root aggregate
- CONTAP-266869: CVE-2024-6387 OpenSSH Vulnerability in ONTAP 9
- CONTAP-170136: FAS8200 and AFF A300 systems might experience non-responsive CPUs followed by multiple watchdog controller disruptions
- CONTAP-47858: Configuration replication service might fail in a MetroCluster configuration
- CONTAP-30152: Feature request: Add secure SMTP support for ONTAP event config
- CONTAP-277483: Schedules missing after SVM-DR migration to MetroCluster
- CONTAP-277809: vifmgr reboots when ONTAP REST API retrieves port information
- CONTAP-361979: Vserver in a MetroCluster config goes to degraded state due to publickey failing to replicate
- CONTAP-265323: Configuration backups fail due to small scratch space available
- CONTAP-349530: Keys managed by External KMIP Server may not be restored during reboot
- CONTAP-391039: New 9.17.1 authentication failed errors seen since upgrade
Recently updated
(date updated)- CONTAP-640978: Vserver online callbacks can be dropped
- CONTAP-363115: IPsec: wildcard policy delete won't delete all IPsec SAs
- CONTAP-429258: DRCGFM: Apply failed for Object: publickey_ui Reason: duplicate entry
- CONTAP-277483: Schedules missing after SVM-DR migration to MetroCluster
- CONTAP-190519:
- CONTAP-203095: Snapmirror Synchronous relationship getting "Transfer failed.(Volume access error(File too large))"
- CONTAP-170030: netif.fatal.err:ALERT: The network device in slot 0 encountered fatal error e0a/e0b
- CONTAP-168265: RFE: Implement graceful takeover during Freeze/migrateOnHostMaintenance events in GCP in a similar way like in Azure
- CONTAP-63613:
- CONTAP-765778: Node fails to boot after upgrading from ONTAP 9.16.1P7 to 9.16.1P12
- CONTAP-587877: ONTAP cluster node reboots unexpectedly during the ONTAP upgrade.
- CONTAP-699188: After upgrading ONTAP from 9.15 to 9.16 Multi-Admin Verification (MAV) stopped sending approval emails to multiple email addresses
- CONTAP-769272: REST API GET /api/private/cli/vserver/export-policy/check-access returns incomplete results in ONTAP 9.16.1
- CONTAP-703971: Amazon FSx for NetApp ONTAP system node is unable to boot up after failover
- CONTAP-542488: Surviving node is unable takeover to regain quorum when Cluster Network and HA Interconnect are unavailable
Recently added
(date created)- CONTAP-809300: systemshell cp command fails when destination path has a trailing slash
- CONTAP-755750: System Manager cannot protect a volume from a newer ONTAP cluster to an older one
- CONTAP-749983: Consistency group Snapshot restore does not warn that newer Snapshots will be deleted
- CONTAP-711693: KMIP boot messages can incorrectly indicate successful key retrieval
- CONTAP-350207: SNMP capability-check messages can cause excessive messages.log rotation
- CONTAP-278887: Azure CVO Page Blob I/O timeout may cause a node reboot
- CONTAP-730134: Upgrade broadcast domain misconfiguration check is a warning
- CONTAP-644212: Max volume count higher than expected for Amazon FSx for NetApp ONTAP cluster
- CONTAP-688256: repeated unexpected reboots due to mutex exhaustion
- CONTAP-701546: Bug public information is not yet available.
- CONTAP-747860: Inconsistencies with MAV rule behaviour for "volume modify" opearation with "-snapshot-policy" parameter
- CONTAP-772813: Sync snapmirror relationship status was reported wrongly as "Insync" lead to loss of data during reverse resync
- CONTAP-765778: Node fails to boot after upgrading from ONTAP 9.16.1P7 to 9.16.1P12
- CONTAP-587877: ONTAP cluster node reboots unexpectedly during the ONTAP upgrade.
- CONTAP-681839: ONTAP I/O module hot-swap can fail while hardware TLS offload sessions are active