The CVO is in failed status and panic frequently after the upgrade
Applies to
- NetApp Cloud Volume ONTAP(CVO) 9.7
- Microsoft Azure
Issue
The CVO is in failed status and panic frequently happens after upgrade to ONTAP9.7P22
- CVO working environment error:
Failed - Show Failure Message
Cloud Manager cannot communicate with Cloud Volumes
ONTAP because there is no connectivity or because the Cloud Volumes ONTAP system is not available.
- EMS log of panic :
Wed Jul 12 07:39:02 +0000 [nodename-01: nodewatchdog: nodewatchdog.node.panic:alert]: Data ONTAP has experienced a serious internal error: Process vldb unresponsive for 210 seconds. This might cause the node experiencing the problem to become unresponsive to data access. The node has been panicked to prevent this condition from continuing.
Wed Jul 12 07:39:02 +0000 [nodename-01: nodewatchdog: sk.panic:alert]: Panic String: Process vldb unresponsive for 210 seconds in process nodewatchdog on release 9.7P22 (C)
Wed Jul 12 07:39:02 +0000 [nodename-01: nodewatchdog: coredump.shutdown.trace:notice]: coredump shutdown times: kmod dumper start 7, panic_info set 14, sf_dumpcore sent 15, sparecore id sent 59, fmot_outage info sent 0, disk_dump_start done 0, coredump begin 24 (all in msec).