Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[bridge] Check workspace instance phase duration #12879

Closed
wants to merge 6 commits into from
Closed

[bridge] Check workspace instance phase duration #12879

wants to merge 6 commits into from

Conversation

laushinka
Copy link
Contributor

@laushinka laushinka commented Sep 12, 2022 •
edited
Loading

Description

This change also checks whether the duration has been longer than 60 minutes.

Related Issue(s)

Fixes #11397

How to test

  1. Run kubectl cordon on the node.
  2. Try running a workspace. It shouldn't be stuck in pending forever.

Release Notes

NONE

Documentation

Werft options:

  • /werft with-preview

@werft-gitpod-dev-com
Copy link

started the job as gitpod-build-laushinka-workspaces-which-cannot-11397.2 because the annotations in the pull request description changed
(with .werft/ from main)

@laushinka laushinka force-pushed the laushinka/workspaces-which-cannot-11397 branch from 23e06d8 to c5457c1 Compare September 12, 2022 13:40
@roboquat roboquat added size/M and removed size/S labels Sep 12, 2022
@laushinka
Copy link
Contributor Author

laushinka commented Sep 12, 2022 •
edited by werft-gitpod-dev-com bot
Loading

/werft run

👍 started the job as gitpod-build-laushinka-workspaces-which-cannot-11397.5
(with .werft/ from main)

@werft-gitpod-dev-com
Copy link

started the job as gitpod-build-laushinka-workspaces-which-cannot-11397.6 because the annotations in the pull request description changed
(with .werft/ from main)

@werft-gitpod-dev-com
Copy link

started the job as gitpod-build-laushinka-workspaces-which-cannot-11397.7 because the annotations in the pull request description changed
(with .werft/ from main)

@laushinka laushinka force-pushed the laushinka/workspaces-which-cannot-11397 branch from a9dd002 to 836804b Compare September 12, 2022 16:21
@roboquat roboquat added size/S and removed size/M labels Sep 12, 2022
@werft-gitpod-dev-com
Copy link

started the job as gitpod-build-laushinka-workspaces-which-cannot-11397.12 because the annotations in the pull request description changed
(with .werft/ from main)

@laushinka laushinka closed this Sep 13, 2022
@laushinka laushinka deleted the laushinka/workspaces-which-cannot-11397 branch September 13, 2022 06:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
do-not-merge/work-in-progress release-note-none size/S
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

workspaces which cannot be scheduled to a cluster get stuck in Pending
2 participants
@laushinka @roboquat