Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Determine whether a build job will ever complete (is there a matching provisioner) #8247

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
Closed
bpmct opened this issue Jun 28, 2023 · 6 comments
Closed

Determine whether a build job will ever complete (is there a matching provisioner) #8247

bpmct opened this issue Jun 28, 2023 · 6 comments
Labels
needs-rfc Issues that needs an RFC due to an expansive scope and unclear implementation path.

Comments

@bpmct
Copy link
Member

bpmct commented Jun 28, 2023 •
edited
Loading

A workspace may be stuck in a "pending" state in a queue forever in the following cases:

  • There are no provisioners
  • There are no provisioners that match the tags required for the job (e.g. local provisioner or tagged provisioner)

Let's surface this to the user via the dashboard and CLI. Right now, the user will just see that their workspace is pending or in a queue, but it will never progress.
@cdr-bot cdr-bot bot added the feature label Jun 28, 2023
@Emyrk Emyrk self-assigned this Jul 10, 2023
@bpmct bpmct unassigned Emyrk Aug 3, 2023
@Emyrk
Copy link
Member

Emyrk commented Aug 30, 2023

@sreya Should this be blocked by the provisioner refactor? I ask because currently we store provisioners in the DB, so this should not be tricky to implement. However there was a PR opened to maybe remove it from the DB as a precursor to refactoring the provisioner stuff.

I just do not want to implement ontop of something that will be removed.

@bpmct
Copy link
Member Author

bpmct commented Aug 30, 2023

Fairly sure this is blocked by the provisioner refactor

@Emyrk
Copy link
Member

Emyrk commented Aug 31, 2023

Removed from the sprint until unblocked

@Emyrk Emyrk removed their assignment Sep 5, 2023
@github-actions github-actions bot added the stale This issue is like stale bread. label Feb 28, 2024
@matifali matifali removed the stale This issue is like stale bread. label Feb 28, 2024
@matifali
Copy link
Member

Related and possible duplicate of #12331. At least we should have a way to delete such workspaces from the coder database. It could be similar to the orphan resources option for failed workspaces.

@johnstcn
Copy link
Member

Needs RFC

@johnstcn johnstcn added the needs-rfc Issues that needs an RFC due to an expansive scope and unclear implementation path. label Mar 11, 2024
@mtojek
Copy link
Member

mtojek commented Mar 27, 2024

Duplicate of #12331 , so resolving this one.

@mtojek mtojek closed this as not planned Won't fix, can't repro, duplicate, stale Mar 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs-rfc Issues that needs an RFC due to an expansive scope and unclear implementation path.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@johnstcn @Emyrk @matifali @mtojek @bpmct