#7427 push to pkgs.stg.fedoraproject.org fails
Closed: Fixed 2 months ago by kevin. Opened 6 months ago by sharkcz.

  • Describe what you need us to do:
    Push to staging instance of src.fp.o fails, fetching works OK.
[dan@talos fedora-release]$ git remote -v show
origin  ssh://sharkcz@pkgs.fedoraproject.org/rpms/fedora-release (fetch)
origin  ssh://sharkcz@pkgs.fedoraproject.org/rpms/fedora-release (push)
sharkcz ssh://sharkcz@pkgs.fedoraproject.org/forks/sharkcz/rpms/fedora-release.git (fetch)
sharkcz ssh://sharkcz@pkgs.fedoraproject.org/forks/sharkcz/rpms/fedora-release.git (push)
sharkcz-stg ssh://sharkcz@pkgs.stg.fedoraproject.org/forks/sharkcz/rpms/fedora-release.git (fetch)
sharkcz-stg ssh://sharkcz@pkgs.stg.fedoraproject.org/forks/sharkcz/rpms/fedora-release.git (push)

[dan@talos fedora-release]$ git push sharkcz-stg s390x                                                                                                                                  Counting objects: 70, done.
Delta compression using up to 64 threads.
Compressing objects: 100% (36/36), done.
Writing objects: 100% (70/70), 13.56 KiB | 6.78 MiB/s, done.
Total 70 (delta 46), reused 50 (delta 33)
remote: Empty compile time value given to use lib at hooks/update line 6.
remote: Use of uninitialized value in require at (eval 13) line 1, <DATA> line 1.
remote: WARNING: Use of uninitialized value $repo in concatenation (.) or string at /usr/share/perl5/vendor_perl/Gitolite/Conf/Load.pm line 252, <DATA> line 1.
remote: 
remote: FATAL: invalid repo ''
remote: error: hook declined to update refs/heads/s390x
To ssh://pkgs.stg.fedoraproject.org/forks/sharkcz/rpms/fedora-release.git
 ! [remote rejected] s390x -> s390x (hook declined)
error: failed to push some refs to 'ssh://sharkcz@pkgs.stg.fedoraproject.org/forks/sharkcz/rpms/fedora-release.git'
  • When do you need this? (YYYY/MM/DD)
    ASAP

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

  • If we cannot complete your request, what is the impact?
    staging instance for src.fp.o is not usable


This is due to it being out of disk space.

Shoud be fixed now.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 months ago

Metadata Update from @sharkcz:
- Issue status updated to: Open (was: Closed)

6 months ago

I'm still getting rejected due the hook :-(

It looks like pkgs01 is running gitolite3-3.6.10-1.el7.noarch which has been reported to break pagure in : https://pagure.io/pagure/issue/3971

I'm going to try to downgrade, but that means we'll need to prevent the update from happening again until we find a fix in either pagure or gitolite :)

@sharkcz gitolite3 has been downgraded, could you try again?

I've tried now and have the same problem still.

Metadata Update from @pingou:
- Issue tagged with: src.fp.o

6 months ago

Metadata Update from @bowlofeggs:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: staging

6 months ago

Metadata Update from @smooge:
- Issue assigned to smooge

5 months ago

@sharkcz please try this again... gitolite has been pulled out completely so if this is still happening we were mis-diagnosing it before :sweat_smile:

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

5 months ago

hi @smooge, I see still the same symptoms.

Can you please paste the entire thing you are seeing.. since there is no gitolite the errors you put originally should not be happening.. so I need to see exactly to give it to the owners.

from a run a moment ago

[dan@talos fedora-release]$ git push sharkcz-stg s390x
Counting objects: 70, done.
Delta compression using up to 64 threads.
Compressing objects: 100% (36/36), done.
Writing objects: 100% (70/70), 13.56 KiB | 6.78 MiB/s, done.
Total 70 (delta 46), reused 50 (delta 33)
remote: Empty compile time value given to use lib at hooks/update line 6.
remote: Use of uninitialized value in require at (eval 13) line 1, <DATA> line 1.
remote: WARNING: Use of uninitialized value $repo in concatenation (.) or string at /usr/share/perl5/vendor_perl/Gitolite/Conf/Load.pm line 251, <DATA> line 1.
remote: 
remote: FATAL: invalid repo ''
remote: error: hook declined to update refs/heads/s390x
To ssh://pkgs.stg.fedoraproject.org/forks/sharkcz/rpms/fedora-release.git
 ! [remote rejected] s390x -> s390x (hook declined)
