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

Pipelines controller removing label from PipelineRun on reconcilation #5297

Closed
sm43 opened this issue Aug 10, 2022 · 6 comments
Closed

Pipelines controller removing label from PipelineRun on reconcilation #5297

sm43 opened this issue Aug 10, 2022 · 6 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@sm43
Copy link
Member

sm43 commented Aug 10, 2022

In Pipelines As Code, we create PipelineRun and then Update the PipelineRun with a Label.

Recently we noticed the label is missing, on debugging it more, we found when pipelines controller adds tekton.dev/pipeline label on the PipelineRun, it is removing the other label.

  --- PipelineRun pac-app-pipelines/pac-app-7-fp9f2 v392837 (2022-08-08T13:53:33+05:30) (gen. 1)
    +++ PipelineRun pac-app-pipelines/pac-app-7-fp9f2 v392871 (2022-08-08T13:53:33+05:30) (gen. 1)
    @@ -32,7 +32,6 @@
  pipelinesascode.tekton.dev/branch: main
  -    pipelinesascode.tekton.dev/check-run-id: "772154487234"
       pipelinesascode.tekton.dev/event-type: pull_request
       pipelinesascode.tekton.dev/git-provider: github
       pipelinesascode.tekton.dev/original-prname: pac-app-7
    @@ -42,9 +41,10 @@
  pipelinesascode.tekton.dev/state: started
  pipelinesascode.tekton.dev/url-org: sm43
  pipelinesascode.tekton.dev/url-repository: pac-app
  +    tekton.dev/pipeline: pac-app-7-fp9f2
    name: pac-app-7-fp9f2
    namespace: pac-app-pipelines
    -  resourceVersion: "392837"
  +  resourceVersion: "392871"
    uid: bcc2a3dc-e9a8-4ba0-9257-2b9308fc2d43
    spec:
      params:

How can we avoid this from happening? if this is a race condition

Slack Thread https://tektoncd.slack.com/archives/CLCCEBUMU/p1659949444059689

@sm43 sm43 added the kind/bug Categorizes issue or PR as related to a bug. label Aug 10, 2022
@sm43
Copy link
Member Author

sm43 commented Aug 10, 2022

cc @imjasonh @afrittoli @vdemeester

@tekton-robot
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 8, 2022
@tekton-robot
Copy link
Collaborator

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 8, 2022
@vdemeester
Copy link
Member

/assign

@vdemeester
Copy link
Member

/lifecycle frozen

@tekton-robot tekton-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Dec 9, 2022
@vdemeester
Copy link
Member

I think this got fixed be #5597 and will not even be relevent once #5146 is fixed, so I will go ahead and close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
Status: Done
Development

No branches or pull requests

3 participants