I'd like to request admin access to the package-review mailing list for being able to set moderation mode when needed.
I currently need to reset the associated staging bugzilla account password and I need to briefly set the list in moderation mode to avoid anyone being reached by the password reset email. This is required for me to login into the staging bugzilla and set up a new api key for the staging review-stats instance (which has been failing since yesterday because the API key expired).
Other options are that someone else resets the password and send me the new one, or take care of set up the new api key themselves.
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-trouble, medium-gain, ops
Metadata Update from @zlopez: - Issue assigned to zlopez
Do you need owner access or is moderator enough?
Also I noticed that @kevin is owner of this mailing list. So I leave the decision to him.
I'm not sure if moderator role is enough to set the list to moderated...
I have no problem giving you perms there... but... the staging bugzilla user uses the production list? I guess thats due to them syncing from production?
I looked at updating this token yesterday, but I couldn't tell what user it was supposed to be.
The token will need updating in private repo, so you will need to get it to me if you can get it.
I added you to the list... I guess we should keep this open to track the token update?
I have created new api keys for prod and staging (prod key is expired as well, but still working), you can find them in the text file named bugzilla_api_keys inside my batcave homedir. The two ansible vars to be updated are reviewstatsbzapikey and reviewstatsbzapikey_stg.
bugzilla_api_keys
reviewstatsbzapikey
reviewstatsbzapikey_stg
I'm now going away, can you also rebuild base images for both prod and staging? Otherwise I'll do that myself tomorrow.
Thanks.
Updated. Playbook run. Image rebuilt.
Note: I see this is using f37. ;( Could we move that to fedora:latest?
I'll leave this open until we are sure things are running ok.
Updated. Playbook run. Image rebuilt. Note: I see this is using f37. ;( Could we move that to fedora:latest? I'll leave this open until we are sure things are running ok.
Thanks, everything works now.
I have tested locally that using fedora:latest works, so it's ok to upgrade the dockerfile.
Done. Updated and pushed out.
Thanks!
Metadata Update from @kevin: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.