Server errors

Causes and remedies for the error codes of self-service servers: states, plans, images, credentials and rescue mode.

`error.server.not_ready`

Text in the console: The server is {state}; the operation is not possible now.
Meaning for API clients: The server is not in a state that allows the operation (creating, deleted, failed or rescue).
Code: FAILED_PRECONDITION, HTTP 412

Argument	What it holds
`state`	the state of the server.

Cause. The server is in a state that does not allow the operation. Most operations need the state active. Leaving rescue mode needs the state rescue. A server in the state creating, deleted or failed accepts none of them. The same code is used when the server has no virtual machine yet.

Remedy.

Show the state of the server: kyvernon servers <tenant> get <server>.
When the state is creating, wait until it is active, then repeat the operation.
When the state is rescue, leave rescue mode first: kyvernon servers <tenant> unrescue <server>.
When the state is failed, an administrator reads the failed task for the cause: kyvernon tasks list. Pass on the id of the server.

See the page Servers.

`error.server.plan_not_larger`

Text in the console: A server can only move to a plan at least as large in vCPUs, memory and disk.
Meaning for API clients: Resize goes to a plan that is at least as large in vCPU, memory and disk.
Code: INVALID_ARGUMENT, HTTP 400

Argument	What it holds
`field`	the request field that holds the rejected plan, here `plan`.

Cause. A server can move only to a plan that is at least as large as its plan in vCPUs, memory and disk, and is not the same plan. A move to a smaller or equal plan is refused.

Remedy.

List the plans: kyvernon plans list.
Choose a plan that is not smaller in any dimension: kyvernon servers <tenant> resize <server> <plan>.
To end up with a smaller server, create a new server on a smaller plan and move the data.

`error.server.plan_not_orderable`

Text in the console: This plan cannot be ordered.
Meaning for API clients: The plan is not orderable.
Code: INVALID_ARGUMENT, HTTP 400

Argument	What it holds
`field`	the request field that holds the rejected plan, here `plan`.

Cause. The plan is not orderable. It is kept for servers that exist already, and no new server or resize can choose it.

Remedy.

Choose a plan that is orderable: kyvernon plans list.
An administrator can make the plan orderable again by setting orderable to true: kyvernon plans update <id> --body-file <file>.

`error.server.image_not_allowed`

Text in the console: The plan does not allow this image.
Meaning for API clients: The plan does not allow the image.
Code: INVALID_ARGUMENT, HTTP 400

Argument	What it holds
`field`	the request field that holds the rejected value, `image` or `plan`.

Cause. The plan restricts the images that may be used with it, and the image is not on that list. The same check applies when a server is resized to a plan that does not allow its image.

Remedy.

Choose an image that the plan allows, or a plan that allows the image.
An administrator can add the image to the plan: kyvernon plans update <id> --body-file <file>.

`error.server.disk_too_small`

Text in the console: The plan's disk is too small for this image.
Meaning for API clients: The plan's disk is smaller than the image needs.
Code: INVALID_ARGUMENT, HTTP 400

Argument	What it holds
`field`	the request field that holds the rejected value, here `plan`.

Cause. The disk of the plan is smaller than the minimum disk that the image needs.

Remedy.

Choose a plan with a larger disk, or an image that needs a smaller one.
Check the minimum disk of an image: kyvernon catalogue list.

`error.server.no_credentials`

Text in the console: This image takes no SSH keys, password or user data.
Meaning for API clients: The image takes no credentials (no SSH keys, password or user data).
Code: depends on the cause

Argument	What it holds
`field`	the request field that holds the rejected value, for example `sshKeys`.

Cause. The image takes no credentials, so SSH keys, a password and user data are all refused.

Remedy.

Create or reinstall the server without --ssh-key, --password and --user-data.
To set a way in, use an image that supports credentials, or set it inside the image.

`error.server.rescue_active`

Text in the console: The server is already in rescue mode.
Meaning for API clients: The server is already in rescue mode.
Code: FAILED_PRECONDITION, HTTP 412

Cause. The server is in rescue mode already.

Remedy.

Use the rescue session that is open.
To leave rescue mode, run kyvernon servers <tenant> unrescue <server>.

`error.server.no_rescue_image`

Text in the console: No rescue image is configured.
Meaning for API clients: No catalogue image is marked as a rescue image.
Code: FAILED_PRECONDITION, HTTP 412

Cause. Rescue mode was started without naming an image, and no image of the catalogue is marked as a rescue image.

Remedy.

Name a rescue image: kyvernon servers <tenant> rescue <server> --image <image>.
An administrator marks a template as the rescue image: kyvernon catalogue set <id> --body '{"catalogue":false,"rescue":true}', then adds the other catalogue fields that the template needs.