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

Review known issues

When a problem occurs during a repair operation, your virtual machine (VM)instance might displayFAILED_WITH_UNEXPECTED_STATUS or remain in theREPAIRING state.

Avoid duplicate calls for the same VM

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

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

HandleINTERNAL_ERROR duringreportHostAsFaulty operation

If you delete a VM while thereportHostAsFaulty operation is in progress, thenanINTERNAL_ERROR might occur and thereportHostAsFaulty operation fails.

Workaround: No workaround is available. Before you delete a VM, you mustverify that thereportHostAsFaulty 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 theRUNNING 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 thereservation-bound provisioning model.To report a faulty host for an A4X, A4, or A3 Ultra VM that uses the flex-startor spot provisioning model, contact your account team.

Fault reason is missing

This error appears when you don't specify thefaultReasons field in a reportfaulty host request.

Error message:

FAULT_REASONS_EMPTY_SHOULD_BE_SPECIFIED

Resolution: ThefaultReasons field is required. To resolve this issue,restart the VM and specify thefaultReasons fieldwhen 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 theinstances.reportHostAsFaulty method, or Google lacks sufficient capacity tofulfill your request.