15:30:40 #startmeeting Pulp Triage 2021-01-08 15:30:40 #info fao89 has joined triage 15:30:40 !start 15:30:40 Meeting started Fri Jan 8 15:30:40 2021 UTC. The chair is fao89. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:30:40 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:30:40 The meeting name has been set to 'pulp_triage_2021-01-08' 15:30:40 fao89: fao89 has joined triage 15:30:43 #info dkliban has joined triage 15:30:43 !here 15:30:43 dkliban: dkliban has joined triage 15:30:47 #info ppicka has joined triage 15:30:47 !here 15:30:47 ppicka: ppicka has joined triage 15:31:18 #info ggainey has joined triage 15:31:18 !here 15:31:18 ggainey: ggainey has joined triage 15:31:29 #info dalley has joined triage 15:31:29 !here 15:31:29 dalley: dalley has joined triage 15:31:56 #info daviddavis has joined triage 15:31:56 !here 15:31:56 daviddavis: daviddavis has joined triage 15:32:03 no items so far 15:32:10 should we start the triage? 15:32:31 let's do it 15:32:39 fao89: sure - let's not borrow trouble :) 15:32:52 !next 15:32:53 #topic https://pulp.plan.io/issues/8052 15:32:53 fao89: 5 issues left to triage: 8052, 8048, 8047, 8044, 7950 15:32:54 RM 8052 - pieta - NEW - Some repositories cannot be synchronized with error: Artifact() got an unexpected keyword argument 'sha' 15:32:55 https://pulp.plan.io/issues/8052 15:33:40 #idea Proposed for #8052: move to rpm project 15:33:40 !propose other move to rpm project 15:33:40 fao89: Proposed for #8052: move to rpm project 15:33:49 +1 15:34:02 +1 15:34:13 #agreed move to rpm project 15:34:13 !accept 15:34:13 fao89: Current proposal accepted: move to rpm project 15:34:13 #topic https://pulp.plan.io/issues/8048 15:34:14 fao89: 4 issues left to triage: 8048, 8047, 8044, 7950 15:34:15 RM 8048 - newswangerd - NEW - Object permissions endpoint breaks for objects with unknown viewsets 15:34:16 https://pulp.plan.io/issues/8048 15:36:17 hmm 15:36:18 skip for now until someone with rbac knowledge can weigh in? 15:36:35 i think we should accept and have someone dig into this 15:36:41 #info ttereshc has joined triage 15:36:41 !here 15:36:41 ttereshc: ttereshc has joined triage 15:36:43 it is not exactly rbac issue 15:36:46 #info x9c4 has joined triage 15:36:46 !here 15:36:46 x9c4: x9c4 has joined triage 15:36:59 I will take a look 15:37:07 #info ipanova has joined triage 15:37:07 !here 15:37:07 ipanova: ipanova has joined triage 15:37:25 x9c4: that would be great ... so let's add it to the sprint? 15:37:35 they don't use NamedModelViewset so their Namespace model doesn't have a viewset "attached" to it 15:38:18 I see 15:38:22 is this a pulpcore issue, or an ansible-plugin issue? 15:38:41 (I think we should add/investigate either way, just wondering if we want to move to the ansible project) 15:38:46 they could hit this without pulp_ansible so it's a pulpcore issue 15:38:48 kinda blur thing 15:38:51 ah kk 15:38:55 let's lv in core then 15:38:58 it's poossibly an issue with pulpcore ... or we close it as won't fix 15:39:08 or not a bug 15:39:09 gotcha 15:39:22 #idea Proposed for #8048: accept and add to sprint 15:39:22 !propose other accept and add to sprint 15:39:22 fao89: Proposed for #8048: accept and add to sprint 15:39:33 +1 15:39:42 or skip for investigation? 15:40:06 let's accept 15:40:16 #agreed accept and add to sprint 15:40:16 !accept 15:40:16 fao89: Current proposal accepted: accept and add to sprint 15:40:17 #topic https://pulp.plan.io/issues/8047 15:40:17 fao89: 3 issues left to triage: 8047, 8044, 7950 15:40:18 RM 8047 - fao89 - NEW - New artifact is downloaded even when we already have a content unit with the same identity 15:40:19 https://pulp.plan.io/issues/8047 15:41:10 this is another situation where it is in the middle of ansible and core 15:41:29 fun 15:41:50 so when pulpcore doesn't know how to differentiate signed x unsigned content, it end up download both artifacts 15:42:07 but only one is linked to ContentArtifact 15:42:18 so this seems like a pulp_ansible bug becuase there needs to be another uniqueness constraint on the content 15:42:32 if the checksum is different, i would think that the content is different 15:42:39 even if it is called the same thing 15:42:45 fao89: so what happens with the old aritfact, is it being replaced with the new one? 15:42:51 I agree. 15:42:59 it is not 15:43:10 no you get two artifacts on the same contnet unit I belive 15:43:12 dkliban: i agree 15:43:17 it keeps the old, and just downloads the new one for nothing 15:43:25 +1 to ansible bug 15:43:38 It is then still serving the unofficial one as official? 15:44:09 it serves the first synced 15:44:22 #idea Proposed for #8047: move to ansible project 15:44:22 !propose other move to ansible project 15:44:22 fao89: Proposed for #8047: move to ansible project 15:44:28 +1 15:44:30 +1 15:44:34 +1 15:44:35 #agreed move to ansible project 15:44:35 !accept 15:44:35 fao89: Current proposal accepted: move to ansible project 15:44:36 fao89: 2 issues left to triage: 8044, 7950 15:44:36 #topic https://pulp.plan.io/issues/8044 15:44:37 RM 8044 - ttereshc - ASSIGNED - no index for _last_updated on content models causes a fatal error when ordered result is queried 15:44:38 https://pulp.plan.io/issues/8044 15:44:50 accept and add - I'm prepping a PR for this today :) 15:44:56 pretty please :) 15:45:09 #idea Proposed for #8044: accept and add to sprint 15:45:09 !propose other accept and add to sprint 15:45:09 fao89: Proposed for #8044: accept and add to sprint 15:45:13 +1 15:45:15 +1 15:45:23 +1 15:45:24 #agreed accept and add to sprint 15:45:24 !accept 15:45:24 fao89: Current proposal accepted: accept and add to sprint 15:45:25 #topic https://pulp.plan.io/issues/7950 15:45:25 fao89: 1 issues left to triage: 7950 15:45:26 RM 7950 - newswangerd - NEW - Backport 7912 15:45:27 https://pulp.plan.io/issues/7950 15:45:28 (this is the 2.21.5 side of the order-by-_last_updated for the migration plugin) 15:45:52 I think it still in review, so I'll skip 15:45:56 !skip 15:45:57 fao89: No issues to triage. 15:45:57 +1 15:46:07 #endmeeting 15:46:07 !end