fedora_infrastructure_ops_daily_standup_meeting
LOGS
19:00:22 <nirik> #startmeeting Fedora Infrastructure Ops Daily Standup Meeting
19:00:22 <zodbot> Meeting started Wed Dec  1 19:00:22 2021 UTC.
19:00:22 <zodbot> This meeting is logged and archived in a public location.
19:00:22 <zodbot> The chair is nirik. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
19:00:22 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
19:00:22 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
19:00:23 <nirik> #chair mboddu nirik pingou mobrien nb
19:00:23 <zodbot> Current chairs: mboddu mobrien nb nirik pingou
19:00:23 <nirik> #meetingname fedora_infrastructure_ops_daily_standup_meeting
19:00:23 <nirik> #info meeting is 30 minutes MAX. At the end of 30, its stops
19:00:23 <nirik> #info agenda is at https://board.net/p/fedora-infra-daily
19:00:23 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
19:00:24 <nirik> #info reminder: speak up if you want to work on a ticket!
19:00:26 <nirik> #topic Tickets needing review
19:00:28 <nirik> #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1
19:00:32 <mboddu> Hello nirik
19:00:49 <nirik> morning
19:01:11 <nirik> .ticket 10389
19:01:12 <zodbot> nirik: Issue #10389: new group in Fedora Accounts: websites-apps - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10389
19:01:17 <nirik> low low ops?
19:01:21 <mboddu> +1
19:01:31 <nirik> .ticket 10390
19:01:32 <zodbot> nirik: Issue #10390: Set up Old Metrics Process to send a Fedora Message Bus Message when complete. - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10390
19:01:34 <pmoura_> hello
19:01:37 <nirik> also low low ops?
19:01:42 <nirik> hey pmoura_
19:01:52 <nirik> and thats it for infra. any releng?
19:02:50 <mboddu> No new releng one's that needs processing
19:02:54 <mboddu> Hello pmoura_
19:02:54 <nirik> great!
19:03:03 <nirik> #topic Planning / Upcoming work
19:03:04 <carlwgeorge> i'd love to get help on https://pagure.io/releng/issue/10402 this week if possible
19:03:21 <mboddu> Yeah, I will work on it later today carlwgeorge
19:03:31 <carlwgeorge> awesome, thanks mboddu
19:03:37 <mboddu> I was a bit busy with F33 EOL and other CS stuff
19:03:47 <carlwgeorge> no worries, i was on pto anyways
19:03:54 <nirik> I'm hoping to start on builders updates, but I got sidetracked with a rhel qemu thing...
19:04:44 <nirik> #info friday is a red hat day of learning
19:04:57 <nirik> #info nirik out after next week
19:05:25 <nirik> #topic Discussion / AOB
19:05:29 <nirik> anything else to discuss?
19:05:41 <Leo[m]> Hey!
19:05:42 <Leo[m]> .hello leo
19:05:43 <zodbot> Leo[m]: leo 'Leo Puvilland' <leo@craftcat.dev>
19:05:50 <mboddu> Nothing from me, I hope epel-release symlink thing is fixed for good, thanks pmoura_ for your help
19:05:56 <mboddu> Hello Leo[m]
19:06:24 <nirik> hey Leo[m]
19:07:03 <pmoura_> thank you mboddu, sorry for forgeting to add "/" before "pub/epel" btw... thanks for fixing it
19:07:58 <nirik> pmoura_: I'll ping you when I start on builders... perhaps I can feed you info and you can work on updaing/rewriting the SOP on it as we go...
19:09:16 <nirik> the current sop is... all wrong. :)
19:09:33 <pmoura_> ok nirik.. Ill just stop to eat something in an hour, but Ill be here
19:10:40 <nirik> pmoura_: I'm needing to take someone into a appointment, then epel meeting... and this qemu stuff, so might not be until tomorrow too. we will see
19:11:06 <pmoura_> ok, no problem
19:11:08 <nirik> one problem I already know we need to solve is getting a f35 install to work on s390x... :(
19:12:14 <sharkcz> nirik: what problem do you have with f35 on s390x?
19:12:29 <nirik> sharkcz: that brltty error... I can try another one.
19:12:34 <sharkcz> ah, this one
19:13:03 <nirik> 19:12:58,372 WARNING brltty:mounted file systems table open erorr: /etc/mtab: No such file or directory
19:13:03 <nirik> 19:12:58,373 ERR brltty:file system mount error: usbfs[brltty-usbfs] -> /run/brltty/usbfs: No such device
19:13:53 <nirik> anyhow, I can file a bug and we can poke at it? or is there one already?
19:14:15 <sharkcz> I believe there is already one and it's a generic issue, not s390x specific
19:14:49 <nirik> https://bugzilla.redhat.com/show_bug.cgi?id=2007477
19:15:12 <sharkcz> I can give it few attemps in the morning to see if there is a pattern or something like that
19:15:16 <nirik> but yeah, that makes it sound like it's no issue really.
19:15:40 <nirik> sharkcz: we have f35 host there too... which may not be a setup many people are using
19:15:42 <sharkcz> ack, I don't recall seeing it personally
19:16:07 <sharkcz> this is the kvm setup, right?
19:16:38 <nirik> ah wait.
19:16:42 <nirik> Is is my fault
19:16:51 <nirik> - Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-35&arch=s390x [Could not resolve host: mirrors.fedoraproject.org]
19:17:06 <nirik> let me look at dns... but I can do that out of meeting. ;)
19:17:16 <nirik> anything else to discuss?
19:17:28 <sharkcz> ok, let me know if I should try something tomorrow
19:18:05 <nirik> can do. Many thanks sharkcz
19:18:17 <sharkcz> np
19:18:32 <nirik> ok, thanks everyone!
19:18:37 <nirik> #endmeeting