Troubleshoot the faulty host API

This document explains how to resolve issues that you might encounter when you make a call to the report a faulty host API, as well as the known issues for this API.

Review known issues

When a problem occurs during a repair operation, your virtual machine (VM) instance might display FAILED_WITH_UNEXPECTED_STATUS or remain in the REPAIRING state.

Avoid duplicate calls for the same VM

If you send a request to the report faulty host API more than once on the same VM before the previous operation completes, then Compute Engine rejects the extra requests.

Workaround: Wait until the first report faulty host operation completes before you send another request to the API. If the VM is unresponsive, then restart the VM before you send another request to the API.

Handle INTERNAL_ERROR during reportHostAsFaulty operation

If you delete a VM while the reportHostAsFaulty operation is in progress, then an INTERNAL_ERROR might occur and the reportHostAsFaulty operation fails.

Workaround: No workaround is available. Before you delete a VM, you must verify that the reportHostAsFaulty operation has completed.

Error messages

The report faulty host API might display one of the following error messages.

Unsupported VM state

This error appears when the VM is in an unsupported state.

Error message:

INSTANCE_SHOULD_BE_RUNNING

Resolution: Verify that the VM is in the RUNNING state.

Incorrect machine type

This error appears when the VM uses an unsupported machine type.

Error message:

MACHINE_TYPE_NOT_SUPPORTED

Resolution: The report faulty host API supports only VMs that use A4X, A4, or A3 Ultra machine types.

VM not in a reservation

This error appears when the VM was created without using a reservation.

Error message:

INSTANCES_WITHOUT_RESERVATION_NOT_SUPPORTED

Resolution: Verify that the VM was created by using the reservation-bound provisioning model. To report a faulty host for an A4X, A4, or A3 Ultra VM that uses the flex-start or spot provisioning model, contact your account team.

Fault reason is missing

This error appears when you don't specify the faultReasons field in a report faulty host request.

Error message:

FAULT_REASONS_EMPTY_SHOULD_BE_SPECIFIED

Resolution: The faultReasons field is required. To resolve this issue, restart the VM and specify the faultReasons field when you make a new report faulty host request.

Rate limit exceeded

Error message:

RATE_LIMIT_EXCEEDED

Reason: You have exceeded the allowed limits of requests to the instances.reportHostAsFaulty method, or Google lacks sufficient capacity to fulfill your request.