18:00:01 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:01 Meeting started Mon Sep 21 18:00:01 2020 UTC. 18:00:01 This meeting is logged and archived in a public location. 18:00:01 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:01 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:01 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:01 #chair mboddu nirik smooge pingou mobrien 18:00:01 Current chairs: mboddu mobrien nirik pingou smooge 18:00:01 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:00:01 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:01 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:02 #info agenda is at https://board.net/p/fedora-infra-daily 18:00:03 #topic Tickets needing review 18:00:04 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:00:10 Hello 18:00:30 hey mboddu 18:00:37 I can update the tickets 18:00:42 okey dokey 18:00:50 .ticket 9332 18:00:51 nirik: Issue #9332: Stage Wiki login redirects to production ipsilon - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9332 18:00:57 hola 18:01:41 this seems like a config bug... not sure if it's in the auth path or what tho 18:01:43 hey smooge 18:01:58 me either.. 18:02:17 No idea here as well 18:02:32 High Gain, Med Trouble, Ops ? 18:03:04 +1 18:03:26 actually... 18:03:29 pagure.issue.tag.added -- mohanboddu tagged ticket fedora-infrastructure#9332: high-gain, medium-trouble, and ops https://pagure.io/fedora-infrastructure/issue/9332 18:03:30 pagure.issue.edit -- mohanboddu edited the priority fields of ticket fedora-infrastructure#9332 https://pagure.io/fedora-infrastructure/issue/9332 18:03:46 I think it might be due to wiki01.stg not being in stg group. I added it, but possibly didn't re-run the playbook. 18:04:13 but +1 18:04:28 .ticket 9335 18:04:28 nirik: Issue #9335: sundries01 is overloaded - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9335 18:04:46 I think this is just the limits. +1 to applying smooge's patch... 18:05:29 I agree with https://pagure.io/fedora-infrastructure/issue/9335#comment-687487 18:05:30 Med gain / Low trouble / Ops? 18:05:39 +1 18:06:02 yeah I think this will help. if not, the next is to make the rsync script sleep random up to 120 seconds or so 18:06:58 thats all the infra ones... any releng ones? 18:07:04 Yup 18:07:18 pagure.issue.tag.added -- mohanboddu tagged ticket fedora-infrastructure#9335: low-trouble, medium-gain, and ops https://pagure.io/fedora-infrastructure/issue/9335 18:07:19 pagure.issue.edit -- mohanboddu edited the priority fields of ticket fedora-infrastructure#9335 https://pagure.io/fedora-infrastructure/issue/9335 18:07:47 .releng 9762 18:07:48 mboddu: Issue #9762: Error creating new scm repo for python-bokeh: "The PDC branch already exists" - releng - Pagure.io - https://pagure.io/releng/issue/9762 18:08:07 huh, do we know why it happened? 18:08:09 I need to fix the pdc entries and rerun the fedscm-admin 18:08:56 nirik: Sometimes pdc entries get created but not the git repo and then fedscm-admin thinks the repo already exists 18:09:20 is there a way we could just create the git repo in that case? 18:09:57 Yes, pingou can do it or we can remove the pdc entry and process the ticket 18:10:01 * mboddu checks something 18:10:17 ok. Just thinking longer term how to avoid having to manually deal with these. 18:11:29 make a toddler which does it anyway? 18:11:32 So, med gain, low risk, ops? 18:11:41 ack 18:12:11 toddler depends on messages, this is more of processing the ticket 18:12:41 I was thinking of changing fedscm-admin to see this case and just make the git repo/finish processing. 18:13:43 anyhow, don't need to solve it here now. 18:13:46 Yes, we could do that 18:14:01 any other blockers, freeze breaks or tickets to discuss? 18:14:02 .releng 9763 18:14:03 mboddu: Issue #9763: newRepo "outage"/failures earlier 2020-09-21 - releng - Pagure.io - https://pagure.io/releng/issue/9763 18:14:11 yeah, this is weird. 18:14:13 nirik: What is the status on the nfs mounts? 18:14:39 some of the builders just didn't seem to have their nfs mounts anymore. Nothing dmesg or journal, just wasn't there. 18:14:59 I am running playbooks which should bring them back 18:15:36 the buildvm one is still running. 18:15:39 Okay 18:16:01 Thanks nirik for the update 18:16:07 So, med,med,ops? 18:16:16 mah, let me just mass mount on them... 18:16:19 ack, +1 18:17:07 Thats all I got 18:17:23 I have a few info items... 18:17:57 #info s390x builders i/o should be MUCH better now. cpu is still somewhat constrained, but there's nothing we can do about that. Please report issues to the s390x ticket. 18:18:31 #info staging is mostly installed, see list for exceptions. 18:18:59 I think thats all I had. 18:19:07 anything else? if not, will close in a min 18:19:58 #info No RC request yet, we have a new blocker accepted and couple of proposed blockers (which might be voted as FE's) 18:21:41 #info one of the s390x builders sshfs mount has hung, delaying todays f33 compose, should be done soon now. 18:22:32 thanks everyone 18:22:37 #endmeeting