#meeting-3:fedoraproject.org log

<@meetbot:fedora.im>

08:29:45

HTML Minutes: https://meetbot.fedoraproject.org/meeting-3_matrix_fedoraproject-org/2024-10-16/cpe-infra-releng-daily-standup.2024-10-16-08.02.html

<@phsmoura:fedora.im>

19:00:28

!startmeeting Fedora Infrastructure Ops Daily Standup Meeting

<@meetbot:fedora.im>

19:00:29

Meeting started at 2024-10-16 19:00:28 UTC

<@meetbot:fedora.im>

19:00:29

The Meeting name is 'Fedora Infrastructure Ops Daily Standup Meeting'

<@phsmoura:fedora.im>

19:00:32

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

<@phsmoura:fedora.im>

19:00:32

!info reminder: speak up if you want to work on a ticket!

<@phsmoura:fedora.im>

19:00:32

!chair nirik smooge phsmoura

<@phsmoura:fedora.im>

19:00:32

!meetingname fedora_infrastructure_ops_daily_standup_meeting

<@phsmoura:fedora.im>

19:00:32

!info meeting is 30 minutes MAX. At the end of 30, its stops

<@meetbot:fedora.im>

19:00:32

The Meeting Name is now fedora_infrastructure_ops_daily_standup_meeting

<@phsmoura:fedora.im>

19:00:37

hello

<@phsmoura:fedora.im>

19:03:10

!topic Tickets needing review

<@nirik:matrix.scrye.com>

19:03:11

morning.

<@phsmoura:fedora.im>

19:03:19

!info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1

<@phsmoura:fedora.im>

19:03:41

!ticket 12242

<@zodbot:fedora.im>

19:03:42

● **Last Updated:** 36 minutes ago

<@zodbot:fedora.im>

19:03:42

<@zodbot:fedora.im>

19:03:42

**fedora-infrastructure #12242** (https://pagure.io/fedora-infrastructure/issue/12242):**many CentOS Stream repos on mirrors have bad hashes**

<@zodbot:fedora.im>

19:03:42

● **Opened:** 4 hours ago by tdawson

<@zodbot:fedora.im>

19:03:42

● **Assignee:** Not Assigned

<@nirik:matrix.scrye.com>

19:04:09

I'm not sure whats the issue here... I guess med med ops?

<@nirik:matrix.scrye.com>

19:04:32

I mean there's always a lag between sync -> mirrormanager finding new data -> mirrorlists updating.

<@james:fedora.im>

19:05:10

I think it's fixed now, but asked to make sure

<@phsmoura:fedora.im>

19:05:35

ok, med med ops wait the reporter then?

<@nirik:matrix.scrye.com>

19:05:59

sure. sounds ok to me.

<@phsmoura:fedora.im>

19:06:47

!info https://pagure.io/releng/issues?status=Open

<@phsmoura:fedora.im>

19:06:57

!releng 12397

<@zodbot:fedora.im>

19:06:58

● **Opened:** 7 hours ago by ksurma

<@zodbot:fedora.im>

19:06:58

**releng #12397** (https://pagure.io/releng/issue/12397):**Change Impact: Python 3.14**

<@zodbot:fedora.im>

19:06:58

<@zodbot:fedora.im>

19:06:58

● **Last Updated:** Never

<@zodbot:fedora.im>

19:06:58

● **Assignee:** Not Assigned

<@nirik:matrix.scrye.com>

19:07:32

low low ops, we can talk about it in the next releng meeting...

<@nirik:matrix.scrye.com>

19:07:42

I don't think it's going have too much impact specifically on us.

<@phsmoura:fedora.im>

19:09:23

!topic Planning, Upcoming work and Open floor

<@nirik:matrix.scrye.com>

19:09:41

!info we are in f41 final freeze now

<@nirik:matrix.scrye.com>

19:10:05

Mostly just catching up for me today... no super big plans off hand.

<@james:fedora.im>

19:11:07

FWIW I read a bunch of docs and got: https://central-rhacs-operator.apps.ocp.stg.fedoraproject.org/ "installled" for the cluster security thing ... but as you can probably tell with a click, there's an SSL connection problem.

<@james:fedora.im>

19:12:34

Also I'm pretty sure the main intent is to look at the images running within openshift, and checking those ... it says it can check repos. for images, but I think that's mainly for a "this is where we pull from" kind of thing. Will know more when I can actually connect to it though ;)

<@nirik:matrix.scrye.com>

19:12:42

so, the way our openshift clusters work is that our proxy servers do the ssl termination and proxy in to the cluster.

<@nirik:matrix.scrye.com>

19:12:56

but it should work...

<@james:fedora.im>

19:13:03

Ahh, I wondered if our routing was special

<@nirik:matrix.scrye.com>

19:13:44

it should just work normally tho

<@nirik:matrix.scrye.com>

19:13:58

unless that app is setting up it's own certs or something

<@james:fedora.im>

19:14:29

Ahh, fair enough ... I'll try to join the upstream slack then next, I think ... and see if they know anything.

<@james:fedora.im>

19:14:45

I think the app. does create it's own certs.

<@nirik:matrix.scrye.com>

19:15:31

yeah, then we will need to trust that somehow or get it to not. ;)

<@james:fedora.im>

19:15:43

No, nevermind ... there's space to add certs in, but they are blank

<@james:fedora.im>

19:16:47

says "passthrough" ... which I assume should work fine. I'll try pinging someone upstream

<@james:fedora.im>

19:17:18

Anyway, that was it for me.

<@nirik:matrix.scrye.com>

19:17:19

I think we need to tell our proxy httpd to trust that ca for that connection or something like that.

<@nirik:matrix.scrye.com>

19:17:27

sounds good.

<@phsmoura:fedora.im>

19:21:04

nirik: looked at nagios there is openqa with critical warning, but this is ack... is there something I can help with that or with another issue?

<@nirik:matrix.scrye.com>

19:26:43

that machine is down due to bad memory in it.

<@nirik:matrix.scrye.com>

19:27:10

and we are getting rid of it soon, so replacing the memory isn't probibly worth it.

<@nirik:matrix.scrye.com>

19:27:29

but good catch for looking at those alerts. ;)

<@nirik:matrix.scrye.com>

19:28:32

probibly we should just remove those 2 from ansible, but we are in freeze now, so probibly just wait until after.

<@phsmoura:fedora.im>

19:29:52

ok, I can do tha after freeze if there isnt anyone assigned to it

<@nirik:matrix.scrye.com>

19:30:12

sure.

<@phsmoura:fedora.im>

19:30:49

ok then, lets go back

<@phsmoura:fedora.im>

19:30:53

thanks everyone

<@phsmoura:fedora.im>

19:31:02

!endmeeting