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

Fixes to support PVC on loadgen and integration test #12560

Closed
4 of 6 tasks
Tracked by #7901
kylos101 opened this issue Aug 31, 2022 · 9 comments
Closed
4 of 6 tasks
Tracked by #7901

Fixes to support PVC on loadgen and integration test #12560

kylos101 opened this issue Aug 31, 2022 · 9 comments
Labels
meta: stale This issue/PR is stale and will be closed soon team: workspace Issue belongs to the Workspace team

Comments

@kylos101
Copy link
Contributor

kylos101 commented Aug 31, 2022

Today, we got workspaces running with loadgen via this branch, https://github.com/gitpod-io/gitpod/commits/fo/pvc-chown. However, that left us with some questions and changes to make:

@kylos101 kylos101 changed the title Fix loadgen to support PVC [loadgen] Fixes to support PVC Aug 31, 2022
@jenting
Copy link
Contributor

jenting commented Sep 7, 2022

Related #12567

@jenting jenting added the team: workspace Issue belongs to the Workspace team label Sep 7, 2022
@jenting jenting changed the title [loadgen] Fixes to support PVC Fixes to support PVC on loadgen and integration test Sep 7, 2022
@kylos101
Copy link
Contributor Author

kylos101 commented Sep 7, 2022

@jenting are you sure 1 (SupervisorRef) is still needed? I am skeptical of it. Also, I believe 3 (WorkspaceLocation) and 4 (CheckoutLocation) were resolved in #12567.

@kylos101
Copy link
Contributor Author

kylos101 commented Sep 7, 2022

Also, how does this related to integration test? I believe it would be better if loadgen and integration test changes were tracked in separate issues.

@jenting
Copy link
Contributor

jenting commented Sep 7, 2022

Remove the SupervisorRef.

I think the loadgen test and integration test do not require the parameters WorkspaceLocation and CheckoutLocation in the start workspace request. These two parameters should be optional.

@kylos101
Copy link
Contributor Author

kylos101 commented Sep 7, 2022

These two parameters should be optional.

Why?

In other words, what is the side effect if we do not do this issue, @jenting ?

@kylos101
Copy link
Contributor Author

@jenting as this is an optimization, I moved later in our plan, so we can focus on getting operational first

@jenting
Copy link
Contributor

jenting commented Sep 29, 2022

The startWorkspace request, field workspaceLocation is a required field.
ref to

validation.Field(&req.Spec.WorkspaceLocation, validation.Required),

@jenting
Copy link
Contributor

jenting commented Sep 29, 2022

Without checkoutLocation with PVC, the error message shown

{"@type":"type.googleapis.com/google.devtools.clouderrorreporting.v1beta1.ReportedErrorEvent","error":"cannot initialize workspace:\n    github.com/gitpod-io/gitpod/content-service/pkg/initializer.InitializeWorkspace\n        github.com/gitpod-io/gitpod/[email protected]/pkg/initializer/initializer.go:439\n  - git chown -R -L gitpod /workspace failed (exit status 1): chown: changing ownership of '/workspace': Operation not permitted\n","file":"supervisor.go:1340","func":"func1","level":"fatal","message":"content initialization failed","serviceContext":{"service":"supervisor","version":"commit-6e8efd1aee02a9c13db6c03f886f39ceee178ac1"},"severity":"CRITICAL","time":"2022-09-29T08:20:14Z"}
{"@type":"type.googleapis.com/google.devtools.clouderrorreporting.v1beta1.ReportedErrorEvent","error":"rpc error: code = Canceled desc = context canceled","file":"rings.go:1083","func":"WorkspaceInfo","level":"error","message":"could not get workspace info","serviceContext":{"service":"workspacekit","version":"commit-6e8efd1aee02a9c13db6c03f886f39ceee178ac1"},"severity":"ERROR","time":"2022-09-29T08:20:14Z"}

@stale
Copy link

stale bot commented Jan 16, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Jan 16, 2023
@kylos101 kylos101 closed this as not planned Won't fix, can't repro, duplicate, stale Feb 2, 2023
@github-project-automation github-project-automation bot moved this to Awaiting Deployment in 🌌 Workspace Team Feb 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta: stale This issue/PR is stale and will be closed soon team: workspace Issue belongs to the Workspace team
Projects
None yet
Development

No branches or pull requests

2 participants