An instance’s statusReason says why it is in its current status. get-instance and list-instances return it next to status.
It’s set in two cases:
- Every
FAILEDinstance carries one. - A
STOPPEDinstance carries one when the platform stopped it because its machine failed. ASTOPPEDinstance you stopped yourself, or that shut itself down, carries none.
For every other status it’s null, and starting the instance clears it. A reason starts with one of the fixed texts below. Some texts are followed by a colon and a detail, such as a quota refusal you can act on. A reason never contains raw host errors, file paths or machine names. If the reason isn’t enough to act on, contact Origin Cloud support and quote the instance URN.
The texts are listed in the order an instance can meet them: launch, start, stop, and machine failure.
A volume could not be created
Text: a volume this instance needs could not be created, optionally followed by : <detail>
Status: FAILED
Meaning: A volume the launch creates, such as the root disk, could not be created. A detail you can act on is appended, for example a volume this instance needs could not be created: invalid input on field quota: volume storage quota exceeded.
What to do: For a quota detail, free volume storage or request a higher limit. Then terminate the instance and launch again.
A volume could not be attached
Text: a volume this instance needs could not be attached, optionally followed by : <detail>
Status: FAILED
Meaning: A volume exists but couldn’t be handed to the instance, for example a volume this instance needs could not be attached: volume is not available.
What to do: Act on the detail, then start the instance or terminate it.
The network interface could not be created
Text: the network interface this instance needs could not be created, optionally followed by : <detail>
Status: FAILED
Meaning: The launch couldn’t create the instance’s network interface. The most common detail is a subnet with no free addresses. The launch call returns the same error.
What to do: Terminate the instance. Launch again into a subnet with free addresses. See VPC addressing.
The instance could not be placed
Text: this instance could not be placed on a machine to start on, optionally followed by : <detail>
Status: FAILED
Meaning: The instance finished preparing its resources but had no machine to start on, and none could be found. The detail usually names the capacity shortfall, for example no host has capacity for an instance of this type.
What to do: Start the instance again later, or terminate it and launch again.
INSUFFICIENT_No host has room for this type right now. Retry in a few minutes; a larger type may have room. gp1.core.2 is the smallest type, so there is no smaller one to try.
The instance could not be started on its host
Text: the instance could not be started on its host
Status: FAILED
Meaning: The machine the instance was placed on refused to start it.
What to do: Start the instance again, or terminate it.
The start operation failed
Text: the operation failed (ERR_INSTANCE_START)
Status: FAILED
Meaning: The host reported an error while carrying out the start.
What to do: Start the instance again, or terminate it.
The stop operation failed
Text: the operation failed (ERR_INSTANCE_STOP)
Status: FAILED
Meaning: The host reported an error while carrying out a stop or a termination’s shutdown. The guest may still be running.
What to do: Start the instance to return it to the normal lifecycle and stop it again, or terminate it.
The operation failed
Text: the operation failed
Status: FAILED
Meaning: The host reported an error without a classification.
What to do: Start the instance again, or terminate it.
The host did not confirm the start
Text: the instance's host did not confirm that it started
Status: FAILED
Meaning: The instance’s machine is reachable but didn’t confirm a start, after the platform sent it three times over about 30 minutes. The guest may be running.
What to do: Start the instance again, or terminate it.
The host did not confirm the stop
Text: the instance's host did not confirm that it stopped
Status: FAILED
Meaning: The instance’s machine is reachable but didn’t confirm a stop or a termination’s shutdown, after the platform sent it three times over about 30 minutes. The guest may still be running.
What to do: Start the instance to return it to the normal lifecycle and stop it again, or terminate it.
The machine failed
Text: the machine this instance was running on failed, and the instance went down with it; start it again to bring it back
Status: STOPPED
Meaning: The machine under the running instance restarted, and the platform proved it. The guest didn’t survive. See When the machine under an instance fails.
What to do: Start the instance when you want it back. A start usually brings it back; check that the guest answers afterwards. If it reads RUNNING and AVAILABLE but stays unreachable, see Troubleshoot Compute.
The machine was taken out of service
Text: the machine this instance was running on failed and has been taken out of service; the instance went down with it, and starting it again will place it on another machine
Status: STOPPED
Meaning: The machine under the instance failed and didn’t come back, and the platform took it out of service. See When the machine under an instance fails.
What to do: Start the instance when you want it back. It starts on another machine with its volumes and addresses unchanged.