#3700 github mirroring broken
Closed: Fixed 5 years ago Opened 5 years ago by jhrozek.

SSSD has a github mirror that is normally pushed to by a remote hook on pagure. But it looks like since today's upgrade, the mirroring is broken.

I don't know for sure if this is caused by any of the known issues; if it is, please close this ticket as a duplicate.


This was something custom placed by the infra team, no?

I honestly don't remember. I only remember @puiterwijk helped us set the mirror up. I no longer remember how he did it..

There is now a built-in feature to mirror projects externally, may be a good idea to take a stab at it ;-)
(just to be safe, you may want to try it against a dummy repo on github first)

FreeIPA's mirroring to GH is broken, too. AFAIK we use the same setup as SSSD.

Could either of you provide the full output of a git push?

@puiterwijk Yesterday afternoon (CEST), GH mirroring started to work again. I haven't changed any settings in FreeIPA's GH or Pagure repos.

Here is the server-side output from a git push. The message looks far longer than I remember.

remote: Changes: {u'refs/heads/master': (u'5052641a42e5252f47d0216d6e0164d03177f717', u'e1a30d3ce32aef2492689de8eff09360f5480a99')}        
remote: Running hooks for freeipa        
remote: Auth backend <class 'pagure.lib.git_auth.Gitolite3Auth'> is static-only        
remote: Running plugin default        
remote: Running plugin Pagure tickets        
remote: The ticket hook only runs on the ticket git repository.        
remote: Running plugin Block non fast-forward pushes        
remote: Running legacy hooks with args: [], stdin: 5052641a42e5252f47d0216d6e0164d03177f717 e1a30d3ce32aef2492689de8eff09360f5480a99 refs/heads/master        
remote: 
remote: No handlers could be found for logger "pagure.hooks.default"        
remote: Pushing to github...        
remote: To git@github.com:freeipa/freeipa.git        
remote:    5052641..e1a30d3  master -> master        
remote:    d0c503e..35d3b57  github/ipa-4-7 -> github/ipa-4-7        
remote: Push to github finished        
remote: Changes: {u'refs/heads/master': (u'5052641a42e5252f47d0216d6e0164d03177f717', u'e1a30d3ce32aef2492689de8eff09360f5480a99')}        
remote: Running hooks for freeipa        
remote: Auth backend <class 'pagure.lib.git_auth.Gitolite3Auth'> is static-only        
remote: Running plugin default        
remote: Sending to redis to log activity and send commit notification emails        
remote: * Publishing information for 1 commits        
remote:   - to fedmsg        
remote:   - to web-hooks        
remote: Running plugin Pagure tickets        
remote: Running plugin Block non fast-forward pushes        
remote: Running legacy hooks with args: [], stdin: 5052641a42e5252f47d0216d6e0164d03177f717 e1a30d3ce32aef2492689de8eff09360f5480a99 refs/heads/master        
remote: 
remote: Running legacy hook post-receive.ghpush. Please ask your admin to port this to the new plugin format, as the current system will cease functioning in a future Pagure release        
To ssh://pagure.io/freeipa.git
   5052641a4..e1a30d3ce  e1a30d3ce32aef2492689de8eff09360f5480a99 -> master

@cheimes right. I am going to guess that the other errors were causing it to fail.
And yeah, the message is longer, since we've currently enabled debugging.

I didn't do much for SSSD either. I wanted to set up the mirroring myself, so I enabled the mirror hook in pagure, but the public ssh key never showed up despite a message saying "The public SSH key is being generated by pagure and will be available in this page...."

We had issues with this and pagure 5.1 which just got released should have fixed them.

Could you try again?

Hm, service is refusing the start, I'll have a look at it shortly and get back here

Ok, I fixed the few configuration issues we had around this feature and mirroring seems to work just fine for me now: https://github.com/pypingou/pagure_mirror/branches :)

As far as I can tell, including via: https://github.com/pagure/pagure it is working correctly now :)

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

5 years ago

Login to comment on this ticket.

Metadata