<@phsmoura:fedora.im>
19:00:40
!startmeeting Fedora Infrastructure Ops Daily Standup Meeting
<@meetbot:fedora.im>
19:00:40
Meeting started at 2024-03-13 19:00:40 UTC
<@meetbot:fedora.im>
19:00:41
The Meeting name is 'Fedora Infrastructure Ops Daily Standup Meeting'
<@phsmoura:fedora.im>
19:00:51
!chair nirik smooge phsmoura
<@nirik:matrix.scrye.com>
19:00:56
morning.
<@phsmoura:fedora.im>
19:01:02
!meetingname fedora_infrastructure_ops_daily_standup_meeting
<@leo:fedora.im>
19:01:18
!hi
<@zodbot:fedora.im>
19:01:19
Leo Puvilland (leo) - he / him / his
<@phsmoura:fedora.im>
19:01:43
!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!
<@phsmoura:fedora.im>
19:01:46
hello
<@nirik:matrix.scrye.com>
19:02:10
Hows things?
<@jnsamyak:matrix.org>
19:02:50
0/
<@phsmoura:fedora.im>
19:03:04
busy days. lots to do
<@nirik:matrix.scrye.com>
19:03:29
never a dull moment. ;)
<@leo:fedora.im>
19:03:45
indeed
<@phsmoura:fedora.im>
19:04:09
!topic Tickets needing review
<@phsmoura:fedora.im>
19:04:21
!info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1
<@phsmoura:fedora.im>
19:04:47
!ticket 11834
<@zodbot:fedora.im>
19:04:48
**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
<@nirik:matrix.scrye.com>
19:04:57
low low ops, assign to me.
<@nirik:matrix.scrye.com>
19:05:06
easy enough to do, just need to go do it.
<@phsmoura:fedora.im>
19:05:35
done
<@phsmoura:fedora.im>
19:05:48
!ticket 11835
<@zodbot:fedora.im>
19:05:48
**fedora-infrastructure #11835** (https://pagure.io/fedora-infrastructure/issue/11835):**burninate spammer**
● **Opened:** an hour ago by mattdm
● **Last Updated:** Never
● **Assignee:** Not Assigned
<@nirik:matrix.scrye.com>
19:06:05
same here. Just needs doing
<@phsmoura:fedora.im>
19:06:06
low low ops?
<@nirik:matrix.scrye.com>
19:06:10
yep
<@phsmoura:fedora.im>
19:06:44
!info https://pagure.io/releng/issues?status=Open
<@phsmoura:fedora.im>
19:07:00
!releng 12010
<@zodbot:fedora.im>
19:07:01
**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
<@nirik:matrix.scrye.com>
19:07:41
med med I guess... I am not sure how to solve it off hand.
<@phsmoura:fedora.im>
19:09:05
!topic Planning, Upcoming work and Open floor
<@phsmoura:fedora.im>
19:09:15
anything for open floor?
<@leo:fedora.im>
19:09:20
nothing from me
<@nirik:matrix.scrye.com>
19:09:44
waiting for the next rc...
<@nirik:matrix.scrye.com>
19:10:05
and this meeting now is at my lunch time. oh well.
<@phsmoura:fedora.im>
19:11:55
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..
<@phsmoura:fedora.im>
19:12:10
any other ideas that could be done?
<@nirik:matrix.scrye.com>
19:12:32
weird. can you see in logs if the cron fires off?
<@nirik:matrix.scrye.com>
19:14:01
oh, i guess its a timer now
<@nirik:matrix.scrye.com>
19:14:36
systemctl status logrotate.timer ? (or .service)
<@phsmoura:fedora.im>
19:14:48
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
<@nirik:matrix.scrye.com>
19:15:34
might also add verbose or whatever to the .coonf file, then check it the next day
<@nirik:matrix.scrye.com>
19:15:40
might add more to logs
<@nirik:matrix.scrye.com>
19:16:44
it should be the same as all the others, so no idea why its broken\
<@phsmoura:fedora.im>
19:17:07
ok, I think I ran with -v but will double check
<@nirik:matrix.scrye.com>
19:18:32
well, if you add to the config it will run verbose for the timer job the next time it runs...
<@nirik:matrix.scrye.com>
19:18:44
that env might be different than just calling it.
<@phsmoura:fedora.im>
19:20:59
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...
<@phsmoura:fedora.im>
19:21:03
good idea
<@nirik:matrix.scrye.com>
19:21:33
well, to debug an outage/problem, sure...but be carefull not to break it
<@nirik:matrix.scrye.com>
19:22:07
nothing more from me off hand
<@nirik:matrix.scrye.com>
19:22:39
I guess technically that should be a freeze break...
<@nirik:matrix.scrye.com>
19:22:49
but... it seems pretty harmless
<@phsmoura:fedora.im>
19:23:42
dont have anything else as well
<@phsmoura:fedora.im>
19:24:20
thats all then.. thanks everyone :)
<@phsmoura:fedora.im>
19:24:40
!endmeeting