#10441 why can't the scm scripts find me? (failure to create repo after package review)
Closed: Duplicate 2 years ago by kevin. Opened 2 years ago by mattdm.

Describe what you would like us to do:


See https://pagure.io/releng/fedora-scm-requests/issue/39868 -- for some reason, the script can't associate my Bugzilla account with my Fedora one. However, I see in Fedora Accounts that my Bugzilla email is properly set. What's going wrong?

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


Not an emergency but annoying if it's just happening to me.


I am pretty sure none of our tooling is currently making use of the bugzilla
field that was added in the new account system.
IIRC some works needs to be done (iirc in ipsilon) before we can actually make
use of it

Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: dev, high-trouble, medium-gain

2 years ago

FASJSON does not currently return the RHBZ email value, but I can easily add it: https://github.com/fedora-infra/fasjson/issues/288.

Metadata Update from @abompard:
- Issue untagged with: dev, high-trouble, medium-gain
- Issue priority set to: Needs Review (was: Waiting on Assignee)

2 years ago

Metadata Update from @abompard:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: dev, high-trouble, medium-gain

2 years ago

IIRC there is also the issue of sending the correct email to BZ when login in
via ipsilon/noggin

Wait, so this wasn't working for anyone? How did this ever work before?

Especially since there seems to be no way to intervene (I kept re-opening the ticket, it kept getting auto-closed by the script...) seems like we need this fixed! I can't possibly be the only one....

Wait, so this wasn't working for anyone? How did this ever work before?

Before we had a hard coded list of exceptions for people who wanted different bugzilla and main addresses.

Especially since there seems to be no way to intervene (I kept re-opening the ticket, it kept getting auto-closed by the script...) seems like we need this fixed! I can't possibly be the only one....

We have been working on it.... see ticket 9863.
The validation is now working. We need to clear all old unvailidated content, then enable tools to use it.

Ah, okay. Is there a workaround in the meantime?

Wait, so this wasn't working for anyone? How did this ever work before?

Before we had a hard coded list of exceptions for people who wanted different bugzilla and main addresses.

We still do, toddlers uses it :)

Currently the only workaround I know is to make sure your bugzilla account and fedora primary email are the same. ;(

Lets track this in https://pagure.io/fedora-infrastructure/issue/9863 since thats what we have been using to do the work.

Hopefully we will have this working soon!

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

2 years ago

Login to comment on this ticket.

Metadata
Boards 1
dev Status: Backlog