So, I don't see how our current override is working at all. It seems to me it should be broken for everyone with an override. :(

We override fas (but that just grants the fedoraproject.org address packager privs). Nothing overrides it for the assignment...

@pingou can you confirm? Am I missing something here?

When I log into pagure (here) and select preferences/email, I see my correct and current fas email (mxbits) and my (fedoraproject) email, but the notifications, e.g. that a new comment was posted above, are being sent to my yahoo email which I am trying to get away from. That yahoo address is stuck in some internal area that I cannot access to remove it.

So there are (at least) two problems -- fedora is still notifying me at yahoo and bugzilla is assigning bugs to me at yahoo.

On pagure, on your settings' page you can have multiple email, one of which is the default one.
Looking at the pagure database, it looks like the yahoo email is set to be your default email thus the one that will be used to send you notifications.

For dist-git we know the sync script is misbehaving and we need some time to fix it but haven't done so yet :(

@pingou Yeah but you see the yahoo account on your side, but I don't see it at all. This is the problem.

I added the old yahoo address back into pagure and src.fedoraproject.org and I see three addresses now:

pkdevel@yahoo.com (starred)
phil@mxbits.io (unstarred, my desired email, also in FAS)
pkfed@fedoraproject.org (unstarred)

I cannot select email address 2 or 3 using the star button. It is simply not working. It is locked on the yahoo email. I tried different browsers and with no extensions running -- it refuses to alow a change to another email.

Please help me purge the yahoo address, completely, from fedora. Changing email should not be so painful.

I've just tried changing my default email address and it looks like there is indeed a bug in pagure :(

I've adjusted your account in the DB to set the default_email to be your mxbits.io email.

Sorry for the inconvenience!

Pagure issue reported at: https://pagure.io/pagure/issue/4639

I've just tried changing my default email address and it looks like there is indeed a bug in pagure :(
I've adjusted your account in the DB to set the default_email to be your mxbits.io email.
Sorry for the inconvenience!

@pingou My default email is correct after your change in pagure, but elsewhere, e.g. in src.fedoraproject.org, the default email remains set to yahoo. Not sure why the contact setting is stored in so many different places.

This has been fixed as part of https://pagure.io/fedora-infrastructure/issue/8372

I propose we close this ticket as the underlying issue is being tracked upstream as well.

Sorry again for the inconvenience @pkfed :(

@pingou Before you close this one, could you please submit a test bug on bugzilla to fedora project slurm. I want to see how the bug email is delivered.

https://bugzilla.redhat.com/show_bug.cgi?id=1772548
Email sent to:
.... pkdevel@yahoo.com, ....

There's no mxbits.io on cc

@pingou Before you close this one, could you please submit a test bug on bugzilla to fedora project slurm. I want to see how the bug email is delivered.

The issue, as pointed out by @karsten for this to work is that we first need to fix: https://pagure.io/fedora-infrastructure/issue/7690

This work is being planned to be worked on in the coming weeks, we will be announcing that when we're ready as I expect this will impact more people in the community and I want everyone to have a chance to review the changes before we push them out.
So keep an eye to devel or devel-announce :)

@pingou OK, I did get the email on the yahoo address (unfortunately) as is mentioned above. I want to ask you about the end result here, since I now have two accounts on bugzilla: the old one (yahoo) and the fp.o alias which points to mxbits. WIll the script that you deploy "break" because there is no existing mxbits account on bz? I really don't want three bz accounts. I had hoped an alias address would afford me more flexibility, but I am almost sure the absense of a true mxbits account on bz will cause yet another problem.

You're not the only one using their @fedoraproject.org alias on bugzilla so no worries, that's the use-case we'll have to support :)

@pingou I'm going to add an mxbits account to bugzilla because this sentence from the requirements statement of bug 7690 absolutely terrifies me:

If there is not a bugzilla account corresponding to the email set in FAS for
this user, orphan the package or remove the person from the watch list.

It is badly formulated, this meant to be read something like: no bugzilla account corresponding to the email set in FAS or in its override for this user.

It's to prevent the cases we've had a few times in the past where people have 0 bugzilla account and still asked to be CC'ed (or worst, made assignee) on bugs.

I don't think we'll want the removal to be immediate, that's not acceptable indeed. For CC'ed I'd be fine, but surely not for default assignee.
The way the current script works is that it notifies the packagers first, asking them to take corrective actions. @kevin and I are CC'ed on these notifications.

Ideally we would just make it so you can never get in the bad state in the first place (ie, all those places that add you to cc/assignee should check and make sure you have a bz account (either with your fas email or your fedoraproject alias). I am not sure if thats possible yet given the tools we have, but thats what we should work for, IMHO.

@pingou I'm going to add an mxbits account to bugzilla

I'm using you as a test case for the updated script, out of curiosity did you end up creating an mxbits account on bugzilla finally?

@pingou Nope, bugzilla still has only the yahoo and fp.o alias. I'm trusting your promise not to orphan my packages.

@pingou Nope, bugzilla still has only the yahoo and fp.o alias. I'm trusting your promise not to orphan my packages.

Thanks, that will help us :)

