18:00:17 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:17 #chair mboddu nirik pingou mobrien nb 18:00:17 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:00:17 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:17 #info agenda is at https://board.net/p/fedora-infra-daily 18:00:17 Meeting started Tue Jun 1 18:00:17 2021 UTC. 18:00:17 This meeting is logged and archived in a public location. 18:00:17 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:17 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:17 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:17 Current chairs: mboddu mobrien nb nirik pingou 18:00:17 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:17 #info reminder: speak up if you want to work on a ticket! 18:00:19 #topic Tickets needing review 18:00:21 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:00:30 I am here 18:01:23 cool. 18:01:31 .ticket 10001 18:01:32 nirik: Issue #10001: Can't log into buildvm-x86-{02,03,04,05}.stg.iad2 - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10001 18:01:48 med,med, ops 18:01:58 +1 18:02:16 .ticket 10002 18:02:17 nirik: Issue #10002: ppc64le-test.fedorainfracloud.org cleanup - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10002 18:02:21 low,low,ops 18:02:28 +1 18:02:55 Done 18:03:34 there's another, but I think we can just do it... except I need to know which token. 18:04:05 low,low,ops I guess.. 18:04:12 .ticket 10003 18:04:13 nirik: Issue #10003: API token missing permission - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10003 18:04:15 thats ^ 18:04:35 thats it on infra. releng? 18:04:43 Can we not ask limb to create a new token and remove the one she created? 18:05:38 users cannot create admin tokens you have to use pagure-admin on the host 18:06:26 I guess I can assume it's the newest one... 18:06:31 Ahhh, this is the not the releng/fedora-scm-requests ticket token 18:06:44 Okay, low, low, ops 18:06:50 wait a sec... 18:06:59 yeah, if this was just renewed it should have the same perms? 18:07:06 Yeah 18:07:19 so I am confused then too. ;) 18:07:26 And how did she renew it? 18:07:38 so we can ask in ticket I guess... she doesn't seem online right now 18:07:57 +1 18:08:19 anyhow, thats the last infra one. 18:09:02 Yeah, couple releng one's 18:09:14 .releng 10140 18:09:15 mboddu: Issue #10140: Issue with creating a new repo - releng - Pagure.io - https://pagure.io/releng/issue/10140 18:09:34 Maybe related to the limb issue? 18:09:49 yes, likely so. 18:10:03 low, low, ops 18:10:06 I will fix it 18:10:27 .releng 10139 18:10:28 mboddu: Issue #10139: Please retire `master` modules - releng - Pagure.io - https://pagure.io/releng/issue/10139 18:11:05 Did we or did we not retire master stream in modules? 18:11:26 I thought we didn't, but we disabled pushes to master branch? 18:12:06 we did not 18:12:41 modules: 18:12:41 Existing repos: Leave them with master as default branch 18:12:41 Future repos: adjust tools to not require master request at repo creation 18:12:55 so, we need to try and somehow unblock master for modules. 18:14:29 So, mention in the ticket that we haven't retired master in modules and close the ticket? 18:14:34 which I am not sure how we can do with still blocking the other things 18:14:56 sure, I guess 18:16:37 * nirik has a meeting at the bottom of the hour, so will have to leave a few min before. 18:17:11 nirik: I think eclipseo is talking about https://pagure.io/fedora-infra/ansible/blob/main/f/roles/distgit/pagure/templates/pagure_shared.cfg#_80-81 ? 18:17:15 Not able to push to master? 18:17:36 yes, but we don't want to remove that block globally. 18:17:40 only for modules 18:17:45 Right 18:17:59 So, ask pingou on how to do it? 18:17:59 if we remove it globally, people will mistakenly push to that branch and it will re-appear. 18:18:01 yes 18:18:12 Okay, I will ping in the ticket 18:18:16 That is all from releng 18:19:01 #topic work plans / upcoming tasks 18:19:01 #info everyone should note what things they are hoping to work on over the next day/week 18:19:29 I was working on finishing builder upgrades... but turns out python10 _STILL_ blows up on 32 bit arm with f34. 18:20:19 I am working on CS stuff and will learn/document how to sign windows fmw builds tomorrow 18:20:21 Right now I think I will just finish upgrading them all anyhow. I've spent too much time on it... time to let other people fix it. 18:20:30 I think so 18:20:31 +1 18:21:09 when is the next mass rebuild? 18:21:11 After that I plan to push the sidetag cleanup cron (I have the commit ready), and then I guess focus on tickets for a while (we got a gigantic pile over the last few weeks) 18:21:36 hey smooge 18:21:37 ok my schedule this week is meeting heavy until Friday 18:21:38 Wed 2021-07-21 18:21:49 I cleaned up a few tickets last week, but I do also want to clean up some more tickets in releng 18:22:10 Oh, I figured out how to reset the network on the dell fx'es mgmt that dropped off. Plan to fix those... still not sure how I can fix the chassis one. 18:22:38 yeah no idea myself.. it was a power reset on it but that takes it all down 18:22:58 If I can find where it's attached serial I can do it from there... 18:23:24 #topic Discussion / AOB 18:23:29 I do not know if it has a working serial 18:23:33 any tickets or pr's or issues to discuss? 18:24:06 so for RDU-CC systems... the next step is to try and get the mgmt interfaces working. 18:24:22 smooge: yeah, another one dropped off this weekend btw. ;( 18:24:26 04 is now down 18:25:10 basically it is ssh into cloud-noc-os01.rdu-cc.fedoraproject.org and see what ips it has dhcpd.. then determine which ones are working mgmt interfaces 18:25:19 ah ha. ok. 18:25:36 then cry when you figure out that none of them are 18:26:16 it might be that the fx chassis has a 192.168.0.x ip also. Might try and bring up something on the mgmt interface on that net and see if I can find it. 18:26:32 ah ha! I need to add one more interface to that box 18:26:53 nirik, the bvmhost-a64-05 is my iad2 goto for that 18:26:56 the blades that 'forgot' all their mgmt config had 192.168.0.x 18:27:17 well, buildhw-x86-01 anyhow (haven't fixed any others yet) 18:27:25 ok, if nothing else will close in a min... 18:27:59 None from me 18:28:00 I need to reboot cloud-noc to add an ethernet interface to it 18:28:31 ok, lets continue in noc. ;) 18:28:34 #endmeeting