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

Skip to content

there is no way to delete workspaces that are pending due to provisioner not availble #12331

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
Open
matifali opened this issue Feb 27, 2024 · 5 comments
Open

there is no way to delete workspaces that are pending due to provisioner not availble #12331

matifali opened this issue Feb 27, 2024 · 5 comments
Labels
needs-rfc Issues that needs an RFC due to an expansive scope and unclear implementation path. s3 Bugs that confuse, annoy, or are purely cosmetic

Comments

@matifali
Copy link
Member

I have created a workspace that was provisioned by a provisioner that no longer exists. There is no way to delete such a workspace and it stays in the queue forever.

image
@matifali matifali added s2 Broken use cases or features (with a workaround). Only humans may set this. bug labels Feb 27, 2024
@matifali matifali mentioned this issue Feb 28, 2024
Closed
@matifali matifali added s3 Bugs that confuse, annoy, or are purely cosmetic and removed s2 Broken use cases or features (with a workaround). Only humans may set this. labels Mar 10, 2024
@mtojek mtojek self-assigned this Mar 27, 2024
@mtojek mtojek added the needs-rfc Issues that needs an RFC due to an expansive scope and unclear implementation path. label Mar 27, 2024
@bpmct
Copy link
Member

bpmct commented Mar 28, 2024

You can orphan these workspaces. I think we mostly just need a better error message + steps for resolution when someone hovers.

I also wish our queue could be per-provisioner tag but idk if we support that rn

@matifali matifali mentioned this issue May 21, 2024
Closed
@matifali
Copy link
Member Author

@bpmct Could you share the steps for how these can be orphaned? I am currently not able to resolve this.

@matifali
Copy link
Member Author

matifali commented May 23, 2024 •
edited
Loading

One can prevent this by rejecting all such jobs with a message that no provisioners are found with the provided unmatched tag.

@mtojek mtojek removed their assignment Sep 18, 2024
@matifali matifali mentioned this issue Oct 12, 2024
Closed
@matifali matifali removed the bug label Oct 14, 2024
@matifali matifali mentioned this issue Oct 23, 2024
Closed
@matifali matifali mentioned this issue Jan 3, 2025
Open
@matifali matifali marked this as a duplicate of #8247 Jan 23, 2025
@matifali
Copy link
Member Author

We should have a way to solve this after we have #15084.

@deansheather deansheather mentioned this issue Feb 7, 2025
Open
@EdwardAngert EdwardAngert mentioned this issue Feb 13, 2025
Closed
@matifali
Copy link
Member Author

It is still not possible to solve the issue after we have #15193. See the screenshot.
We should probably link to the job view on the provisioners page from the workspace page.

Image

cc: @bartekgatzcoder

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. s3 Bugs that confuse, annoy, or are purely cosmetic
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@matifali @mtojek @bpmct