#8468 fedora-scm-requests new repository procedure repeatedly keeps the repo owned by the releng person
Opened 8 months ago by churchyard. Modified 5 months ago

  1. I've create a new repository request, where something was wrong
  2. @limb processed the request, closed as invalid
  3. I fixed the thing and reopened the issue
  4. @limb processed the request, closed as invalid again (already exists)
  5. as a result, the repo was created, but owned by @limb

This is probably broken in some script that @limb runs, it probably creates the repo, checks some constraints and assigns the repo to me. When the constraints fail, the repo exists, but is not assigned to me. I cannot provide more details, because I have no idea what happens "on the other side".

This already happened twice to me:

https://pagure.io/releng/fedora-scm-requests/issue/10706 https://pagure.io/releng/issue/8233
https://pagure.io/releng/fedora-scm-requests/issue/13178 https://pagure.io/releng/issue/8467

In both cases, the branch was set to epel7 and initial_commit to false, if that makes any difference.

This could be an artifact of the script crashing due to 500 or 400 errors.

I believe this is caused by "initial_commit": false

Either this was fixed, or the previous comment is not true.

I have seen this before, but as @limb mentioned it is random and mostly the script crashing while processing the request.

Login to comment on this ticket.