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.

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

Start an ephemeral workspace fails #21164

Closed
Tracked by #21254
l0rd opened this issue Feb 14, 2022 · 3 comments · Fixed by eclipse-che/che-dashboard#486
Closed
Tracked by #21254

Start an ephemeral workspace fails #21164

l0rd opened this issue Feb 14, 2022 · 3 comments · Fixed by eclipse-che/che-dashboard#486
Assignees
Labels
area/dashboard area/devworkspace-operator kind/bug Outline of a bug - must adhere to the bug report template. new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes severity/P1 Has a major impact to usage or development of the system.
Milestone

Comments

@l0rd
Copy link
Contributor

l0rd commented Feb 14, 2022

Describe the bug

I have tried setting attribute at the root of the devfile as mentioned in the DevWorkspace documentation

attributes:
  controller.devfile.io/storage-type: ephemeral

I have also tried to set “Temporary storage” on from the Dashboard.

In both cases PVC are attached to the workspace pod:

image

Che version

next (development version)

Steps to reproduce

Try one of the badges in this repo README to start an ephemeral workspace on Che team dogfooding instance.

Expected behavior

When the workspace starts no PVC is attached to the workspace.

Runtime

other (please specify in additional context)

Screenshots

No response

Installation method

other (please specify in additional context)

Environment

other (please specify in additional context)

Eclipse Che Logs

No response

Additional context

I am testing in Che team dogfooding instance

Release Notes Text

The fix allows to start workspaces in ephemeral mode, and therefore faster.

@l0rd l0rd added kind/bug Outline of a bug - must adhere to the bug report template. area/dashboard area/devworkspace-operator severity/P1 Has a major impact to usage or development of the system. labels Feb 14, 2022
@l0rd
Copy link
Contributor Author

l0rd commented Feb 14, 2022

cc @ibuziuk

@ibuziuk ibuziuk added area/factory/dashboard Issues related to factories frontend (che user dashboard side) area/devworkspace-operator sprint/next and removed area/factory/dashboard Issues related to factories frontend (che user dashboard side) area/devworkspace-operator labels Feb 14, 2022
@amisevsk
Copy link
Contributor

amisevsk commented Mar 1, 2022

For clarity, it appears that the issue is that the attributes field in the devfile is being dropped somewhere in the dashboard. I'm unable to add attributes to existing workspaces either.

@ibuziuk ibuziuk mentioned this issue Mar 11, 2022
35 tasks
@olexii4 olexii4 self-assigned this Mar 16, 2022
@l0rd l0rd added the new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes label Apr 7, 2022
@l0rd l0rd added this to the 7.46 milestone Apr 7, 2022
@l0rd l0rd added the status/release-notes-review-needed Issues that needs to be reviewed by the doc team for the Release Notes wording label Apr 7, 2022
@l0rd l0rd changed the title I am not able to start an ephemeral workspace Start an ephemeral workspace fails Apr 7, 2022
@nickboldt
Copy link
Contributor

this sounds like a temporary regression, fixed before anyone will encounter it in 3.0; not sure though, perhaps @l0rd has a different opinion on whether this merits inclusion in downstream N&N

@max-cx max-cx removed the status/release-notes-review-needed Issues that needs to be reviewed by the doc team for the Release Notes wording label Jan 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dashboard area/devworkspace-operator kind/bug Outline of a bug - must adhere to the bug report template. new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants