#8286 bugzilla assigning packages to my old email address
Opened a month ago by pkfed. Modified a day ago

I changed my FAS email from pkdevel@yahoo.com to phil@mxbits.io. Along with that I wanted to use pkfed@fedoraproject.org on bugzilla instead of my real email. Kevin (nirik) helped me with this. I set up a new bugzilla account for pkfed@fedoraproject.org and he helped migrate my permissions onto it. So now I have two BZ accounts, the former one I no longer wish to use (pkdevel@yahoo.com) and the new one (pkfed@fedoraproject.org).

When bugs are submitted onto my packages, they are assigned to the wrong BZ account (yahoo). Also interesting is the email preferences for the various apps in Fedora -- I have visited many of them and updated them, BUT, I notice that I am unable to select the "star" on any of them, i.e. I cannot tag one as preferred.

I am also getting some notifications sent to the old address.

ref: https://bugzilla.redhat.com/show_bug.cgi?id=1759988 (see that I had to change emails)
ref: https://pagure.io/fedora-infrastructure/issue/8220 (original pagure issue)


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?

Metadata Update from @kevin:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

a month ago

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!

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.

Login to comment on this ticket.

Metadata