#7409 Unable to checkout repository in staging dist-git
Opened 4 months ago by mizdebsk. Modified 6 days ago

  • Describe what you need us to do:
    rpms/atinject repository in staging dist-git cannot be checked out:
$ fedpkg-stage clone atinject
Cloning into 'atinject'...
remote: Welcome to repoSpanner 0.3+19.4de0303739e95661cc7a1b4324d2f91d12005d90.el7, node fedora01.rpms.stg.fedoraproject.org
remote: Building packfile
remote: Packfile built, sending
remote: Packfile sent
Receiving objects: 100% (121/121), 70.93 KiB | 92.00 KiB/s, done.
warning: remote HEAD refers to nonexistent ref, unable to checkout.

$ git --git-dir atinject/.git log
fatal: your current branch 'master' does not have any commits yet
  • When do you need this? (YYYY/MM/DD)
    Earliest convenience.

  • When is this no longer needed or useful? (YYYY/MM/DD)
    N/A

  • If we cannot complete your request, what is the impact?
    I will have to use production environment for testing.


I guess we'll need input from @puiterwijk on this one

Metadata Update from @pingou:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

4 months ago

This might be caused by the out of space on pkgs01.stg, but it still seems to be happening after I fixed that.

It might be that repospanner needs to catch up on it's syncing before this repo is back to normal...

This is the cause of a disrepancy in symref updates between various repoSpanner builds.
I'm now adding symref updating to it, so that we can make sure all repos have the correct symrefs.

Note that a temporary workaround would be to just do a "git checkout master" (or any other ref) after the cloning.
The actual issue is just that Git isn't told what the standard ref is.

Status report: This is waiting some changes in the repoSpanner code and then working out a coordination time with CentOS to roll out the changes on both sides.

Time to check back: 2019-03-01

Metadata Update from @kevin:
- Issue tagged with: repoSpanner

2 months ago

This is fixed in repoSpanner, waiting on our pagure 5.3 upgrade then we will update this. Hopefully in the next few weeks.

So, this now behaves a bit differently:

Cloning into 'atinject'...
remote: Welcome to repoSpanner 0.4+1.f38383546f7ce0e88ec7b9c5bf7959521af2c941.el7.infra, node fedora01.rpms.stg.fedoraproject.org
remote: Building packfile
remote: Packfile built, sending
remote: Packfile sent
Receiving objects: 100% (121/121), 70.93 KiB | 115.00 KiB/s, done.
warning: remote HEAD refers to nonexistent ref, unable to checkout.

But then checking out any branch after that works fine.

@kevin With the new repoSpanner, we can fix this, from the server-side.
If we're sure that the entire cluster is 0.4 or higher, edit the symref of the repo.

Login to comment on this ticket.

Metadata