CVO in GCP environment reboots due to heartbeat loss
- Views:
- 840
- Visibility:
- Public
- Votes:
- 0
- Category:
- cloud-volumes-ontap-cvo
- Specialty:
- cloud_provider_agnostic
- Last Updated:
Applies to
- NetApp Cloud Volumes ONTAP (CVO)
- High Availability (HA)
- Google Cloud Provider (GCP)
- Event Management System (EMS)
Issue
- CVO VM reboots unexpectedly
- EMS logs show the following message:
cf_main: cf.fsm.takeover.noheartbeat:ALERT]: Failover monitor: Takeover initiated after no heartbeat was detected from the partner node.
- GCP log query show
compute.instance.hostErrorandcompute.instance.automaticRestartmessages