On the comment line 282 below , please make this correction: pkfed at mxbits should be phil @ mxbits. The fp.o alias below the comment is correct -- leave that alone.
| https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/distgit/pagure/files/fas2.py#n282

On the comment line 282 below

You did see that this line is a comment right? The information it contains is purely informational, it does not influence the logic of the script in any way :)

I've fixed it though so that information is up to date for you :)

I'm curious when the fix will actually be deployed. I am still getting my bugs assigned to the old yahoo address.

I'm curious when the fix will actually be deployed. I am still getting my bugs assigned to the old yahoo address.

Planned for this week, we didn't want to turn it on before the shutdown :)

The script has been running since yesterday and finished successfully both times.

So I believe this is now fixed. Could you confirm that it worked for you as well?

The script has been running since yesterday and finished successfully both times.
So I believe this is now fixed. Could you confirm that it worked for you as well?

Still broken. I logged into bz with my yahoo account and created
https://bugzilla.redhat.com/show_bug.cgi?id=1789821

I then logged in with my fp.o account and created
https://bugzilla.redhat.com/show_bug.cgi?id=1789828

In both cases my expectation was that the bug would be assigned to my fp.o account and in both cases bz assigned the bugs to yahoo and sent emails to yahoo.

Bug 1789828 has been successfully created Email sent to: bulletins-coordon@cert.orangecyberdefense.com, fedora.qa@rmrf.net, <hidden by me>@yahoo.com, bugbot@bugzilla.org

Ok, I see the issue for slurm.
Slurm has an user: @yuwata who is watching it for both commits and tickets: https://src.fedoraproject.org/api/0/rpms/slurm/watchers
However, that user does not have a bugzilla account associated with their email address.

So when the script tries to update the information in bugzilla, it sends the default_assignee and the CC list in one request, which fails since one of the person in the CC list does not have an account.

The solution would be to:
- Ask @yuwata to create a bugzilla account for their email set in FAS
- Remove @yuwata from the watchers list (on tickets)
- Have the script perform multiple queries (but the bugzilla admins would not like this as it puts a certain load on the server then)

People are free to come and go as watchers. I want no involvement in that.

The default assignee should be the maintainer's starred email address. I thought that was the whole point of the star feature. I don't think it should be more complicated than that.

Edit: I forgot you have that hard-coded exception list for fp.o addresses.

Edit: I just noticed another problem -- in pagure, the star selector will not let me select the fp.o entry -- I can only use the yahoo and mxbits stars.

The default assignee should be the maintainer's starred email address. I thought that was the whole point of the star feature. I don't think it should be more complicated than that.

The star feature is for notifications coming from pagure/src.fp.o not for bugzilla integration. This relies on either the email set in FAS or the override asked to the infra team (which is your case).

The issue here isn't with your account but with @yuwata's.

You can remove him from ticket watchers if you want to, but I don't see how that fixes the problem permanently.

Hypothetical question. Suppose I abandon the fp.o alias and use an alias that I create on my side (an mxbits alias), as follows:

1) Create an mxbits email alias called (new alias at mxbits).
2) Set my email in fedora to (new alias at mxbits).
3) Create a matching bugzilla account (new alias at mxbits).

Would this make the problem go away even if the other watchers remained?

Would this make the problem go away even if the other watchers remained?

No, since all the changes are done in a single query, if one of the change fails the entire query fails and thus the other changes (in this case the default assignee) aren't applied.

Back up one step. When a bug is created for my projects, why is my old yahoo address being used as the default assignee in the first place?

I thought your script was managing the transition of the bug from the maintainers true email address (mxbits) to the fp.o alias. The fact that this old yahoo email is STILL being pulled into the equation is a mystery wrapped in an enigma.

I don't understand why this is such a problem. I don't understand why I am now being asked to contact third watcher parties. I just want the yahoo address to go away. Such heavy lifting for such a minor request. My goodness.

Euh, there is some mis-communication here, I have asked to confirm if it worked and you told me it didn't. So I went and look at why it didn't and provided the answer here.

So:

I thought your script was managing the transition of the bug from the maintainers true email address (mxbits) to the fp.o alias

this is correct but as I have explained above it doesn't work at the moment.

I don't understand why I am now being asked to contact third watcher parties

I have not asked you anything of the sort, merely tried to explain what the current situation and problem is.

If I understand correctly, your script needs to run once successfully to correct the email problem permanently, i.e. it need not run on a per bug basis. Once it finishes successfully at least once, all will be well and it need not run again unless my email situation changes sometime in the future.

I don't have the ability to manage ticket watchers, but surely you can on your side. Can you remove him, run your script to completion and re-add him?

After contacting @yuwata and not hearing from them, I took it on myself to remove them from the (tickets) watchlist for slurm.
The sync script just ran and I've received notifications from bugzilla that it worked: https://bugzilla.redhat.com/show_bug.cgi?id=1772548

I think we can finally consider this ticket fixed!