#11169 Dedicated bugzilla account/email address for the FTI bugzillas
Closed: Fixed a year ago by churchyard. Opened a year ago by churchyard.

  • Describe the issue

I run a script from this repository that opens bugzillas for packages that fail to install according to https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs

Since I use my personal/work bugzilla account for this, it has some disadvantages:

  • some non-RH contributors seem to be unhappy that a Red Hat account is telling them their package is broken
  • some contributors assume this is my personal initiative
  • I don't get a reminder when my own package breaks
  • I get a lot of bugzilla emails about packages I don't care about specifically

I'd appreciate it if I can get a dedicated bugzilla account for this. Ideally, it would be a @fedoraproject.org email address that is redirected to me, so I can setup my email filters. I can open the Bugzilla account myself, once I get such an email address. I'd like to avoid creating a fake FAS account for the address but will do so if you instruct me to do so.

The email address could be installation-failures@fedoraproject.org or even policy@fedoraproject.org.

  • When do you need this? when possible

  • When is this no longer needed or useful? when I burn out and stop doing this or when we stop requiring bugzillas for our policies

  • If we cannot complete your request, what is the impact? unhappy contributors, sad Miro

Thanks,


Metadata Update from @kevin:
- Issue tagged with: low-trouble, medium-gain, ops

a year ago

If we cannot complete your request, what is the impact? unhappy contributors, sad Miro

+1 for this alone

The email address could be installation-failures@fedoraproject.org or even policy@fedoraproject.org.

Perhaps fti@fedoraproject.org or fti-bugs@fedoraproject.org would be better? failures has a negative connotation and policy feels harsh.

Thanks. Testing the alias. So far the email was not delivered in 5+ minutes.

550 5.1.1 fti-bugs@fedoraproject.org: Recipient address rejected: User unknown in local recipient table

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

a year ago

Somehow it didn't get deployed. I did run the playbook, but perhaps it failed in some way that wasn't obvious on that host?

Anyhow I have run it again and confirmed it's there now.

The email alias works, thank you.

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

a year ago

So the email works and I have created the Bugzilla account, but it apparently:

  • cannot close bugzillas created by my old account
  • cannot add the F38FailsToInstall tracker to the blocks field of new bugzillas

I think the account is treated as non-packager and should be treated as a Fedora packager. Maybe it needs to be added to the fedora_contrib group?

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

a year ago

I've added it to fedora_contrib / fedora_bugs. Can you check if it can do all it needs to now?

BTW, does this count as a 'bot account' ? if so, it likely needs the wiki page with information on it?

https://docs.fedoraproject.org/en-US/fesco/Package_maintainer_responsibilities/#_bot_accounts

BTW, does this count as a 'bot account' ?

I don't think so. It does not even have a FAS account.

The account only ever comments with:

Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py
If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/

So I am not afraid users will not know what to do if they need to reach out.


I verified the account can close bugzillas. To see if it can add blockers I need to wait for a new breakage, but I'll reopen this ticket if I find problems.

Thanks.

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

a year ago

Login to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog
Related Pull Requests