Cross fork changes broken

Summary

I have encounter problems when approaching several cross-fork actions belonging to my usual workflow:

  • Opening a merge request from a branch within my fork towards the master of the upstream repo, this results in 503 errors.
  • Updating existing cross-fork merge request with new commits, they do not show up in the merge requests, neither do the diffs. However, the branch in the fork shows the newly added commit.

The issues happened first after upgrading from 11.1.4 to 11.2.3

Steps to reproduce

  1. Have a repo forked
  2. Open a merge request from a branch with new commits that forked repo into the upstream repo
  1. Have a forked repo
  2. Create a new branch without changes
  3. Create a cross-fork MR for this branch into upstream repo
  4. Add commits to this branch

Example Project

N/A

What is the current bug behavior?

  • merge request creation dialog results in 503 error
  • newly added commits do not update merge request

What is the expected correct behavior?

  • cross-fork merge requests can be created
  • existing cross-fork merge requests can be updated

Relevant logs and/or screenshots

I need help here; I could not find anything suspicious in any log file.

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 
Coming


(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:env:info)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production)

Results of GitLab application Check

Expand for output related to the GitLab application check 
Coming


(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes

A current workaround is that MRs are opened within the same repo. There also updates of MRs are shown properly. Somehow it seems that the cross-fork commit relation cannot be established properly anymore.

Edited by Andreas Schöneck