-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
PipelineRun volumeClaimTemplate creation can race with PVC deletion #3855
Labels
kind/bug
Categorizes issue or PR as related to a bug.
Comments
/assign wlynch |
wlynch
added a commit
to wlynch/pipeline
that referenced
this issue
Mar 25, 2021
We've noticed that using Owner names can lead to race conditions in deleting a volumeClaimTemplate PVC in where a PipelineRun is quickly deleted then recreated (see tektoncd#3855). Using the UID allows us to uniquely identify independent runs with the same name, avoiding this issue while keeping the same semantic.
2 tasks
wlynch
added a commit
to wlynch/pipeline
that referenced
this issue
Mar 25, 2021
We've noticed that using Owner names can lead to race conditions in deleting a volumeClaimTemplate PVC in where a PipelineRun is quickly deleted then recreated (see tektoncd#3855). Using the UID allows us to uniquely identify independent runs with the same name, avoiding this issue while keeping the same semantic.
wlynch
added a commit
to wlynch/pipeline
that referenced
this issue
Mar 25, 2021
We've noticed that using Owner names can lead to race conditions in deleting a volumeClaimTemplate PVC in where a PipelineRun is quickly deleted then recreated (see tektoncd#3855). Using the UID allows us to uniquely identify independent runs with the same name, avoiding this issue while keeping the same semantic.
wlynch
added a commit
to wlynch/pipeline
that referenced
this issue
Mar 25, 2021
We've noticed that using Owner names can lead to race conditions in deleting a volumeClaimTemplate PVC in where a PipelineRun is quickly deleted then recreated (see tektoncd#3855). Using the UID allows us to uniquely identify independent runs with the same name, avoiding this issue while keeping the same semantic.
tekton-robot
pushed a commit
that referenced
this issue
Mar 25, 2021
We've noticed that using Owner names can lead to race conditions in deleting a volumeClaimTemplate PVC in where a PipelineRun is quickly deleted then recreated (see #3855). Using the UID allows us to uniquely identify independent runs with the same name, avoiding this issue while keeping the same semantic.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
I should be able to run
kubectl delete -f pipelinerun.yaml; kubectl apply -f pipelinerun.yaml
repeatedly with avolumeClaimTemplate
.Actual Behavior
Talking with @sbwsg, we suspect that something along these lines is happening:
When in the stuck state,
kubectl describe
shows:We suspect that this is a race condition where the new PipelineRun is waiting for the PVC to be deleted since it's in the terminating state, but the PVC isn't being deleted because it thinks the the new PipelineRun has a claim on it.
Deleting the pipelinerun and waiting lets the PVC finish deleting, at which point the new pipelinerun can be applied.
Steps to Reproduce the Problem
kubectl delete ; kubectl apply
)Additional Info
Kubernetes version:
Output of
kubectl version
:Tekton Pipeline version:
The text was updated successfully, but these errors were encountered: