When working with workspaces, you may encounter several error states indicating that something went wrong. This section explains the most common workspace states, how to interpret related error messages, and what actions you can take.
Failed
A workspace is marked as "failed" when a critical error occurs during provisioning or execution.
To diagnose the issue:
- Open the portal and navigate to the failed workspace.
- Use the Actions menu to download the log file.
- Scroll to the bottom to find the relevant error message or failed step.
Below are common error messages and recommended actions:
Error message | Description | Action |
|---|---|---|
{"changed": false, "elapsed": 348, "msg": "timed out waiting for ping module test: Failed to connect to the host via ssh: ssh: connect to host … port 22: Operation timed out"} | Ansible was unable to connect to the VM, possibly due to a temporary network or capacity issue. | Try again later. |
{"error": "Workspace creation error: Command exited with non-zero code 1: b'\nError: Error waiting for instance to become ready: unexpected state \\'ERROR\\', wanted target \\'ACTIVE\\'. last error: %!s(<nil>)\n\n with openstack_compute_instance_v2.vm-openstack,\n on instance.tf line ..., in resource \"openstack_compute_instance_v2\" \"vm-openstack\":\n 45: resource \"openstack_compute_instance_v2\" \"vm-openstack\" \{\n\n'"} | A common error occurs when cloud capacity is temporarily unavailable. | Try again later. If the problem persists, contact the Service Desk. |
| {"error": "Command exited with non-zero code 2: ...FAILED! => \\{\"changed\": false, \"msg\": \”some error message\”}”} | Ansible failed on one of the tasks. This typically indicates an error in the component's script. | Check the last part of the log message to identify the specific issue. If you're developing this component, review your script. If it's a SURF-supported component, contact the Service Desk. |
Unhealthy
A workspace is marked as "unhealthy" when an unexpected condition arises outside of the scenarios described in the "failed" section.
When this happens, a ticket is automatically sent to the Service Desk. We will review and correct the workspace state based on the action that triggered the error. For example:
- If the workspace failed during deletion, we will delete it.
- If it failed during the resume, we will set it back to "paused".
What you can do:
No action is required from your side. We receive automatic notifications and will resolve the issue as soon as possible.
Unaccounted
The "unaccounted" state appears when a resource is linked to a wallet that has run out of credits. This may affect:
- Workspaces
- External storage volumes
- Networks
- Floating IPs
A workspace in this state cannot be resumed, even if it was originally created with a valid wallet.
Note: No visible error message is currently shown when a workspace becomes unaccounted.
What you can do:
- Check if your wallet has expired or run out of credits.
- If you're on an RCCS contract, contact the contract owner to request additional credits.
- If you’re using an NWO grant, apply for a new one or an extension.
- Always ensure you meet the conditions and request credits in advance to avoid interruptions.