#meeting-3:fedoraproject.org log

<@phsmoura:fedora.im>

16:00:08

!startmeeting Infrastructure (2025-10-23)

<@meetbot:fedora.im>

16:00:10

Meeting started at 2025-10-23 16:00:08 UTC

<@meetbot:fedora.im>

16:00:11

The Meeting name is 'Infrastructure (2025-10-23)'

<@phsmoura:fedora.im>

16:00:16

!info Agenda is at: https://board.net/p/fedora-infra

<@phsmoura:fedora.im>

16:00:16

!info Fedora Infra documentation: https://docs.fedoraproject.org/en-US/infra

<@phsmoura:fedora.im>

16:00:16

!topic Hola y bienvenido

<@phsmoura:fedora.im>

16:00:16

!info About our team: https://docs.fedoraproject.org/en-US/cle/

<@phsmoura:fedora.im>

16:00:16

!chair @nirik:matrix.scrye.com @zlopez:fedora.im @jnsamyak:matrix.org @james:fedora.im

<@phsmoura:fedora.im>

16:00:16

!meetingname infrastructure

<@meetbot:fedora.im>

16:00:17

The Meeting Name is now infrastructure

<@phsmoura:fedora.im>

16:00:35

hello

<@zlopez:fedora.im>

16:00:38

!hi

<@zodbot:fedora.im>

16:00:39

Michal Konecny (zlopez)

<@james:fedora.im>

16:00:40

Hey

<@gwmngilfen:fedora.im>

16:01:19

!hi

<@zodbot:fedora.im>

16:01:22

Greg Sutcliffe (gwmngilfen) - he / him / his

<@phsmoura:fedora.im>

16:02:10

!info Getting Started Guide: https://docs.fedoraproject.org/en-US/infra/gettingstarted/

<@phsmoura:fedora.im>

16:02:10

!info This is a place where people who are interested in Fedora Infrastructure can introduce themselves

<@phsmoura:fedora.im>

16:02:10

!topic New folks introductions

<@phsmoura:fedora.im>

16:02:25

lets see if we have new people

<@nirik:matrix.scrye.com>

16:03:45

morning

<@nirik:matrix.scrye.com>

16:03:51

not new, but here. ;)

<@gwmngilfen:fedora.im>

16:04:27

beat me to that joke

<@phsmoura:fedora.im>

16:04:46

!info magic eight ball says:

<@phsmoura:fedora.im>

16:04:46

!info chair 2025-11-13 - ???

<@phsmoura:fedora.im>

16:04:46

!info chair 2025-11-06 - ???

<@phsmoura:fedora.im>

16:04:46

!info chair 2025-10-30 - nirik

<@phsmoura:fedora.im>

16:04:46

!info chair 2025-10-23 - phsmoura

<@phsmoura:fedora.im>

16:04:46

!topic Next chair

<@phsmoura:fedora.im>

16:05:13

anyone would like to chair the meeting in the next weeks?

<@zlopez:fedora.im>

16:05:33

I can probably take the 11-06

<@phsmoura:fedora.im>

16:08:26

!topic announcements and information

<@phsmoura:fedora.im>

16:08:26

!info CLE Infra&Releng EU-hours team has a Monday through Thursday 30 minute meeting going through tickets at 0815 UTC in https://matrix.to/#/#meeting-3:fedoraproject.org

<@phsmoura:fedora.im>

16:08:26

!info CLE Infra&Releng NA-hours team has a Monday through Thursday 30 minute meeting going through tickets at 1900 UTC in https://matrix.to/#/#meeting-3:fedoraproject.org

<@phsmoura:fedora.im>

16:08:51

do we have any other announcement?

<@zlopez:fedora.im>

16:09:54

!info Final freeze for F43 is still in effect

<@gwmngilfen:fedora.im>

16:09:59

is my zabbix talk appropriate, or just a note for further own the logs?

<@gwmngilfen:fedora.im>

16:10:04

is my zabbix talk appropriate, or just a note for further down the logs?

<@nirik:matrix.scrye.com>

16:10:21

please link it. ;)

<@gwmngilfen:fedora.im>

16:11:06

