18:00:00 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:00 Meeting started Thu Aug 13 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:01 #chair mboddu nirik smooge pingou 18:00:01 Current chairs: mboddu nirik pingou 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:01:32 anyone ready for standup today? 18:01:41 #info red hat recharge day tomorrow, no standup 18:01:42 sorry was in a spreadsheet 18:01:43 I am here 18:01:54 #info nirik on PTO next week, will not be here. :) 18:01:56 * mboddu is here and everywhere 18:02:07 Enjoy your time off nirik 18:02:16 .ticket 9226 18:02:17 nirik: Issue #9226: Relocate Dogtag PKI's four public mailing lists from "www.redhat.com/mailman/listinfo" to "lists.fedoraproject.org" - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9226 18:02:19 I hope we wont see you next week :) 18:03:15 I'll be around, but doing fun projects. ;) 18:03:16 so I don't think we have done this with any new lists since we moved to mailman3 18:03:37 anyhow, on this one... yeah, we need to figure the process. perhaps abompard could help us. I think there's just a mailman3 import type thing... 18:03:40 I know it's possible 18:03:45 lists high-trouble medium-gain groomed 18:04:23 it can be moved to medium-trouble if we get misc/duck or abompard to help groom it more? 18:04:28 and ops? 18:04:36 (to go on the board) 18:04:51 and @ mention them in ticket to see if they know how to do it? 18:04:55 I haven't looked at the board.. what is it link 18:05:16 https://pagure.io/fedora-infrastructure/boards/ops 18:05:30 I used it for the outage tickets, we should try and use it more now 18:05:47 also, I'd like to see if we can change the 'groomed' tag to 'triaged' 18:06:01 do I click + and add it there or do I type ops in the tags ? 18:06:36 add the 'ops' tag and it will appear there. 18:06:43 then you drag it to whatever col you want. 18:06:45 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#9226: high-trouble, lists, and 2 others https://pagure.io/fedora-infrastructure/issue/9226 18:06:46 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#9226: "Relocate Dogtag PKI's four public mailing lists from "www.redhat.com/mailman/listinfo" to "lists.fedoraproject.org"" https://pagure.io/fedora-infrastructure/issue/9226#comment-671162 18:07:12 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#9226 https://pagure.io/fedora-infrastructure/issue/9226 18:07:30 got it.. it showed up where I wanted it for the time being 18:07:37 yep. :) 18:07:40 next... 18:07:48 .ticket 9231 18:07:49 nirik: Issue #9231: Improve monitoring for container registry - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9231 18:08:09 looks like nasirhm wants to work on this one. ;) 18:08:31 high gain, med trouble, ops? 18:08:55 nirik: I am, with the help from siddharthvipul . 18:08:55 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#9231: medium-gain, medium-trouble, and ops https://pagure.io/fedora-infrastructure/issue/9231 18:08:56 pagure.issue.assigned.added -- smooge assigned ticket fedora-infrastructure#9231 to nasirhm https://pagure.io/fedora-infrastructure/issue/9231 18:08:57 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#9231 https://pagure.io/fedora-infrastructure/issue/9231 18:09:17 nasirhm: great! 18:09:24 .ticket 9232 18:09:25 nirik: Issue #9232: Very pure resource for s390 build - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9232 18:09:42 so, we have been asked to collection more info about our pain with s390x. 18:09:50 I am not going ot put in my comments about SLE versus SLA 18:09:51 so, proposal: retitle this ticket: 18:10:08 s390x is in dire need 18:10:08 s390x builder issues 18:10:23 s390x is in a tail dive 18:10:40 and add a note that we can't make it better ourselves but would like to collect problems, so please add to it when you see them. 18:10:54 I can add that note. 18:10:56 pagure.issue.edit -- smooge edited the title fields of ticket fedora-infrastructure#9232 https://pagure.io/fedora-infrastructure/issue/9232 18:11:09 .ticket 9233 18:11:10 nirik: Issue #9233: Add COPR's sending IP to relay - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9233 18:11:29 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#9232: groomed, high-gain, and 3 others https://pagure.io/fedora-infrastructure/issue/9232 18:11:30 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#9232 https://pagure.io/fedora-infrastructure/issue/9232 18:11:45 pagure.issue.edit -- kevin edited the title fields of ticket fedora-infrastructure#9232 https://pagure.io/fedora-infrastructure/issue/9232 18:12:49 so bastion does not accept email except on the VPN or internal 18:13:03 it has a access file I thought? 18:13:53 oh wait.. I am thinking of something else 18:13:58 yeah it has an access file 18:13:59 well, it used to anyhow. 18:14:10 because we allowed relay from the cloud network I know... 18:16:06 anyhow, I am ok with just adding this for now, hopefully they will move to rdu2 for this later? 18:16:38 pagure.issue.tag.removed -- kevin removed the ops tags from ticket fedora-infrastructure#9232 https://pagure.io/fedora-infrastructure/issue/9232 18:16:39 pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#9232: "Ticket to collect issues and problems with s390x builders" https://pagure.io/fedora-infrastructure/issue/9232#comment-671168 18:17:04 med / med / ops ? 18:17:16 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#9233: medium-gain and medium-trouble https://pagure.io/fedora-infrastructure/issue/9233 18:17:17 pagure.issue.assigned.added -- smooge assigned ticket fedora-infrastructure#9233 to smooge https://pagure.io/fedora-infrastructure/issue/9233 18:17:18 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#9233 https://pagure.io/fedora-infrastructure/issue/9233 18:17:32 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#9233: ops https://pagure.io/fedora-infrastructure/issue/9233 18:17:39 .ticket 9234 18:17:40 nirik: Issue #9234: Bodhi gives unusual number of 500 errors today: NoSuchColumnError: "Could not locate column in row for column 'comments.id'" - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9234 18:17:56 I was seeing this in bodhi emails, but didn't realize users were seeing it. ;( 18:18:25 high gain / med trouble / groomed / dev and @cverna in it to look? 18:18:54 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#9234: bodhi, groomed, and 3 others https://pagure.io/fedora-infrastructure/issue/9234 18:18:55 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#9234 https://pagure.io/fedora-infrastructure/issue/9234 18:18:56 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#9234: "Bodhi gives unusual number of 500 errors today: NoSuchColumnError: "Could not locate column in row for column 'comments.id'"" https://pagure.io/fedora-infrastructure/issue/9234#comment-671172 18:19:17 I wonder if a database migration didn't happen or something. 18:19:24 Oh, and it's also affecting blockerbugs 18:19:35 Nice... 18:19:53 mboddu: have any releng tickets to go thru? 18:20:00 yes 18:20:15 .releng 9674 18:20:16 mboddu: Issue #9674: Create an ansible playbook to do the mass-branching - releng - Pagure.io - https://pagure.io/releng/issue/9674 18:20:47 Its a great idea, but might be complicated 18:20:53 high-trouble, high-gain, dev? 18:21:03 ack 18:21:21 yeah, I'd love to be able to just run a playbook for branching or beta freeze or whatever and have it do everything. 18:22:34 Agreed 18:22:38 .releng 9681 18:22:39 mboddu: Issue #9681: unblock tag f31 for package libvma #1826439 to build at koji - releng - Pagure.io - https://pagure.io/releng/issue/9681 18:22:57 Seems like something in the unretirement was not fixed properly or something 18:23:05 low-trouble, med gain, groomed? 18:23:13 sure. 18:23:20 needs so looking at 18:23:51 some 18:24:01 I think only rawhide was unblocked. 18:24:09 Yup 18:24:11 Probibly because they didn't specify at all. ;( 18:25:21 Yeah, I need to check it, but thats all I got 18:25:39 Oh FYI, I am working on the openh264 repos, finally.... 18:25:45 hurray 18:26:03 I'm hoping to work on some staging installs later today, but we will see. 18:26:29 I am not sure if I am able to get it done today (centos stream compose is kinda on fire), but I will see 18:26:33 anyone have anything else? blockers? prs? 18:27:19 And I am documenting the new process as I go 18:27:30 ^ openh264 18:27:39 good 18:27:42 As it changed with odcs 18:28:27 ok, if nothing else will close out. 18:28:31 #endmeeting