<@lenkaseg:fedora.im>
16:00:22
!startmeeting Infrastructure (2024-08-29)
<@meetbot:fedora.im>
16:12:52
Meeting started at 2024-08-29 16:00:22 UTC
<@meetbot:fedora.im>
16:12:52
The Meeting name is 'Infrastructure (2024-08-29)'
<@lenkaseg:fedora.im>
16:13:11
meetbot is back!
<@zodbot:fedora.im>
16:13:12
None (smilner)
<@lenkaseg:fedora.im>
16:13:36
we can decide the chair on the next meeting
<@lenkaseg:fedora.im>
16:13:45
!topic announcements and information
<@lenkaseg:fedora.im>
16:13:55
!info CPE Infra&Releng NA-hours team has a Monday through Thursday 30 minute meeting going through tickets at 1800 UTC in #fedora-meeting-3
<@lenkaseg:fedora.im>
16:13:55
!info CPE Infra&Releng EU-hours team has a Monday through Thursday 30 minute meeting going through tickets at 0800 UTC in https://matrix.to/#/#meeting-3:fedoraproject.org
<@lenkaseg:fedora.im>
16:14:10
!info F41 Beta freeze started ( 2024-08-27 )
<@lenkaseg:fedora.im>
16:14:25
Is there something more to announce?
<@lenkaseg:fedora.im>
16:16:32
let's move on to oncall!
<@lenkaseg:fedora.im>
16:16:43
!info https://fedoraproject.org/wiki/Infrastructure/Oncall
<@lenkaseg:fedora.im>
16:16:43
!topic Oncall
<@lenkaseg:fedora.im>
16:16:43
!info https://docs.fedoraproject.org/en-US/cpe/day_to_day_fedora/
<@lenkaseg:fedora.im>
16:16:54
!info lenkaseg is on call from 2024-08-30 to 2024-09-05
<@lenkaseg:fedora.im>
16:16:54
!info leo is on call from 2024-08-22 to 2024-08-29
<@lenkaseg:fedora.im>
16:16:54
<@lenkaseg:fedora.im>
16:17:50
Do we have any volunteers for oncall 2024-09-06 to 2024-09-12?
<@lenkaseg:fedora.im>
16:20:01
no problem, this week it's gonna be me and we can decide next week
<@lenkaseg:fedora.im>
16:20:11
can someone assign me to oncall please?
<@lenkaseg:fedora.im>
16:20:19
!info Summary of last week: (from current oncall)
<@lenkaseg:fedora.im>
16:20:25
Over to Leo!
<@lenkaseg:fedora.im>
16:22:25
ah, leo is probably not here (I'd swear I saw that nickname today around, but seems that not)
<@lenkaseg:fedora.im>
16:22:33
next topic:
<@lenkaseg:fedora.im>
16:22:34
!info Go over existing out items and fix
<@lenkaseg:fedora.im>
16:22:34
!info https://nagios.fedoraproject.org/nagios
<@lenkaseg:fedora.im>
16:22:34
!topic Monitoring discussion [nirik]
<@nirik:matrix.scrye.com>
16:22:36
I can do it...
<@nirik:matrix.scrye.com>
16:22:41
I mean assign you. ;)
<@lenkaseg:fedora.im>
16:23:46
Anything for Monitoring discussion nirik ?
<@nirik:matrix.scrye.com>
16:24:17
lets see... well, it's kinda grim looking right now because of the network upgrades. ;)
<@nirik:matrix.scrye.com>
16:24:24
But it should be clearing up soon.
<@nirik:matrix.scrye.com>
16:24:40
I managed to get those 2 arm boxes that were down fixed up with help from the folks onsite this week.
<@nirik:matrix.scrye.com>
16:25:19
So I think otherwise we are down to know issues: planet messages, vmhost-x86-11.stg with bad disk, vmhost-x86-copr01 down with power supply problems...
<@lenkaseg:fedora.im>
16:26:20
Thanks for the report nirik !
<@lenkaseg:fedora.im>
16:26:59
Now, RHEL7 EOL, blocked tickets or backlog refinement?
<@lenkaseg:fedora.im>
16:27:13
RHEL7 EOL
<@lenkaseg:fedora.im>
16:27:15
blocked
<@lenkaseg:fedora.im>
16:27:20
backlog refinement
<@lenkaseg:fedora.im>
16:27:23
vote please!
<@lenkaseg:fedora.im>
16:28:29
!topic RHEL7 EOL
<@lenkaseg:fedora.im>
16:28:29
!ticket https://pagure.io/fedora-infrastructure/issue/11815
<@lenkaseg:fedora.im>
16:28:29
!info Check the progress on tickets related to RHEL7 EOL (end of June)
<@lenkaseg:fedora.im>
16:28:53
I see two green issues
<@lenkaseg:fedora.im>
16:29:05
!8213
<@lenkaseg:fedora.im>
16:29:17
!ticket 8213
<@zodbot:fedora.im>
16:29:18
● **Last Updated:** a month ago
<@zodbot:fedora.im>
16:29:18
● **Opened:** 4 years ago by kevin
<@zodbot:fedora.im>
16:29:18
● **Assignee:** zlopez
<@zodbot:fedora.im>
16:29:18
<@zodbot:fedora.im>
16:29:18
**fedora-infrastructure #8213** (https://pagure.io/fedora-infrastructure/issue/8213):**fedmsg -> fedora-messaging migration tracker**
<@lenkaseg:fedora.im>
16:29:56
What's missing here?
<@smilner:fedora.im>
16:30:20
Good question. I can't really tell skimming through the comments :-/
<@lenkaseg:fedora.im>
16:30:52
fedimg maybe? https://pagure.io/fedora-infrastructure/issue/11803
<@lenkaseg:fedora.im>
16:31:18
Can pdc.yml be considered as done?
<@nirik:matrix.scrye.com>
16:31:41
we are waiting until the github2fedmsg is done to retire fedmsg. ;)
<@nirik:matrix.scrye.com>
16:32:09
fedimg and pdc should both be done. I think github2fedmsg is the last thing.
<@lenkaseg:fedora.im>
16:33:42
and yes, the other ticket is about github2fedmsg as well
<@lenkaseg:fedora.im>
16:33:48
!ticket 11804
<@zodbot:fedora.im>
16:33:48
● **Last Updated:** 6 days ago
<@zodbot:fedora.im>
16:33:48
● **Assignee:** abompard
<@zodbot:fedora.im>
16:33:48
● **Opened:** 6 months ago by zlopez
<@zodbot:fedora.im>
16:33:48
<@zodbot:fedora.im>
16:33:48
**fedora-infrastructure #11804** (https://pagure.io/fedora-infrastructure/issue/11804):**rhel7 EOL - github2fedmsg**
<@lenkaseg:fedora.im>
16:35:07
we probably don't have any update about that one
<@lenkaseg:fedora.im>
16:35:33
Ok, what now? blocked/backlog, discussion or ...
<@nirik:matrix.scrye.com>
16:35:51
I need to leave in a few here to take someone to the airpot... just FYI.
<@lenkaseg:fedora.im>
16:36:14
Yup, so in that case maybe let's finish early today?
<@lenkaseg:fedora.im>
16:39:01
Alright then, everybody thanks for attending and see you next time!
<@lenkaseg:fedora.im>
16:39:07
!endmeeting