19:00:02 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 19:00:02 Meeting started Tue Feb 15 19:00:02 2022 UTC. 19:00:02 This meeting is logged and archived in a public location. 19:00:02 The chair is nirik. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 19:00:02 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:02 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 19:00:02 #chair mboddu nirik mobrien nb 19:00:02 #meetingname fedora_infrastructure_ops_daily_standup_meeting 19:00:02 Current chairs: mboddu mobrien nb nirik 19:00:02 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 19:00:02 #info meeting is 30 minutes MAX. At the end of 30, its stops 19:00:02 #info agenda is at https://board.net/p/fedora-infra-daily 19:00:17 .hi 19:00:18 nb: nb 'Nick Bebout' 19:00:49 hey everyone 19:01:46 morning everyone. 19:01:50 hey nb, phsmoura 19:01:52 Hello 19:01:56 hey mboddu 19:02:14 one new infra ticket to triage 19:02:20 .ticket 10560 19:02:21 nirik: Issue #10560: review and permissions for building bodhi in the infra target on koji - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10560 19:02:36 med/med/ops? 19:03:23 +1 19:03:33 +1 19:03:58 thats it today, releng? 19:04:24 No new releng tickets to triage 19:05:09 hurray 19:05:14 #topic Planning / Upcoming 19:05:33 #info mass updates/reboots underway yesterday/today/tomorrow. 19:05:39 #info red hat recharge day friday 19:05:53 I'm hoping to look at bugzilla login stuff thursday 19:06:34 #info next tuesday beta freeze starts 19:06:38 nirik: bugzilla login as in with python-bugzilla with new login (iirc openidc?) 19:07:25 mboddu: no, we need to make 100% sure non of our apps or scripts uses bugzilla username/passwords or tokens... they need to use api tokens only. 19:07:51 at the end of the month those won't work, and in fact will lock accounts that try and use them. ;( 19:07:58 So we don't have much time to fix anything/everything 19:08:06 nirik: Ack, I need to look at the releng one as well 19:08:32 yeah we need to check everything that interacts with bz. I think it should be pretty easy to find login/pass in ansible... 19:10:30 #topic Discussion / AOB 19:10:40 anything anyone would like to discuss? 19:11:03 Yeah, so how to check if the account is using old auth or new auth? As in, releng user we only use it when we file ftbfs, so, how I can make it not deactivate? (I didn't know they are deactivating the accounts as well) 19:11:31 I can get the api key for the releng user 19:11:45 yes, we have to switch it to use an api key. 19:12:10 So, if I generate the key for the releng user, is that sufficient not to get deactivated? 19:12:23 you avoid deactivation by not useing username/password or token. ;) 19:12:35 Oh okay 19:12:36 as long as you USE that api key for any access, yes. 19:12:48 Got it, thanks nirik 19:13:20 things like this need fixing: 19:13:22 roles/distgit/pagure/templates/pagure-sync-bugzilla.py.j2:BZPASS = '{{ bugzilla_password }}' 19:13:27 nirik: Does bitwarden support saving the keys? 19:13:53 you can save an api key there, sure. We need it in ansible-private for ansible use tho... 19:13:54 ^ just wondering 19:14:26 I wish we had more time for this, but oh well. ;( 19:14:28 Yeah, that I know, in releng user case, I can save it in bitwarden (and start using it more) 19:14:44 ^ start using bitwarden more 19:15:38 sure 19:16:17 That is all I got 19:17:27 nb: might you have any time to help with updates/reboots tomorrow? I know you're busy with your dayjob... 19:18:51 ok, if nothing else will close out in a few. 19:19:11 phsmoura: did you and mobrien get together about fedimg debugging? 19:21:09 nirik: yes, we did. He told me where he hit and I took from there. Working on it right now 19:21:27 phsmoura: awesome. thank you. 19:22:03 ok, thanks everyone for coming! See you tomorrow, same time same channel. 19:22:06 #endmeeting