error: failed to push some refs to 'ssh://sharkcz@pkgs.stg.fedoraproject.org/forks/sharkcz/rpms/fedora-release.git'

OK thanks for the bug report. This will need a fix which needs to be pushed at both our side and CentOS side. ETA for this is unknown at this time.

This should be fixed in pagure 5.3 (coming out soon now). As soon as thats out and passed testing we will schedule updates here.

still a problem :-(

[dan@talos fedora-release]$ git push sharkcz-stg s390x                                                                                                                                  :s390x
Counting objects: 70, done.
Delta compression using up to 64 threads.
Compressing objects: 100% (36/36), done.
Writing objects: 100% (70/70), 13.56 KiB | 6.78 MiB/s, done.
Total 70 (delta 46), reused 50 (delta 33)
remote: Protected namespaces: ['rpms', 'modules', 'container']
remote: Blocking unspecified refs: False
remote: Blacklists: [<_sre.SRE_Pattern object at 0x7f28b061c630>]
remote: User: User: 1399 - name sharkcz
remote: User groups: set([u'packager', u'provenpackager'])
remote: Committer: True
remote: SIG memberships: set([])
remote: RCM: False
remote: Committer push to unprotected
remote: Empty compile time value given to use lib at hooks/update line 6.
remote: Use of uninitialized value in require at (eval 13) line 1, <DATA> line 1.
remote: WARNING: Use of uninitialized value $repo in concatenation (.) or string at /usr/share/perl5/vendor_perl/Gitolite/Conf/Load.pm line 252, <DATA> line 1.
remote: 
remote: FATAL: invalid repo ''
remote: error: hook declined to update refs/heads/s390x
To ssh://pkgs.stg.fedoraproject.org/forks/sharkcz/rpms/fedora-release.git
 ! [remote rejected] s390x -> s390x (hook declined)
error: failed to push some refs to 'ssh://sharkcz@pkgs.stg.fedoraproject.org/forks/sharkcz/rpms/fedora-release.git'

OK I will take this up with @puiterwijk and see why fork permissions are still broken.

So, while I need to see why syncing of new repos to repoSpanner is hitting problems, I have fixed the hook script for this package.
@sharkcz could you try pushing to that fork, to see if it works now?
(Note: my current fix was only for this repository. If this is confirmed to be working, I'll fix it in general)

Thanks Patrick, my push was successful after your change

[dan@talos fedora-release]$ git push sharkcz-stg s390x  
Counting objects: 70, done.
Delta compression using up to 64 threads.
Compressing objects: 100% (36/36), done.
Writing objects: 100% (70/70), 13.56 KiB | 4.52 MiB/s, done.
Total 70 (delta 46), reused 50 (delta 33)
remote: Protected namespaces: ['rpms', 'modules', 'container']
remote: Blocking unspecified refs: False
remote: Blacklists: [<_sre.SRE_Pattern object at 0x7f246f9eb630>]
remote: User: User: 1399 - name sharkcz
remote: User groups: set([u'packager', u'provenpackager'])
remote: Committer: True
remote: SIG memberships: set([])
remote: RCM: False
remote: Committer push to unprotected
remote: Protected namespaces: ['rpms', 'modules', 'container']
remote: Blocking unspecified refs: False
remote: Blacklists: [<_sre.SRE_Pattern object at 0x7f8d2c573630>]
remote: User: User: 1399 - name sharkcz
remote: User groups: set([u'packager', u'provenpackager'])
remote: Committer: True
remote: SIG memberships: set([])
remote: RCM: False
remote: Committer push to unprotected
remote: sh: /usr/lib/python2.7/site-packages/pagure/hooks/files/default_hook.py: Adresář nebo soubor neexistuje
remote: sh: /usr/lib/python2.7/site-packages/pagure/hooks/files/pagure_hook.py: Adresář nebo soubor neexistuje
To ssh://pkgs.stg.fedoraproject.org/forks/sharkcz/rpms/fedora-release.git
   40797ca..aef7132  s390x -> s390x

I think this is fixed now (at least I am able to make and push to forks just fine there).

Reopen if there's anything more to do.

:cherry_blossom:

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 months ago

Login to comment on this ticket.

Metadata