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

Repositories aren't synced with generics anymore #42

Closed
6 of 9 tasks
itrich opened this issue Aug 17, 2022 · 4 comments · Fixed by SovereignCloudStack/github-manager#17
Closed
6 of 9 tasks

Repositories aren't synced with generics anymore #42

itrich opened this issue Aug 17, 2022 · 4 comments · Fixed by SovereignCloudStack/github-manager#17
Assignees
Labels
action required Issues or pull requests that urgently require action bug Something isn't working Container Issues or pull requests relevant for Team 2: Container Infra and Tooling housekeeping Internal housekeeping

Comments

@itrich
Copy link
Contributor

itrich commented Aug 17, 2022

After renaming all old master branches to main, all workflows that try to sync with this generics repository fail.

I've switched to version: main on all repositories, but the problem seems to be some kind of authorization problem.

> Pushing to SovereignCloudStack/gx-scs-identity-provider@chore/sync-with-generics-repository...
  git push origin chore/sync-with-generics-repository:refs/heads/chore/sync-with-generics-repository
    >> To https://github.com/SovereignCloudStack/gx-scs-identity-provider.git
    >>  ! [remote rejected] chore/sync-with-generics-repository -> chore/sync-with-generics-repository (refusing to allow a GitHub App to create or update workflow `.github/workflows/ci-test-workflow.yml` without `workflows` permission)
    >> error: failed to push some refs to 'https://github.com/SovereignCloudStack/gx-scs-identity-provider.git'
  
  Error: command [git push origin chore/sync-with-generics-repository:refs/heads/chore/sync-with-generics-repository] exited with code 1. message: To https://github.com/SovereignCloudStack/gx-scs-identity-provider.git
   ! [remote rejected] chore/sync-with-generics-repository -> chore/sync-with-generics-repository (refusing to allow a GitHub App to create or update workflow `.github/workflows/ci-test-workflow.yml` without `workflows` permission)
  error: failed to push some refs to 'https://github.com/SovereignCloudStack/gx-scs-identity-provider.git'
  
      at Command.value [as execAsync] (/home/runner/work/_actions/technote-space/create-pr-action/v2/lib/main.js:100210:31)
      at processTicksAndRejections (node:internal/process/task_queues:96:5)
      at async GitHelper.value [as runCommand] (/home/runner/work/_actions/technote-space/create-pr-action/v2/lib/main.js:100291:45)
      at async GitHelper.value [as push] (/home/runner/work/_actions/technote-space/create-pr-action/v2/lib/main.js:100725:17)
      at async push (/home/runner/work/_actions/technote-space/create-pr-action/v2/lib/main.js:107342:5)
      at async diffProcess (/home/runner/work/_actions/technote-space/create-pr-action/v2/lib/main.js:107854:5)
      at async createPr (/home/runner/work/_actions/technote-space/create-pr-action/v2/lib/main.js:107890:31)
      at async runCreatePr (/home/runner/work/_actions/technote-space/create-pr-action/v2/lib/main.js:107949:28)
      at async execute (/home/runner/work/_actions/technote-space/create-pr-action/v2/lib/main.js:107995:9)
      at async main (/home/runner/work/_actions/technote-space/create-pr-action/v2/lib/main.js:108018:5)  

Let's get this up and running again.

In particular, these repositories are:

  • gx-scs-identity-provider
  • k8s-cassandra
  • k8s-cortex
  • k8s-gatekeeper
  • k8s-grafana
  • k8s-harbor
  • k8s-minio
  • k8s-prometheus
  • k8s-template
@itrich itrich added bug Something isn't working housekeeping Internal housekeeping action required Issues or pull requests that urgently require action Container Issues or pull requests relevant for Team 2: Container Infra and Tooling labels Aug 17, 2022
@joshmue
Copy link
Contributor

joshmue commented Aug 17, 2022

I'll take a look into the k8s-harbor repo.

For the other ones, I think it's fair to archive a bunch of these repositories and only revive if they are actually used.

IMHO that would include k8s-cassandra, k8s-cortex, k8s-gatekeeper, k8s-grafana, k8s-minio, and k8s-prometheus.

@itrich
Copy link
Contributor Author

itrich commented Aug 19, 2022

@garloff
Copy link

garloff commented Aug 29, 2022

Kurt to clean up and then add push permissions to the repo. @joshmue to advise.

@jschoone
Copy link

Looks like this is done @garloff @joshmue ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
action required Issues or pull requests that urgently require action bug Something isn't working Container Issues or pull requests relevant for Team 2: Container Infra and Tooling housekeeping Internal housekeeping
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants