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

Failed to update base image versions on elyra-aidevsecops-tutorial repository #175

Closed
mayaCostantini opened this issue May 19, 2022 · 7 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@mayaCostantini
Copy link
Contributor

Describe the bug
Log from the pipeline run:

remote: error: GH006: Protected branch update failed for refs/heads/aicoe-ci-base-image-updater.        
remote: error: Cannot force-push to this protected branch        
To github.com:AICoE/elyra-aidevsecops-tutorial.git
 ! [remote rejected] aicoe-ci-base-image-updater -> aicoe-ci-base-image-updater (protected branch hook declined)
error: failed to push some refs to 'github.com:AICoE/elyra-aidevsecops-tutorial.git'

To Reproduce

See https://tekton.operate-first.cloud/#/namespaces/opf-ci-pipelines/pipelineruns/aicoe-pipelinerun-42e0f0c2-ed35-40c0-ad9a-901f4afb555c?pipelineTask=base-image-update-run&step=rebase

@mayaCostantini mayaCostantini added the kind/bug Categorizes issue or PR as related to a bug. label May 19, 2022
@codificat
Copy link
Member

I initially thought that the prow config for the AICoE org is missing some exclusions for branch protection.

However, the same pipeline actually works for the thoth-station org (right?) and there's no exclude pattern there...

/priority critical-urgent

@sesheta sesheta added the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label May 30, 2022
@mayaCostantini
Copy link
Contributor Author

/sig devsecops
/remove priority-critical-urgent
/priority important-soon

@sesheta sesheta added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jun 27, 2022
@sesheta
Copy link
Contributor

sesheta commented Jun 27, 2022

@mayaCostantini: The label(s) sig/devsecops cannot be applied, because the repository doesn't have them.

In response to this:

/sig devsecops
/remove priority-critical-urgent
/priority important-soon

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@sesheta
Copy link
Contributor

sesheta commented Sep 25, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
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.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 25, 2022
@sesheta
Copy link
Contributor

sesheta commented Oct 25, 2022

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@sesheta sesheta 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 Oct 25, 2022
@sesheta
Copy link
Contributor

sesheta commented Nov 24, 2022

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

@sesheta
Copy link
Contributor

sesheta commented Nov 24, 2022

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@sesheta sesheta closed this as completed Nov 24, 2022
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/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

3 participants