#9012 Cannot push to pagure.io/docs/odcs.git
Opened 2 months ago by jkaluza. Modified a month ago

Log from Jenkins job:

15:01:40 + git commit -m 'Automatic commit of docs built by Jenkins job ${env.JOB_NAME} #${env.BUILD_NUMBER}'
15:01:40 [master c993621] Automatic commit of docs built by Jenkins job ${env.JOB_NAME} #${env.BUILD_NUMBER}
15:01:40  17 files changed, 496 insertions(+), 193 deletions(-)
15:01:40  rewrite searchindex.js (86%)
15:01:40 + git push origin master
15:01:42 remote: Empty compile time value given to use lib at hooks/update line 6.        
15:01:42 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.        
15:01:42 remote: 
15:01:42 remote: FATAL: invalid repo ''        
15:01:42 remote: error: hook declined to update refs/heads/master        
15:01:42 To ssh://pagure.io/docs/odcs.git
15:01:42  ! [remote rejected] master -> master (hook declined)
15:01:42 error: failed to push some refs to 'ssh://git@pagure.io/docs/odcs.git'

I ran into the same issue from another Jenkins job: https://pagure.io/pagure/issue/4763
In this case though I think there is no deployment key used.

This is likely an upstream issue but I'll pick it up, nothing changed in pagure.io recently (except for the 5.10 release being deployed there) that should result in this.

This is broken for some time already, but I've just noticed it. The jenkins job which cannot commit is executed only when ODCS documentation is updated and this is not done quite often.

It failed for first time on May 22, 2020 6:10 AM.

I ran into the same issue from another Jenkins job: https://pagure.io/pagure/issue/4763
In this case though I think there is no deployment key used.

From the discussion on IRC, it is using a deploy key there as well, so it is the same bug.

Let's see if I can fix this quickly

So annoyingly, I'm not able to reproduce the error, I have generated a ssh key in a brand new user on my machine, set it up in pagure.io for the pagure project as a deploy key with commit access.

Using this blank profile, I was able to push to the pagure docs repo :(

Could it be some left over file in the repo on the server?

If you try deleting and re-uploading the key, does it change anything?

Metadata Update from @smooge:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: groomed, low-trouble, medium-gain, pagure

2 months ago

@lsedlar should we schedule some time for both of us to try to get to the bottom of this? (and if you could set-up an user that has access to the private key before that would be awesome)

Login to comment on this ticket.

Metadata