Chapter 25. Troubleshooting OpenShift Dev Spaces administration

FailedScheduling: 0/N nodes are available: insufficient cpu or insufficient memory

The cluster does not have enough resources to schedule the workspace Pod. Free resources by stopping idle workspaces, or add nodes to the cluster.

FailedScheduling: 0/N nodes are available: pod has unbound immediate PersistentVolumeClaims

A PersistentVolumeClaim (PVC) cannot be bound. Verify that a StorageClass is configured and that the cluster has available persistent volumes.

node(s) didn’t match Pod’s node affinity/selector

The workspace Pod has a nodeSelector or node affinity that does not match any available node. Verify the nodeSelector configuration in the CheCluster Custom Resource.

ErrImagePull or ImagePullBackOff

The container runtime cannot pull the workspace image. Verify that the image exists, the image name is correct in the devfile, and that image pull secrets are configured if the image is in a private registry.

x509: certificate signed by unknown authority

The container runtime does not trust the TLS certificate of the container registry. Import the registry Certificate Authority (CA) certificate into OpenShift Dev Spaces.

DevWorkspace failed to start: timed out waiting for DevWorkspace to be ready

The workspace did not reach the Running phase within the configured timeout. Increase startTimeoutSeconds in the CheCluster Custom Resource or investigate Pod events for resource or scheduling issues.

Failed to create DevWorkspace: admission webhook denied the request

The Dev Workspace Operator webhook rejected the DevWorkspace. Verify that the Dev Workspace Operator is running and that CRDs are up to date.

BadRequest or InfrastructureFailure

An infrastructure-level error prevented workspace creation. Check the Dev Workspace Operator logs for details.

exceeded quota or forbidden: exceeded quota

The user namespace has a ResourceQuota that prevents creating the workspace Pod or PVC. Increase the quota or reduce the workspace resource requests in the devfile.

OOMKilled

The workspace container exceeded its memory limit and was terminated. Increase the memory limit in the devfile components section or in the CheCluster Custom Resource defaults.

Users see 401 Unauthorized when cloning a private repository.

The OAuth application credentials are incorrect. Verify the client ID and client secret in the OpenShift Secret. Recreate the Secret if needed.

Users see The redirect URI provided is missing or does not match on the Git provider.

The OAuth callback URL configured in the Git provider application does not match the OpenShift Dev Spaces callback URL. The callback URL must be https://__<devspaces_fqdn>__/api/oauth/callback.

Users are not prompted to authorize the OAuth application.

The OAuth OpenShift Secret is not in the openshift-devspaces namespace, or the Secret labels are incorrect. Verify the Secret exists with the required labels.

OAuth works for some users but not others.

The Git provider OAuth application restricts access to specific organizations or groups. Expand the application permissions to include all required organizations.

Users see token expired errors after a period of inactivity.

The OAuth token has expired and cannot be refreshed. The user must revoke the token on the Git provider and re-authorize.

Git push fails with 403 Forbidden despite successful initial authentication.

The OAuth token scope is insufficient for push operations. Verify that the OAuth application requests the repo scope (GitHub), api scope (GitLab), or equivalent write permissions.