18:00:57 <smooge> #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:57 <zodbot> Meeting started Mon Mar 16 18:00:57 2020 UTC. 18:00:57 <zodbot> This meeting is logged and archived in a public location. 18:00:57 <zodbot> The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:57 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:57 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:57 <smooge> #chair cverna mboddu nirik smooge 18:00:57 <smooge> #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:57 <zodbot> Current chairs: cverna mboddu nirik smooge 18:00:57 <smooge> #info agenda is at https://board.net/p/fedora-infra-daily 18:00:58 <smooge> #topic Tickets needing review 18:00:59 <smooge> #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:01:08 <nirik> morning 18:01:23 <nirik> .ticket 8749 18:01:24 <zodbot> nirik: Issue #8749: Setup EPEL8 in stg to use CentOS Devel repo - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8749 18:01:27 <cverna> hello :) 18:01:46 <nirik> needs mirroring it, then enabling it... so move to waiting for asignee I guess 18:02:01 <nirik> .ticket 8750 18:02:04 <zodbot> nirik: Issue #8750: VMs don't boot correctly on openqa-aarch64-02.qa and we don't know why - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8750 18:02:23 <smooge> ok so back to mirroring it 18:02:24 <nirik> not sure what to do here. I guess have another set of eyes look and see if we can see anything he missed? 18:03:12 <fm-admin> pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#8749: koji and medium-gain https://pagure.io/fedora-infrastructure/issue/8749 18:03:13 <fm-admin> pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8749 https://pagure.io/fedora-infrastructure/issue/8749 18:03:30 <smooge> nirik, I spent friday trying to figure out what the problem on that box is 18:03:33 <nirik> I guess we could try a virt-install on it and see if it fails the same way? 18:04:09 <smooge> it is identical to the others but it acts like the CPU doesn't have the bits to do virtual machines 18:04:24 <smooge> that was my last idea also 18:04:46 <nirik> weird. yeah, dunno. You want me to try and look? or you want to poke at it some more? 18:05:03 <smooge> I can poke at it now I am done being account manager for the day 18:05:17 <smooge> well I think I am 18:05:39 <nirik> odd that it was also working for a while and then broke... 18:05:44 <fm-admin> pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#8750: hardware https://pagure.io/fedora-infrastructure/issue/8750 18:05:45 <fm-admin> pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8750 https://pagure.io/fedora-infrastructure/issue/8750 18:05:56 <nirik> ok, other tickets we want to discuss? 18:06:05 <cverna> I have couple of bz 18:06:12 <cverna> https://bugzilla.redhat.com/show_bug.cgi?id=1739529 18:06:21 <cverna> and https://bugzilla.redhat.com/show_bug.cgi?id=1738095 18:06:30 * nirik clicks 18:06:34 <cverna> these 2 packages have been orphaned and retired 18:06:53 <cverna> I don't think we have any dependencies on it, so I guess we could just close 18:07:01 <smooge> and I just checked and the cpu's say htey have the same flags also 18:07:15 <nirik> +1 to close all/any bugs on those... 18:08:06 <cverna> ok will do, I ll try to look at the others and send a email to the infra list to see if we find people willing to help 18:08:13 <nirik> cool. 18:08:41 <cverna> that's all from him 18:08:55 <nirik> so I wonder, do we want to start trying to triage new releng tickets here too... since we usually have more time now? 18:09:03 * mboddu is here 18:09:14 <cverna> +1 for releng 18:09:50 <nirik> the only one in the last 24 hours is really a infra one anyhow... 18:09:56 <nirik> .releng 9328 18:09:57 <zodbot> nirik: Issue #9328: Cannot ssh to aarch64 test machines - releng - Pagure.io - https://pagure.io/releng/issue/9328 18:10:03 <mboddu> nirik: Haha, I was about to say that :) 18:10:59 <nirik> this is likely a authconfig/pam doom... the machines are up 18:11:32 <nirik> I can try and fix it 18:11:45 <nirik> .ticket 9327 18:11:51 <zodbot> nirik: An error has occurred and has been logged. Check the logs for more information. 18:11:55 <nirik> .releng 9327 18:11:56 <zodbot> nirik: Issue #9327: Please add tags, target, and Bodhi release for f32-flatpak - releng - Pagure.io - https://pagure.io/releng/issue/9327 18:12:30 <mboddu> nirik: I will take it 18:12:45 <nirik> cool. 18:12:48 <nirik> .ticket 9316 18:12:53 <zodbot> nirik: An error has occurred and has been logged. Check the logs for more information. 18:12:57 <nirik> can just get closed? we can't retire there... 18:13:24 <mboddu> nirik: Any other options? 18:13:27 <cverna> .releng 9316 18:13:28 <zodbot> cverna: Issue #9316: Please retire fontpackages in F31 - releng - Pagure.io - https://pagure.io/releng/issue/9316 18:13:37 <nirik> .releng 9312 18:13:38 <zodbot> nirik: Issue #9312: Please send openh264 2.1.0 builds to Cisco - releng - Pagure.io - https://pagure.io/releng/issue/9312 18:13:45 <nirik> this one I think is done... ^ 18:13:51 <mboddu> nirik: I have to do it 18:13:52 <nirik> or not perhaps 18:13:57 <mboddu> Nope, its a newer release 18:14:24 <nirik> ok 18:14:37 <mboddu> Newer release of openh264 18:14:55 <nirik> so, releng gets a pile of unretire requests... is there any way to better automate it or get more people able to do them so it's spread out? 18:15:10 <mboddu> nirik: Did you guys talked about odcs box? 18:15:25 <nirik> no, not yet 18:16:11 <cverna> unretire policy involves some checks ? 18:16:17 <mboddu> nirik: We could automate it, we actually looked at it but the only thing stopping is verifying the re-review 18:16:40 <nirik> cverna: yeah, needs to check how long it was retired and check a re-review if it was more than X 18:17:22 <cverna> could make the case to FESCO to not verify the re-review ? 18:17:24 <nirik> and I guess it needs koji admin to unblock and pdc admin to reset the eol date 18:17:29 <cverna> could we * 18:17:37 <cverna> or find a way to check that 18:17:55 <nirik> you could try... I am not sure how well it would be received... 18:18:10 <cverna> haha :) 18:18:35 <mboddu> cverna: Exactly, you need to careful when unretiring the package 18:18:40 <cverna> we could actually automate the simple case ? 18:18:52 <mboddu> cverna: As in? 18:18:58 <cverna> ie the one that don't need the re-review ? 18:19:02 <nirik> also if it's unblocking it in some places you have to be carefull to make sure it's signed. ;( 18:19:28 <nirik> cverna: could we do a playbook? 18:19:49 <cverna> if it was retired for less than X week do you still need to check everything ? 18:19:52 <nirik> takes name, unblocks in koji, sets eol in pdc... it would need a pdc token tho 18:20:05 <cverna> nirik: yeah that could be a quick way to do that :) 18:20:30 <nirik> the same thing could be used for the other case, just after the person running it checked the re-review 18:20:50 <smooge> ok this sounds like it needs to be discussed in depth outside of the standup 18:20:56 <nirik> I guess it needs to know what branches to unretire. 18:21:07 <nirik> yeah, lets start a thread on it on ml? 18:21:16 <nirik> any other standing up items? 18:21:17 <mboddu> cverna: If its retired less than 8 weeks, then sure, but then it confuses people making them check and do different things based on eol 18:21:19 <cverna> smooge: agreed 18:21:31 <cverna> +1 to mailing list discussion :) 18:22:02 <smooge> I do no thave anything else. mboddu mentioned odcs? 18:22:08 <nirik> mboddu: on the odcs thing... can it wait until thursday? then I can just do it after freeze and not need a freeze break... 18:22:14 <cverna> mboddu: if the less than 8 weeks are processed automatically then you don't even know about them :) 18:22:42 <mboddu> nirik: Sure, not a problem, thanks 18:22:54 <nirik> cool. 18:23:00 * nirik makes a note to do that thursday 18:23:14 <smooge> ok thank you all for the day 18:23:23 <smooge> same bat-time/same bat channel tomorrow 18:23:28 <smooge> #endmeeting