18:00:09 <nirik> #startmeeting Fedora Infrastructure Ops Daily Standup Meeting
18:00:09 <zodbot> Meeting started Tue Jul 28 18:00:09 2020 UTC.
18:00:09 <zodbot> This meeting is logged and archived in a public location.
18:00:09 <zodbot> The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:09 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:09 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
18:00:09 <nirik> #chair mboddu nirik smooge pingou
18:00:09 <nirik> #meetingname fedora_infrastructure_ops_daily_standup_meeting
18:00:09 <zodbot> Current chairs: mboddu nirik pingou smooge
18:00:09 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
18:00:09 <nirik> #info meeting is 30 minutes MAX. At the end of 30, its stops
18:00:10 <nirik> #info agenda is at https://board.net/p/fedora-infra-daily
18:00:11 <nirik> #topic Tickets needing review
18:00:12 <nirik> #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1
18:00:17 <mboddu> Ahoy
18:00:52 <nirik> mboddu: want to edit tickets again? or want me to?
18:00:53 <mboddu> I can update the tickets
18:00:56 <nirik> cool.
18:01:02 <nirik> .ticket 9173
18:01:03 <zodbot> nirik: Issue #9173: Create group "dns-sig" in FAS - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9173
18:01:04 <mboddu> nirik: Haha ;)
18:01:18 <nirik> just needs doing.
18:01:42 <mboddu> med,med,groomed?
18:01:45 <nirik> med/med/groomed
18:01:46 <nirik> yeah
18:02:08 <nirik> .ticket 9174
18:02:09 <zodbot> nirik: Issue #9174: spam on arm mailing list - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9174
18:02:13 <fm-admin> 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 <fm-admin> pagure.issue.edit -- mohanboddu edited the priority fields of ticket fedora-infrastructure#9173 https://pagure.io/fedora-infrastructure/issue/9173
18:02:17 <nirik> I can just do this one now...
18:02:41 <mboddu> low,low,groomed?
18:03:16 <nirik> sure
18:03:18 <mboddu> nirik: Is there a document on how to solve it?
18:03:36 <fm-admin> 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 <fm-admin> pagure.issue.edit -- mohanboddu edited the priority fields of ticket fedora-infrastructure#9174 https://pagure.io/fedora-infrastructure/issue/9174
18:04:58 <nirik> 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 <nirik> .ticket 9175
18:05:10 <zodbot> 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 <nirik> needs looking at logs I guess.
18:05:28 <mboddu> " mark their fas account spam" can be done in the admin interface?
18:05:41 <nirik> the fas interface, yes.
18:05:49 <mboddu> Okay
18:06:05 <nirik> but they don't seem to have one here, just spammed via email.
18:06:18 <fm-admin> 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 <fm-admin> 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 <mboddu> On 9175, its random and its getting fixed automatically after couple of hours
18:07:21 <mboddu> 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 <nirik> 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 <podname>
18:09:32 <nirik> I'm not sure what could be causing this issue.
18:09:58 <nirik> thats the last of the infra needs-reviews.
18:10:03 <nirik> anything on releng side ?
18:10:16 <pgnd> 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 <mboddu> nirik: Yes, there is one
18:10:41 <nirik> indeed. software can smell it. ;)
18:11:28 <mboddu> .releng 9636
18:11:29 <zodbot> mboddu: Issue #9636: Mass rebuilds should be done with `koji --fail-fast` - releng - Pagure.io - https://pagure.io/releng/issue/9636
18:11:50 <mboddu> Seems like a useful idea and I made the PR for it (although we cant use it until next mass rebuild)
18:11:52 <nirik> we could do that...
18:12:08 <mboddu> low-trouble, high-gain, groomed?
18:12:27 <nirik> 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 <nirik> sure.
18:12:52 <nirik> 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 <mboddu> Right, but people will try to build again and can find the issue
18:13:15 <mboddu> With any specific arches
18:13:27 <mboddu> Well, we could try and remember :D
18:13:56 <nirik> I sometimes have trouble remembering for 6 days... less 6 months... but sure. ;)
18:14:00 <mboddu> (who am I kidding here) :D
18:14:18 <mboddu> Anyway, thats all I got
18:14:37 <nirik> cool.
18:14:43 <nirik> 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 <mikem> nirik, sure, maybe Thursday afternoon?
18:16:28 <nirik> mikem: sure!
18:16:42 <nirik> #endmeeting