#7508 the-new-hotness - Check bugzilla user
Closed: Fixed 5 years ago by kevin. Opened 5 years ago by zlopez.

  • Describe what you need us to do:
    the-new-hotness is not working right now and according to the error (thanks @jcline) it is not working because the credentials are no longer valid. When trying to create or update bug the-new-hotness gets Fault: <Fault 410: 'You must log in before using this part of Red Hat Bugzilla.'>
    Could somebody please check, if these private variables are still valid:
upstream_release_bugzilla_user
upstream_release_bugzilla_password

If not could they be updated?

  • When do you need this? (YYYY/MM/DD)
    As soon as possible

  • When is this no longer needed or useful? (YYYY/MM/DD)
    When bugzilla will no longer be used by the-new-hotness

  • If we cannot complete your request, what is the impact?
    the-new-hotness will not be able to create or update any bug in bugzilla


It is likely that you need to switch to using a Bugzilla API token instead of a username/password. When the Bugzilla 5 upgrade happened last month they started expiring login sessions (I don't know if Bugzilla 4 ever expired sessions, but if it did they lasted a long time).

I had a similar problem on Bodhi: https://github.com/fedora-infra/bodhi/issues/2827

Here's how I fixed it: https://github.com/fedora-infra/bodhi/pull/2862

@bowlofeggs You may be right, thanks for the info.

I was able to manually login with that username/password. ;(

So, perhaps something changed with bugzilla 5 that broke things?

I will use the API token instead of username and password and we will see if this helps.

ok, api token made... I guess we can close this? feel free to reopen or file a new one if there's still further to do.

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

5 years ago

Login to comment on this ticket.

Metadata