Geo: Git push with options over SSH to secondary site fails

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Summary

When performing a git push with options (e.g. ci.skip) over SSH to a secondary Geo site fails with unexpected disconnect error message

Steps to reproduce

1. Setup single node Geo primary and secondary site.
2. Create a repository
3. Clone repository from secondary site via SSH
4. Commit some changes and push via SSH to secondary site with push option (e.g. ci.skip)
5. Observe push failing with unexpected disconnect error message

Example Project

What is the current bug behavior?

Push fails with unexpected disconnect error.

What is the expected correct behavior?

Push succeeds with no errors

Relevant logs and/or screenshots

sampath_ranasinghe@Sampaths-MacBook-Pro clone-test % git push origin main -o ci.skip 
remote: 
remote: This request to a Geo secondary node will be forwarded to the
remote: Geo primary node:
remote: 
remote:   git@sranasinghe.gogitlab.xyz:root/clone-test.git
remote: 
Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Delta compression using up to 10 threads
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 273 bytes | 273.00 KiB/s, done.
Total 3 (delta 1), reused 0 (delta 0), pack-reused 0
remote: 
remote: ========================================================================
remote: 
remote: Remote repository is unavailable
remote: 
remote: ========================================================================
remote: 
send-pack: unexpected disconnect while reading sideband packet
fatal: the remote end hung up unexpectedly

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

(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

(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