14:01:08 <dalley> #startmeeting Pulp Triage 2021-05-17 14:01:08 <dalley> #info dalley has joined triage 14:01:08 <dalley> !start 14:01:08 <pulpbot> Meeting started Mon May 17 14:01:08 2021 UTC. The chair is dalley. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:08 <pulpbot> Useful Commands: #action #agreed #help #info #idea #link #topic. 14:01:08 <pulpbot> The meeting name has been set to 'pulp_triage_2021-05-17' 14:01:08 <pulpbot> dalley: dalley has joined triage 14:01:30 <daviddavis> #info daviddavis has joined triage 14:01:30 <daviddavis> !here 14:01:30 <pulpbot> daviddavis: daviddavis has joined triage 14:02:17 <x9c4> #info x9c4 has joined triage 14:02:17 <x9c4> !here 14:02:17 <pulpbot> x9c4: x9c4 has joined triage 14:03:26 <dalley> do we need to discuss either of the two issues currently in POST? 14:04:35 <daviddavis> yea, I'd propose we hold 8386 until 3.14 and not merge the day before we releaes 14:05:47 <dalley> no objections to that 14:06:11 <ipanova> #info ipanova has joined triage 14:06:11 <ipanova> !here 14:06:11 <pulpbot> ipanova: ipanova has joined triage 14:06:13 <x9c4> +1 14:06:17 <daviddavis> cool, I'll set it to 3.14 then 14:06:36 <ipanova> +1 to that 14:06:53 <x9c4> The other one is in post but not assigned to anyone. 14:07:13 <dalley> gerrod is working on it and there's a PR, so i'll mark assigned 14:07:21 <daviddavis> +1 14:07:30 <ipanova> it is a fairly small pr, should not a problem to review/merge 14:07:36 <ipanova> be* 14:09:43 <dalley> +1 14:10:30 <dalley> I kind of want to discuss some of the tasking system issues that have been reported 14:11:20 <ipanova> do you have a link handy? 14:11:49 <dalley> I'm just going to look through and paste them separately 14:11:53 <dalley> for one: https://pulp.plan.io/issues/8750 14:12:00 <dalley> this should be moved to pulpcore I believe 14:14:17 <ipanova> based on traceback, yes 14:14:29 <dalley> and a second one, https://pulp.plan.io/issues/8637 14:14:40 <x9c4> It's complaining about a deadlock with rpm_package_pkgId_key 14:15:27 <dalley> I know wibbit ran into that one too, and there was definitely at least one other person but I forget who 14:16:55 <dalley> what I want to ask is basically - should we release without fixes to these bugs? they are a real pain to clean up after 14:17:18 <ipanova> dalley: so #8637 is not that theoretical anymore like stated in the desc? 14:17:19 <dalley> they aren't currently targeted for 3.13 14:18:29 <dalley> ipanova, it appears so. ggainey had to walk wibbit through manually deleting reserved resources 14:19:48 <ipanova> dalley: both of the issues do seem to be there for quite some time, i'd probably get 3.13 out of the door without blocking it but would target for 3.14 14:20:18 <daviddavis> or even a z-stream release 14:20:33 <daviddavis> if needed 14:20:47 <ipanova> daviddavis: or, yes 14:20:56 <dalley> I'm not against a z-stream 14:21:53 <ipanova> dalley: do you want to put these 2 issues on the sprint? 14:22:21 <dalley> one already is, I can add the other one 14:22:22 <ipanova> actually one is on the sprint already 14:23:26 <ipanova> is there anything else on the list to be discussed for the 3.13 release? 14:24:05 <dalley> no 14:24:18 <dalley> regarding those two issues, are there any objections to also bumping the priority/severity? 14:24:35 <wibbit1> I've not yet cleaned up my mess, it doesn't appear to cause issues with normal working, and I've not yet had a chance to do it. 14:25:26 <wibbit1> I did some initial looking, at there appeared to be no reserved resources being held open, though the tasks are still waiting 14:26:07 <dalley> #endmeeting 14:26:07 <dalley> !end