18:00:09 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:09 Meeting started Tue Jul 28 18:00:09 2020 UTC. 18:00:09 This meeting is logged and archived in a public location. 18:00:09 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:09 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:09 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:09 #chair mboddu nirik smooge pingou 18:00:09 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:00:09 Current chairs: mboddu nirik pingou smooge 18:00:09 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:09 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:10 #info agenda is at https://board.net/p/fedora-infra-daily 18:00:11 #topic Tickets needing review 18:00:12 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:00:17 Ahoy 18:00:52 mboddu: want to edit tickets again? or want me to? 18:00:53 I can update the tickets 18:00:56 cool. 18:01:02 .ticket 9173 18:01:03 nirik: Issue #9173: Create group "dns-sig" in FAS - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9173 18:01:04 nirik: Haha ;) 18:01:18 just needs doing. 18:01:42 med,med,groomed? 18:01:45 med/med/groomed 18:01:46 yeah 18:02:08 .ticket 9174 18:02:09 nirik: Issue #9174: spam on arm mailing list - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9174 18:02:13 pagure.issue.tag.added -- mohanboddu tagged ticket fedora-infrastructure#9173: groomed, medium-gain, and medium-trouble https://pagure.io/fedora-infrastructure/issue/9173 18:02:14 pagure.issue.edit -- mohanboddu edited the priority fields of ticket fedora-infrastructure#9173 https://pagure.io/fedora-infrastructure/issue/9173 18:02:17 I can just do this one now... 18:02:41 low,low,groomed? 18:03:16 sure 18:03:18 nirik: Is there a document on how to solve it? 18:03:36 pagure.issue.tag.added -- mohanboddu tagged ticket fedora-infrastructure#9174: groomed, low-trouble, and medium-gain https://pagure.io/fedora-infrastructure/issue/9174 18:03:37 pagure.issue.edit -- mohanboddu edited the priority fields of ticket fedora-infrastructure#9174 https://pagure.io/fedora-infrastructure/issue/9174 18:04:58 not sure, basically list admins can remove archive posts from the interface, then unsubscribe them, then mark their fas account spam if they have one 18:05:09 .ticket 9175 18:05:10 nirik: Issue #9175: random "500 - Internal Server Error" failures @ FAS login(s) - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9175 18:05:18 needs looking at logs I guess. 18:05:28 " mark their fas account spam" can be done in the admin interface? 18:05:41 the fas interface, yes. 18:05:49 Okay 18:06:05 but they don't seem to have one here, just spammed via email. 18:06:18 pagure.issue.edit -- kevin edited the close_status and status fields of ticket fedora-infrastructure#9174 https://pagure.io/fedora-infrastructure/issue/9174 18:06:19 pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#9174: "spam on arm mailing list" https://pagure.io/fedora-infrastructure/issue/9174#comment-667812 18:06:30 On 9175, its random and its getting fixed automatically after couple of hours 18:07:21 pgnd pinged me about it during oncall, but I dont know how to fix it or where to look at to start with 18:09:05 well, ipsilon runs in openshift... you can go to os-master01 and oc project ipsilon and oc get pods and look at the pod logs via oc logs 18:09:32 I'm not sure what could be causing this issue. 18:09:58 thats the last of the infra needs-reviews. 18:10:03 anything on releng side ? 18:10:16 nirik: mboddu I sure as heck can't realiably reproduce it on demand :-/ seems the _best_ bet for getting it to misbehave is _needing_ to get some work done. which ain't helpful ... 18:10:39 nirik: Yes, there is one 18:10:41 indeed. software can smell it. ;) 18:11:28 .releng 9636 18:11:29 mboddu: Issue #9636: Mass rebuilds should be done with `koji --fail-fast` - releng - Pagure.io - https://pagure.io/releng/issue/9636 18:11:50 Seems like a useful idea and I made the PR for it (although we cant use it until next mass rebuild) 18:11:52 we could do that... 18:12:08 low-trouble, high-gain, groomed? 18:12:27 in some cases it might hide a problem on arches that didn't get a chance to finish, but usually people just do new scratch builds anyhow to debug things. 18:12:30 sure. 18:12:52 if we do do it, we should note it in the next mass rebuild email (but not sure how to remind ourselves) 18:12:57 Right, but people will try to build again and can find the issue 18:13:15 With any specific arches 18:13:27 Well, we could try and remember :D 18:13:56 I sometimes have trouble remembering for 6 days... less 6 months... but sure. ;) 18:14:00 (who am I kidding here) :D 18:14:18 Anyway, thats all I got 18:14:37 cool. 18:14:43 if nothing else will close out in a min 18:14:49 * pgnd marvels: 6 whole days! ah, the blessings of youth ... 18:15:40 nirik, sure, maybe Thursday afternoon? 18:16:28 mikem: sure! 18:16:42 #endmeeting