18:00:07 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:07 Meeting started Tue Mar 30 18:00:07 2021 UTC. 18:00:07 This meeting is logged and archived in a public location. 18:00:07 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:07 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:07 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:07 #chair mboddu nirik smooge pingou mobrien 18:00:07 Current chairs: mboddu mobrien nirik pingou smooge 18:00:07 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:00:07 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:07 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:07 #info agenda is at https://board.net/p/fedora-infra-daily 18:00:08 #info reminder: speak up if you want to work on a ticket! 18:00:09 #topic Tickets needing review 18:00:11 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:00:49 * mboddu is here 18:01:33 If smooge isn't around, I can take mod the tickets 18:01:40 is here 18:01:49 * mboddu leaves it to smooge :) 18:01:50 just trying to deal with a fire I didn't start 18:03:05 we didn't start the fire! 18:04:11 just a sec... putting out a fire and then we can start 18:04:40 Okay 18:04:41 billy joel 18:05:23 .ticket 9797 18:05:24 nirik: Issue #9797: Use Fedora logo on OTP application - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9797 18:05:43 I think we should ask they file against noggin, or do it outselves and close this one. 18:08:08 yeah 18:08:22 ok 18:08:27 where is noggin? 18:08:36 github.com/fedora-infra/noggin 18:09:30 +1 to upstream noggin ticket 18:09:50 nirik: We already have enough at our hands 18:09:59 +1 18:09:59 and I broke pagure 18:10:05 ha. well, the change needs to be in there. 18:10:11 o: 18:10:22 * mboddu learned it the very very hard way yesterday, turning a pebble like task to a mountain just because I wanted to do it right :( 18:10:24 .ticket 9803 18:10:25 nirik: Issue #9803: Document how to clean/clear a 2FA token - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9803 18:10:48 low/low/ops ? 18:10:51 +1 18:11:08 Basically then can be able to remove it from the UI and then create a new one, right? 18:11:13 done 18:11:49 I vaguely remember seeing a "trash" symbol next to the token 18:11:50 mboddu: users cannot remove the last otp 18:11:56 * mboddu verifies 18:11:56 you can remove all but one 18:12:14 if you need to remove that one, you have to: prove who you are, and have an admin remove it 18:12:31 so, very like the old tokens we had, where an admin had to clear 18:12:52 does otp work with yubikey? I was confused by a comment earlier 18:13:05 no, but it's planned I think? 18:13:21 https://github.com/fedora-infra/noggin/issues/202 18:13:54 u2f would be very great 18:14:05 nirik: Ahhh okay, I created only one but I can still see the "trash" symbol next to it 18:14:23 mboddu: try and trash it? it should reject it... 18:14:27 * mboddu tries to remove it and see what happens 18:14:33 .ticket 9808 18:14:34 nirik: Issue #9808: Copr ELN builds failing with 403: Cannot download Packages/glib2-2.67.4-2.eln110.x86_64.rpm: All mirrors were tried - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9808 18:14:36 will create one later today so I can be absolutely useless afterwords :) 18:14:44 "Sorry, You cannot delete your last active token." and nirik is right again :) 18:15:30 not sure whats happening here. 18:15:35 med/med/ops I guess? 18:15:39 +1 18:16:22 My suspicion: 18:16:46 this compose was a long time ago, that build has since been garbage collected/deleted and odcs just links to koji builds. 18:16:51 but would have to look to make sure. 18:17:00 .ticket 9809 18:17:01 nirik: Issue #9809: MBS builds often fail with krbLogin error - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9809 18:17:09 med/med/ops 18:17:19 I don't know how it could fail only part of the time. 18:17:29 lrwxrwxrwx. 1 64321 64321 124 Mar 2 21:08 production/latest-Fedora-ELN/compose/Everything/x86_64/os/Packages/glib2-2.67.4-2.eln110.x86_64.rpm -> ../../../../../../../../mnt/koji/packages/gl 18:17:29 ib2/2.67.4/2.eln110/data/signed/9867c58f/x86_64/glib2-2.67.4-2.eln110.x86_64.rpm 18:18:24 nirik, I think your subscription is correct 18:19:44 .ticket 9812 18:19:45 nirik: Issue #9812: Update acceptable_aliases for coreos-infra@lists.fp.o - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9812 18:20:27 low, low, ops? 18:20:36 the config here is... the database as far as I know. :) 18:20:36 this is one of those low-gain, high-trouble, ops 18:20:51 high-trouble? 18:20:59 I thought it will be a simple config change 18:21:06 you have to tickle the database directly 18:21:14 there's a bug where you cannot change this via the web interface. 18:21:15 I messed it up once 18:21:25 we had to restore the db 18:21:35 brb 18:22:21 thats it on infra. 18:22:25 mboddu: any releng ones? 18:22:53 Nope, well closed them, but I did find the ticket interesting 18:22:59 .releng 10071 18:23:00 mboddu: Issue #10071: Unorphan memstomp - releng - Pagure.io - https://pagure.io/releng/issue/10071 18:24:26 ok. 18:24:30 sop ? 18:25:06 copperi_: sop for? 18:25:07 mboddu: wait... they wanted to unorphan it... 18:25:17 they shouldn't need the old maintainer to approve that? 18:25:35 nirik: Its not even unorphaned, Jeff still owns it 18:25:46 ok. 18:25:47 But they want to assign it to them just because he left RH 18:25:51 ah, I see. ok. 18:26:03 copperi_: for unorphaning? or ? 18:26:59 for taking ownership, but it seems clear now 18:27:22 copperi_: If unorphaning, there is https://docs.pagure.org/releng/sop_unretire.html, its for unretirement, but unorphan is part of it 18:27:26 yeah. 18:27:31 #topic work plans 18:27:31 #info everyone should note what things they are hoping to work on over the next day/week 18:27:59 nirik: As I said, turned a pebble into a mountain, working on CentOS Stream 18:28:11 so. I have started updating/rebooting things... I guess I'd like to try and do a outage, but it's really pretty late notice for tomorrow. we could do it anyhow, or do thursday? 18:28:25 On that note, I have a question on koji 18:28:37 I'd like to get it done... we haven't done one in quite a while. 18:28:57 nirik: Did we ever enable notifications on koji based on the package ownership in koji? 18:29:15 we did long long ago. We disabled it long ago. 18:29:28 but there's still things that use it (or try to) 18:29:33 Since I started, we were just setting the ownership of the package to releng (I guess it started with pkgdb2 to pagure-dist-git move) 18:29:40 (well, the ownership info, which is broken) 18:29:45 yes 18:30:58 nirik: Okay, do you know/remember how it worked? Does it used to go to FAS to get the email id of the owner and send the email? Or the owner is set with the email id and koji hub can send the email directly? 18:31:16 going to be working on documenting more of my job this week 18:31:18 The owner was set in koji 18:31:28 there's even a releng ticket to fix this. 18:31:41 I have a question - I find it strange that noggin does not give you the users email 18:31:55 I got it to work if i searched in fasjson-client 18:31:55 .fasinfo mohanboddu 18:31:56 mboddu: User: mohanboddu, Name: Mohan Boddu, email: mboddu@bhujji.com, Creation: 2016-04-25, IRC Nick: mboddu, Timezone: US/Eastern, Locale: en, GPG key ID: 7C6B59BD, Status: active 18:31:57 https://pagure.io/releng/issue/7067 18:32:00 mboddu: Approved Groups: sysadmin-cvs cla_fpca cla_done releng-team sysadmin packager fedorabugs bodhiadmin cvsadmin torrentadmin @sysadmin-releng @signers provenpackager sysadmin-web sysadmin-main sysadmin-bodhi epel-cabal 18:32:22 * mboddu looks 18:32:24 nb: thats a statement? :) but yeah... I think there's already a RFE to noggin on that 18:32:38 nirik well, i guess my question is "why doesn't noggin show the user's email" 18:32:58 so, what do folks think about mass update tomorrow or alternately thursday? 18:33:08 nb: because it just wasn't implemented in noggin... 18:33:16 oh ok 18:33:21 nirik: +1 on update/reboot 18:34:05 +1 on updates 18:35:17 so should we try tomorrow or thursday? I haven't sent an outage yet. 18:36:11 I guess lets try thursday... give us more time to get things done. 18:36:16 * nirik can send the outage. 18:36:24 #topic Open Floor / AOB 18:36:34 anything else folks want to discuss ? 18:36:39 I am expecting we will be looking at a very long outage on this 18:36:56 but I will be pleasently surprised otherwise 18:37:00 well, I sure hope not 18:38:52 but that is it from me 18:38:55 ok, if nothing will close 18:38:58 #endmeeting