This document explains how to resolve issues when reporting a faulty host. It also documents some known issues for this API.
Known issues
This page describes known issues that you might run into while using the faulty
node API. When a problem occurs, your VMs might return a
FAILED_WITH_UNEXPECTED_STATUS or they might stay in a stopped state.
Duplicate calls for the same VM causes the operation to fail
If you call the API more than once on the same VM instance prior to the completion of previous calls, duplicate calls will fail.
Workaround: You must wait until the operation completes before trying to re-run the call. If the operation looks stuck, restart the VM before you make another call to the API.
INTERNAL_ERROR returned while the reportHostAsFaulty operation is in progress
If a VM is deleted while the reportHostAsFaulty operation is in progress,
then an INTERNAL_ERROR might be returned and the reportHostAsFaulty
operation fails.
Workaround: No workaround is available. Ensure that the operation completes before you try to delete a VM.
Error messages
The faulty node API might return one of the following error messages.
VM state not supported
Error message:
INSTANCE_SHOULD_BE_RUNNING
Resolution: Ensure that the VM is in a running state. This message is returned if the VM is in any other state.
Machine type incorrect
Error message:
MACHINE_TYPE_NOT_SUPPORTED
Resolution: This method is supported only on A4, A3 High, A3 Mega and A3 Ultra VM families that are part of a reserved block of capacity. Reserved blocks must be created for you by a technical account manager (TAM). Calling this API on any other VM instance will fail with this error.
Fault reason is missing
Error message:
FAULT_REASONS_EMPTY_SHOULD_BE_SPECIFIED
Resolution: faultReasons is a required field. The faulty node API
returns this error when you omit the faultReasons field. To fix this, restart
the VM and specify a value for faultReasons.
VM not a part of a reservation block
Error message:
INSTANCES_WITHOUT_RESERVATION_NOT_SUPPORTED
Resolution: This method is only supported on A4, A3 High, A3 Mega, and A3 Ultra VMs that are part of a reserved block of capacity. Reserved blocks must be created for you by a technical account manager (TAM). Running this method on a VM that is not part of a block reservation leads to this error.
Rate limit exceeded
Error message:
RATE_LIMIT_EXCEEDED
Resolution: You have exceeded the allowed limits for calling this method or Google doesn't have enough capacity to fulfill the request.