#3 Issuebot needs BZ API changes
Closed by bcotton. Opened by bcotton.

I see that issuebot is on a RH-internal list of accounts passing the API key improperly.

I'm not sure if it's because python-bugzilla does the wrong thing when api_key is passed as an argument or if it's because you're using python-bugzilla < 3.2. It doesn't look like the former, so I'd suggest checking the latter.


I'm using python-bugzilla 2.5 on the RHEL 7 system I'm running this on for now.

That'd explain it. The deadline has been extended to March 14, but you'll need to upgrade before then or else your API key will be invalidated whenever you try to use it.

This is a top priority ticket now, I believe.

Thanks for the reminder. I'll upgrade python-bugzilla on the system.

Has this been fixed? I see at least two topics which should have been updated (because the bugs were fixed & closed), but weren't:
https://ask.fedoraproject.org/t/cursor-position-is-slightly-off-in-f36-kde-virtual-machines/20639
https://ask.fedoraproject.org/t/f36-workstation-cant-configure-a-hidden-wifi-or-wpa2-enterprise-wifi/20615

If this should be fixed, can you kick the bot or investigate? If the bot doesn't handle it, I'll update it manually on Monday at latest, because we need it ready for the Beta release. Thanks!

It was still picking up 3.1 from a local path. I really need to figure out how to get this running somewhere other than my personal server and into a proper deployment.

Should run in about 2 minutes and be correct. We'll see :)

It's working now, thanks!

This can be closed, I guess.

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

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/quality/issuebot/issues/3

Please continue any further discussion there.

Metadata