Is the long thread of emails for people getting asked to deal with bugzilla related to any software updates that happened this week?
---------- Forwarded message ---------- From: Christian Dersch lupinix.fedora@gmail.com Date: 16 December 2017 at 14:08 Subject: Re: Please fix your bugzilla.redhat.com account To: accounts@fedoraproject.org Cc: kevin@fedoraproject.org, pingou@fedoraproject.org, ralph@fedoraproject.org, mprahl@fedoraproject.org
Hi,
what is the issue here? I use lupinix.fedora@gmail.com for both (changed mail ~2 months ago, but have been always in sync for FAS and bugzilla) and also receive the bugzilla mails for my packages.
Greetings, Christian
On 12/16/2017 08:03 PM, accounts@fedoraproject.org wrote:
Greetings.
You are receiving this email because there's a problem with your bugzilla.redhat.com account.
If you recently changed the email address associated with your Fedora account in the Fedora Account System, it is now out of sync with your bugzilla.redhat.com account. This leads to problems with Fedora packages you own or are CC'ed on bug reports for.
Please take one of the following actions:
a) login to your old bugzilla.redhat.com account and change the email address to match your current email in the Fedora account system. https://bugzilla.redhat.com login, click preferences, account information and enter new email address.
b) Create a new account in bugzilla.redhat.com to match your email listed in your Fedora account system account. https://bugzilla.redhat.com/ click 'new account' and enter email address.
c) Change your Fedora Account System email to match your existing bugzilla.redhat.com account. https://admin.fedoraproject.org/accounts login, click on 'my account', then 'edit' and change your email address.
If you have questions or concerns, please let us know.
Your prompt attention in this matter is appreciated.
The Fedora admins.
On 12/17/2017 09:54 AM, Stephen John Smoogen wrote:
Is the long thread of emails for people getting asked to deal with bugzilla related to any software updates that happened this week?
Yeah, I suspect it's a bug in the new pagure-sync-bugzilla script that ralph landed friday. ;(
I am not sure what the bug is off hand, but perhaps someone could track it down based on that (I think Ralph is out the rest of the year now, but perhaps he will check in or Pierre or Patrick can see what the issue is).
kevin --
---------- Forwarded message ---------- From: Christian Dersch lupinix.fedora@gmail.com Date: 16 December 2017 at 14:08 Subject: Re: Please fix your bugzilla.redhat.com account To: accounts@fedoraproject.org Cc: kevin@fedoraproject.org, pingou@fedoraproject.org, ralph@fedoraproject.org, mprahl@fedoraproject.org
Hi,
what is the issue here? I use lupinix.fedora@gmail.com for both (changed mail ~2 months ago, but have been always in sync for FAS and bugzilla) and also receive the bugzilla mails for my packages.
Greetings, Christian
On 12/16/2017 08:03 PM, accounts@fedoraproject.org wrote:
Greetings.
You are receiving this email because there's a problem with your bugzilla.redhat.com account.
If you recently changed the email address associated with your Fedora account in the Fedora Account System, it is now out of sync with your bugzilla.redhat.com account. This leads to problems with Fedora packages you own or are CC'ed on bug reports for.
Please take one of the following actions:
a) login to your old bugzilla.redhat.com account and change the email address to match your current email in the Fedora account system. https://bugzilla.redhat.com login, click preferences, account information and enter new email address.
b) Create a new account in bugzilla.redhat.com to match your email listed in your Fedora account system account. https://bugzilla.redhat.com/ click 'new account' and enter email address.
c) Change your Fedora Account System email to match your existing bugzilla.redhat.com account. https://admin.fedoraproject.org/accounts login, click on 'my account', then 'edit' and change your email address.
If you have questions or concerns, please let us know.
Your prompt attention in this matter is appreciated.
The Fedora admins.
On Sun, Dec 17, 2017 at 10:19:27AM -0800, Kevin Fenzi wrote:
On 12/17/2017 09:54 AM, Stephen John Smoogen wrote:
Is the long thread of emails for people getting asked to deal with bugzilla related to any software updates that happened this week?
Yeah, I suspect it's a bug in the new pagure-sync-bugzilla script that ralph landed friday. ;(
Hi,
Turns out, we had a small bug in our logic that made the script check the wrong bugzilla instance.
This has been fixed in: http://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=e7eb8bb
Fingers crossed it's the only fix needed :)
Pierre
Pierre-Yves Chibon wrote:
On Sun, Dec 17, 2017 at 10:19:27AM -0800, Kevin Fenzi wrote:
On 12/17/2017 09:54 AM, Stephen John Smoogen wrote:
Is the long thread of emails for people getting asked to deal with bugzilla related to any software updates that happened this week?
Yeah, I suspect it's a bug in the new pagure-sync-bugzilla script that ralph landed friday. ;(
Hi,
Turns out, we had a small bug in our logic that made the script check the wrong bugzilla instance.
This has been fixed in: http://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=e7eb8bb
Fingers crossed it's the only fix needed :)
I don't know if it's related, but I appear to be listed as the default assignee for mock bugs in bugzilla. I am not even a co-maintainer of mock though. This looks like it could be a combination of the bug(s) which included forks in various queries for maintainers and the bugzilla sync script.
I filed https://pagure.io/fedora-infrastructure/issue/6593 for this.
--- I wrote:
I don't know if it's related, but I appear to be listed as the default assignee for mock bugs in bugzilla. I am not even a co-maintainer of mock though. This looks like it could be a combination of the bug(s) which included forks in various queries for maintainers and the bugzilla sync script.
I filed https://pagure.io/fedora-infrastructure/issue/6593 for this.
I also attached this patch to the ticket, but in case it's easier to review here, I'll include it. I could be way off on this, so it definitely needs checked by those who know pagure/distgit. :)
roles/distgit/pagure/templates/pagure-sync-bugzilla.py.j2 | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/roles/distgit/pagure/templates/pagure-sync-bugzilla.py.j2 b/roles/distgit/pagure/templates/pagure-sync-bugzilla.py.j2 index cf6c411e8..16c23b1e8 100644 --- a/roles/distgit/pagure/templates/pagure-sync-bugzilla.py.j2 +++ b/roles/distgit/pagure/templates/pagure-sync-bugzilla.py.j2 @@ -694,11 +694,13 @@ if __name__ == '__main__': poc_url = PAGURE_DIST_GIT_URL + '/extras/pagure_poc.json' if DEBUG: print("Querying %r for points of contact." % poc_url) - pagure_namespace_to_poc = session.get(poc_url, timeout=120).json() + pagure_namespace_to_poc = session.get( + poc_url, params={'fork': False}, timeout=120).json() cc_url = PAGURE_DIST_GIT_URL + '/extras/pagure_bz.json' if DEBUG: print("Querying %r for initial cc list." % cc_url) - pagure_namespace_to_cc = session.get(cc_url, timeout=120).json() + pagure_namespace_to_cc = session.get( + cc_url, params={'fork': False}, timeout=120).json() · # Combine and collapse those two into a single list: pagure_projects = [] --· 2.15.1
On 12/21/2017 06:51 AM, Todd Zullinger wrote:
Pierre-Yves Chibon wrote:
On Sun, Dec 17, 2017 at 10:19:27AM -0800, Kevin Fenzi wrote:
On 12/17/2017 09:54 AM, Stephen John Smoogen wrote:
Is the long thread of emails for people getting asked to deal with bugzilla related to any software updates that happened this week?
Yeah, I suspect it's a bug in the new pagure-sync-bugzilla script that ralph landed friday. ;(
Hi,
Turns out, we had a small bug in our logic that made the script check the wrong bugzilla instance.
This has been fixed in: http://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=e7eb8bb
Fingers crossed it's the only fix needed :)
I don't know if it's related, but I appear to be listed as the default assignee for mock bugs in bugzilla. I am not even a co-maintainer of mock though. This looks like it could be a combination of the bug(s) which included forks in various queries for maintainers and the bugzilla sync script.
I filed https://pagure.io/fedora-infrastructure/issue/6593 for this.
Should be all fixed now.
The script broke due to test namespace changes. Thats fixed and it has run and should have set everything back.
kevin
infrastructure@lists.fedoraproject.org