#9109 Default RHBZ assignee for nginx not synced with src.fpo
Closed: Fixed 3 years ago by pingou. Opened 3 years ago by jamielinux.

Describe what you would like us to do:

9 months ago I gave Main Admin of nginx to fas=heffer, but this morning the NEW nginx bug rhbz#1853789 got assigned to me instead of heffer.

I assume something went wrong with the sync between src.fpo and RHBZ?

Can you please change the RHBZ default Assignee for nginx to heffer?

Also, having recently given or orphaned 200+ packages, it's possible there are many other packages in RHBZ where the default Assignee is still me by mistake. I have Main Admin on only one package now (rpms/bashmount). If it's possible for you to easily search, am I default Assignee for anything else by mistake?

Thank you! :-)

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

Not urgent.


So the sync is indeed failing because the user @affix does not have a bugzilla account associated with the email they have set on bugzilla.

This is direct consequences of the situation we've been calling out for in our emails: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/HDK6TTRXN7BQTYNSOR3TA5HMMKWQ5UQT/

If you have a way to contact @affix and to ask them to create a bugzilla account with the email they have set in FAS, the sync will fix itself.

(Note that @affix's situation affects both Fedora and Fedora EPEL, the module is affect because of the account of @rpitonak, different account but same issue though).

@jamielinux Please contact the main-admin of nginx @heffer to make the necessary changes (removing @affix) or contact @affix to make the bz account.

Metadata Update from @mohanboddu:
- Issue close_status updated to: Will Not/Can Not fix
- Issue status updated to: Closed (was: Open)

3 years ago

Thanks for the replies.

I don't even have commit access to nginx package (I gave it up), so I am just an innocent bystander here affected by the sync script.

I don't understand why you can't change it manually? While waiting for affix to reply (which could be several weeks or never), new bugs will still get assigned to me.

If you could prod things to make the assignee not be me, that would be greatly appreciated :)

Metadata Update from @jamielinux:
- Issue status updated to: Open (was: Closed)

3 years ago

Well, who do we assign the bugs to? We can't assign them to affix (they have no bugzilla account). Should we randomly pick someone, we have no idea who is active there or wants the bugs...

I have removed @affix from the RPM and @rpitonak from the module for the time being. They can reach out to me after linking their email address to BZ for regaining access to the repo.

Well, who do we assign the bugs to? We can't assign them to affix (they have no bugzilla account). Should we randomly pick someone, we have no idea who is active there or wants the bugs...

@kevin Main Admin (heffer) would have been a fine choice ;)

@heffer Brilliant, thank you!

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

3 years ago

Nginx bugs for EPEL 7/8 are still being assigned to me. (I am not a committer or admin.)

https://bugzilla.redhat.com/show_bug.cgi?id=1867577
https://bugzilla.redhat.com/show_bug.cgi?id=1867261

Could you please change the default bugzilla assignee to the main admin (heffer)?

Metadata Update from @jamielinux:
- Issue status updated to: Open (was: Closed)

3 years ago

So looking at https://src.fedoraproject.org/api/0/rpms/nginx/watchers you can see the user @affix is listed there and @affix is one of the remaining 12 users that do not have a valid bugzilla account and that I've asked FESCo for input on: https://pagure.io/fesco/issue/2460

Thank you @pingou :) I'll watch and wait.

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

3 years ago

The user affix has been removed from this package, turns out the script has not run in a few days because of a bug that we just fixed. So (fingers crossed) this should be fixed in the next run :)

Metadata Update from @pingou:
- Issue assigned to pingou

3 years ago

Next run happened and correctly synced to bugzilla.

We should be all set now for this ticket!

Let us know if you still face issues.

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

3 years ago

Great, thank you. Hopefully that's sorted now.

Login to comment on this ticket.

Metadata