!info there was a recent [CLE Tech talk on Zabbix](https://gwmngilfen.fedorapeople.org/recordings/Intro%20to%20Zabbix%20for%20users,%20devs%20&%20sysadmins%20(2025-10-13).mp4) for folks interacting with our monitoring

<@gwmngilfen:fedora.im>

16:11:41

i've opened a ticket on getting it up on YT, but for now, there it is 😛

<@nirik:matrix.scrye.com>

16:12:09

oh, and...

<@nirik:matrix.scrye.com>

16:12:38

!info nirik out tomorrow ( 2025-10-24) and monday ( 2025-10-27 ).

<@gwmngilfen:fedora.im>

16:13:22

i suspect you might not get a *lot* from it, given how much we've talked about it 😛

<@gwmngilfen:fedora.im>

16:13:43

i plan to record another one specifically on creating/testing/rolling out a set of checks

<@zlopez:fedora.im>

16:14:24

!info zlopez is out on 2025-10-27 and 2025-10-28

<@phsmoura:fedora.im>

16:16:29

!info https://docs.fedoraproject.org/en-US/infra/day_to_day_fedora/#_the_oncall_role_in_our_team

<@phsmoura:fedora.im>

16:16:29

!info on call from 2025-10-10 to 2025-10-16 - nirik

<@phsmoura:fedora.im>

16:16:29

!info on call from 2025-11-07 to 2025-11-13 - ???

<@phsmoura:fedora.im>

16:16:29

!info on call from 2025-10-24 to 2025-11-06 - ???

<@phsmoura:fedora.im>

16:16:29

!info on call from 2025-10-17 to 2025-10-23 - zlopez

<@phsmoura:fedora.im>

16:16:29

!topic Oncall

<@phsmoura:fedora.im>

16:16:49

anyone would like to be oncall in the next weeks?

<@nirik:matrix.scrye.com>

16:17:24

I can take it and I do still have on my list to start a discussion about it, just keep not getting to it.

<@phsmoura:fedora.im>

16:18:36

2025-10-24 to 2025-11-06 nirik ?

<@nirik:matrix.scrye.com>

16:18:41

sure

<@nirik:matrix.scrye.com>

16:21:08

!oncall

<@zodbot:fedora.im>

16:21:08

<@zodbot:fedora.im>

16:21:08

The following people are oncall:

<@zodbot:fedora.im>

16:21:08

● @nirik:matrix.scrye.com (kevin) Current Time for them: 09:21 (US/Pacific)

<@zodbot:fedora.im>

16:21:08

If they do not respond, please file a ticket (https://pagure.io/fedora-infrastructure/issues)

<@phsmoura:fedora.im>

16:21:46

!info Summary of last week: ( Zlopez )

<@zlopez:fedora.im>

16:22:12

I didn't saw any ping

<@zlopez:fedora.im>

16:22:26

At least not oncall ping

<@phsmoura:fedora.im>

16:23:15

!info Go over existing items and fix them

<@phsmoura:fedora.im>

16:23:15

!topic Monitoring discussion [nirik]

<@phsmoura:fedora.im>

16:23:15

!info https://nagios.fedoraproject.org/nagios & https://zabbix.fedoraproject.org

<@nirik:matrix.scrye.com>

16:23:46

lets see

<@gwmngilfen:fedora.im>

16:23:51

so before I have to run

<@gwmngilfen:fedora.im>

16:24:21

I did a bit of digging on the frequent alerts on sundries. https://pagure.io/fedora-infrastructure/issue/12863 is a suggestion to maybe help

<@nirik:matrix.scrye.com>

16:24:22

nothing much new in nagios land... there's some vmhost-p09-copr alerts, but we were working on that this morning.

<@nirik:matrix.scrye.com>

16:24:42

yeah, I am not sure I like that for various reasons... but we can figure something out.

<@gwmngilfen:fedora.im>

16:24:49

fair enough

<@gwmngilfen:fedora.im>

16:25:02

i can think of one reason for sure

<@nirik:matrix.scrye.com>

16:25:20

ie, on release days we want docs all updating at the same time for release or the like... or to know when a change syncs out...

<@gwmngilfen:fedora.im>

16:25:20

which only occurred to me about an hour ago

<@gwmngilfen:fedora.im>

16:25:36

right, all the pages should be the same at the same time

<@gwmngilfen:fedora.im>

16:25:42

anyway, -> ticket for that

<@gwmngilfen:fedora.im>

16:26:22

otherwise zabbix looks pretty normal too. still a bunch of thresholds to tune but seems sane

<@gwmngilfen:fedora.im>

16:26:45

I've been testing some stuff for RAID and Anubis monitoring on stg too

<@gwmngilfen:fedora.im>

16:27:02

(and shortly HAProxy too, when I have a moment)

<@gwmngilfen:fedora.im>

16:27:49

fin

<@nirik:matrix.scrye.com>

16:28:26

I'm not sure when we can shut off nagios, but we are well on our way.

<@nirik:matrix.scrye.com>

16:28:40

Would be great to have it just as a backup role by the end of the year at least.

<@gwmngilfen:fedora.im>

16:29:14

definitely Q4 is my target to make it "official", but with nagios as the backup

<@gwmngilfen:fedora.im>

16:29:36

I was chatting with Anton today, he's going to dig into what is most essential for releng's monitoring needs

<@nirik:matrix.scrye.com>

16:29:55

excellent

<@gwmngilfen:fedora.im>

16:30:52

its been a long road, but as I hoped, I've learned a lot about our infra along the way 😛

<@zodbot:fedora.im>

16:31:10

james gave a cookie to gwmngilfen. They now have 12 cookies, 8 of which were obtained in the Fedora 42 release cycle

<@zodbot:fedora.im>

16:31:25

zlopez gave a cookie to gwmngilfen. They now have 13 cookies, 9 of which were obtained in the Fedora 42 release cycle

<@zodbot:fedora.im>

16:32:07

kevin gave a cookie to gwmngilfen. They now have 14 cookies, 10 of which were obtained in the Fedora 42 release cycle

<@gwmngilfen:fedora.im>

16:32:22

he, maybe I don't need to go cook after all

<@nirik:matrix.scrye.com>

16:32:24

cookie party

<@gwmngilfen:fedora.im>

16:32:25

heh, maybe I don't need to go cook after all

<@gwmngilfen:fedora.im>

16:32:35

so many cookies!

<@gwmngilfen:fedora.im>

16:32:47

but actually I do, so, laters folks 😛

<@phsmoura:fedora.im>

16:33:02

!info Refine oldest tickets on Fedora Infra tracker

<@phsmoura:fedora.im>

16:33:02

!topic Fedora Infra backlog refinement https://pagure.io/fedora-infrastructure/report/weekly_refinement

<@phsmoura:fedora.im>

16:33:02

!link https://pagure.io/fedora-infrastructure/report/weekly_refinement

<@nirik:matrix.scrye.com>

16:34:02

a report eh? nice...

<@nirik:matrix.scrye.com>

16:34:42

so what is this sorted by...

<@zlopez:fedora.im>

16:35:07

Open date

<@nirik:matrix.scrye.com>

16:35:14

just oldest. Thats not what we want I don't think. I think we want oldest NOT updated

<@zlopez:fedora.im>

16:35:45

We had that before

<@nirik:matrix.scrye.com>

16:36:55

I am not sure how to fix it.

<@zlopez:fedora.im>

16:37:24

I don't know how the weekly_refinement link is even created

<@zlopez:fedora.im>

16:37:33

But here is the correct sorting

<@zlopez:fedora.im>

16:37:34

https://pagure.io/fedora-infrastructure/issues?status=Open&order_key=last_updated&order=asc

<@zlopez:fedora.im>

16:38:27

!ticket 12292

<@nirik:matrix.scrye.com>

16:38:28

I see where I can delete it, but not edit it.

<@zodbot:fedora.im>

16:38:28

● **Opened:** 11 months ago by music

<@zodbot:fedora.im>

16:38:28

**fedora-infrastructure #12292** (https://pagure.io/fedora-infrastructure/issue/12292):**Pagure returns error 500 trying to open a PR on https://src.fedoraproject.org/rpms/python-setuptools-gettext**

<@zodbot:fedora.im>

16:38:28

<@zodbot:fedora.im>

16:38:28

● **Last Updated:** 10 months ago

<@zodbot:fedora.im>

16:38:28

● **Assignee:** kevin

<@nirik:matrix.scrye.com>

16:38:31

oh well.

<@zlopez:fedora.im>

16:38:55

This is the oldest update I can see

<@nirik:matrix.scrye.com>

16:39:14

oh man, I totally failed to do whatever I said I would there.

<@nirik:matrix.scrye.com>

16:39:36

I can update it, probibly want to wait until after freeze? or not I guess.

<@nirik:matrix.scrye.com>

16:40:00

added a comment

<@zlopez:fedora.im>

16:40:21

Let go for next one than

<@zlopez:fedora.im>

16:40:31

!ticket 12270

<@zodbot:fedora.im>

16:40:32

● **Assignee:** Not Assigned

<@zodbot:fedora.im>

16:40:32

● **Opened:** 11 months ago by horth

<@zodbot:fedora.im>

16:40:32

<@zodbot:fedora.im>

16:40:32

**fedora-infrastructure #12270** (https://pagure.io/fedora-infrastructure/issue/12270):**Define a more appropriate fallback for the UA mirror**

<@zodbot:fedora.im>

16:40:32

● **Last Updated:** 10 months ago

<@nirik:matrix.scrye.com>

16:41:00

oh yeah, this one.

<@nirik:matrix.scrye.com>

16:41:10

I would really like to be able to do something here... but it's not easy

<@nirik:matrix.scrye.com>

16:44:06

So, I'm torn here...

<@nirik:matrix.scrye.com>

16:44:27

we could just close it and say sorry, we don't have any easy way to do this.

<@zlopez:fedora.im>

16:45:05

What is the benefit to have the fallback?

<@nirik:matrix.scrye.com>

16:45:06

or we could I guess refile it as a mirrormanager RFE and see if they can think of anything, but adrian already chimed in

<@nirik:matrix.scrye.com>

16:45:33

that users there don't get a bunch of 404/401/timeouts when updating

<@james:fedora.im>

16:45:49

Yeh, your initial comment seems like the best we can do unless someone wants to invest in MM development.

<@nirik:matrix.scrye.com>

16:45:56

I'm not sure which way they are blocking things... I guess that could weigh into how anoying it is.

<@nirik:matrix.scrye.com>

16:47:24

I guess I could ask them about that?

<@nirik:matrix.scrye.com>

16:48:26

let me ask them about that and ask for ways forward in the ticket? or do we think we should close it?

<@zlopez:fedora.im>

16:49:27

I'm not sure about this, it definitely seems like something useful and it would be helpful in future

<@nirik:matrix.scrye.com>

16:50:16

sure, but it would be work in mirrormanager for sure.

<@nirik:matrix.scrye.com>

16:50:46

I'll ask if they can refile upstream?

<@zlopez:fedora.im>

16:50:57

I assume that is the best option

<@james:fedora.im>

16:51:13

Yeh, can't hurt.

<@nirik:matrix.scrye.com>

16:51:26

(but note... Aurélien B did work on mirrormanager to port it to python3, but I don't know that he's 'maintaining' it... and adrian is very busy too, so I am not sure anyone is 'maintaining' it :)

<@phsmoura:fedora.im>

16:53:37

we have about 7 min should we revisit blocked tickets?

<@zlopez:fedora.im>

16:54:23

I think we can either switch to open floor or go to next ticket

<@nirik:matrix.scrye.com>

16:55:44

not much time left. ;)

<@zlopez:fedora.im>

16:56:05

Let's switch to open floor than

<@zlopez:fedora.im>

16:56:15

At least we checked out 2 tickets

<@phsmoura:fedora.im>

16:56:36

!topic Open Floor

<@nirik:matrix.scrye.com>

16:59:15

for any interested the f43 go/nogo is in a few minutes...

<@phsmoura:fedora.im>

17:00:23

ok, lets go back then

<@phsmoura:fedora.im>

17:00:30

thanks everyone :)

<@phsmoura:fedora.im>

17:00:34

!endmeeting