Pagure completely broke after re-forking fedora-server #12388

Open
opened 2025-02-05 23:03:33 +00:00 by vigrond · 7 comments

NOTE

If your issue is for security or deals with sensitive info please
mark it as private using the checkbox below.

Describe what you would like us to do:


I wanted to contribute to fedora by creating a pull request for updates I made to the documentation.

In typical fashion, I completely broke the system and I am unable to recover:

  • had to create a fedora accounts account first, then sign the agreement, or pagure just hangs and is unresponsive
  • I wanted to scrub my existing fork, so I deleted it in pagure with the intention of recreating it.
  • When trying to fork again in pagure, after a long http request, it fails with a cryptic 500 error: " Fatal Error (500) A fatal error has occurred, we're sorry :("
  • All other repository pages produce the same cryptic error - issues, history, etc
  • There are now 2 fedora-server forks in my pagure account, with no way of deleting them, and when I try to access them, the above 500 error occurs.
  • There is no way to clear or delete my Pagure account from the UI
  • There is no way to clear or delete my Fedora Accounts account

It appears my account is completely fubared, with no way to recover it. Is there a way to "reset"?

When do you need this to be done by? (YYYY/MM/DD)


**NOTE** If your issue is for security or deals with sensitive info please mark it as private using the checkbox below. # Describe what you would like us to do: ---- I wanted to contribute to fedora by creating a pull request for updates I made to the documentation. In typical fashion, I completely broke the system and I am unable to recover: - had to create a fedora accounts account first, then sign the agreement, or pagure just hangs and is unresponsive - I wanted to scrub my existing fork, so I deleted it in pagure with the intention of recreating it. - When trying to fork again in pagure, after a long http request, it fails with a cryptic 500 error: " Fatal Error (500) A fatal error has occurred, we're sorry :(" - All other repository pages produce the same cryptic error - issues, history, etc - There are now 2 fedora-server forks in my pagure account, with no way of deleting them, and when I try to access them, the above 500 error occurs. - There is no way to clear or delete my Pagure account from the UI - There is no way to clear or delete my Fedora Accounts account It appears my account is completely fubared, with no way to recover it. Is there a way to "reset"? # When do you need this to be done by? (YYYY/MM/DD) ----
Contributor

Few things first:

  • Could you provide the links for the repositories that are having the issues?
  • You shouldn't be able to delete your pagure or fedora account by yourself.
Few things first: * Could you provide the links for the repositories that are having the issues? * You shouldn't be able to delete your pagure or fedora account by yourself.
Contributor

Metadata Update from @zlopez:

  • Issue priority set to: Waiting on Assignee (was: Needs Review)
  • Issue tagged with: Needs investigation, low-gain, ops
**Metadata Update from @zlopez**: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: Needs investigation, low-gain, ops
Author
the issue began when clicking "fork" from this link https://pagure.io/fedora-server/blob/main/f/docs/modules/ROOT/pages/services/filesharing-nfs-installation.adoc which is the https://pagure.io/fedora-server repo

There were definitely 2 projects for this fork, causing pagure to throw a 500 for returning 2 rows when it expected only one.

I tried to delete the older one, but somehow it's still showing up, and I can't see why. ;(

There were definitely 2 projects for this fork, causing pagure to throw a 500 for returning 2 rows when it expected only one. I tried to delete the older one, but somehow it's still showing up, and I can't see why. ;(
Contributor

Probably needs some database cleaning as well.

Probably needs some database cleaning as well.

Well, I deleted that row, but there must be something else thats keeping it thinking there's duplicates.

Perhaps @pingou could save us?

Well, I deleted that row, but there must be something else thats keeping it thinking there's duplicates. Perhaps @pingou could save us?

Or perhaps @abompard might be able to see something?

Or perhaps @abompard might be able to see something?
Sign in to join this conversation.
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Infrastructure/fedora-infrastructure#12388
No description provided.