19:02:38 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 19:02:38 Meeting started Wed Feb 5 19:02:38 2020 UTC. 19:02:38 This meeting is logged and archived in a public location. 19:02:38 The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:02:38 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:02:38 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 19:02:38 #chair smooge nirik relrod cverna 19:02:38 #info meeting is 30 minutes MAX. At the end of 30, its stops 19:02:38 #info agenda is at https://board.net/p/fedora-infra-daily 19:02:38 Current chairs: cverna nirik relrod smooge 19:02:38 #topic Tickets needing review 19:02:39 #info https://pagure.io/fedora-infrastructure/issues 19:02:49 good morning 19:03:06 https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 19:05:06 .ticket 8615 19:05:06 smooge: Issue #8615: Retire keys.fedoraproject.org 2020-02-07 - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8615 19:05:24 This is in progress. I have sent an email to the mailing lsits and taken over ticket. 19:05:33 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8615 https://pagure.io/fedora-infrastructure/issue/8615 19:05:55 pagure.issue.assigned.added -- smooge assigned ticket fedora-infrastructure#8617 to smooge https://pagure.io/fedora-infrastructure/issue/8617 19:06:07 .ticket 8617 19:06:08 smooge: Issue #8617: Rack, stack, and install new retrace server - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8617 19:06:20 ok, here now 19:06:22 .ticket 8617 19:06:23 nirik: Issue #8617: Rack, stack, and install new retrace server - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8617 19:06:24 huh, why does zodbot hate me. ;) 19:06:26 anyhow, we have the new hardware? 19:06:34 The system has been racked. it just needs to start doing the opendcim changes 19:06:47 ok 19:06:47 nirik, we have it for the retrace box. 19:06:48 pagure.issue.comment.added -- lucarval commented on ticket fedora-infrastructure#8248: "MTS is now running in prod in dry_run mode" https://pagure.io/fedora-infrastructure/issue/8248#comment-624602 19:06:55 the copr boxes arrive next week 19:07:13 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8617 https://pagure.io/fedora-infrastructure/issue/8617 19:07:20 that ordering got sorted? and they are going to phx2? 19:07:30 yep 19:07:41 lots o emails 19:07:48 ok, that answers the question I sent you in email then 19:08:01 .ticket 8620 19:08:02 nirik: Issue #8620: Access requested - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8620 19:08:05 and a long spread sheet I am now trakcking 19:09:17 so, I can do this now... we don't actually have a team for that project/app tho 19:09:51 i have no knowledge of what is needed for htis so I was going to ask you 19:09:54 relrod: you around? 19:10:18 looks like there's a authdev team, but not sure thats where we want to add them... 19:11:02 * cverna around 19:11:26 It may be authdev, but that might be broader... 19:11:44 looking at the people already in the authdev it looks like people working on AAA 19:11:58 yeah, and it has the right repos... 19:12:00 but yeah we can ask relrod to ack :) 19:12:16 just wanted to make sure so we don't add to a group that has access to a bunch of security related things. 19:12:33 proposal: ask relrod to ack in ticket and add them if thats the right group 19:13:01 .ticket 8621 19:13:02 nirik: Issue #8621: XML parser error when building two flatpak containers - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8621 19:13:26 cverna: you were gonna look at this one? might move it to waiting on asignee? 19:13:58 Yes 19:14:08 pagure.issue.edit -- kevin edited the priority fields of ticket fedora-infrastructure#8620 https://pagure.io/fedora-infrastructure/issue/8620 19:14:09 pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#8620: "Access requested" https://pagure.io/fedora-infrastructure/issue/8620#comment-624604 19:14:15 I have assigned it to myself but forgot to update the status 19:14:24 easy to do 19:14:25 would be nice if that could be automated :) 19:14:39 pagure.issue.edit -- cverna edited the priority fields of ticket fedora-infrastructure#8621 https://pagure.io/fedora-infrastructure/issue/8621 19:14:45 ok, thats all the needs review. 19:14:45 done 19:14:51 any other ones to discuss today? 19:15:06 so I have some old ones 19:15:10 I pinged, updated quite a few tickets this morning 19:15:24 go on smooge 19:15:34 cverna: I saw. thanks for that. ;) 19:15:39 .ticket 5887 19:15:40 smooge: Issue #5887: Log spew messages from /var/log/merged/messages.log - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/5887 19:16:02 so, this was orig a ticket to give apprentices something to work on... but it never really panned out. 19:16:22 so I was going to close it as we will need to work out something different when we move to RHEL-8 19:16:47 right, epylog sadly will need replacement 19:17:05 yeah and the replacements are basically 10 systems to run elasticsearch 19:17:14 pagure.issue.edit -- smooge edited the close_status and status fields of ticket fedora-infrastructure#5887 https://pagure.io/fedora-infrastructure/issue/5887 19:17:28 and they all suck/are not as simple/good 19:17:36 .ticket 7115 19:17:37 smooge: Issue #7115: We need application monitoring against openshift routers - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/7115 19:18:25 so that needs the other apps added I think? 19:18:28 so I was going to unassign myself to this and let someone else start defining things to it 19:18:45 I don't want to give the impression I can work on it soon 19:18:50 sure, please do. 19:18:53 +1 19:19:01 pagure.issue.assigned.reset -- smooge reset the assignee of ticket fedora-infrastructure#7115 https://pagure.io/fedora-infrastructure/issue/7115 19:19:11 in the ideal world we would only be assigned to 1 ticket at a time 19:19:38 2 or 3 would be a good start :) 19:19:51 BTW, on log spew, here's the top 5 machines by log lines: 19:19:53 1674624 autosign01.stg.phx2.fedoraproject.org 19:19:53 676575 notifs-backend01.phx2.fedoraproject.org 19:19:53 375268 oci-registry01.phx2.fedoraproject.org 19:19:53 374878 oci-registry02.phx2.fedoraproject.org 19:19:54 278561 pagure01.vpn.fedoraproject.org 19:20:02 oof 19:20:10 I think autosign01.stg is still set to DEBUG level of spew 19:20:24 notifs has always been noisy 19:20:26 that is per day correct? or hour 19:20:38 and the registry logs every single access to the journal. 19:20:44 per day. 19:21:04 ok that makes it 24 times less ugly 19:21:17 still comically bad 19:21:21 anyhow. 19:21:23 can we put that in the ticket ? that might give an idea to where to look first ? happy to do it 19:21:41 cverna: we closed the ticket... :) 19:21:52 perhaps we could be more targeted? 19:21:53 ha ha then forget it :P 19:22:03 open a new one 'reduce log spew on autosign01.stg' ? 19:22:05 cverna if you want to do it then reopen 5887 19:22:11 or I can do that 19:22:15 or reopen,ywah 19:22:45 how bad is it ? is it worth to spend a lot of time on it ? 19:22:59 if not I would not bother too much 19:23:08 well, I am ok punting it now, since we are going to have to address it when we replace epylog 19:23:32 then let's move on :) 19:24:14 cverna, it is several gigabytes per day 19:24:27 any other tickets to look at in the last 5min? 19:24:31 we are currently only able to have about a month of data uncompressed 19:24:46 no the rest of my 30 tickets I am going to wait til later 19:25:00 #endmeeting