14:32:20 #startmeeting Pulp Triage 2017-04-28 14:32:20 #info ttereshc has joined triage 14:32:21 Meeting started Fri Apr 28 14:32:20 2017 UTC and is due to finish in 60 minutes. The chair is ttereshc. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:32:21 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:32:21 The meeting name has been set to 'pulp_triage_2017_04_28' 14:32:21 ttereshc has joined triage 14:32:30 !here 14:32:30 #info asmacdo has joined triage 14:32:30 asmacdo has joined triage 14:32:37 !here 14:32:37 #info jortel has joined triage 14:32:37 jortel has joined triage 14:32:54 !here 14:32:54 #info bmbouter has joined triage 14:32:54 bmbouter has joined triage 14:32:57 !next 14:32:59 11 issues left to triage: 2639, 2725, 2727, 2729, 2730, 2732, 2734, 2735, 2736, 2737, 2739 14:32:59 #topic Upgrade fails on Fedora - http://pulp.plan.io/issues/2639 14:33:00 Pulp Issue #2639 [ASSIGNED] (pcreech) - Priority: Normal | Severity: Medium 14:33:00 Upgrade fails on Fedora - http://pulp.plan.io/issues/2639 14:33:30 !here 14:33:30 #info pcreech has joined triage 14:33:30 pcreech has joined triage 14:33:44 !here 14:33:44 #info ipanova has joined triage 14:33:44 ipanova has joined triage 14:33:55 So, this one isn't fixed, and preethi marked it as un-triaged so we can re prioritize it 14:34:21 do you have a recommendation pcreech? 14:34:25 it looks like high prio to me 14:34:31 !here 14:34:31 #info dalley has joined triage 14:34:32 dalley has joined triage 14:34:55 I do not, as I do not know how important it is to be able to upgrade from pulp in fedora to pulp upstream 14:35:46 our rpms should upgrade cleanly regardless of which dist they come from 14:36:17 !propose triage h h 14:36:17 #idea Proposed for #2639: Priority: High, Severity: High 14:36:17 Proposed for #2639: Priority: High, Severity: High 14:36:45 the fix at this point will probably be re-naming all our python-* packages for fedora to match the pulp in fedora spec file namings 14:36:54 well, python-pulp* 14:37:07 shall we add this to sprint as well? 14:37:14 can you elaborate on that pcreech? 14:37:14 it is on the sprint 14:37:26 oh blind me 14:37:27 python-pulp becomes what? 14:37:44 asmacdo: this is probably not teh best venue, but form python-pulp to python2-pulp wiht a provides python-pulp 14:37:49 just mirrornign what we do in fedora better 14:37:53 oh ok 14:38:08 so the upgrade path is followed when we have a superceeding update 14:38:12 didn't mean to get into the weeds, I just didnt understand 14:38:17 np 14:38:21 +1 hh 14:38:25 +1 h, h, keeping it on sprint 14:38:32 !accept 14:38:32 #agreed Priority: High, Severity: High 14:38:32 Current proposal accepted: Priority: High, Severity: High 14:38:34 #topic Celery killed during applicability regeneration due to out of memory condition - http://pulp.plan.io/issues/2725 14:38:34 10 issues left to triage: 2725, 2727, 2729, 2730, 2732, 2734, 2735, 2736, 2737, 2739 14:38:34 Pulp Issue #2725 [NEW] (daviddavis@redhat.com) - Priority: Normal | Severity: Medium 14:38:35 Celery killed during applicability regeneration due to out of memory condition - http://pulp.plan.io/issues/2725 14:38:48 !propose skip 14:38:48 #idea Proposed for #2725: Skip this issue for this triage session. 14:38:49 Proposed for #2725: Skip this issue for this triage session. 14:38:52 waiting for info 14:39:19 if no update: propose skip 14:39:31 I checked with daviddavis 14:39:35 +1 skip 14:39:36 !accept 14:39:36 #agreed Skip this issue for this triage session. 14:39:36 Current proposal accepted: Skip this issue for this triage session. 14:39:38 #topic Updating importer with ssl_* options along with other options fails "Cannot update 'config.remove_missing' and 'config' at the same time" - http://pulp.plan.io/issues/2727 14:39:38 9 issues left to triage: 2727, 2729, 2730, 2732, 2734, 2735, 2736, 2737, 2739 14:39:38 RPM Support Issue #2727 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:39:39 Updating importer with ssl_* options along with other options fails "Cannot update 'config.remove_missing' and 'config' at the same time" - http://pulp.plan.io/issues/2727 14:40:01 this one looks kind of fun :) 14:40:33 I hit similar issue with errata pkglists once 14:40:56 there is a workaround to do updates one by one but we better solve this soon 14:41:33 !propose accept 14:41:33 #idea Proposed for #2727: Leave the issue as-is, accepting its current state. 14:41:34 Proposed for #2727: Leave the issue as-is, accepting its current state. 14:41:55 normal/high 14:42:09 this is probably a regression from mongoengine 14:42:11 * pcreech brb's 14:42:19 +1 normal/high 14:42:27 !propose triage n h 14:42:27 #idea Proposed for #2727: Priority: Normal, Severity: High 14:42:27 Proposed for #2727: Priority: Normal, Severity: High 14:42:37 !accept 14:42:37 #agreed Priority: Normal, Severity: High 14:42:37 Current proposal accepted: Priority: Normal, Severity: High 14:42:39 8 issues left to triage: 2729, 2730, 2732, 2734, 2735, 2736, 2737, 2739 14:42:39 #topic pulp_user_metadata is ignored during ISO import - http://pulp.plan.io/issues/2729 14:42:40 RPM Support Issue #2729 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:42:40 pulp_user_metadata is ignored during ISO import - http://pulp.plan.io/issues/2729 14:44:47 so it looks like a regression from 2.7, as for the rcm comment 14:44:51 it looks like a regression 14:45:15 http://docs.pulpproject.org/dev-guide/integration/rest-api/content/upload.html#creating-an-upload-request 14:45:16 Title: Uploading Content — Pulp Project 2.13 documentation (at docs.pulpproject.org) 14:45:17 maybe h/m since it fails silently but dont put on sprint 14:45:32 since there is a work around 14:45:42 oh whoops, wrong upload 14:45:57 jortel: I agree 14:46:05 !propose triage h m 14:46:05 #idea Proposed for #2729: Priority: High, Severity: Medium 14:46:06 Proposed for #2729: Priority: High, Severity: Medium 14:46:06 if they aren't calling it a blocker 14:46:11 +1 14:46:15 they are not 14:46:16 +1 14:46:20 !accept 14:46:20 #agreed Priority: High, Severity: Medium 14:46:21 Current proposal accepted: Priority: High, Severity: Medium 14:46:21 #topic As user I want to be able to provide custom rsync arguments to rsync distributor - http://pulp.plan.io/issues/2730 14:46:22 8 issues left to triage: 2730, 2732, 2734, 2735, 2736, 2737, 2739, 2741 14:46:22 RPM Support Issue #2730 [NEW] (unassigned) - Priority: High | Severity: Medium 14:46:23 As user I want to be able to provide custom rsync arguments to rsync distributor - http://pulp.plan.io/issues/2730 14:46:43 should be a story? 14:46:53 +1 to story 14:47:04 !propose other convert to a story 14:47:04 #idea Proposed for #2730: convert to a story 14:47:05 Proposed for #2730: convert to a story 14:47:17 +1 14:47:21 +1 14:47:24 !accept 14:47:24 #agreed convert to a story 14:47:24 Current proposal accepted: convert to a story 14:47:26 7 issues left to triage: 2732, 2734, 2735, 2736, 2737, 2739, 2741 14:47:26 #topic Syncing from one pulp instance to another is slow - http://pulp.plan.io/issues/2732 14:47:27 Puppet Support Issue #2732 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:47:27 Syncing from one pulp instance to another is slow - http://pulp.plan.io/issues/2732 14:47:50 !here 14:47:50 #info fdobrovo has joined triage 14:47:51 fdobrovo has joined triage 14:49:33 there is a bit more info on BZ and lzap reproduced the issue, so it looks to me that at least it is worth investigating 14:49:45 need more information ... what does "slow" mean? 14:50:11 whenever these types of issues come in I want to retitled them for example 14:50:15 n/m issue has metrics 14:50:16 2 hours pulp-to-pulp vs 10 mins forge-to-pulp 14:50:21 'puppet sync is slow' 14:50:43 propose h/m 14:51:06 given those numbers the current title does seem right 14:51:17 that's what I got from BZ 14:51:23 agree with ttereshc let's investigate 14:51:40 !propose triage h m 14:51:40 #idea Proposed for #2732: Priority: High, Severity: Medium 14:51:40 Proposed for #2732: Priority: High, Severity: Medium 14:52:51 no objections? 14:53:08 !accept 14:53:08 #agreed Priority: High, Severity: Medium 14:53:08 Current proposal accepted: Priority: High, Severity: Medium 14:53:10 #topic cancelling task does not update task group - http://pulp.plan.io/issues/2734 14:53:10 6 issues left to triage: 2734, 2735, 2736, 2737, 2739, 2741 14:53:11 Pulp Issue #2734 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:53:12 cancelling task does not update task group - http://pulp.plan.io/issues/2734 14:54:35 i think we need more info since not reproduced w/ just pulp; 14:55:22 I was working w/ him on this 14:55:46 I also want it reproduced on only Pulp but beav nor I had time to do it 14:56:12 skip? 14:56:44 unless someone is going to take an AI to reproduce it I'm not sure anything will be different next time 14:56:57 !propose other skip and find volunteer to reproduce 14:56:57 #idea Proposed for #2734: skip and find volunteer to reproduce 14:56:57 Proposed for #2734: skip and find volunteer to reproduce 14:56:59 good point :) 14:57:30 what if we skip and put a note on it asking for a pulp-only reproducer to be posted on it? 14:57:35 can we ask the reporter to reproduce? 14:57:43 i like this idea more 14:57:59 we can definitly ask 14:58:08 +1 to bmbouter proposal 14:58:28 !propose other skip, put a not on issue and find a volunteer 14:58:28 #idea Proposed for #2734: skip, put a not on issue and find a volunteer 14:58:28 Proposed for #2734: skip, put a not on issue and find a volunteer 14:58:34 !accept 14:58:34 #agreed skip, put a not on issue and find a volunteer 14:58:34 Current proposal accepted: skip, put a not on issue and find a volunteer 14:58:36 5 issues left to triage: 2735, 2736, 2737, 2739, 2741 14:58:36 #topic Add support for failover to v1 protocol - http://pulp.plan.io/issues/2735 14:58:37 Docker Support Issue #2735 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:58:37 Add support for failover to v1 protocol - http://pulp.plan.io/issues/2735 14:59:27 !propose other convert to a story 14:59:27 #idea Proposed for #2735: convert to a story 14:59:27 Proposed for #2735: convert to a story 15:00:16 i am not sure if it a story or bug but with current situation it is impossible to docker pull v1 from pulp 15:00:31 addition of failover support would fix this issue 15:00:47 i think story is correct because this is a new feature we never had 15:00:57 but we used to be able to do that? 15:01:09 my understanding is no 15:01:11 bmbouter: yes, but docker client changed its behaviour 15:01:20 this bug only occurs if the client tries to use v2 api but we only serve v1 api 15:01:21 oic 15:02:03 !here 15:02:03 #info daviddavis has joined triage 15:02:04 daviddavis has joined triage 15:02:08 everyone agree on converting it to story? 15:02:13 +1 15:02:16 +1 15:02:18 I /think/ so 15:02:22 !accept 15:02:22 #agreed convert to a story 15:02:22 Current proposal accepted: convert to a story 15:02:24 4 issues left to triage: 2736, 2737, 2739, 2741 15:02:24 #topic pulp_rpm.yum_plugin.utils.generate_listing_files should move in the platform - http://pulp.plan.io/issues/2736 15:02:25 Pulp Issue #2736 [NEW] (unassigned) - Priority: Normal | Severity: Medium 15:02:25 pulp_rpm.yum_plugin.utils.generate_listing_files should move in the platform - http://pulp.plan.io/issues/2736 15:02:58 we are out of time, do we continue triage? (I am all for it) what others think 15:03:09 i dont mind 15:03:13 I don't mind 15:03:13 i dont mind either 15:03:25 good we have quorum 15:03:26 ok 15:03:27 this seems more like a refactor? 15:03:34 definitly 15:03:46 !propose other convert to refactor 15:03:46 #idea Proposed for #2736: convert to refactor 15:03:47 Proposed for #2736: convert to refactor 15:03:47 !propose low low 15:03:47 Error: "propose" is not a valid command. 15:04:03 +1 15:04:16 this would be nice, but it doesn't actually change anything in our code 15:04:22 +1 15:04:29 !accept 15:04:29 #agreed convert to refactor 15:04:29 Current proposal accepted: convert to refactor 15:04:30 +1 15:04:31 3 issues left to triage: 2737, 2739, 2741 15:04:31 #topic pulp_rpm.common.version_utils has some functionality that seems useful for the platform - http://pulp.plan.io/issues/2737 15:04:32 Pulp Issue #2737 [NEW] (unassigned) - Priority: Normal | Severity: Medium 15:04:32 pulp_rpm.common.version_utils has some functionality that seems useful for the platform - http://pulp.plan.io/issues/2737 15:04:37 !propose other convert to refactor 15:04:37 #idea Proposed for #2737: convert to refactor 15:04:38 Proposed for #2737: convert to refactor 15:04:43 yeah same here 15:04:44 same deal, but i dont think we should accept this one 15:04:44 +1 15:04:47 -1 15:04:52 +1 15:05:00 those version_utils look very specific to rpm 15:05:12 i think those should stay there 15:05:38 I see what you are saying 15:05:40 what about adding this to pulp_deb as well instead of moving to platform 15:06:14 I'm +1 to ina's idea for the short term, but -1 for long term due to DRY 15:06:24 well, if debian and rpm actually do use the same versioning scheme, then this could be renmaed and moved 15:06:28 oh, if only rpm/deb specific then -1 to moving to platform. 15:06:35 it is only rpm/deb specific 15:06:42 is my understanding 15:07:01 I think both of these issues are an attempt to have the pulp_deb plugin not depend on pulp_rpm 15:07:18 so I don't think either of these will actually be done 15:07:20 in either case, this should be a task/refactor not an issue. 15:07:24 definitly 15:07:39 i think this should be to implement this type of thing in pulp_deb 15:07:51 asmacdo, would you mind putting comment on the issue with your thoughts on that, to start a conversation in the issue maybe? 15:08:03 asmacdo: you're point is still valid I'm just pointing out some context 15:08:03 sure 15:08:07 yeah that would be good 15:08:11 yep 15:08:13 can we skip w/ asmacdo leaving a note? 15:08:25 +1 15:08:25 if we switch it to a refactor now we won't rediscuss it next triage3 15:08:32 !propose skip and asmacdo will comment on it 15:08:32 propose skip Propose skipping the current issue for this triage session. 15:08:46 !propose other skip and asmacdo will comment on it 15:08:46 #idea Proposed for #2737: skip and asmacdo will comment on it 15:08:46 Proposed for #2737: skip and asmacdo will comment on it 15:08:55 !accept 15:08:55 #agreed skip and asmacdo will comment on it 15:08:55 Current proposal accepted: skip and asmacdo will comment on it 15:08:56 #topic Cannot see downloaded content units durinf sync of the repo in repo details - http://pulp.plan.io/issues/2739 15:08:57 2 issues left to triage: 2739, 2741 15:08:57 RPM Support Issue #2739 [NEW] (unassigned) - Priority: Normal | Severity: Medium 15:08:58 Cannot see downloaded content units durinf sync of the repo in repo details - http://pulp.plan.io/issues/2739 15:10:02 arent the content unit numbers generated at the end of a sync? 15:10:10 not sure now important it is just noticed change in behavior 15:10:30 asmacdo: it was possible to see unit numbers during sync 15:10:51 hmm ok 15:10:52 does anyone remember when we had such possibility? 15:11:01 yeah i think this changed with the mongoengine conversion also 15:11:13 so since 2.7 15:11:14 the content units were updated by the conduits as they were importerd 15:11:36 but now, iirc that didnt work for some reason, so we had to do it all at once after the sync was done 15:11:41 jortel: does that ring a bell? 15:12:39 iirc, the counts are managed by the conduit but the plugin is responsible for reporting it 15:12:55 conduits aren't used post mongoengine in manyplaces 15:13:09 if nobody is complaining, let's leave it as m/m 15:13:27 works for me 15:13:31 +1 15:13:43 !propose accept 15:13:43 #idea Proposed for #2739: Leave the issue as-is, accepting its current state. 15:13:43 Proposed for #2739: Leave the issue as-is, accepting its current state. 15:13:53 !accept 15:13:53 #agreed Leave the issue as-is, accepting its current state. 15:13:53 Current proposal accepted: Leave the issue as-is, accepting its current state. 15:13:54 1 issues left to triage: 2741 15:13:55 #topic Pulp is not compatible with Django 1.10 - http://pulp.plan.io/issues/2741 15:13:55 Pulp Issue #2741 [NEW] (unassigned) - Priority: Normal | Severity: Medium 15:13:55 Pulp is not compatible with Django 1.10 - http://pulp.plan.io/issues/2741 15:15:01 i think we changed our urlpatterns stuff for django forward compatibility 15:15:05 I took a quick look here, and it's in one place 15:15:24 a minor overlooked point for something including "content" 15:15:51 !propose other triage high/high and add to sprint 15:15:51 #idea Proposed for #2741: triage high/high and add to sprint 15:15:51 Proposed for #2741: triage high/high and add to sprint 15:15:54 ./server/pulp/server/content/web/urls.py:urlpatterns = patterns( 15:16:00 +1 15:16:02 +1 15:16:12 !accept 15:16:12 #agreed triage high/high and add to sprint 15:16:12 Current proposal accepted: triage high/high and add to sprint 15:16:13 +1 15:16:14 No issues to triage. 15:16:19 !end 15:16:19 #endmeeting