2024-03-13 19:00:40 <@phsmoura:fedora.im> !startmeeting Fedora Infrastructure Ops Daily Standup Meeting
2024-03-13 19:00:40 <@meetbot:fedora.im> Meeting started at 2024-03-13 19:00:40 UTC
2024-03-13 19:00:41 <@meetbot:fedora.im> The Meeting name is 'Fedora Infrastructure Ops Daily Standup Meeting'
2024-03-13 19:00:51 <@phsmoura:fedora.im> !chair nirik smooge phsmoura
2024-03-13 19:00:56 <@nirik:matrix.scrye.com> morning.
2024-03-13 19:01:02 <@phsmoura:fedora.im> !meetingname fedora_infrastructure_ops_daily_standup_meeting
2024-03-13 19:01:18 <@leo:fedora.im> !hi
2024-03-13 19:01:19 <@zodbot:fedora.im> Leo Puvilland (leo) - he / him / his
2024-03-13 19:01:43 <@phsmoura:fedora.im> !info meeting is 30 minutes MAX. At the end of 30, its stops
!info agenda is at https://board.net/p/fedora-infra-daily
!info reminder: speak up if you want to work on a ticket!
2024-03-13 19:01:46 <@phsmoura:fedora.im> hello
2024-03-13 19:02:10 <@nirik:matrix.scrye.com> Hows things?
2024-03-13 19:02:50 <@jnsamyak:matrix.org> 0/
2024-03-13 19:03:04 <@phsmoura:fedora.im> busy days. lots to do
2024-03-13 19:03:29 <@nirik:matrix.scrye.com> never a dull moment. ;)
2024-03-13 19:03:45 <@leo:fedora.im> indeed
2024-03-13 19:04:09 <@phsmoura:fedora.im> !topic Tickets needing review
2024-03-13 19:04:21 <@phsmoura:fedora.im> !info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1
2024-03-13 19:04:47 <@phsmoura:fedora.im> !ticket 11834
2024-03-13 19:04:48 <@zodbot:fedora.im> **fedora-infrastructure #11834** (https://pagure.io/fedora-infrastructure/issue/11834):**Grant @jlebon:fedora.im & @siosm:matrix.org moderator access in #coreos:fedoraproject.org**

● **Opened:** an hour ago by siosm
● **Last Updated:** Never
● **Assignee:** Not Assigned
2024-03-13 19:04:57 <@nirik:matrix.scrye.com> low low ops, assign to me.
2024-03-13 19:05:06 <@nirik:matrix.scrye.com> easy enough to do, just need to go do it.
2024-03-13 19:05:35 <@phsmoura:fedora.im> done
2024-03-13 19:05:48 <@phsmoura:fedora.im> !ticket 11835
2024-03-13 19:05:48 <@zodbot:fedora.im> **fedora-infrastructure #11835** (https://pagure.io/fedora-infrastructure/issue/11835):**burninate spammer**

● **Opened:** an hour ago by mattdm
● **Last Updated:** Never
● **Assignee:** Not Assigned
2024-03-13 19:06:05 <@nirik:matrix.scrye.com> same here. Just needs doing
2024-03-13 19:06:06 <@phsmoura:fedora.im> low low ops?
2024-03-13 19:06:10 <@nirik:matrix.scrye.com> yep
2024-03-13 19:06:44 <@phsmoura:fedora.im> !info https://pagure.io/releng/issues?status=Open
2024-03-13 19:07:00 <@phsmoura:fedora.im> !releng 12010
2024-03-13 19:07:01 <@zodbot:fedora.im> **releng #12010** (https://pagure.io/releng/issue/12010):**Collision between nightly and candidate compose use of `/mnt/koji/compose/ostree/repo/` with same refs**

● **Opened:** 3 hours ago by adamwill
● **Last Updated:** 2 hours ago
● **Assignee:** Not Assigned
2024-03-13 19:07:41 <@nirik:matrix.scrye.com> med med I guess... I am not sure how to solve it off hand.
2024-03-13 19:09:05 <@phsmoura:fedora.im> !topic Planning, Upcoming work and Open floor
2024-03-13 19:09:15 <@phsmoura:fedora.im> anything for open floor?
2024-03-13 19:09:20 <@leo:fedora.im> nothing from me
2024-03-13 19:09:44 <@nirik:matrix.scrye.com> waiting for the next rc...
2024-03-13 19:10:05 <@nirik:matrix.scrye.com> and this meeting now is at my lunch time. oh well.
2024-03-13 19:11:55 <@phsmoura:fedora.im> I dont know what else to do to keep investigating logrotate.. checked config files, ran it to debug, checked disk space and the only error I saw was about its aliases.. seems it doesnt relate to logrotate..
2024-03-13 19:12:10 <@phsmoura:fedora.im> any other ideas that could be done?
2024-03-13 19:12:32 <@nirik:matrix.scrye.com> weird. can you see in logs if the cron fires off?
2024-03-13 19:14:01 <@nirik:matrix.scrye.com> oh, i guess its a timer now
2024-03-13 19:14:36 <@nirik:matrix.scrye.com> systemctl status logrotate.timer ? (or .service)
2024-03-13 19:14:48 <@phsmoura:fedora.im> can check, also checked root crontab and it only has a blocklist-update for ansible, but other services are being rotated.. anyway Ill check it
2024-03-13 19:15:34 <@nirik:matrix.scrye.com> might also add verbose or whatever to the .coonf file, then check it the next day
2024-03-13 19:15:40 <@nirik:matrix.scrye.com> might add more to logs
2024-03-13 19:16:44 <@nirik:matrix.scrye.com> it should be the same as all the others, so no idea why its broken\
2024-03-13 19:17:07 <@phsmoura:fedora.im> ok, I think I ran with -v but will double check
2024-03-13 19:18:32 <@nirik:matrix.scrye.com> well, if you add to the config it will run verbose for the timer job the next time it runs...
2024-03-13 19:18:44 <@nirik:matrix.scrye.com> that env might be different than just calling it.
2024-03-13 19:20:59 <@phsmoura:fedora.im> ah so is it ok to change those files to debug? I didnt do it to not mess with things in prod, maybe a bkp file to make it go back to previous state...
2024-03-13 19:21:03 <@phsmoura:fedora.im> good idea
2024-03-13 19:21:33 <@nirik:matrix.scrye.com> well, to debug an outage/problem, sure...but be carefull not to break it
2024-03-13 19:22:07 <@nirik:matrix.scrye.com> nothing more from me off hand
2024-03-13 19:22:39 <@nirik:matrix.scrye.com> I guess technically that should be a freeze break...
2024-03-13 19:22:49 <@nirik:matrix.scrye.com> but... it seems pretty harmless
2024-03-13 19:23:42 <@phsmoura:fedora.im> dont have anything else as well
2024-03-13 19:24:20 <@phsmoura:fedora.im> thats all then.. thanks everyone :)
2024-03-13 19:24:40 <@phsmoura:fedora.im> !endmeeting