<@phsmoura:fedora.im>
19:00:30
!startmeeting Fedora Infrastructure Ops Daily Standup Meeting
<@meetbot:fedora.im>
19:00:31
Meeting started at 2025-03-17 19:00:30 UTC
<@meetbot:fedora.im>
19:00:31
The Meeting name is 'Fedora Infrastructure Ops Daily Standup Meeting'
<@phsmoura:fedora.im>
19:00:36
!chair nirik phsmoura james
<@phsmoura:fedora.im>
19:00:36
!info reminder: speak up if you want to work on a ticket!
<@phsmoura:fedora.im>
19:00:36
!info agenda is at https://board.net/p/fedora-infra-daily
<@phsmoura:fedora.im>
19:00:36
!info meeting is 30 minutes MAX. At the end of 30, its stops
<@phsmoura:fedora.im>
19:00:36
!meetingname fedora_infrastructure_ops_daily_standup_meeting
<@meetbot:fedora.im>
19:00:36
The Meeting Name is now fedora_infrastructure_ops_daily_standup_meeting
<@phsmoura:fedora.im>
19:00:38
hello
<@smilner:fedora.im>
19:01:00
!hi
<@zodbot:fedora.im>
19:01:01
None (smilner)
<@nirik:matrix.scrye.com>
19:01:51
morning
<@phsmoura:fedora.im>
19:03:06
pagure is timing out here... am I the only one having this issue?
<@smilner:fedora.im>
19:03:13
Checking
<@smilner:fedora.im>
19:03:32
Seems to be responding for me
<@nirik:matrix.scrye.com>
19:03:34
phsmoura let me know your IP.
<@nirik:matrix.scrye.com>
19:03:49
you are likely blocked. I had to block all .br. ;(
<@nirik:matrix.scrye.com>
19:04:57
feel free to DM me or otherwise let me know and I can unblock that net
<@nirik:matrix.scrye.com>
19:05:18
I guess I could try dropping the global block and see if it's still causing problems...
<@nirik:matrix.scrye.com>
19:06:14
ok, unblocked. lets see how long until it's having problems again
<@phsmoura:fedora.im>
19:06:28
ah thanks
<@phsmoura:fedora.im>
19:06:50
I sent a DM with my IP, but now I can access it again
<@nirik:matrix.scrye.com>
19:07:19
I have no idea why there is so much traffic from .br. ;(
<@phsmoura:fedora.im>
19:07:40
!info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1
<@phsmoura:fedora.im>
19:07:40
!topic Tickets needing review
<@phsmoura:fedora.im>
19:08:02
!ticket 12450
<@zodbot:fedora.im>
19:08:03
● **Opened:** 2 hours ago by mulhern
<@zodbot:fedora.im>
19:08:03
<@zodbot:fedora.im>
19:08:03
**fedora-infrastructure #12450** (https://pagure.io/fedora-infrastructure/issue/12450):**rpminspect task failing on stratisd bodhi updates in a consistent(?) manner**
<@zodbot:fedora.im>
19:08:03
● **Assignee:** Not Assigned
<@zodbot:fedora.im>
19:08:03
● **Last Updated:** Never
<@nirik:matrix.scrye.com>
19:08:38
I looked at this a tiny bit and asked in the #fedora-ci:fedoraproject.org channel, but it's unclear exactly where the problem is.
<@nirik:matrix.scrye.com>
19:09:50
the test is actually passing, but there's a core dump (from something?) that prevents it from outputting the results.
<@smilner:fedora.im>
19:09:53
> We think that the failure we see in Bodhi must be due to the testing infrastructure failing, somehow.
<@smilner:fedora.im>
19:09:53
Sounds like deeper debugging would be needed to isolate. Given they haven o pressing deadline sounds like med or high trouble for low gain?
<@smilner:fedora.im>
19:09:59
> We think that the failure we see in Bodhi must be due to the testing infrastructure failing, somehow.
<@smilner:fedora.im>
19:09:59
<@smilner:fedora.im>
19:09:59
Sounds like deeper debugging would be needed to isolate. Given they haven o pressing deadline sounds like med or high trouble for low gain?
<@smilner:fedora.im>
19:10:32
> We think that the failure we see in Bodhi must be due to the testing infrastructure failing, somehow.
<@smilner:fedora.im>
19:10:32
<@smilner:fedora.im>
19:10:32
Sounds like deeper debugging would be needed to isolate. Given they have no pressing deadline sounds like med or high trouble for low gain?
<@nirik:matrix.scrye.com>
19:10:36
well, the test thats failing... isn't blocking
<@nirik:matrix.scrye.com>
19:10:48
both of those updates are already stable
<@nirik:matrix.scrye.com>
19:11:03
oh no, one isn't
<@nirik:matrix.scrye.com>
19:11:26
but thats just because it's not passed the karma/time requirements
<@nirik:matrix.scrye.com>
19:11:43
med trouble sounds right...
<@nirik:matrix.scrye.com>
19:11:54
and hopefully ci folks can figure out more?
<@smilner:fedora.im>
19:13:00
Sounds reasonable. Let's make sure they know we are looking to them to investigate!
<@nirik:matrix.scrye.com>
19:13:59
yeah, I am not sure who to exactly cc there, perhaps mvadkert ?
<@smilner:fedora.im>
19:15:48
Sounds like a good start. If it's the wrong person I'm sure they'll tell us :-D
<@phsmoura:fedora.im>
19:17:07
!topic Planning, Upcoming work and Open floor
<@phsmoura:fedora.im>
19:17:13
anything for open floor?
<@nirik:matrix.scrye.com>
19:17:36
!info f42 beta release is tomorrow ( 2025-03-18 )
<@nirik:matrix.scrye.com>
19:17:44
!info infra freeze ends on wed
<@nirik:matrix.scrye.com>
19:19:16
Nothing much else from me. just trying to catch back up.
<@phsmoura:fedora.im>
19:19:27
I was trying to reproduce issue 12447, but now its resolved... looking for something else
<@nirik:matrix.scrye.com>
19:21:03
did you ever get to the bottom of that planet crashing stuff?
<@nirik:matrix.scrye.com>
19:21:23
resultsdb has still been having issues. I've not figured out that one tierh
<@nirik:matrix.scrye.com>
19:21:27
resultsdb has still been having issues. I've not figured out that one either
<@phsmoura:fedora.im>
19:22:36
no.. the logs in stg are poiting invalid credentials..
<@nirik:matrix.scrye.com>
19:23:19
ah... wait, this is in staging only?
<@phsmoura:fedora.im>
19:24:16
the alerts are from stg
<@nirik:matrix.scrye.com>
19:24:44
ok, the resultsdb ones are all prod, so I think two seperate issues.
<@phsmoura:fedora.im>
19:26:14
ok, I dont have anything else
<@smilner:fedora.im>
19:26:26
Nothing from me :-)
<@nirik:matrix.scrye.com>
19:26:53
nothing more from me too
<@phsmoura:fedora.im>
19:27:14
ok, lets go back then
<@phsmoura:fedora.im>
19:27:17
thanks everyone
<@phsmoura:fedora.im>
19:27:20
!endmeeting