CONTAP-168265 asks for graceful GCP takeover during host maintenance

Primary item: NetApp Knowledge Base via Google News — CONTAP-168265.

What NetApp published

The item is titled “CONTAP-168265: RFE: Implement graceful takeover during Freeze/migrateOnHostMaintenance events in GCP in a similar way like in Azure.” Its specifics are unusually important: it names two Google Compute Engine maintenance signals, limits the requested behavior to GCP, and uses Azure as the comparison point.

It does not say the enhancement has shipped. There is no public fixed-in version, release date, patch number or deployment deadline in the surfaced item. Calling this an announcement of availability would therefore overstate the evidence. There is also no separate press release attached to the RFE; the KB item itself is the official source.

The operational gap the RFE describes

A graceful takeover is a coordinated ONTAP HA action: the surviving partner assumes the affected node’s storage before the maintenance interruption. The requested change is for Cloud Volumes ONTAP to translate advance notice from Google Cloud into that coordinated path, instead of merely encountering the host event as an interruption.

The distinction matters during planned infrastructure work. Google documents migrateOnHostMaintenance as metadata that tells a VM whether live migration is available for a host-maintenance event. A TERMINATE policy means Compute Engine stops the VM; live migration is not universally available. The RFE title’s separate reference to Freeze indicates that operators should not collapse all provider events into one failure mode.

What changes for customers today

• Cloud Volumes ONTAP on GCP: no supported-behavior change is proven yet. Treat the RFE as a visibility signal, not authorization to remove maintenance controls or availability testing.
• Cloud Volumes ONTAP on Azure: the comparison is consistent with NetApp’s public Azure KB, which shows ONTAP receiving scheduled Freeze events and records takeover/giveback symptoms. That evidence explains the requested parity; it is not proof that every Azure event is nondisruptive.
• On-premises ONTAP, StorageGRID and Azure NetApp Files: the item does not announce a change for these products. Azure NetApp Files is a Microsoft-managed service and should not be confused with a customer-managed Cloud Volumes ONTAP HA pair in Azure.
• BlueXP / NetApp Console: no new control, API or workflow is named. Continue to use the management plane for supported lifecycle operations, but do not infer that it can enable CONTAP-168265 before NetApp documents a release.

A practical watch list

1. Look for a fixed-in Cloud Volumes ONTAP release or explicit release-note entry tied to CONTAP-168265.
2. Check whether the implementation covers both GCP single-node and HA deployments; graceful takeover is meaningful only where an HA partner exists.
3. Verify which machine families and maintenance policies emit usable advance notice, and whether local write mode or takeover readiness introduces exclusions.
4. Require documented behavior for event cancellation, repeated notices, giveback and a partner that is not takeover-ready before changing a runbook.

Bottom line

CONTAP-168265 is useful because it makes the desired end state explicit: GCP maintenance notice should trigger a coordinated Cloud Volumes ONTAP takeover in the same broad manner as Azure handling. But the safe reading on 2026-10-12 is requested, not released. Keep existing GCP maintenance and recovery procedures until NetApp publishes a supported version and scope.

Sources: NetApp Knowledge Base / CONTAP-168265 via Google News; NetApp KB — Azure HA rebooted with a scheduled Freeze event; Google Cloud — VM host maintenance behavior.