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

[PVC] take prebuild, and write data, all subsequent data won't be recovered #11770

Closed
Tracked by #7901
jenting opened this issue Aug 1, 2022 · 1 comment · Fixed by #12180
Closed
Tracked by #7901

[PVC] take prebuild, and write data, all subsequent data won't be recovered #11770

jenting opened this issue Aug 1, 2022 · 1 comment · Fixed by #12180
Assignees
Labels
team: workspace Issue belongs to the Workspace team type: bug Something isn't working

Comments

@jenting
Copy link
Contributor

jenting commented Aug 1, 2022

Bug description

Enable feature flag PVC, and once we have ever taken prebuild, all the subsequent data won't be recovered from the VolumeSnapshot. The data is always recovered from the prebuild VolumeSnapshot.

Steps to reproduce

  1. Enable feature flag PVC
  2. Open the workspace, write some data (A), and close the workspace.
  3. Manually trigger the prebuild, for example, gitpod.io/#prebuild/https://gitlab.com/gitpod-io/template-python-django
  4. Open the workspace again, write some data (B), close the workspace and reopen it.
  5. content B won't be recovered, but content A recovered. Double check the PVC's VolumeSnapshot, it always uses the prebuild VolumeSnapshot ID.

Workspace affected

No response

Expected behavior

No response

Example repository

No response

Anything else?

#7901

@jenting jenting added the type: bug Something isn't working label Aug 1, 2022
@jenting jenting added the team: workspace Issue belongs to the Workspace team label Aug 1, 2022
@sagor999 sagor999 moved this to In Progress in 🌌 Workspace Team Aug 17, 2022
@sagor999 sagor999 self-assigned this Aug 17, 2022
Repository owner moved this from In Progress to Awaiting Deployment in 🌌 Workspace Team Aug 18, 2022
@jenting
Copy link
Contributor Author

jenting commented Aug 25, 2022

The PR is deployed by WebApp rather than Workspace, therefore, I changed the status from Awaiting Deployment to Done.

@jenting jenting moved this from Awaiting Deployment to Done in 🌌 Workspace Team Aug 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team: workspace Issue belongs to the Workspace team type: bug Something isn't working
Projects
No open projects
Status: Done
2 participants