15:31:33 #startmeeting Pulp Triage 2018-02-23 15:31:33 #info dalley has joined triage 15:31:33 Meeting started Fri Feb 23 15:31:33 2018 UTC and is due to finish in 60 minutes. The chair is dalley. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:31:33 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:31:33 The meeting name has been set to 'pulp_triage_2018_02_23' 15:31:33 dalley: dalley has joined triage 15:31:36 !here 15:31:36 #info dkliban has joined triage 15:31:36 dkliban: dkliban has joined triage 15:31:56 !here 15:31:56 #info ipanova has joined triage 15:31:56 ipanova: ipanova has joined triage 15:32:28 !here 15:32:28 #info asmacdo has joined triage 15:32:29 asmacdo: asmacdo has joined triage 15:32:49 !here 15:32:49 #info bizhang has joined triage 15:32:49 bizhang: bizhang has joined triage 15:32:59 !next 15:33:00 dalley: 6 issues left to triage: 3387, 3388, 3390, 3391, 3392, 3393 15:33:00 #topic Improve error message when uploading a file already in Pulp3 - http://pulp.plan.io/issues/3387 15:33:01 Issue #3387 [NEW] (unassigned) - Priority: Low | Severity: Low 15:33:02 Improve error message when uploading a file already in Pulp3 - http://pulp.plan.io/issues/3387 15:33:03 !here 15:33:03 #info mansari has joined triage 15:33:04 mansari: mansari has joined triage 15:33:59 !propose accept 15:33:59 #idea Proposed for #3387: Leave the issue as-is, accepting its current state. 15:33:59 dalley: Proposed for #3387: Leave the issue as-is, accepting its current state. 15:34:08 this behavior seems right to me 15:34:29 I'm not sure what else we can say other than the checksum isnt unique 15:34:49 the message could make it clear that the artifact already exists 15:34:55 ^ 15:35:02 it's clear to us, but not to a new user 15:35:04 !here 15:35:04 #info milan_ has joined triage 15:35:04 milan_: milan_ has joined triage 15:35:08 I agree with dkliban 15:35:09 +1 accept 15:35:12 +1 15:35:17 +1 15:35:23 !accept 15:35:23 #agreed Leave the issue as-is, accepting its current state. 15:35:23 dalley: Current proposal accepted: Leave the issue as-is, accepting its current state. 15:35:24 dalley: 5 issues left to triage: 3388, 3390, 3391, 3392, 3393 15:35:24 #topic Syncing Debian (Ubuntu) example repo fails - http://pulp.plan.io/issues/3388 15:35:25 Issue #3388 [NEW] (unassigned) - Priority: Normal | Severity: Medium 15:35:26 Syncing Debian (Ubuntu) example repo fails - http://pulp.plan.io/issues/3388 15:35:43 skip ? 15:35:46 re: that last one, mark easy fix? 15:35:56 dalley: i don't know how easy it is :) 15:35:59 fair 15:36:36 lets move this one to the deb tracker 15:36:42 agree 15:36:59 !propose other move to the pulp_deb tracker 15:36:59 #idea Proposed for #3388: move to the pulp_deb tracker 15:36:59 dalley: Proposed for #3388: move to the pulp_deb tracker 15:37:24 +1 15:37:48 my money is on a permissions problem in the dev environment 15:38:03 s/dev// 15:38:43 yeah .... or something is broken 15:38:57 misa: do you want us to triage this issue>? 15:39:07 brb 15:40:26 unless misa wants to do something else IMO we should skip and ask some questions on the ticket 15:41:21 ok 15:41:25 +1 to skip 15:43:20 any objection to skipping? 15:43:25 !propose skip 15:43:25 #idea Proposed for #3388: Skip this issue for this triage session. 15:43:25 dalley: Proposed for #3388: Skip this issue for this triage session. 15:44:11 !accept 15:44:11 #agreed Skip this issue for this triage session. 15:44:11 dalley: Current proposal accepted: Skip this issue for this triage session. 15:44:13 #topic Missing repository field when syncing an importer - http://pulp.plan.io/issues/3390 15:44:13 dalley: 4 issues left to triage: 3390, 3391, 3392, 3393 15:44:14 Issue #3390 [NEW] (unassigned) - Priority: Low | Severity: Low 15:44:15 Missing repository field when syncing an importer - http://pulp.plan.io/issues/3390 15:44:40 This one and the next one share the same core problem with coreapi 15:44:58 but the specific problem should be filed against pulp_file 15:46:11 this is a docs issue 15:46:21 the docs don't match the API 15:46:29 asmacdo, are you suggesting that this one and the next be consolidated into one issue? 15:46:57 the underlying issue might already have a ticket... bizhang? 15:47:33 not sure how that ticket will resolve, but i think we should keep them both for now 15:48:13 but they should be moved to the pulp_file tracker? 15:48:41 I think this is a dupe of https://pulp.plan.io/issues/3351#note-6 15:49:31 it is 15:49:44 since we have to create a schema for each detail route, shouldnt we keep an issue for each one that needs it? 15:49:45 !propose other close-duplicate 15:49:45 #idea Proposed for #3390: close-duplicate 15:49:45 bizhang: Proposed for #3390: close-duplicate 15:49:55 i agree asmacdo 15:50:25 #3353 is for both publish and sync 15:50:42 +1 close 15:50:56 I think it is reasonable to have one to cover adding the schema for both 15:51:04 alright 15:51:09 i am ok with this plan 15:51:46 !accept 15:51:46 #agreed close-duplicate 15:51:46 dalley: Current proposal accepted: close-duplicate 15:51:47 dalley: 3 issues left to triage: 3391, 3392, 3393 15:51:47 #topic Missing repository field when creating a publication - http://pulp.plan.io/issues/3391 15:51:48 Issue #3391 [NEW] (unassigned) - Priority: Low | Severity: Low 15:51:49 Missing repository field when creating a publication - http://pulp.plan.io/issues/3391 15:51:54 !propose other close-duplicate 15:51:54 #idea Proposed for #3391: close-duplicate 15:51:54 dalley: Proposed for #3391: close-duplicate 15:51:58 +1 15:52:32 !accept 15:52:32 #agreed close-duplicate 15:52:32 dalley: Current proposal accepted: close-duplicate 15:52:33 dalley: 2 issues left to triage: 3392, 3393 15:52:34 #topic Redudant fields for distribution model - http://pulp.plan.io/issues/3392 15:52:34 Issue #3392 [NEW] (unassigned) - Priority: Normal | Severity: Medium 15:52:35 Redudant fields for distribution model - http://pulp.plan.io/issues/3392 15:52:54 i didnt understand this one 15:53:29 kersom: does it change things that we have removed the relationship between publishers and repositories? 15:53:56 kersom noticed that the fields are not needed 15:54:19 because a distribution has a relationship to a publication. the publication has a relationship to a repository version and to a publisher 15:54:19 asmacdo, not sure. 15:54:29 yeah 15:54:37 a publisher is needed for auto-distribute 15:54:57 repo is needed for the same reason 15:54:57 but then you can add a publication, and a publisher and repo that are not related 15:54:58 is that a feature for teh MVP? 15:55:24 let's skip for now and discuss on the ticket 15:55:28 jortel: we already pretty much have this right? 15:55:37 asmacdo: jortel is not in triage right now 15:56:01 +1 skip 15:56:02 skip for now and i'll comment on the ticket 15:56:08 !propose skip 15:56:08 #idea Proposed for #3392: Skip this issue for this triage session. 15:56:08 dalley: Proposed for #3392: Skip this issue for this triage session. 15:56:39 +1 15:56:56 !accept 15:56:56 #agreed Skip this issue for this triage session. 15:56:56 dalley: Current proposal accepted: Skip this issue for this triage session. 15:56:58 #topic API break: unit_key became mandatory during RPM upload - http://pulp.plan.io/issues/3393 15:56:58 dalley: 1 issues left to triage: 3393 15:56:59 Issue #3393 [NEW] (unassigned) - Priority: Normal | Severity: Medium 15:57:00 API break: unit_key became mandatory during RPM upload - http://pulp.plan.io/issues/3393 15:57:10 this is not good 15:57:12 this one was already reported 15:57:15 it is a dupe 15:57:18 oh ok 15:57:23 https://pulp.plan.io/issues/3307 15:57:56 the API docs never sais unit_key is an optional key 15:58:01 dkliban: (previous issue) fyi auto publish is on the mvp in red 15:58:04 https://docs.pulpproject.org/dev-guide/integration/rest-api/content/upload.html#import-into-a-repository 15:58:41 i think what we did - we just fixed the gap in the code 15:58:56 ipanova: so was this 'fixed' on purpose? 15:59:25 dkliban: i don't think so, we need to look into the commi 15:59:26 t 15:59:45 i just hightlight that in in docs we never said it is optional 16:01:09 well, even if it was never declared optional, it is still technically backwards-incompatible 16:01:25 yeah ... i don't think this ticket https://pulp.plan.io/issues/2754 meant to make this change 16:01:37 it is, but it;s kinda user's fault he did not follow the docs specs 16:02:25 i would argue that the docs are wrong 16:02:38 anyway 16:02:42 let's fix it but we will need cautious not to break other things which rely on the fact the unit_key cannot be null 16:02:44 let's close it as a duplicate 16:03:13 yeah #3393 needs to be closed 16:03:19 should we reprioritize the original since there is a second report? 16:03:25 yes 16:03:27 !propose other close-duplicate 16:03:27 #idea Proposed for #3393: close-duplicate 16:03:27 dalley: Proposed for #3393: close-duplicate 16:03:27 for sure 16:03:51 +1 16:04:05 !accept 16:04:05 #agreed close-duplicate 16:04:05 dalley: Current proposal accepted: close-duplicate 16:04:06 dalley: No issues to triage. 16:04:08 !issue 3307 16:04:09 #topic import_upload: improve data validation - http://pulp.plan.io/issues/3307 16:04:09 Issue #3307 [NEW] (unassigned) - Priority: Normal | Severity: Medium 16:04:10 import_upload: improve data validation - http://pulp.plan.io/issues/3307 16:04:57 i think it needs to get on the sprint 16:05:02 can we add a comment to accept unit_key: null which will default to {} 16:05:03 yes 16:06:41 !propose other add to sprint, add relation to 3393 16:06:41 #idea Proposed for #3307: add to sprint, add relation to 3393 16:06:41 dalley: Proposed for #3307: add to sprint, add relation to 3393 16:06:50 +1 16:07:20 asmacdo: will you add the comment to the issue with the outcome of our discussion? 16:07:29 sure 16:07:45 asmacdo++ 16:07:45 ipanova: asmacdo's karma is now 34 16:08:06 dkliban, We're a few merges away from this: https://travis-ci.org/Ichimonji10/devel/builds/345313538 16:08:23 nice 16:08:56 !accept 16:08:56 #agreed add to sprint, add relation to 3393 16:08:56 dalley: Current proposal accepted: add to sprint, add relation to 3393 16:08:58 dalley: No issues to triage. 16:08:59 !end 16:08:59 #endmeeting