19:00:59 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 19:00:59 Meeting started Tue Feb 7 19:00:59 2023 UTC. 19:00:59 This meeting is logged and archived in a public location. 19:00:59 The chair is phsmoura. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 19:00:59 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:59 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 19:00:59 #chair nirik smooge 19:00:59 #meetingname fedora_infrastructure_ops_daily_standup_meeting 19:00:59 Current chairs: nirik phsmoura smooge 19:00:59 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 19:00:59 #info meeting is 30 minutes MAX. At the end of 30, its stops 19:00:59 #info agenda is at https://board.net/p/fedora-infra-daily 19:01:20 good morning everyone 19:01:30 hello 19:01:34 hello 19:01:54 #info reminder: speak up if you want to work on a ticket! 19:01:54 #topic Tickets needing review 19:02:12 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 19:02:23 .ticket 11119 19:02:24 phsmoura: Issue #11119: Is FMN alive? - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/11119 19:02:42 med med ops 19:02:50 I was looking at it, but not sure whats going on yet. 19:03:06 it needs a McCoy-bot to kick start it 19:03:27 soon the new one will roll out. ;) 19:03:39 or report back -- It's dead Nirik. I'm a doctor not a computer programmer 19:04:37 #info https://pagure.io/releng/issues?status=Open 19:04:47 .releng 11262 19:04:48 phsmoura: Issue #11262: Unretire rust-hamcrest2 - releng - Pagure.io - https://pagure.io/releng/issue/11262 19:04:52 low low ops 19:05:41 +1 19:06:10 #topic Planning, Upcoming work and Open floor 19:07:07 I've been fighting fires and emails and chats all morning. ;) 19:07:30 But I hope to get past that and move to to more rhel9 reinstalls. Been doing the staging virthosts. 19:07:32 I hope that gets better soon 19:07:54 I hit one that has a bad disk... anaconda won't deal with degraded raid, so I skipped it for now. 19:08:26 anaconda isn't as forgiving as it used to be 19:08:51 s/forgiving/able to potentially install on crap/ :) 19:08:54 naw, it never handled it. I found some really old fedora bugs where people asked for it and they said nope nope nope 19:09:15 oh I used to be able to do it with the EL6/EL7? anaconda 19:09:38 you just installed around that disk and then added it in afterwords 19:09:57 but it was 'possible' because you could individually select things with the older disk util 19:10:15 or at least there was some way I used it on the ibm boxes a couple of times long ago 19:10:30 anyway... I understand why they wouldn't want to support it 19:10:40 yeah. 19:11:02 I couldn't figure how to do it now. I could start the raid, but if I clicked rescan it saw it was degraded and stopped it. 19:11:17 and if I didn't rescan it saw it as degraded and wouldn't open it. 19:11:57 Anyhow, I don't think I have anything else for today... 19:12:13 oh wait 19:12:38 a wild Steve Jobs has entered the chat 19:12:43 I did have one more note: I upgraded the kernel on bvmhost-p09-01... it's got a higher load now, but it is staying very responsive... so I guess we can wait and see 19:12:58 Im having trouble to deploy fedora planet in ocp. Dont think the problem is in build config. added resources in build config and still having the same error, maybe it cant pull fedora:36 from a registry? can any of you help? 19:14:38 that should work... perhaps we can debug in noc after this? 19:14:46 sure 19:14:57 should we close already? 19:15:31 +1 19:15:55 +1 19:16:00 thanks for joining today :) 19:16:05 #endmeeting