Describe the issue I got reached by anaconda team that they are not able to merge pull requests as all the pull requests are show red merge button with error message: Did not manage to rebase this pull-request. From what I found out this is happening one or two weeks ago.
Did not manage to rebase this pull-request
When do you need this? (YYYY/MM/DD) Asap
When is this no longer needed or useful? (YYYY/MM/DD) When anaconda is no longer around
If we cannot complete your request, what is the impact? PRs couldn't be merged on anaconda
I tried to investigate a little. It seems that there is some issue with the metadata of the repository. I tried to run Project settings -> Regenerate Repos, but it doesn't seem to be helping.
Re-opening the pull request doesn't seem to change anything and when I tried to create a new fork it ended up in broken state The permissions on this repository are being updated. This may take a while. During this time, you or some of the project's contributors may not be able to push to this repository. It's still in the same state even after a hour.
The permissions on this repository are being updated. This may take a while. During this time, you or some of the project's contributors may not be able to push to this repository.
Found this in the logs:
2024-12-11 09:17:28,386 [ERROR] celery.app.trace: Task pagure.lib.tasks.fork[a9c5848c-ad70-4d1f-b42f-d4465de906a4] raised unexpected: PagureException('Did not manage to rebase> Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/pagure/lib/repo.py", line 35, in run_command command, stderr=subprocess.STDOUT, cwd=cwd File "/usr/lib64/python3.6/subprocess.py", line 356, in check_output **kwargs).stdout File "/usr/lib64/python3.6/subprocess.py", line 438, in run output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '['git', 'clone', '/srv/git/repositories/rpms/anaconda.git', '/tmp/pagure-fork-fis3g3tk']' returned non-zero exit status 128. During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/celery/app/trace.py", line 385, in trace_task R = retval = fun(*args, **kwargs) File "/usr/lib/python3.6/site-packages/celery/app/trace.py", line 648, in __protected_call__ return self.run(*args, **kwargs) File "/usr/lib/python3.6/site-packages/pagure/lib/tasks_utils.py", line 36, in decorated_function return function(self, session, *args, **kwargs) File "/usr/lib/python3.6/site-packages/pagure/lib/tasks.py", line 501, in fork repo_from, "main", "fork" File "/usr/lib/python3.6/site-packages/pagure/lib/git.py", line 1028, in __enter__ PagureRepo.clone(self._origpath, self.repopath) File "/usr/lib/python3.6/site-packages/pagure/lib/repo.py", line 78, in clone run_command(cmd) File "/usr/lib/python3.6/site-packages/pagure/lib/repo.py", line 47, in run_command "Did not manage to rebase this pull-request" pagure.exceptions.PagureException: Did not manage to rebase this pull-request
I tried the clone manually I didn't saw the issue. The project got cloned without issue. I'm currently trying to recreate my fork to see if creating a new fork will help, but I'm not able to find all the places to delete the project from as it's still thinks the fork exists when trying to create a new one.
I deleted it from projects table and /srv/git/repositories/forks. I'm not sure what I could have missed.
projects
/srv/git/repositories/forks
Metadata Update from @zlopez: - Issue tagged with: investigation
So, I guess this is:
https://src.fedoraproject.org/rpms/anaconda/pull-request/202 ?
Thats pretty strange.
There is this: https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/pagure/#_pull_request_throws_500_when_opened
Metadata Update from @phsmoura: - Issue tagged with: low-gain, low-trouble, ops
Checked the permissions again and they are correct. So that is not the issue in this case.
So, I think I have this fixed.
I ran the clone command that was failing as the pagure user and got:
# sudo -u pagure git clone /srv/git/repositories/rpms/anaconda.git /tmp/pagure-fork-aksdsasdasd Cloning into '/tmp/pagure-fork-aksdsasdasd'... warning: error opening directory '/srv/git/repositories/rpms/anaconda.git/objects/tmp_objdir-incoming-Vsr4rA/': Permission denied fatal: failed to iterate over '/srv/git/repositories/rpms/anaconda.git/objects/'
So, the problem was the tmp_objdir-incoming-* dir. I guess a rebase got stuck or something. I moved that aside and everything looks normal again to me. I can see that PR file now, and it shows that it should be mergable.
Can you all confirm it looks ok now and close?
@kevin Could you please give more details about how you fixed it in case we run into this in the future? I'm not sure what exactly "moving it aside" means in this context. Thanks!
On pkgs01 I simply did a mv of that directory off to another place. I suppose just removing it would have had the same effect.
That directory tree didn't have permissions to allow pagure to read it.
Looks like the pull request was successfully merged 2 days ago. Can this be closed?
Yep
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.