18:00:00 <nirik> #startmeeting Fedora Infrastructure Ops Daily Standup Meeting
18:00:00 <zodbot> Meeting started Mon May 10 18:00:00 2021 UTC.
18:00:00 <zodbot> This meeting is logged and archived in a public location.
18:00:00 <zodbot> The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:00 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:00 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
18:00:00 <nirik> #chair mboddu nirik smooge pingou mobrien nb
18:00:00 <nirik> #meetingname fedora_infrastructure_ops_daily_standup_meeting
18:00:00 <zodbot> Current chairs: mboddu mobrien nb nirik pingou smooge
18:00:00 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
18:00:00 <nirik> #info meeting is 30 minutes MAX. At the end of 30, its stops
18:00:01 <nirik> #info agenda is at https://board.net/p/fedora-infra-daily
18:00:02 <nirik> #info reminder: speak up if you want to work on a ticket!
18:00:03 <nirik> #topic Tickets needing review
18:00:05 <nirik> #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1
18:00:10 <mboddu> Hello
18:00:15 <mboddu> And I can update tickets
18:00:46 <nirik> .ticket 9941
18:00:47 <zodbot> nirik: Issue #9941: meetingminutes emails does not contain correct email subject now - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9941
18:00:51 <nirik> this is actually a duplicate.
18:01:09 <nirik> of 9820
18:01:20 <nirik> so, close -> duplicate and mention 9820
18:02:20 <mboddu> +1
18:02:39 <nirik> .ticket 9943
18:02:40 <zodbot> nirik: Issue #9943: Insecure HTTP logins - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9943
18:02:58 <nirik> I think this is intended/fine, but I'd prefer our security officer check it.
18:03:05 <nirik> med / med / ops / security
18:03:26 <nirik> thats it for infra
18:03:44 <mboddu> +1
18:03:56 <nirik> any releng ones?
18:04:01 <mboddu> nirik: Assign it to Patrick?
18:04:03 <mboddu> Yes
18:04:14 <nirik> sure
18:04:16 <mboddu> I saw 'security officer check' :D
18:05:34 <mboddu> .releng 10109
18:05:37 <zodbot> mboddu: Issue #10109: ELN builds referenced in Fedora 34 mass rebuild bugzillas - releng - Pagure.io - https://pagure.io/releng/issue/10109
18:05:53 <nirik> yeah. :(
18:05:56 <mboddu> I think, medium gain, low risk, dev?
18:06:16 <nirik> sure. It seems it should be a fix in the mass rebuild/ftbfs scripting
18:06:17 <mboddu> I think https://pagure.io/releng/issue/10109#comment-731789 is the problem
18:06:22 <mboddu> ack
18:06:42 <mboddu> That is all
18:06:48 <asaleh> nirik: question, I would probably plan to update bodhi in prod on wednesday, still testing it in stg, but s far so good. Does wednesday sound reasonable? where do I need to notify people?
18:07:15 <nirik> asaleh: sounds good to me. How much downtime will there be?
18:07:16 <mboddu> asaleh: infra list for sure
18:08:50 <nirik> I guess the web part would be pretty quick (just new deploy in openshift)...
18:09:15 <nirik> so may be not much end user visible I guess.
18:09:27 <asaleh> best case scenario, ~30 mins? its 4 playbooks, each takes 5-10 mins to run. Realistic scenario, 4 hours, I would start after EU infra standup, and Tomas would help me destroy the backend worker
18:10:12 <asaleh> I think I managed to iron out all of the kinks in staging deployment, but I could have introduced new ones :D
18:10:29 <nirik> ok. I'd say file an outage ticket, get it reviewd as ok then we can send to devel-announce and infrastructure lists...
18:10:38 <nirik> there's a template for them in pagure...
18:10:51 <asaleh> link? tracker?
18:11:03 <nirik> pagure.io/fedora-infrastructure
18:11:16 <asaleh> 👍️
18:11:37 <nirik> just new ticket and choose outage from the pull down... then make the "Planned outage: ..." line copied to the subject of the ticket.
18:11:48 <nirik> I can do the emailing (unless you want to, thats fine too)
18:11:50 <mboddu> ^ "Types" pull down
18:12:08 <asaleh> ah, I was searching for planned downtime :) thanks!
18:12:56 <nirik> you can look at some old one to see... but hopefully the template is reasonable
18:13:28 <nirik> and many thanks for pushing that forward.
18:13:55 <nirik> we should probibly push some updates after the backend is updated ( just to make sure it's working)
18:15:03 <nirik> #topic weekly plans
18:15:36 <nirik> I've been in meetings all morning, so I haven't really had a chance to read emails and plan my week. ;(
18:15:50 <mboddu> Mohan's week plan: As they come :D
18:16:08 <nirik> but one issue thats come up, is that fedora_koji is getting too large again. ;( I'm looking, but might be kojira isn't correctly deleting repos again or something.
18:17:16 <nirik> #topic Open floor / discussion / all other business
18:17:20 <nirik> anything to discuss?
18:17:28 <mboddu> None from me
18:17:51 <nirik> when is f32 eol again?
18:18:14 <nirik> 25th it seems
18:18:49 <mboddu> Yeah, 25th
18:19:18 <nirik> we are going to have to be more careful archiving f32 than we have been.
18:20:05 <nirik> anyhow
18:20:10 <nirik> will close out if nothing else...
18:20:20 <mboddu> Thanks nirik
18:20:25 <nirik> #endmeeting