18:02:36 <phsmoura> #startmeeting Fedora Infrastructure Ops Daily Standup Meeting
18:02:36 <zodbot> Meeting started Wed Nov  2 18:02:36 2022 UTC.
18:02:36 <zodbot> This meeting is logged and archived in a public location.
18:02:36 <zodbot> The chair is phsmoura. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
18:02:36 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:02:36 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
18:02:36 <phsmoura> #chair nirik mobrien aheath1992 smooge
18:02:36 <phsmoura> #meetingname fedora_infrastructure_ops_daily_standup_meeting
18:02:36 <zodbot> Current chairs: aheath1992 mobrien nirik phsmoura smooge
18:02:36 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
18:02:36 <phsmoura> #info meeting is 30 minutes MAX. At the end of 30, its stops
18:02:36 <phsmoura> #info agenda is at https://board.net/p/fedora-infra-daily
18:02:47 <nirik> morning everyone
18:03:01 <phsmoura> morning
18:03:43 <smooge> hello
18:04:46 <phsmoura> #info reminder: speak up if you want to work on a ticket!
18:04:47 <phsmoura> #topic Tickets needing review
18:04:56 <phsmoura> #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1
18:05:13 <phsmoura> .ticket 10971
18:05:14 <zodbot> phsmoura: Issue #10971: Greenwave: Remove no longer used objects in OpenShift - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10971
18:05:21 <nirik> low low ops?
18:06:11 <phsmoura> +1
18:06:55 <nirik> in fact, easy to do... just did it. ;)
18:06:57 <phsmoura> just delete using the manifest? Can I do that?
18:07:02 <phsmoura> ah ok :)
18:07:23 <nirik> just ran that command. done. closing it.
18:07:47 <phsmoura> #info https://pagure.io/releng/issues?status=Open
18:08:02 <phsmoura> .releng 11117
18:08:05 <zodbot> phsmoura: Issue #11117: Useless comps files in Modular repository - releng - Pagure.io - https://pagure.io/releng/issue/11117
18:09:04 <nirik> This might be a pungi bug... or misconfiguration on our part.
18:09:47 <smooge> or both
18:11:16 <smooge> next?
18:11:26 <smooge> or med/med/ops?
18:11:44 <phsmoura> I dont know how to tag this or how hard it is to solve
18:12:13 <phsmoura> done
18:12:16 <nirik> yeah, unclear... I guess med/med ops...
18:12:59 * smooge has only un-useful suggestions that come with kerosene and matches
18:13:34 <phsmoura> #topic Planning, Upcoming work and Open floor
18:13:38 <phsmoura> open floor
18:13:50 <nirik> I asked lsedlar there (he's upstream pungi)
18:14:11 <nirik> So, for me... we will likely have a rc to make in a bit here (hopefully the last one)
18:14:50 <nirik> We finally have FMN processing and catching up I think now... mkonecny switched it from redis to memcached and it increased it's speed a lot.
18:15:26 <smooge> i think it has been.. mailq has been filling with either fedmsg for redhat.com
18:15:55 <smooge> or other domains which dont like firehoses
18:16:32 <nirik> only 1180484 messages left to process.
18:16:41 <smooge> tomorrow then
18:16:49 <smooge> geez
18:17:16 <nirik> note that many messages have 0 people who get notifications for them... so emails/irc will be a lot less in the end.
18:17:18 <smooge> what should be done about notification emails which get regularly bounced?
18:17:35 <smooge> and 'nothing' is a good answer
18:17:49 <nirik> depends on how it bounces I think.
18:18:04 <nirik> if it gets rejected right off, it disables the user
18:18:17 <nirik> if the message bounces back I am not sure if it does anything.
18:18:21 <smooge> there are some from redhat.com which regularly bounce due to no user there
18:18:45 <nirik> yeah, I noticed in fact that we have a bunch if redhat.com addresses on lists that are no more.
18:18:51 <smooge> but maybe I am misunderstanding where notifications@fpo works
18:18:55 <nirik> we should perhaps try and nuke all those manually.
18:18:59 <smooge> I cleaned out a bunch of those
18:19:08 <nirik> sadly the bounces from redhat.com are useless.
18:19:52 <nirik> for example, every email to the infrastructure list sends me an email saying a redhat.com address doesn't exist. However, they are not subscribed with that address and the bounce doesn't give me info to tell what address it was sent to.
18:19:57 <smooge> went through the logs on /var/log/maillog and found all the ones which gave redhat saying it wasn't a person anymore
18:20:17 <nirik> smooge: when was that?
18:20:23 <smooge> this weekend
18:20:48 <smooge> grep said: /var/log/maillog | awk -F'said:' '$2~/550 5.1.1/{split($1,a," "); print a[7]}' | sort | uniq -c | sort -bnr | head -n 40
18:22:00 <nirik> huh, because I see still on the infra list subscribers like wwoods@redhat.com  and people I know that are not at redhat anymore
18:22:57 <smooge> for some reason some emails get accepted and others get bounced
18:23:04 <smooge> wwoods gets accepted
18:23:16 <nirik> perhaps its going to management... dunno.
18:23:38 <nirik> anyhow, if you notice any notifications ones that are bouncing a lot, we can manually remove those people
18:23:42 <smooge> mskalick@redhat.com gets : Recipient address rejected: User unknown in local recipient table (in reply to RCPT TO command))
18:23:47 <nirik> or disable them rather
18:24:31 <smooge> that is a notifications person
18:25:37 <nirik> disabled them
18:26:51 <smooge> anyway I can mass unsubscribe wwoods then. I had hoped that seeing the `Recipient address rejected: User unknown in local recipient table` was for all ex-RH'ers since various people I know had left in mgmt were bouncing
18:27:43 <smooge> that would be about 11 lists
18:29:43 <nirik> sure, less bounces the better.
18:29:49 <smooge> other than that I don't have anything for this meeting.
18:30:41 <phsmoura> ok, thanks for joining :)
18:30:53 <phsmoura> #endmeeting