<@james:fedora.im>
20:02:41
!startmeeting Fedora Infrastructure Ops Daily Standup Meeting
<@meetbot:fedora.im>
20:02:42
Meeting started at 2025-03-04 20:02:41 UTC
<@meetbot:fedora.im>
20:02:43
The Meeting name is 'Fedora Infrastructure Ops Daily Standup Meeting'
<@james:fedora.im>
20:02:45
!chair nirik phsmoura james
<@james:fedora.im>
20:02:49
!meetingname fedora_infrastructure_ops_daily_standup_meeting
<@meetbot:fedora.im>
20:02:50
The Meeting Name is now fedora_infrastructure_ops_daily_standup_meeting
<@james:fedora.im>
20:02:53
!info meeting is 30 minutes MAX. At the end of 30, its stops
<@smilner:fedora.im>
20:02:55
!hi
<@james:fedora.im>
20:02:56
!info agenda is at https://board.net/p/fedora-infra-daily
<@zodbot:fedora.im>
20:02:56
None (smilner)
<@nirik:matrix.scrye.com>
20:02:58
moring to all.
<@james:fedora.im>
20:03:00
!info reminder: speak up if you want to work on a ticket!
<@james:fedora.im>
20:03:14
!topic Tickets needing review
<@james:fedora.im>
20:03:18
!info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1
<@james:fedora.im>
20:03:36
!ticket 12435
<@zodbot:fedora.im>
20:03:37
Issue querying Pagure: 403: FORBIDDEN
<@smilner:fedora.im>
20:03:59
12436?
<@james:fedora.im>
20:04:06
Closed => Wait for pagure to go away ;)
<@james:fedora.im>
20:04:21
No, it's marked as private
<@nirik:matrix.scrye.com>
20:04:26
thats a private ticket I think, we just skip those here.
<@james:fedora.im>
20:04:35
Ahh, fair enough
<@james:fedora.im>
20:04:43
!ticket 12436
<@zodbot:fedora.im>
20:04:43
● **Assignee:** Not Assigned
<@zodbot:fedora.im>
20:04:43
● **Opened:** 3 hours ago by mattia
<@zodbot:fedora.im>
20:04:43
<@zodbot:fedora.im>
20:04:43
**fedora-infrastructure #12436** (https://pagure.io/fedora-infrastructure/issue/12436):**Inactive provenpackagers for the F42 cycle**
<@zodbot:fedora.im>
20:04:43
● **Last Updated:** Never
<@nirik:matrix.scrye.com>
20:04:54
med gain, low trouble, ops?
<@nirik:matrix.scrye.com>
20:05:25
we usually wait a few days on these in case someone pops up at the last minute to say they are still around. ;)
<@james:fedora.im>
20:05:50
Sure. I know I can't do it anyway ;)
<@james:fedora.im>
20:06:09
Maybe just you and Fabian?
<@nirik:matrix.scrye.com>
20:06:30
yeah, needs accounts access. Should be sysadmin-main only...
<@nirik:matrix.scrye.com>
20:06:52
but it's super easy. Just ipa remove-account-from-group in a loop or whatever.
<@james:fedora.im>
20:07:09
!info https://pagure.io/releng/issues?status=Open
<@james:fedora.im>
20:07:22
So technically no new tickets, but...
<@james:fedora.im>
20:07:24
!releng 12595
<@zodbot:fedora.im>
20:07:25
**releng #12595** (https://pagure.io/releng/issue/12595):**Rawhide netinstall broken.**
<@zodbot:fedora.im>
20:07:25
<@zodbot:fedora.im>
20:07:25
● **Opened:** 2 weeks ago by eddy02
<@zodbot:fedora.im>
20:07:25
● **Last Updated:** a week ago
<@zodbot:fedora.im>
20:07:25
● **Assignee:** Not Assigned
<@james:fedora.im>
20:07:40
We never tagged this one ... med/med?
<@nirik:matrix.scrye.com>
20:08:06
I guess. It's still unclear to me if it's something with the infra or something in the contents...
<@smilner:fedora.im>
20:08:38
From my very quick scan it looks more like a distro or compose bug
<@nirik:matrix.scrye.com>
20:08:39
oh, although...
<@james:fedora.im>
20:08:39
Yeh, I'd lean heavily towards contents ... so we could close.
<@nirik:matrix.scrye.com>
20:09:13
I was not able to boot rawhide kernels here form rc3->rc4... but then it's been working again. Perhaps this was the same issue... and it will work for them now?
<@nirik:matrix.scrye.com>
20:09:36
we could ask them to retest with current?
<@smilner:fedora.im>
20:10:24
We could. But what can we do about it if they figure out the issue? Should this be a Fedora bug report?
<@nirik:matrix.scrye.com>
20:11:20
well, if it works now, it's fixed? but if it still doesn't... I don't know... yeah, should probibly be a bug, but against what?
<@james:fedora.im>
20:11:21
I made a comment
<@james:fedora.im>
20:11:44
And tagged it, so we won't see it again anyway ;)
<@nirik:matrix.scrye.com>
20:12:08
dracut perhaps, systemd perhaps... dunno. I guess we can see if it's still happening for them
<@smilner:fedora.im>
20:12:13
Not exactly sure either. Maybe anaconda? Dracut?
<@james:fedora.im>
20:12:23
!topic Planning, Upcoming work and Open floor
<@nirik:matrix.scrye.com>
20:12:34
!info nirik is out on PTO thursday and friday
<@nirik:matrix.scrye.com>
20:12:46
!info f42 go/nogo is on thursday
<@nirik:matrix.scrye.com>
20:13:19
I thought I would mention that https://pagure.io/fedora-infrastructure/issue/12427 continues to vex me... if anyone has cycles to look it over and see if they can see anything that would be great
<@james:fedora.im>
20:13:42
I did patch and a PR based on yesterday's nftable deployment ... so can try deploying to another koji builder today and it "should work perfectly". https://pagure.io/fedora-infra/ansible/pull-request/2497
<@nirik:matrix.scrye.com>
20:13:56
(sporadic for some small number of people ostree getting 502's....)
<@nirik:matrix.scrye.com>
20:14:12
cool! sounds good. Thanks for driving that forward.
<@nirik:matrix.scrye.com>
20:14:59
other random news: DC folks fully power cycled bvmhost-p09-03 and it's back up! Also, ordered a replacement drive for the drive it has thats wonky...
<@james:fedora.im>
20:15:10
Yeh, when I first saw the 502 thing I wondered if it was related to the koji s390 problems ... but that seems to have been solved by a kernel change.
<@nirik:matrix.scrye.com>
20:15:56
yeah, Its the same machines, so it could be related...
<@nirik:matrix.scrye.com>
20:16:33
¯\\\_(ツ)\_/¯ but it's basically that some of the things people are requesting don't exist. They are 404 on the kojipkgs end (which cloudfront returns as a 502)
<@nirik:matrix.scrye.com>
20:16:53
I don't know enough about how ostree requests things/repo is setup. ;(
<@james:fedora.im>
20:17:12
We could ping ostree people?
<@nirik:matrix.scrye.com>
20:17:21
Bad disk on bvmhost-p09-03 has last error at: Error 2474 occurred at disk power-on lifetime: 51455 hours (2143 days + 23 hours)
<@smilner:fedora.im>
20:17:25
James Antill: they opened the issue
<@nirik:matrix.scrye.com>
20:17:34
I did ping a bunch of people in the ticket. ;(
<@smilner:fedora.im>
20:17:49
But they still may be able to help look through logs or have more ideas as to what could have happened.
<@nirik:matrix.scrye.com>
20:17:54
https://mirrors.fedoraproject.org/metalink?repo=fedora-cisco-openh264-$releasever&arch=$basearch
<@nirik:matrix.scrye.com>
20:17:56
oops
<@nirik:matrix.scrye.com>
20:18:05
https://mirrors.fedoraproject.org/metalink?repo=fedora-cisco-openh264-$releasever&arch=$basearch
<@nirik:matrix.scrye.com>
20:18:09
dammit paste
<@nirik:matrix.scrye.com>
20:18:21
https://pagure.io/fedora-infrastructure/issue/12427#comment-958728
<@james:fedora.im>
20:18:34
Might be worth asking if there's some kind of repochecker script they could create which we could run in nagios?
<@smilner:fedora.im>
20:18:54
Oddly enough I can hit the url they reference without a 502
<@smilner:fedora.im>
20:18:59
I get a valid dirtree
<@smilner:fedora.im>
20:19:50
I'll poke around a little nirik and then I'll see if I can't get someone from team CoreOS team to help review
<@nirik:matrix.scrye.com>
20:20:10
I think it's sporadic... but no idea why it would be.
<@nirik:matrix.scrye.com>
20:20:26
there's a lot of example urls there, but all different kinds...
<@nirik:matrix.scrye.com>
20:20:32
that would be great if you could.
<@nirik:matrix.scrye.com>
20:21:25
I don't have much else I don't think.
<@james:fedora.im>
20:22:05
Yeh, only other thing is booking 20m after nirik 's lunch to make sure the second PR/deployment is good.
<@nirik:matrix.scrye.com>
20:22:20
yep. I can do that. ;) can ping once I am back at it.
<@james:fedora.im>
20:22:27
Sounds good.
<@james:fedora.im>
20:22:38
And on that note...
<@james:fedora.im>
20:22:40
!endmeeting