18:00:27 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:27 Meeting started Mon Jul 6 18:00:27 2020 UTC. 18:00:27 This meeting is logged and archived in a public location. 18:00:27 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:27 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:27 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:27 #chair cverna mboddu nirik smooge 18:00:27 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:00:27 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:27 Current chairs: cverna mboddu nirik smooge 18:00:27 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:27 #info agenda is at https://board.net/p/fedora-infra-daily 18:00:29 #topic Tickets needing review 18:00:31 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:00:33 who all is around for standup? 18:00:43 Hello 18:00:44 I am here 18:01:01 .ticket 9109 18:01:04 nirik: Issue #9109: Default RHBZ assignee for nginx not synced with src.fpo - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9109 18:02:08 ... gets head out of ppc 18:02:21 so, this is known... there's nothing for us to do. I'd say close can't fix? 18:02:37 I mean we could remove them, but that ideally should be done by the main admin... 18:02:44 smooge: You got updating the tickets or do you want me to? 18:02:58 mboddu, could you?> 18:03:03 smooge: Sure 18:03:32 nirik: Lets ask the reporter to check with the main admin and close the ticket? 18:04:13 sure 18:05:13 .whoowns nginx 18:05:14 mboddu: owner: heffer; admin: jjh, jorton; commit: affix, asrob, luhliarik, tadej 18:05:38 .fasinfo heffer 18:05:39 smooge: User: heffer, Name: None, email: felix@kaechele.ca, Creation: 2008-07-04, IRC Nick: None, Timezone: None, Locale: None, GPG key ID: None, Status: active 18:05:42 smooge: Approved Groups: cla_fedora cla_done packager fedorabugs ambassadors cvsl10n cla_fpca l10n 18:06:56 pagure.issue.edit -- mohanboddu edited the close_status and status fields of ticket fedora-infrastructure#9109 https://pagure.io/fedora-infrastructure/issue/9109 18:06:57 pagure.issue.comment.added -- mohanboddu commented on ticket fedora-infrastructure#9109: "Default RHBZ assignee for nginx not synced with src.fpo" https://pagure.io/fedora-infrastructure/issue/9109#comment-663617 18:07:06 so can the main admin change if it isn't synced over? 18:07:30 they can remove the user that has no bugzilla account 18:07:34 which will let it sync 18:07:43 any admin can. 18:07:48 ah ok 18:08:26 the way the sync works is it gathers up all the info and tries to change things all to the way it's set... if that fails because a user has no account the entire update of that component fails. 18:08:30 pagure.issue.comment.edited -- mohanboddu edited a comment on ticket fedora-infrastructure#9109: "Default RHBZ assignee for nginx not synced with src.fpo" https://pagure.io/fedora-infrastructure/issue/9109#comment-663617 18:08:34 so nothing changes with it at all until it's fixed. 18:09:38 ok I dealt with the other non-assigned ticket 18:10:25 So, releng one's? 18:10:35 yep 18:10:54 yep 18:10:58 pagure.issue.edit -- nicklevinson edited the close_status and status fields of ticket fedora-infrastructure#9098 https://pagure.io/fedora-infrastructure/issue/9098 18:10:59 pagure.issue.comment.added -- nicklevinson commented on ticket fedora-infrastructure#9098: "ask.fedoraproject.org login failure for my current account" https://pagure.io/fedora-infrastructure/issue/9098#comment-663619 18:11:07 .releng 9580 18:11:07 mboddu: Issue #9580: Fix EPEL8-CentOS-Devel repo - releng - Pagure.io - https://pagure.io/releng/issue/9580 18:11:18 smooge: Did you setup the repo?^ 18:11:43 I am working with CentOS on getting rsync access 18:11:51 Can you make the change or do you want me to? (I am not sure if there is any pre-req's that I need to do before the change) 18:12:01 the other parts of the repo may not exist as it gets started from scratch when a new release occurs 18:12:25 mboddu, at this point we do not have rsync access to get anything from the centos servers 18:12:36 so I don't know if there is anything in the repo or not 18:13:00 smooge: Okay 18:13:15 So, med,med,groomed? And you are already working with centos folks 18:14:16 yes please 18:14:30 sorry our internal dns to redhat seems broken again 18:16:37 Thanks smooge 18:16:41 .releng 9579 18:16:42 mboddu: Issue #9579: Misleading message returned by fedora-scm-request - releng - Pagure.io - https://pagure.io/releng/issue/9579 18:17:03 This just needs an update to fedscm-admin, low,low and groomed. 18:17:08 I will work on it when I get a chance 18:17:14 ack 18:17:39 .releng 9577 18:17:40 mboddu: Issue #9577: Fedora Media Writer 4.1.6 released - releng - Pagure.io - https://pagure.io/releng/issue/9577 18:17:56 nirik: So, I dont have access to mac box, its in the office 18:18:11 Can you take care of it? Sorry for giving you more work 18:18:13 ok. I know where the box mine is in is... 18:18:23 I can try and fire it up. 18:18:44 nirik: Patrick knows how to do the windows signing, do you know anything about it? 18:19:13 winodws? this is just mac I thought? 18:19:18 * nirik reads again 18:19:33 Nope, both windows and macos 18:20:06 ah, ok. well, we will have to figure that out... as I recall we have no cert on the windows side currently. But I could be wrong. 18:20:38 nirik: Yes, we dont as windows stopped allowing us to use non-physical keys 18:20:51 And Patrick was planning on getting one through RH 18:20:54 yeah. fun times. 18:21:21 I think that was put on hold for various reasons. 18:21:33 More fun... :) 18:22:06 I think we need to investgate. I can try and do that and update the ticket. 18:22:23 So, whats the plan here? Does anyone know the RH route? Or should we find our own way or ... ? 18:22:32 nirik: ack 18:22:38 mboddu, nirik, smooge: we did have a windows certificate via Digicert under name of RH. But that expired a few months ago, and I replied on the email thread that *I* didn't need a new cert, but that Kevin might want to get one if we need a new build 18:22:54 (Kevin was on CC) 18:23:06 High trouble, high gain, groomed 18:23:10 * mboddu waves at puiterwijk 18:23:12 neat. I'll look for the message... 18:23:19 So, nirik: just submit a request for a new cert via digicert, and they'll arrange it 18:23:21 * puiterwijk out again 18:23:25 it was likely during datacenter move time and I didn't have cycles 18:23:31 Nah, before 18:23:46 Well, I mean, probably during the preparations for it. So sure 18:23:53 yeah. 18:24:00 ok, thanks puiterwijk! 18:24:38 Thanks puiterwijk 18:25:35 nirik: Also, can you keep me in loop regarding this? I wonder if we can get two certs? 18:25:44 Just to avoid single point of failure 18:26:42 I'll look. I would think we could use 1 cert 18:26:50 but will see what requirements it has 18:27:01 nirik: Cool, thanks 18:27:15 .releng 9574 18:27:16 mboddu: Issue #9574: f33-java11 sidetag - releng - Pagure.io - https://pagure.io/releng/issue/9574 18:27:20 This just needs doing 18:27:27 low,low,groomed 18:27:53 Actually, low trouble, medium gain 18:28:25 .releng 9573 18:28:26 mboddu: Issue #9573: Please help delete 'devel' branch of rpms / kexec-tools - releng - Pagure.io - https://pagure.io/releng/issue/9573 18:28:31 This also just needs doing 18:28:42 medium trouble, low gain, groomed 18:28:57 as long as it passes the check script, sure. 18:29:04 Yes, true 18:29:07 Thats all I got 18:29:54 * nirik has nothing more 18:30:20 smooge: anything? 18:30:32 sorry in another meeting now 18:30:34 so nothing 18:31:05 ok, thanks for coming everyone 18:31:09 #endmeeting