18:00:05 <nirik> #startmeeting Fedora Infrastructure Ops Daily Standup Meeting
18:00:05 <zodbot> Meeting started Mon Oct 18 18:00:05 2021 UTC.
18:00:05 <zodbot> This meeting is logged and archived in a public location.
18:00:05 <zodbot> The chair is nirik. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
18:00:05 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:05 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
18:00:06 <nirik> #chair mboddu nirik pingou mobrien nb
18:00:06 <zodbot> Current chairs: mboddu mobrien nb nirik pingou
18:00:06 <nirik> #meetingname fedora_infrastructure_ops_daily_standup_meeting
18:00:06 <nirik> #info meeting is 30 minutes MAX. At the end of 30, its stops
18:00:06 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
18:00:06 <nirik> #info agenda is at https://board.net/p/fedora-infra-daily
18:00:06 <nirik> #info reminder: speak up if you want to work on a ticket!
18:00:08 <nirik> #topic Tickets needing review
18:00:10 <nirik> #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1
18:01:09 <nirik> .ticket 10281
18:01:10 <zodbot> nirik: Issue #10281: Make the pkgdb/api/collections/ cacheable? - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10281
18:01:17 <nirik> low/low/ops
18:02:31 <eddiejennings> Seems like a "nice to have"
18:02:55 <nirik> yeah, might be pretty easy to do...
18:03:13 <nirik> that file does get downloaded by every user of gnome-software, which is... a lot
18:04:20 <nirik> thats it for infra. There's a few releng ones, but nothing too major... an unretire, a update url thing (which I think happens automatically) and a epel branching override request
18:04:31 <nirik> #topic Planning / Upcoming work
18:04:43 <nirik> #info friday is a Red Hat recharge day.
18:05:50 <eddiejennings> If only Red Hat had systems stuff I could do remotely from Georgia.  Can't relocate at this time :(
18:06:08 <nirik> I have on my plate: get rc if I can do anything to help there, macos notorize pain, greewave/waiverdb for stream and tickets/fires, etc
18:06:30 <nirik> there's often remote jobs. ;) take a look at jobs.redhat.com...
18:06:44 <eddiejennings> Yeah.  Haven't looked in a couple of weeks.  It's about time to look again.
18:06:44 <nirik> #topic Discussion items / AOB
18:06:56 <nirik> anything we should discuss today?
18:07:00 <eddiejennings> one moment
18:07:39 <eddiejennings> .ticket10276
18:07:49 <eddiejennings> .ticket 10276
18:07:50 <zodbot> eddiejennings: Issue #10276: script errors from cron on value01 on the meetings_by_team.sh script - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10276
18:07:55 <eddiejennings> So I started looking at this.
18:08:35 <eddiejennings> As far as the task itself, should I expect the task and the script it's running to be ultimately generated via Ansible?
18:08:51 <eddiejennings> or would this be something that's configured manually on the VM itself?
18:09:16 <nirik> it's 100% in ansible.
18:09:29 <nirik> the script is in there, setting it up in cron is in there. ;)
18:09:47 <nirik> I think you should have access to login to value01 if you want to look at files.
18:10:06 <eddiejennings> Ok.  Did a cursory look for it and didn't find anything, but I figure it probably *is* there just waiting for me to find it :D
18:10:30 <nirik> yeah, it's a weird one. It might be related to that the filesystem is NFS on /srv there
18:10:49 <eddiejennings> ah
18:12:14 <eddiejennings> That's it for me
18:13:34 <nirik> cool. ok, back to it then...
18:13:37 <nirik> #endmeeting