14:29:27 #startmeeting Pulp Triage 2017-06-30 14:29:27 #info ttereshc has joined triage 14:29:28 Meeting started Fri Jun 30 14:29:27 2017 UTC and is due to finish in 60 minutes. The chair is ttereshc. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:29:28 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:29:28 The meeting name has been set to 'pulp_triage_2017_06_30' 14:29:28 ttereshc has joined triage 14:29:36 !here 14:29:36 #info elijah_d has joined triage 14:29:36 elijah_d has joined triage 14:29:38 !here 14:29:38 #info asmacdo has joined triage 14:29:38 asmacdo has joined triage 14:29:47 !here 14:29:47 #info bizhang has joined triage 14:29:47 bizhang has joined triage 14:29:49 !here 14:29:49 #info dalley has joined triage 14:29:50 dalley has joined triage 14:29:53 !next 14:29:54 8 issues left to triage: 2831, 2846, 2847, 2848, 2849, 2850, 2860, 2861 14:29:55 #topic RFE: Changes to pulp_docker and crane metadata structure - http://pulp.plan.io/issues/2831 14:29:55 Crane Issue #2831 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:29:56 RFE: Changes to pulp_docker and crane metadata structure - http://pulp.plan.io/issues/2831 14:30:27 !here 14:30:27 #info mhrivnak has joined triage 14:30:28 mhrivnak has joined triage 14:30:37 !here 14:30:37 #info jortel has joined triage 14:30:37 jortel has joined triage 14:30:45 lets switch to a story, but not groom it 14:30:50 as per mhrivnak comment, convert to two stories? 14:30:59 !propose other convert to 2 stories 14:30:59 #idea Proposed for #2831: convert to 2 stories 14:30:59 Proposed for #2831: convert to 2 stories 14:31:04 +1 14:31:10 !here 14:31:10 #info dkliban has joined triage 14:31:11 dkliban has joined triage 14:31:14 !accept 14:31:14 #agreed convert to 2 stories 14:31:14 Current proposal accepted: convert to 2 stories 14:31:15 7 issues left to triage: 2846, 2847, 2848, 2849, 2850, 2860, 2861 14:31:16 #topic Pulp Yum Repo doesn't support include or exclude features - http://pulp.plan.io/issues/2846 14:31:16 RPM Support Issue #2846 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:31:17 Pulp Yum Repo doesn't support include or exclude features - http://pulp.plan.io/issues/2846 14:31:26 !here 14:31:26 #info daviddavis has joined triage 14:31:27 daviddavis has joined triage 14:31:38 i asked this user to file this issue 14:31:44 it should be converted to a story 14:32:05 and we should probably implement it with pulp 3.1+ 14:32:25 Sounds good. 14:32:30 there is a rm 206 which is about whitelists and blacklists (in the comments) 14:32:31 RPM Support Story #206 [NEW] (unassigned) - Priority: Normal 14:32:32 As a user, I can specify a whitelist of packages for sync - http://pulp.plan.io/issues/206 14:32:41 as bmbouter mentioned 14:32:50 this should focus on "exclude" since whitelist =include 14:32:53 oh yeah ... this is exactly the same thing 14:33:18 not exactly, but the same concept. do we want to keep both open? 14:33:50 We'll may implement in pulp 3 something more general than either of these. 14:33:53 does 206 talk about exlude or blacklist? 14:34:03 So I'd combine them somehow and not worry too much about the details. 14:34:12 asmacdo, only in comments 14:34:24 !here 14:34:24 #info mansari has joined triage 14:34:25 mansari has joined triage 14:34:34 !propose other update rm 206 to include "exclude" :P 14:34:34 #idea Proposed for #2846: update rm 206 to include exclude :P 14:34:34 Proposed for #2846: update rm 206 to include exclude :P 14:34:35 agreed to mhrivnak comment. and, I don't think we should do this for pulp2 14:35:05 +1 mhrivnak 14:35:29 !propose other combine with rm 206 14:35:29 #idea Proposed for #2846: combine with rm 206 14:35:29 Proposed for #2846: combine with rm 206 14:35:31 !accept 14:35:31 #agreed combine with rm 206 14:35:31 Current proposal accepted: combine with rm 206 14:35:32 6 issues left to triage: 2847, 2848, 2849, 2850, 2860, 2861 14:35:33 #topic Skip download of blobs with foreign mediatype. - http://pulp.plan.io/issues/2847 14:35:33 Docker Support Issue #2847 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:35:34 Skip download of blobs with foreign mediatype. - http://pulp.plan.io/issues/2847 14:35:46 !propose triage high high 14:35:46 #idea Proposed for #2847: Priority: High, Severity: High 14:35:46 Proposed for #2847: Priority: High, Severity: High 14:36:00 We talked about this yesterday and put it on the next sprint. 14:36:04 +1 14:36:08 "violate the license" is not good 14:36:15 +1 14:36:16 +1 14:36:24 +1 14:36:25 !accept 14:36:25 #agreed Priority: High, Severity: High 14:36:25 Current proposal accepted: Priority: High, Severity: High 14:36:26 #topic remove tag and name field on the Manifest model - http://pulp.plan.io/issues/2848 14:36:27 5 issues left to triage: 2848, 2849, 2850, 2860, 2861 14:36:28 Docker Support Issue #2848 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:36:29 remove tag and name field on the Manifest model - http://pulp.plan.io/issues/2848 14:37:18 !propose other convert to task 14:37:18 #idea Proposed for #2848: convert to task 14:37:19 Proposed for #2848: convert to task 14:37:36 +1 14:37:44 +1 14:37:51 is this backwards compatible? 14:37:56 This is related to limitations of schema 1 manifests FWIW 14:38:11 !here 14:38:11 #info bmbouter has joined triage 14:38:11 bmbouter has joined triage 14:38:16 asmacdo I suggest discussing that on the issue. 14:38:27 asmacdo: it's not, but it's also broken 14:38:35 and has always been 14:38:54 ok. +1 covert to task 14:38:57 !accept 14:38:57 #agreed convert to task 14:38:57 Current proposal accepted: convert to task 14:38:58 +1 14:38:59 4 issues left to triage: 2849, 2850, 2860, 2861 14:38:59 #topic Worker terminates abnormally while processing task - http://pulp.plan.io/issues/2849 14:39:00 Docker Support Issue #2849 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:39:01 Worker terminates abnormally while processing task - http://pulp.plan.io/issues/2849 14:39:55 !propose triage high high 14:39:55 #idea Proposed for #2849: Priority: High, Severity: High 14:39:55 Proposed for #2849: Priority: High, Severity: High 14:40:01 if it's not the OOM it must be a segfault 14:40:19 +1 to h/h 14:40:26 +1 14:40:28 +1 14:40:32 !accept 14:40:32 #agreed Priority: High, Severity: High 14:40:32 Current proposal accepted: Priority: High, Severity: High 14:40:34 #topic Ensure that users can reach the status api even if the db is down - http://pulp.plan.io/issues/2850 14:40:34 3 issues left to triage: 2850, 2860, 2861 14:40:35 Pulp Issue #2850 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:40:36 Ensure that users can reach the status api even if the db is down - http://pulp.plan.io/issues/2850 14:40:51 !here 14:40:51 #info pcreech has joined triage 14:40:52 pcreech has joined triage 14:40:54 late :( 14:40:57 +tag Pulp 3 14:41:03 yes 14:41:03 !propose other convert to story 14:41:03 #idea Proposed for #2850: convert to story 14:41:03 Proposed for #2850: convert to story 14:41:05 it's tagged pulp 3 already 14:41:30 As a user I can use the status endpoint when the DB is down 14:41:38 +1 14:41:43 +1 14:41:44 +1 14:41:44 +1 14:41:46 +1 14:41:47 +1 14:41:51 +1 14:41:55 !accept 14:41:55 #agreed convert to story 14:41:55 Current proposal accepted: convert to story 14:41:56 Look at all that participation! ;) 14:41:56 2 issues left to triage: 2860, 2861 14:41:57 +1 (semi-related) we should connect to the db early and disconnect late as a best practice 14:41:57 #topic Python3 weakref tracebacks in the log - http://pulp.plan.io/issues/2860 14:41:58 Pulp Issue #2860 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:41:59 Python3 weakref tracebacks in the log - http://pulp.plan.io/issues/2860 14:42:11 er.. switch late/early in my last stament 14:42:11 :) well done, guys 14:42:55 upstream python issue 14:43:07 this is in F25, right? 14:43:16 yes 14:43:24 specifically python 3.5.3 14:43:29 its been fixed upstream 14:43:47 not sure if its been released yet 14:43:48 Gotcha. So we just wait for it to land in Fedora? 14:43:55 yes 14:44:01 probably 14:44:09 it was fixed in 3.6, i dont know about 3.5 14:44:36 yes 14:44:50 should we close it as wontfix on our side with comment about upstream fix? 14:44:57 I not sure if we need to rebuild after that lands or not, but that is fine 14:45:21 that's why I want to figure out if we need to rebuild 14:45:21 thats fine with me. mostly wanted it to be searchable 14:45:28 I'd go for notabug 14:45:33 It's not a pulp bug. 14:45:35 +1 14:45:37 if we have to take an action though then we probably should leave it open 14:45:43 I don't think we take any action. 14:45:51 task to figure out what to do with it? 14:45:58 don't we have to 'rebuild our stuff on the new scl' 14:46:01 If there is an action to take, we could make an issue to do that action. 14:46:03 * bmbouter doesn't know and is guessing 14:46:08 I don't think there's an SCL involved. 14:46:09 bmbouter: rebuild our stuff: no 14:46:18 !propose other close as NOTABUG 14:46:18 #idea Proposed for #2860: close as NOTABUG 14:46:19 Proposed for #2860: close as NOTABUG 14:46:20 thx, +1 closing as NOTABUG 14:46:21 er... untill python36 14:46:25 but hten... maybe 14:46:32 !accept 14:46:32 #agreed close as NOTABUG 14:46:32 Current proposal accepted: close as NOTABUG 14:46:33 1 issues left to triage: 2861 14:46:33 #topic Queued tasks will be lost if the resource manager is restarted via systemctl - http://pulp.plan.io/issues/2861 14:46:34 Pulp Issue #2861 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:46:35 Queued tasks will be lost if the resource manager is restarted via systemctl - http://pulp.plan.io/issues/2861 14:46:36 well we can open a rebuild task later anyway 14:46:44 I think it was fixed in py 3.5.4 14:46:54 this is "Issue A" from last Friday's report 14:47:13 we should put this on the sprint b/c it affects both pulp2 and pulp3 14:47:27 and high/med is my suggestion 14:47:45 !propose other triage high/med, add to sprint 14:47:45 #idea Proposed for #2861: triage high/med, add to sprint 14:47:46 Proposed for #2861: triage high/med, add to sprint 14:47:50 +1 14:47:50 +1 14:47:52 is this a bug to fix upstream? 14:48:20 yes it's going to be another upstream celery activity 14:48:31 this will reproduce outside of pulp easy 14:49:02 +1 14:49:10 dalley: I'm hoping you can file the upstream celery reproducer 14:49:18 Should we move it to the External tracker? 14:49:23 im unclear about when we track upstream bugs 14:49:35 I think we do if we're planning to fix them. :) 14:49:48 let's keep it on pulp 14:50:05 im ok with whatever jortel decides 14:50:06 the root cause is upstream, but it's affecting pulp users in specific ways 14:50:20 good point. 14:50:34 bmbouter: I'll look at it, I've also get the rsync regression fixed first though 14:50:34 !accept 14:50:34 #agreed triage high/med, add to sprint 14:50:34 Current proposal accepted: triage high/med, add to sprint 14:50:36 No issues to triage. 14:50:40 dalley: ty! 14:50:42 !end 14:50:42 #endmeeting