18:00:00 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:00 Meeting started Mon Apr 20 18:00:00 2020 UTC. 18:00:00 This meeting is logged and archived in a public location. 18:00:00 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:00 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:00 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:00 #chair cverna mboddu nirik smooge 18:00:00 Current chairs: cverna mboddu nirik smooge 18:00:01 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:00:01 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:01 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:01 #info agenda is at https://board.net/p/fedora-infra-daily 18:00:02 #topic Tickets needing review 18:00:03 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:00:11 whos around to stand up? ;) 18:00:20 gekki 18:00:24 hello 18:00:25 .ticket 8837 18:00:26 nirik: Issue #8837: Give wwoods access to access_logs / - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8837 18:00:38 .hello mohanboddu 18:00:39 mboddu: mohanboddu 'Mohan Boddu' 18:00:47 pagure.issue.assigned.added -- smooge assigned ticket fedora-infrastructure#8837 to smooge https://pagure.io/fedora-infrastructure/issue/8837 18:00:59 so, not sure how best to do this/ 18:01:00 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8837 https://pagure.io/fedora-infrastructure/issue/8837 18:01:01 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#8837: "Give wwoods access to access_logs / " https://pagure.io/fedora-infrastructure/issue/8837#comment-643139 18:01:22 nirik, for that ticket it is add wwoods to sysadmin-analysis 18:01:23 I guess make a sysadmin-data and add that to data-analysis01 ? 18:01:33 ah, we already have a group? 18:01:39 yep.. for mattdm 18:01:50 cool. Can we just do it now? :) 18:01:59 .ticket 8840 18:02:00 nirik: Issue #8840: backup of copr fe DB by rdiff-backup - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8840 18:02:18 I can do this one. Will probibly need a freeze break since it's adding to inventory... 18:02:52 I am pretty sure I also asked about these since we were backing them up before, but they were going to backup somewhere else, but perhaps I am misremembering 18:03:12 nirik, was working on it when the meeting started 18:03:12 pagure.issue.tag.added -- kevin tagged ticket fedora-infrastructure#8840: high-gain and low-trouble https://pagure.io/fedora-infrastructure/issue/8840 18:03:13 pagure.issue.edit -- kevin edited the priority fields of ticket fedora-infrastructure#8840 https://pagure.io/fedora-infrastructure/issue/8840 18:03:27 .ticket 8843 18:03:28 nirik: Issue #8843: Add python-kerberos to the infra tags - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8843 18:03:41 mboddu: ^ can you do that one? or want me to? 18:04:09 nirik: I can do it 18:04:20 But nils was also looking into it 18:04:21 thanks. 18:04:27 I will check with nils 18:04:27 well, it needs a koji admin 18:04:35 Then I got it 18:04:37 * cverna waive 18:04:53 mboddu, I filed it :) 18:05:02 can we document how to do that ? 18:05:13 at least in the ticket :) 18:05:29 mboddu, it's a task this other one depends on which I can't do myself :) 18:05:40 nils: Oh, its for fixing the other ticket, got it, sorry, I didn't check the ticket per say 18:05:45 koji add-pkg epel7-infra packagename --owner owner 18:05:56 Yup 18:06:02 cverna, you want that in the howtos, right? 18:06:03 thanks :) 18:06:33 nils: would be great, happy to do it but I won't stop you from doing it :P 18:06:49 pagure.issue.edit -- mohanboddu edited the close_status and status fields of ticket fedora-infrastructure#8843 https://pagure.io/fedora-infrastructure/issue/8843 18:06:50 pagure.issue.comment.added -- mohanboddu commented on ticket fedora-infrastructure#8843: "Add python-kerberos to the infra tags" https://pagure.io/fedora-infrastructure/issue/8843#comment-643142 18:06:55 so thats all needs-review from infra, but there was a bunch filed and processed out of band... lets go over the ones that are still open? 18:06:57 cverna, not tonight :) if I remember tomorrow I can file a PR 18:07:01 nils, nirik : ^^ Done 18:07:06 .ticket 8835 18:07:07 nirik: Issue #8835: snapshot epel7 as a point release archive - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8835 18:07:07 mboddu++ thanks! 18:07:09 nils: Karma for mohanboddu changed to 27 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 18:07:24 nils: sure :) 18:07:37 smooge signed up for this one... are you sure you will have time smooge ? and/or perhaps we could script this ? 18:07:43 I got one from releng side 18:08:40 .ticket 8839 18:08:41 nirik: Issue #8839: can no longer contribute in Fedora's Taiga - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8839 18:08:49 pagure.issue.edit -- smooge edited the close_status and status fields of ticket fedora-infrastructure#8837 https://pagure.io/fedora-infrastructure/issue/8837 18:08:50 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#8837: "Give wwoods access to access_logs / " https://pagure.io/fedora-infrastructure/issue/8837#comment-643144 18:08:57 pagure.issue.comment.added -- nphilipp commented on ticket fedora-infrastructure#8824: "posts submitted to Fedora Users List getting lost." https://pagure.io/fedora-infrastructure/issue/8824#comment-643146 18:09:01 I can ask our taiga contacts about this one... I have exchanged emails with them in the past. 18:09:19 .ticket 8842 18:09:20 nirik: Issue #8842: Give the channel OP on #buildsys-build for "copr" pagure.io group - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8842 18:09:22 I tagged the person from tagai in the ticket 18:09:57 cverna: ok. I am not sure if thats the same one I have emailed with, but I can check. 18:10:06 nirik, I am in a stuck state until RDU is racked and networked and IAD2 is networked.. so i was going to do that snapshot after I get the move documented updated 18:10:12 nirik, re #8839 I've talked to Evolution and sent a mail to Taiga support for it 18:10:12 nb signed up on this one, but I think I am the only one in access on that channel. ;) 18:10:33 smooge: ok. fair 18:10:34 nirik: yeah I picked his name from the last taiga ticket we had :) 18:10:50 hi - you might remember that I asked a few weeks ago whether I can run the fedora packaging index scripts for https://apps.fedoraproject.org/packages/ (to solve bug report: https://github.com/fedora-infra/fedora-packages/issues/432 ) 18:10:53 nils: ok, we might coordinate so we don't all mail and ping them differently. ;) 18:11:02 * nils gets the feeling he's run roughshod over established procedures 18:11:25 no, it's fine, but just note it in the ticket or something so we can all be on the same page. 18:11:29 so far I found a few issues and fixed a bunch of potential and actuall uncaught exceptions 18:12:05 nirik, uhm, like in the comment in the ticket? :D 18:12:07 before I can create a merge request I would like to let the script run a few more times completely 18:12:28 chkr, can you wait until the current ticket is finished discussed 18:12:28 chkr: can you hang on a min... 18:12:55 cverna, is migonzalvar a Taiga support person whom we ping in such cases? 18:13:50 nils: ok, I misread then... 'forward on to our tiaga support people' wasn't clear as 'I am going to email our support people'... but thats likely my misreading 18:14:09 could have expressed myself clearer 18:14:15 my understanding is that they actually look at the taiga tag for things, but I am not sure how often 18:14:20 nils: that's the person that solved the last taiga issue we had, so a ping seemed like a good idea 18:14:38 for info https://pagure.io/fedora-infrastructure/issue/7827 18:14:43 but of course we have no way of knowing that they are still with the company/doing that, etc. 18:14:58 yeah :( 18:15:03 actually... 18:15:10 we can only ask and hope for an answer 18:15:28 Anyway, Taiga support knows about it. I'll log off for the day, see y'all tomorrow! 18:15:42 i.e. I sent this email, to be clear ;) 18:16:02 sure. I have an outstanding email with them about accounts actually. 18:16:11 nils: thanks have a good evening 18:16:14 So I should answer that, but this user isn't on that list, so it isn't the same thing 18:16:52 it's a list of users with local accounts instead of fas accounts, local accounts that never logged in and 3 users with both a local and a fas account 18:16:56 pagure.issue.comment.added -- nphilipp commented on ticket fedora-infrastructure#8839: "can no longer contribute in Fedora's Taiga" https://pagure.io/fedora-infrastructure/issue/8839#comment-643147 18:16:58 anyhow... 18:17:20 on the fedora-buildsys thing. I can grant nb privs 18:17:39 but I wonder if we couldn't just start pointing people to #fedora-copr or something more specific? 18:18:01 fedora-buildsys used to be the releng/plague channel, then koji, then... now it's just copr 18:18:22 I guess mock developers used to hang out there too. 18:18:29 I can ask that in the ticket I guess. 18:18:36 msuchy still does at times 18:18:48 just only during his 8-5 hours 18:18:58 mboddu: you had a releng ticket or two? 18:19:03 Yes 18:19:12 .releng 9408 18:19:13 mboddu: Issue #9408: Tag ghc into EPEL8 buildroot for ghc bootstrap - releng - Pagure.io - https://pagure.io/releng/issue/9408 18:19:25 I don't understand that ticket. 18:19:29 Me neither 18:19:41 Hence, I wanted to know if something is missing 18:19:48 if ghc is in rhel8 it cannot be in epel8... 18:19:59 except as a module I guess... 18:20:12 or is it a module in rhel? 18:20:57 I guess lets ask reporter ? 18:21:03 want me to? or you want to mboddu ? 18:21:26 I can check with him in the ticket 18:21:35 thanks. 18:21:46 But he says "ghc is available in the RHEL8 and Centos8 Buildroots" 18:21:46 chkr: ok, you wanted to try and get packages back working? 18:21:52 sorry guys, I did not realize that a meeting is on-going - my apologies... 18:21:56 nirik, yes ;-) 18:22:09 mboddu: yeah, and I don't see it, but might be in some module or steam we don't have? 18:22:16 chkr: no worries :) 18:22:19 before I can create a merge request I would like to let the script run a few more times completely - unfortunately that isn't fun from home - is there a remote system available close to the Fedora infrastructure like koji, pdc etc. which I can use to run them? any recent Fedora release should do (and to run the index scripts no privileges are needed)? 18:22:20 cverna: since you last touched packages... you're it. ;) 18:22:23 Okay 18:24:06 we could add chkr to the apprentice group, that should give him access to the stg instance to run the script ? 18:24:34 well, apprentice has no sudo... 18:25:18 we have a sysadmin-packages tho 18:25:19 chkr: do you need sudo ? or do you want to try your own script ? 18:25:25 to run them I don't need sudo - probably to get everything setup I would have to ask to get a few python packages installed 18:25:26 * cverna don't think the indexing requires sudo 18:26:14 it should need at least the same uid/gid no? 18:26:41 nirik: what happens with packages with the colo move ? I don't think it is in the minimal viable fedora ? 18:27:18 nirik: I believe chkr want to try a custom script so not the one used curently, but I might not have understood that correctly 18:27:20 it's just down until we readd enough capacity I guess. 18:27:54 it is actually this script: https://github.com/fedora-infra/fedora-packages/blob/master/bin/fcomm-index-packages but with bug fixes 18:28:10 packages in stg doesn't seem too happy 18:28:18 "Error loading the data for this page element" 18:28:54 I think we could then add chkr to the sysadmin-packages then, if everyone is happy with that 18:29:12 or I can coordinate with you chkr to try the changes 18:29:15 we should likely try and bring all the people together that are working on this... there's someone on list proposing replacing it with search/indexing and some stuff on top, msuchy partly wrote a re-write... 18:29:42 sure, you can just add them in stg for now? or both is probibly fine too. 18:29:52 yeah, I don't think packages in the current state will survive the move, I least that's my hope 18:29:59 if my bug-fixed version would work, bugz.fedoraproject.org would be back this week ;-) 18:30:18 one of the issues is, that all rpm packages refer to it... 18:31:22 https://github.com/fedora-infra/fedora-packages/issues/432 18:31:39 chkr: so I think the best thing is to open a PR, then we can try to deploy that to staging make the tweaks needed to the PR if needed 18:32:15 cverna, I would - but before opening the PR I need any kind of remote system running Fedora to let it finalize a complete run ;-) 18:32:20 at home, I can only do it partially 18:32:20 chkr: then deploy to prod, but that prod will go offline for a bit ( a few weeks, months) 18:32:38 PR where? ;) 18:32:47 you mean post a patch to the list I guess. ;) 18:33:02 nirik: no on github 18:33:08 for indexing, nothing special is required - to test the results, I can copy the index data back to my system and run fedora-packages in a container 18:33:25 oh, that mirror. ok. 18:33:29 but I can't use up that amount of traffic to generate the index ;-) 18:33:32 chkr: in the infra too it often fails mid way ( all threads dies) :( 18:33:51 cverna, I know ;-) that's what the bug fixes are for 18:34:05 I found lots of uncaught exceptions - it should be much more stable now 18:34:09 we can close the meeting and continue the discussion :) 18:34:23 anyhow, fi-apprentice should get you access or sysadmin-packages sudo if you want to try it out more in stg. 18:34:35 I don't think stg can get any worse, so happy to just update it. 18:34:41 :) 18:34:48 ok, any other tickets or blockers or whatever to discuss? 18:35:05 ok, thanks everyone. 18:35:08 #endmeeting