18:00:13 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:13 Meeting started Wed Jul 29 18:00:13 2020 UTC. 18:00:13 This meeting is logged and archived in a public location. 18:00:13 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:13 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:13 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:13 #chair mboddu nirik smooge pingou 18:00:13 Current chairs: mboddu nirik pingou smooge 18:00:13 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:00:13 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:13 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:14 #info agenda is at https://board.net/p/fedora-infra-daily 18:00:15 #topic Tickets needing review 18:00:16 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:00:26 pagure.pull-request.comment.added -- darknao commented on PR #17 on fedora-docs/translations-scripts https://pagure.io/fedora-docs/translations-scripts/pull-request/17#comment-126510 18:00:28 * mboddu is here and can update tickets 18:00:46 cool. 18:01:00 .ticket 9177 18:01:02 nirik: Issue #9177: Pulling container images breaks randomly (registry problem?) - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9177 18:01:34 needs looking into. I'm a bit confused as to why most hits don't go to cloudfront tho. 18:01:56 anyhow, high gain, med trouble, groomed? 18:03:03 +1 18:03:21 pagure.issue.tag.added -- mohanboddu tagged ticket fedora-infrastructure#9177: groomed, high-gain, and medium-trouble https://pagure.io/fedora-infrastructure/issue/9177 18:03:22 pagure.issue.edit -- mohanboddu edited the priority fields of ticket fedora-infrastructure#9177 https://pagure.io/fedora-infrastructure/issue/9177 18:03:39 .ticket 9178 18:03:40 nirik: Issue #9178: https://data-analysis.fedoraproject.org/ giving a proxy error - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9178 18:03:51 I think this is related to an existing ticket... 18:03:52 looking 18:05:15 9164? but I guess they aren't 100% the saem.. or at least it's not clear 18:05:23 * smooge stops focusing on other things 18:05:48 hey smooge. you back today? 18:05:59 9178 is because data-analysis is pointing to the wrong host 18:06:05 9164 is related to it. 18:06:58 If 9164 decided to go with data-analysis.fp.o then we have to fix 9178 first 18:07:09 correct 18:07:35 So, its dependent based on the decision 18:07:37 actually I need to fix part of 9164, then 9178 and then the rest of 9164 18:07:59 But just 9178 is, I guess med, med, groomed? 18:08:10 sure 18:08:35 pagure.issue.tag.added -- mohanboddu tagged ticket fedora-infrastructure#9178: groomed, medium-gain, and medium-trouble https://pagure.io/fedora-infrastructure/issue/9178 18:08:36 pagure.issue.edit -- mohanboddu edited the priority fields of ticket fedora-infrastructure#9178 https://pagure.io/fedora-infrastructure/issue/9178 18:09:01 I need to have log01 put stuff into /srv/spot, set up selinux, get httpd tested, then fix the proxies to go to log01, then finish up the other parts on log01 18:09:31 nirik, I am sort of back today. I have a bunch of must be done by 5pm paperwork so my 'do things that matter' time is low 18:09:53 .ticket 9179 18:09:54 nirik: Issue #9179: Copr stucked - - can not start VMs - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9179 18:10:05 smooge: fair. There's likely a few emails for you to read too. :) 18:10:14 this one looks to me like a amazon issue. 18:10:30 so perhaps tag outage, groomed waiting on external? 18:10:37 +1 18:10:49 smooge: do you thinking fixing data-analysis by the end of the week is doable? 18:10:50 Good luck smooge with your paperwork 18:11:24 pagure.issue.tag.added -- mohanboddu tagged ticket fedora-infrastructure#9179: groomed and outage https://pagure.io/fedora-infrastructure/issue/9179 18:11:25 pagure.issue.edit -- mohanboddu edited the priority fields of ticket fedora-infrastructure#9179 https://pagure.io/fedora-infrastructure/issue/9179 18:11:53 thats all needs-review from infra side. mboddu: any releng ones to triage? 18:13:06 No news ones from releng 18:13:47 cool. any other ones to discuss? prs? blockers? 18:13:58 None from me 18:14:03 the pdc-updater ticket will be closed shortly 18:14:12 I believe the last toddlers just got merged 18:14:18 I am blocked on staging rollout waiting for some firewall rule changes. 18:14:34 so I might try and fight tickets down this afternoon 18:14:48 and we've found a bug in fedora-messaging: https://github.com/fedora-infra/fedora-messaging/issues/223 18:14:51 pingou++ 18:15:15 and tomorrow mikem wants to look at mbs. I scheduled it, but if someone else wants to look too, or take it over, feel free... smooge: I know you looked at it a bunch too. 18:15:16 that impacts toddlers and likely other consumers (though not the CI folks since they have their own client) 18:16:09 fun 18:16:43 yay bugs 18:17:02 nirik: I would like to join your meeting with mikem about mbs, but I might not be able to take it over :( 18:17:18 I figured we would meet here in irc... 18:17:23 when was this meeting? 18:17:26 this is just supposed to be a small sync meeting 18:17:40 mikem: sorry for scope creep. ;) 18:17:47 I'm afraid of having too many cooks in the kitchen 18:17:56 I want to actually get things done ;) 18:17:58 i am going to stay out of the kitchen 18:17:58 I think we just all want to understand better how it works... 18:18:19 but we can focus on that and I can knowledge share after too. 18:18:23 mikem: I am definitely not a cook, I am just a apprentice :D 18:18:37 when it comes to mbs, we all are 18:18:45 all the experts have flown the coop 18:18:57 yeah. ;( 18:19:04 (who put garlic in that things??) 18:19:18 pingou: That would be me since I like it :D 18:19:55 anyhow, we can focus on getting it working first, then worry about sharing how it works. (at least I mainly want it to work) 18:20:07 +1 18:20:21 * pingou happy to read the log in IRC if the meeting happens in IRC, but will stay out of it 18:20:22 +1 18:22:09 anyhow, anything else for here? or shall we close out? 18:25:04 ok, thanks for coming everyone... 18:25:07 #endmeeting