question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

devworkspace failed to progress past phase 'Starting' for longer than timeout (5m)

See original GitHub issue

Summary

i’m receiving below error while the workspace gets created. please let me know how to increase the timeout devworkspace failed to progress past phase 'Starting' for longer than timeout (5m)

i’m using chectl version chectl/0.0.20220422-next.08c2079 linux-x64 node-v16.13.2

as of now i have increased the timeout limit for below properties chectl server:start --k8spoddownloadimagetimeout=1000000 --k8spoderrorrechecktimeout=1000000 --k8spodreadytimeout=1000000 --k8spodwaittimeout=1000000

image

Also, i want to view the logs that gets recorded while the workspace is starting. Please let me know how to view that as well

i’m running the eclipse-che instance in minikube cluster created using minikube start --driver=docker --memory=15000 --cpus=4 --ports="30670,30700,30710,30720,80:80,443:443,31728:31728"

i deployed eclipse-che using chectl server:deploy --platform minikube --installer=operator --debug

Relevant information

No response

Issue Analytics

  • State:open
  • Created a year ago
  • Comments:13 (7 by maintainers)

github_iconTop GitHub Comments

2reactions
tolushacommented, Jul 10, 2022

@Divine1 Pls try in devworkspace-controller namespace

1reaction
amisevskcommented, Jul 8, 2022

To configure the start timeout in DevWorkspace Operator, you can use the .config.workspace.progressTimeout field in the DevWorkspaceOperatorConfig:

apiVersion: controller.devfile.io/v1alpha1
kind: DevWorkspaceOperatorConfig
metadata:
  name: devworkspace-operator-config
  namespace: <devworkspace/che installation namespace>
config:
  workspace:
    progressTimeout: 15m # This would set it to 15 minutes, for example

If a DevWorkspaceOperatorConfig named devworkspace-operator-config already exists, you’ll likely want to leave other fields in the .config unchanged.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Why workspace fails with error "devworkspace failed to ...
Workspace fails with error devworkspace failed to progress past phase 'Starting' for longer than timeout (5m) . Environment. Red Hat OpenShift ...
Read more >
Monitoring the Dev Workspace Operator - Eclipse
Collecting Dev Workspace Operator metrics with Prometheus; Dev Workspace-specific ... Number of Dev Workspaces successfully entering the Running phase.
Read more >
Devfile v2 and IDE plug-ins in Eclipse Che - Medium
If the devfile.yaml has schemaVersion2 2.0.0 (or greater like 2.1.0), it will use DevWorkspace controller to deploy this devfile.
Read more >
Pulse · eclipse/che · GitHub
38 Unresolved conversations. Sometimes conversations happen on old items that aren't yet closed. Here is a list of all the Issues and Pull...
Read more >
Search OpenShift CI
#1910801 bug 23 months ago #1890995 bug 22 months ago #1921857 bug 22 months ago #1936404 bug 21 months ago
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found