18:00:14 <nirik> #startmeeting Fedora Infrastructure Ops Daily Standup Meeting
18:00:14 <zodbot> Meeting started Wed Apr 29 18:00:14 2020 UTC.
18:00:14 <zodbot> This meeting is logged and archived in a public location.
18:00:14 <zodbot> The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:14 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:14 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
18:00:14 <nirik> #chair cverna mboddu nirik smooge
18:00:14 <nirik> #meetingname fedora_infrastructure_ops_daily_standup_meeting
18:00:14 <nirik> #info meeting is 30 minutes MAX. At the end of 30, its stops
18:00:14 <zodbot> Current chairs: cverna mboddu nirik smooge
18:00:14 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
18:00:15 <nirik> #info agenda is at https://board.net/p/fedora-infra-daily
18:00:17 <nirik> #topic Tickets needing review
18:00:18 <nirik> #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1
18:00:22 <smooge> cuts and pastes too late
18:00:25 <nirik> who all is around to stand up and be counted!
18:00:43 <nirik> .ticket 8872
18:00:44 <zodbot> nirik: Issue #8872: Fedora CI not working - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8872
18:00:46 <smooge> we who are about to die salute you Emperor Nirik
18:00:56 <adamw> nirik: i sent that change to ansible, looks like it's working
18:01:06 <adamw> oh sorry, didn't notice the meeting
18:01:07 <nirik> this looks like some dns issue in centos-ci... move to assigned and ask siddharthvipul to look
18:01:15 <nirik> adamw: no worries. thanks.
18:01:18 <smooge> will do so nirik
18:01:30 <nirik> .ticket 8873
18:01:31 <zodbot> nirik: Issue #8873: Create osbuild group - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8873
18:01:53 <fm-admin> pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8872 https://pagure.io/fedora-infrastructure/issue/8872
18:01:54 <fm-admin> pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#8872: "Fedora CI not working" https://pagure.io/fedora-infrastructure/issue/8872#comment-645082
18:02:26 <mboddu> Hello
18:02:36 <fm-admin> pagure.issue.edit -- kevin edited the close_status and status fields of ticket fedora-infrastructure#8873 https://pagure.io/fedora-infrastructure/issue/8873
18:02:37 <fm-admin> pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#8873: "Create osbuild group" https://pagure.io/fedora-infrastructure/issue/8873#comment-645084
18:02:48 <nirik> those are the two needs-reviews.
18:03:05 <mboddu> I have a couple of tickets
18:03:15 <mboddu> .releng 9424
18:03:16 <zodbot> mboddu: Issue #9424: Retire rpms/whois, rpms/perl-perl-Convert-ASN1, rpms/perl-LDAP in EPEL8 - releng - Pagure.io - https://pagure.io/releng/issue/9424
18:03:17 <nirik> mboddu: sure, fire away
18:03:20 <smooge> and I have a non-ticket
18:03:47 <mboddu> nirik: How is it done currently when a package is added to rhel and retired in epel?
18:03:59 <nirik> this is a fedpkg bug
18:04:02 <nirik> https://pagure.io/fedpkg/issue/395
18:04:33 <nirik> so, I don't know... downgrade fedpkg and do it?
18:04:56 <mboddu> I figured out the problem, its because, fedpkg is looking at bodhi api to figure out which one are active and which one aren't
18:04:58 <mboddu> I can fix it
18:05:03 <mboddu> Or send a PR to fedpkg
18:05:16 <nirik> yeah, they were trying to fix something else and broke epel retirements
18:05:40 <nirik> cool. you had another?
18:05:44 <mboddu> Yes, but iirc, there is also a cron job or something that does this as well, isn't it?
18:06:14 <mboddu> Or am I misremembering things?
18:06:22 <nirik> there's a fedmsg listener looking for it... and it does the blocks in koji.
18:06:37 <nirik> but it's triggered from the fedpkg retire
18:07:32 <mboddu> Ah okay
18:07:41 <mboddu> .releng 9423
18:07:42 <zodbot> mboddu: Issue #9423: Deploy ELN configuration to PROD environment - releng - Pagure.io - https://pagure.io/releng/issue/9423
18:08:10 <mboddu> I will work on it later today. It needs changes to bodhi and robosig configs
18:08:14 <nirik> we are out of freeze, so I'm fine with it landing in prod
18:08:16 <mboddu> I will deploy them
18:08:25 <mboddu> Okay, ^^ is what I wanted to check
18:08:29 <mboddu> Thats all I got
18:08:34 <nirik> cool. I can help with the autosign stuff
18:08:37 <mboddu> smooge: Go ahead
18:08:52 <mboddu> nirik: I think everything is there, just to deploy the config to prod
18:09:46 <nirik> ok
18:10:03 <smooge> ok I am trying to add a mirror in mirrormanager
18:10:35 <smooge> it is a server in RDU-CC and should be able to serve the CI and other items
18:11:02 <smooge> however I am guessing I didn't set it up correctly because it does not show up for ips on that subnet
18:11:24 * nirik looks
18:11:25 <smooge> I was wondering if someone could help me on it
18:11:28 <smooge> https://admin.fedoraproject.org/mirrormanager/host/2623
18:12:18 <misc> nirik: yup, I was looking at that rabiit hole :)
18:13:43 <nirik> smooge: looks ok... when did you add it? might take a few hours to sync out to mirrorlists
18:13:47 <smooge> I am not sure if I need to add more bandwidth or I don't have it mirroring correctly
18:13:52 <smooge> I added it yesterday morning
18:14:49 <nirik> yeah, it looks ok from a quick glance. Its not showing up in metalinks from those nets?
18:16:06 <smooge> checking what it gets
18:17:22 <smooge> goes to find a fedora host because rhel7 curl does not have --connect
18:17:26 <nirik> any other blockers, reviews needed, tickets to discuss?
18:17:30 <smooge> nope
18:18:29 <nirik> I have looked at the mailman-api issues, but haven't seen anything sticking out so far.
18:20:36 <nirik> ok, I guess we will close out then...
18:20:40 <nirik> #endmeeting