14:29:28 #startmeeting Pulp Triage 2017-05-12 14:29:28 #info asmacdo has joined triage 14:29:29 Meeting started Fri May 12 14:29:28 2017 UTC and is due to finish in 60 minutes. The chair is asmacdo. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:29:29 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:29:29 The meeting name has been set to 'pulp_triage_2017_05_12' 14:29:29 asmacdo has joined triage 14:29:36 !here 14:29:36 #info daviddavis has joined triage 14:29:37 daviddavis has joined triage 14:30:14 !here 14:30:14 #info bizhang has joined triage 14:30:14 bizhang has joined triage 14:30:38 !next 14:30:39 6 issues left to triage: 2734, 2748, 2749, 2750, 2751, 2754 14:30:39 #topic cancelling task does not update task group - http://pulp.plan.io/issues/2734 14:30:40 Pulp Issue #2734 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:30:40 cancelling task does not update task group - http://pulp.plan.io/issues/2734 14:31:08 !here 14:31:08 #info jortel has joined triage 14:31:08 jortel has joined triage 14:31:19 !here 14:31:19 #info ipanova has joined triage 14:31:20 ipanova has joined triage 14:31:48 !heer 14:31:48 Error: "heer" is not a valid command. 14:31:52 let's skip it? 14:31:52 !here 14:31:52 #info dkliban has joined triage 14:31:53 dkliban has joined triage 14:32:00 !propose skip 14:32:00 #idea Proposed for #2734: Skip this issue for this triage session. 14:32:01 Proposed for #2734: Skip this issue for this triage session. 14:32:07 dkliban: sounds almost like !beer 14:32:10 lol 14:32:13 !cheers 14:32:13 Error: "cheers" is not a valid command. 14:32:22 dkliban: it's friday, you know ;) 14:32:26 +1 14:32:26 ipanova: That's Numberwang! 14:32:36 beav: any updates?^ 14:33:25 let's give him another week and skip for now? 14:33:30 +1 14:33:31 !skip 14:33:32 5 issues left to triage: 2748, 2749, 2750, 2751, 2754 14:33:33 #topic Complex/Strange Upstream Yum URL Results In Incorrect Upstream Package URLs - http://pulp.plan.io/issues/2748 14:33:33 Pulp Issue #2748 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:33:33 Complex/Strange Upstream Yum URL Results In Incorrect Upstream Package URLs - http://pulp.plan.io/issues/2748 14:33:58 ipanova: not yet :( i have another issue to look into first related to pulp-rpm before that one, i havent created a redmine for it yet 14:34:07 !here 14:34:07 #info dralley has joined triage 14:34:08 dralley has joined triage 14:34:24 beav: ok we skipped it again to give you some more time 14:34:34 !here 14:34:34 #info fdobrovo has joined triage 14:34:35 fdobrovo has joined triage 14:35:10 looks like we have some issue in parsing the feed itseld 14:35:14 itself 14:35:15 ok thx. if someone is interested in the pulp-rpm packaging issue it would be helpful. it is easy to reproduce 14:35:36 is this one a mirror list issue? I'm not sure 14:35:47 it's not 14:35:58 no I think pulp is just having trouble with the url since the relative path is a get parameter 14:36:07 yeah 14:36:09 seems like an RFE almost 14:36:09 I'm just glancing at this, but it's real weird to have the path in the query parameter. 14:36:14 yea 14:36:17 agreed 14:36:27 asmacdo: mirrorlist do not have primary, so it is a feed 14:36:33 it's definitely weird but i would like us to be able to support taht 14:36:34 I wonder if this layout is even an RFC violation. 14:36:41 mhrivnak: i agree 14:37:29 let's investigate this and see whether it is a valid path or rfc violation? 14:37:35 i wonder if this same thing works with dnf 14:37:50 "Using a yum configuration to hit the upstream repo directly works. 14:38:37 i interpreted that to mean it worked with yum, not necessarily dnf 14:38:55 ah yea, maybe it doesn't work with dnf 14:39:06 daviddavis: with dnf work many things because it forgives many issues, but it does not that those are correct 14:39:20 agreed 14:39:20 does not mean* 14:39:27 * mhrivnak isn't able to focus on triage but wanted to comment on this one in particular 14:39:28 !propose accept 14:39:28 #idea Proposed for #2748: Leave the issue as-is, accepting its current state. 14:39:28 Proposed for #2748: Leave the issue as-is, accepting its current state. 14:39:42 ipanova: will you add a comment? 14:40:03 asmacdo: before adding a comment we need to make an investigation 14:40:18 +1 14:40:18 if the stuff is valid as pointed out mhrivnak 14:40:32 I was thinking the comment would just ask the question to investigate 14:40:38 It may be hard to know without having an example repo to poke. 14:40:43 ipanova: are you suggesting we skip? 14:42:13 !propose skip 14:42:13 #idea Proposed for #2748: Skip this issue for this triage session. 14:42:13 Proposed for #2748: Skip this issue for this triage session. 14:42:50 asmacdo: yeah 14:43:01 !accept 14:43:01 #agreed Skip this issue for this triage session. 14:43:01 Current proposal accepted: Skip this issue for this triage session. 14:43:02 #topic _release_resource should be acks_late and idempotent - http://pulp.plan.io/issues/2749 14:43:03 4 issues left to triage: 2749, 2750, 2751, 2754 14:43:03 Pulp Issue #2749 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:43:04 _release_resource should be acks_late and idempotent - http://pulp.plan.io/issues/2749 14:44:28 looks like the conversation is still, ongoing, let's skip it until the reporter will asnwer the questions? 14:45:16 !propose skip 14:45:16 #idea Proposed for #2749: Skip this issue for this triage session. 14:45:16 Proposed for #2749: Skip this issue for this triage session. 14:45:44 +1 14:46:00 +1 14:46:06 +1 14:46:08 !accept 14:46:08 #agreed Skip this issue for this triage session. 14:46:08 Current proposal accepted: Skip this issue for this triage session. 14:46:09 3 issues left to triage: 2750, 2751, 2754 14:46:10 #topic pulp_puppet is not compatible with django 1.10 - http://pulp.plan.io/issues/2750 14:46:10 Puppet Support Issue #2750 [ASSIGNED] (daviddavis@redhat.com) - Priority: Normal | Severity: Medium 14:46:11 pulp_puppet is not compatible with django 1.10 - http://pulp.plan.io/issues/2750 14:46:35 daviddavis: accept? 14:46:37 yes 14:46:49 and add to sprint preferrably since 2741 is on the sprint 14:47:09 +1 14:47:15 +1 14:47:15 !propose accept add to sprint 14:47:16 propose accept Propose accepting the current issue in its current state. 14:47:21 +1 14:47:45 ah, already on the sprint. 14:47:47 !accept 14:47:47 No action proposed, nothing to accept. 14:47:55 hmm 14:48:03 !propose accept 14:48:03 #idea Proposed for #2750: Leave the issue as-is, accepting its current state. 14:48:04 Proposed for #2750: Leave the issue as-is, accepting its current state. 14:48:06 !accept 14:48:06 #agreed Leave the issue as-is, accepting its current state. 14:48:06 Current proposal accepted: Leave the issue as-is, accepting its current state. 14:48:07 2 issues left to triage: 2751, 2754 14:48:08 #topic Unittest builder for plugins fails if the minimum required platform version is unavailable - http://pulp.plan.io/issues/2751 14:48:08 Packaging Issue #2751 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:48:08 Unittest builder for plugins fails if the minimum required platform version is unavailable - http://pulp.plan.io/issues/2751 14:50:03 we should accept as is 14:50:13 and we can add it to the next sprint at sprint planning 14:50:16 +1 14:50:17 dkliban: i was thinking this one needed discussion 14:50:34 asmacdo: what questions do you have? 14:50:35 it looks like a change in our release process right? 14:51:20 i'm not sure that I agree that we should build pulp 2.10 for fedora just because pulp_ostree only requires 2.10 on fedora 14:51:43 asmacdo: i think it's just a change in our PR builder job. it looks at the spec file to see what the minimum platform version is needed. it only tries that minimum. if that minimum is not available it should try to install teh next version 14:52:32 the bug as written doesnt look like it is asking for failover 14:52:52 it looks like it wants all platform versions to be installable by the plugins 14:53:23 i think we should triage it and the discussion should happen in the tracker 14:53:50 +1 14:53:53 thats fine by me. dkliban do you have a prio suggestion? 14:54:07 as is 14:54:12 !propose accept 14:54:12 #idea Proposed for #2751: Leave the issue as-is, accepting its current state. 14:54:13 Proposed for #2751: Leave the issue as-is, accepting its current state. 14:54:17 +1 14:54:24 !accept 14:54:24 #agreed Leave the issue as-is, accepting its current state. 14:54:24 Current proposal accepted: Leave the issue as-is, accepting its current state. 14:54:25 #topic RPM uploads appear to be missing metadata information - http://pulp.plan.io/issues/2754 14:54:26 1 issues left to triage: 2754 14:54:26 Pulp Issue #2754 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:54:27 RPM uploads appear to be missing metadata information - http://pulp.plan.io/issues/2754 14:55:35 so syncing seems to fill out these fields (Size, Summary, Source RPM, and Group) but uploading does not 14:56:04 daviddavis: do those fields exist on the unit or in the repo metadata? 14:56:30 asmacdo: the metadata - https://pulp.plan.io/issues/2754#note-2 14:56:32 Title: Issue #2754: RPM uploads appear to be missing metadata information - Pulp (at pulp.plan.io) 14:57:45 daviddavis: this sounds familiar to me 14:58:07 Me too, at least a little. 14:58:14 * daviddavis googles 14:58:25 I recall at some point that uploaded rpms weren't getting all the right fields populated. 14:58:40 daviddavis: we can extract just those info which is in package headers 14:58:59 "rpm -qip" can so I believe so 14:59:46 cool 14:59:51 !propose accept 14:59:51 #idea Proposed for #2754: Leave the issue as-is, accepting its current state. 14:59:52 Proposed for #2754: Leave the issue as-is, accepting its current state. 15:00:26 daviddavis, do you have a sense of how big the impact is of this bug? 15:02:21 mhrivnak: minimal unless the user wants this information at some later time 15:02:27 they'll have to reupload the package 15:02:38 This is the similar one I was thinking of: https://pulp.plan.io/issues/2365 15:02:40 Title: Issue #2365: rpm upload fails to populate "files" field on model - RPM Support - Pulp (at pulp.plan.io) 15:02:57 mhrivnak: yes! I was looking for that 15:03:12 daviddavis: so i've just uploaded one rpm, all data is there 15:03:47 weird, it's not for me 15:04:04 What versions of pulp are you each trying/ 15:04:05 ? 15:04:44 I'm on master 15:04:49 pulp 2 15:05:07 hm, interesting. 15:05:40 I wonder if there's a smash test similar to this use case already. 15:05:48 Where we might be able to just add some assertions about these fields? 15:05:49 let's triage it and then continue the discussion 15:06:01 Sounds reasonable. 15:06:09 as is? 15:06:28 +1 15:06:36 !accept 15:06:36 #agreed Leave the issue as-is, accepting its current state. 15:06:36 Current proposal accepted: Leave the issue as-is, accepting its current state. 15:06:38 No issues to triage. 15:06:42 !end 15:06:42 #endmeeting