#12428 Link in staging distgit instance leads to prod auth
Closed: Fixed 6 months ago by lenkaseg. Opened a year ago by lenkaseg.

Describe what you would like us to do:


The button for adding members into distgit group leads to authentication on production instance. Correct the link to respect the stg/prod environment.

Check if there's more links in distgit that would cross the stg/prod environment.

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


Not urgent.

Screenshot_From_2025-02-28_09-34-58.png


This also happens when trying to resent the password in .stg. It routes to the prod password reset.
(in case that can be fixed in a similar way/same source).

Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: Needs investigation, low-gain

a year ago

This either means that there is something wrongly configured in the staging deployment or some links are hardcoded in the application. In either case it needs some investigation to find out the cause of this.

Eh, and it originates from my commit 4 years ago...fixing :/

ok, so where is this to be fixed? and is there a upstream link? if so, I think we can close this upstream?

Metadata Update from @lenkaseg:
- Issue assigned to lenkaseg

11 months ago

So, thats likely to land with the next pagure release. ;( I have no idea when that might be...

Do we want to try and do a local hotfix in ansible in the mean time?

@lenkaseg Could you do the local hotfix in ansible, so we don't need to wait for the next pagure release?

Here is the ansible hotfix: https://pagure.io/fedora-infra/ansible/pull-request/2780
Review please, I tried to do it as I saw it done in other places in ansible, but not sure.

Metadata Update from @zlopez:
- Issue untagged with: Needs investigation
- Issue tagged with: low-trouble

6 months ago

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

6 months ago

Log in to comment on this ticket.

Metadata