#1879 Regenerating git repo for Issues does not work
Closed: Invalid 7 years ago Opened 7 years ago by mreynolds.

A ticket migration failed during the push phase because it timed out. Trying to reset the ticket repo, so we can try another push, also times out and fails. Now we are stuck, and can not migrate to pagure

This is blocking our migrations, and it is very important to get this fixed asap.

For more info see : https://pagure.io/pagure-importer/issue/117


This is the error:

The connection has timed out
The server at pagure.io is taking too long to respond.
The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer's network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.

This was the third attempt today.

We tried this from a different system and it did not time out. However, we still can't push our tickets, but I'll use the pagure-importer issue to track that.

@mreynolds changed the status to Closed

7 years ago

So what could be happening there is that the hook takes a while to process all the tickets and thus the client thinks the server is not responding (while it's just being busy).
If you let it run for a while, do you see something in the UI?

I've added (in prod and stg) a flush to force the print of info as they go, this should send back data and potentially avoid that time-out.

Let me know if it helps.

It "worked" when I used a different system, but I have no idea what it is supposed to do. I was told by @cverna that it would reset issues, but after running it all the issues are still there. So I have no idea what this feature is supposed to do - but whatever it is, it's not helping us do another "pgimort push".

@mreynolds this feature it supposed to re-generate the JSON files in the ticket/PR git repo using the info in the DB (helpful if you want to export the data and update the JSON of old issues).

With the changes made by @vivek, if there are no issues/PRs for the project in the DB, the git repos will be re-initialized, so for example if you pushed to the ticket git repo but forgot to activate the pagure ticket hook, then you can re-do the push after having re-initialized the ticket git repo on the server (ie you're restarting from scratch)

Yeah that's not the case with us. The pgimport push almost finished, then it timed out. So there were issues imported, but not all them. So we need to start over, and there does not seem to be a way to do that.

Login to comment on this ticket.

Metadata