You can reset you ticket git repo, but I can't remember if it reset the database too .

I think we need @pingou advice here.

If you try pushing again does it say something?

I am going to fix this: https://pagure.io/pagure/issue/1603 then syncing db and git repo won't be a problem. Any failures that happen in between the push shouldn't be a problem then.

That would be great. This is potentially something that is going to hit several teams very soon (as we are all migrating in the next week).

Also, I'm going to have my colleague try the push again once he gets to work.

Trying to push again sayings everything is update to date.

Tried "Regenerating issues" but that timed out, and the push now fails (instead of saying up to date):

# script -c "time pgimport push test-dogtag-pki.git" typescript.push_2
Script started on Thu 09 Feb 2017 09:42:21 AM MST
Before executing this command, you must have "Pagure Tickets" enabled from pagure project's settings. Continue? [y/N]: y
To ssh://pagure.io/tickets/test-dogtag-pki.git
 ! [rejected]        master -> master (fetch first)
error: failed to push some refs to 'ssh://git@pagure.io/tickets/test-dogtag-pki.git'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

@cverna how do you reset the ticket repo?

I was referring to the regenerate git repo for ticket option in the settings

I was referring to the regenerate git repo for ticket option in the settings

Its not working. It just times out and pushing still fails as noted above. Opening a new issue for it...

Note - we're running out of time to get this stuff working before we are kicked off of fedorahosted/trac :(

Okay the regeneration worked from another system, but we still can not push our tickets :(

Do we need to redo the entire migration process? Reclone the ticket repo, reimport the tickets from trac, and then push again?

Trying this now, but we won't know until tomorrow if it works because it takes so long

So clicking on "Regenerate git repo of Issues" has no effect. All the issues are still there and "pgimport push" still fails as noted above. @mharmsen went through the entire migration process again, but we still can not do a "pgimport push" after the first attempt of pushing failed.

What can we do to fix this issue?

Could you share the output of the pgimport push command?

Eventually, if you go to /tmp/<repo>.git and do a git push from there?

Could you share the output of the pgimport push command?
Eventually, if you go to /tmp/<repo>.git and do a git push from there?

The output is already listed a few comments up...

It hasn't changed with the changed I put server side?

I don't have access to mharmsen's system. He'll be online in a few hours. I'm just sharing what he sent me last night.

Btw, I'm seeing some issues imported at https://pagure.io/test-dogtag-pki/issues (looks like b/w 800 and 900). How many issues should have been imported?

Btw, I'm seeing some issues imported at https://pagure.io/test-dogtag-pki/issues (looks like b/w 800 and 900). How many issues should have been imported?

almost 3000

Ok, do you still have the git repo in your /tmp? Does it contain all 3K JSON files?

This is on mharmsens system. I'm assuming its still there. He's not online yet, but when he is I'll find out. I do know "pgimport fedorahosted" said it imported all the tickets.

I don't see any json files. All I see is:

-bash-4.3$ cd test-dogtag-pki.git
-bash-4.3$ ls -la
total 16
drwxr-xr-x. 7 mharmsen mharmsen 220 Feb 9 15:07 .
drwxrwxrwt. 17 root root 380 Feb 10 09:34 ..
drwxr-xr-x. 2 mharmsen mharmsen 40 Feb 9 15:07 branches
-rw-r--r--. 1 mharmsen mharmsen 139 Feb 9 15:07 config
-rw-r--r--. 1 mharmsen mharmsen 73 Feb 9 15:07 description
-rw-r--r--. 1 mharmsen mharmsen 23 Feb 9 15:07 HEAD
drwxr-xr-x. 2 mharmsen mharmsen 220 Feb 9 15:07 hooks
drwxr-xr-x. 2 mharmsen mharmsen 60 Feb 9 15:07 info
drwxr-xr-x. 4 mharmsen mharmsen 80 Feb 9 15:07 objects
-rw-r--r--. 1 mharmsen mharmsen 98 Feb 9 15:07 packed-refs
drwxr-xr-x. 4 mharmsen mharmsen 80 Feb 9 15:07 refs

This shouldn't be a problem anymore since, pagure now loads json in a different service.

Fixed in : https://pagure.io/pagure/pull-request/1911