14:29:46 #startmeeting Pulp Triage 2016-10-07 14:29:46 #info asmacdo has joined triage 14:29:47 Meeting started Fri Oct 7 14:29:46 2016 UTC and is due to finish in 60 minutes. The chair is asmacdo. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:29:47 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:29:47 The meeting name has been set to 'pulp_triage_2016_10_07' 14:29:47 asmacdo has joined triage 14:30:00 !here 14:30:00 #info pcreech has joined triage 14:30:01 pcreech has joined triage 14:30:22 !here 14:30:22 #info bmbouter has joined triage 14:30:23 bmbouter has joined triage 14:30:36 !here 14:30:36 #info mhrivnak has joined triage 14:30:36 mhrivnak has joined triage 14:30:41 !here 14:30:41 #info bizhang has joined triage 14:30:42 bizhang has joined triage 14:30:51 !next 14:30:52 8 issues left to triage: 2278, 2279, 2287, 2288, 2289, 2321, 2323, 2326 14:30:53 #topic Remove checksum_type from the srpm and drpm collections - http://pulp.plan.io/issues/2278 14:30:53 Pulp Issue #2278 [NEW] (unassigned) - Priority: High | Severity: High | Severity: High 14:30:53 Remove checksum_type from the srpm and drpm collections - http://pulp.plan.io/issues/2278 14:31:08 This looks to be resolved 14:31:11 I upped this to high/high 14:31:19 it's resolved for them but we need to write a migraiton 14:31:21 smyers, there is a workaround, but not resolved 14:31:35 we probably out to call this urgent/high 14:31:36 I also think this should go into a sprint 14:31:38 it is a regression 14:31:46 I see, the update didn't make sense ti I read the whole ticket 14:31:48 !propose triage urgent high 14:31:48 #idea Proposed for #2278: Priority: Urgent, Severity: High 14:31:49 Proposed for #2278: Priority: Urgent, Severity: High 14:31:56 I don't think this should block releases 14:32:16 the regression-ness occured in the 2.8 release 14:32:19 I also don't think this should block releases, but I do agree it should be done very soon. 14:32:26 and this use is just upgrading at this point in time 14:32:30 s/use/user/ 14:32:43 And there's clearly a workaround :) 14:32:49 !propose accept 14:32:49 #idea Proposed for #2278: Leave the issue as-is, accepting its current state. 14:32:50 Proposed for #2278: Leave the issue as-is, accepting its current state. 14:32:54 +1 14:32:54 if we could put it on the sprint that would be great 14:32:55 I suggest high/high 14:32:55 +1 14:33:04 adding to the sprint works for me. 14:33:05 it is high/high 14:33:05 +1 to high/high 14:33:06 It's current state is high/high 14:33:09 its 14:33:12 !suggest add to spritn 14:33:12 #idea add to spritn 14:33:20 #agreed Leave the issue as-is, accepting its current state. 14:33:20 !accept 14:33:20 Current proposal accepted: Leave the issue as-is, accepting its current state. 14:33:21 7 issues left to triage: 2279, 2287, 2288, 2289, 2321, 2323, 2326 14:33:22 #topic Pulp yum_importer fails when syncing SuSE repositories - http://pulp.plan.io/issues/2279 14:33:22 Pulp Issue #2279 [NEW] (unassigned) - Priority: Normal | Severity: Medium | Severity: Medium 14:33:22 Pulp yum_importer fails when syncing SuSE repositories - http://pulp.plan.io/issues/2279 14:34:13 This looks like it's still being investigated 14:34:23 need to keep waiting on suse access? 14:34:28 We've punted this with needinfo for a while, and I'm still waiting on getting access 14:34:31 Yeah, I don't know if we do 14:34:57 I think I'm going to take it and work it as soon as I get access to those repos, at least to repro it 14:35:23 Not sure what th ebest way to proceed is, though 14:35:23 Sounds good. Skip again then? 14:35:38 Maybe? :) 14:35:45 !propose skip 14:35:45 #idea Proposed for #2279: Skip this issue for this triage session. 14:35:46 Proposed for #2279: Skip this issue for this triage session. 14:36:01 !accept 14:36:01 #agreed Skip this issue for this triage session. 14:36:01 Current proposal accepted: Skip this issue for this triage session. 14:36:02 6 issues left to triage: 2287, 2288, 2289, 2321, 2323, 2326 14:36:03 #topic Cannot get v2 repo tags list - http://pulp.plan.io/issues/2287 14:36:03 Docker Support Issue #2287 [NEW] (unassigned) - Priority: Normal | Severity: Medium | Severity: Medium 14:36:03 Cannot get v2 repo tags list - http://pulp.plan.io/issues/2287 14:36:05 :! 14:37:16 still selinux issues to resolve? 14:37:34 If this really is the same sort of thing as #2277, then it's urgent prio 14:38:03 agreed. I wonder if it's just a duplicate though. 14:38:22 same here 14:38:24 same problem, slightly different symptom. 14:38:56 bmbouter, any thoughts? 14:39:25 it looks like he reproduced on systems that have a fix for 2277 14:40:01 #2277 isn't POST or MODIFIED, so I'm not sure we have a fix for that yet (it went back to ASSIGNED 2 days ago) 14:40:05 Right, but I think it was extablished on #2277 that the fix was insufficient. 14:40:23 oh ok, i was just looking at the pr which was merged 14:40:53 Yeah, i's still an issue on 2.10 from what I can see 14:40:58 Lacking input from anyone who is more familiar with this... 14:41:00 !propose skip 14:41:00 #idea Proposed for #2287: Skip this issue for this triage session. 14:41:01 Proposed for #2287: Skip this issue for this triage session. 14:41:04 +1 14:41:20 !accept 14:41:20 #agreed Skip this issue for this triage session. 14:41:20 Current proposal accepted: Skip this issue for this triage session. 14:41:22 #topic unable to access pulp-admin or repositories - http://pulp.plan.io/issues/2288 14:41:22 5 issues left to triage: 2288, 2289, 2321, 2323, 2326 14:41:22 Pulp Issue #2288 [NEW] (unassigned) - Priority: Normal | Severity: Medium | Severity: Medium 14:41:23 +1 sadface 14:41:23 unable to access pulp-admin or repositories - http://pulp.plan.io/issues/2288 14:42:05 I'm not sure what to say about this bug 14:42:43 Looks like a bad upgrade situation to me... stuf still seems to be referencing /srv instead uf /usr/share/pulp 14:42:48 ya, me either. 14:43:05 Maybe they had custom apache config that conflicted with what we provided? 14:43:12 ^ my thought 14:43:23 I suspect it's related to upgrading conffiles (specifically the apache config)...well alright then. 14:43:38 I wonder if another user will experience this? 14:43:51 They might, but this is experience is effectively the correct one 14:43:55 if they modified the apache conf files... amost assuredly 14:43:58 (If it's related to modified apache configs) 14:43:59 oic 14:44:04 i wonder if he ran migrations as root 14:44:10 close as notabug? 14:44:16 pcreech: have not got the change to work on that yet 14:44:19 I think it's notabug. +1 14:44:24 hopefully later today 14:44:29 elyezer: cool, just curious :) 14:44:45 pcreech: I am going to let you know when I do 14:44:55 someone should add a little explanation before it gets closed. 14:44:56 that is getting higher on the task list though 14:45:07 mhrivnak: agreed 14:45:13 volunteer? :) 14:45:14 I can post about the selinux stuff, but not the conf file snaffu 14:45:36 * pcreech reluctantly volunteers... will find a godd conf file as example 14:45:45 s/godd/good/ 14:45:49 thanks! 14:46:05 !propose other pcreech comment and close as notabug 14:46:05 #idea Proposed for #2288: pcreech comment and close as notabug 14:46:06 Proposed for #2288: pcreech comment and close as notabug 14:46:07 might be good to make sure there's actually an rpmnew file that can be used for diffing 14:46:28 yeah perhaps we aren't doing it right but close it now and invite to reopen maybe? 14:46:39 sounds fair 14:47:05 cool. are we ready to move on? 14:47:26 I think so 14:47:40 !accept 14:47:40 #agreed pcreech comment and close as notabug 14:47:41 Current proposal accepted: pcreech comment and close as notabug 14:47:41 #topic Getting Error on pulp installation and configuration - http://pulp.plan.io/issues/2289 14:47:42 4 issues left to triage: 2289, 2321, 2323, 2326 14:47:42 Pulp Issue #2289 [NEW] (unassigned) - Priority: Normal | Severity: Medium | Severity: Medium 14:47:43 Getting Error on pulp installation and configuration - http://pulp.plan.io/issues/2289 14:48:07 The traceback doesn't match the file they provided. 14:48:09 oh yeah this is his fault 14:48:18 line 10 14:48:22 he did that in the wrong place 14:48:27 ill comment and close as not a bug 14:48:31 sounds good. 14:48:51 !propose other close not a bug 14:48:51 #idea Proposed for #2289: close not a bug 14:48:52 Proposed for #2289: close not a bug 14:48:59 +1 14:48:59 bmbouter: That's Numberwang! 14:49:03 :D 14:49:07 haha yes 14:49:08 !accept 14:49:08 #agreed close not a bug 14:49:08 Current proposal accepted: close not a bug 14:49:10 #topic Pulp can't handle mirrorlists with invalid entries - http://pulp.plan.io/issues/2321 14:49:10 3 issues left to triage: 2321, 2323, 2326 14:49:11 RPM Support Issue #2321 [NEW] (unassigned) - Priority: Normal | Severity: Medium | Severity: Medium 14:49:12 Pulp can't handle mirrorlists with invalid entries - http://pulp.plan.io/issues/2321 14:49:46 But...if they're invalid... 14:49:49 * smyers read the bug 14:50:52 I'd rephrase and say that they are valid URLs that do not contain yum repos. 14:51:46 This looks like a regression on master based on his comment. 14:53:00 So... 14:53:01 any suggests? 14:53:04 or proposals? 14:53:11 !propose triage high medium 14:53:11 #idea Proposed for #2321: Priority: High, Severity: Medium 14:53:11 #info smyers has joined triage 14:53:12 smyers has joined triage 14:53:12 ? 14:53:12 Proposed for #2321: Priority: High, Severity: Medium 14:53:22 Do we have a way to express that it should block 2.11.0 but not 2.10.z ? 14:53:33 Prio: Urgent, Version 2.11 14:53:37 (.0) 14:53:53 Seems reasonable. 14:54:01 Then when I look at the blocker report, it looks like this: https://pulp.plan.io/issues?query_id=75 14:54:03 Title: Open Blockers - Pulp (at pulp.plan.io) 14:54:49 !accept 14:54:49 #agreed Priority: High, Severity: Medium 14:54:49 Current proposal accepted: Priority: High, Severity: Medium 14:54:51 #topic Support skipping the standard storage path migration. - http://pulp.plan.io/issues/2323 14:54:51 2 issues left to triage: 2323, 2326 14:54:51 Pulp Issue #2323 [NEW] (unassigned) - Priority: High | Severity: Medium | Severity: Medium 14:54:52 Support skipping the standard storage path migration. - http://pulp.plan.io/issues/2323 14:54:54 but 14:55:01 If it should block 2.11.0 (and that makes sense)... 14:55:14 We should revisit 2321 :) 14:55:22 yes please. :) 14:55:38 !issue 2321 14:55:38 #topic Pulp can't handle mirrorlists with invalid entries - http://pulp.plan.io/issues/2321 14:55:39 RPM Support Issue #2321 [NEW] (unassigned) - Priority: Normal | Severity: Medium | Severity: Medium 14:55:39 Pulp can't handle mirrorlists with invalid entries - http://pulp.plan.io/issues/2321 14:55:43 !propose urgent high 14:55:43 Error: "propose" is not a valid command. 14:55:51 dammit who wrote this crap 14:55:55 !propose triage urgent high 14:55:55 #idea Proposed for #2321: Priority: Urgent, Severity: High 14:55:56 Proposed for #2321: Priority: Urgent, Severity: High 14:56:02 +1 14:56:02 some guy who didn't nkow what he was doing... i guess 14:56:04 +1 14:56:12 version is going to have to me master 14:56:16 is that cool smyers? 14:56:30 asmacdo, why? Does the field need to be updated? 14:56:32 "urgent" feels weird since there's not actual time pressure to do this real soon, but it does fit our process correctly. 14:56:50 agreed and agreed 14:57:10 asmacdo, field updated 14:57:10 smyers, there is no 2.11 version, unless you mean target platform release 14:57:23 Nope, set the version to 2.11.0 14:57:30 You may have to refresh the page 14:57:44 !accept 14:57:44 #agreed Priority: Urgent, Severity: High 14:57:44 Current proposal accepted: Priority: Urgent, Severity: High 14:57:46 #topic Support skipping the standard storage path migration. - http://pulp.plan.io/issues/2323 14:57:46 2 issues left to triage: 2323, 2326 14:57:46 Pulp Issue #2323 [NEW] (unassigned) - Priority: High | Severity: Medium | Severity: Medium 14:57:47 Support skipping the standard storage path migration. - http://pulp.plan.io/issues/2323 14:58:20 not a bug 14:58:24 maybe a task? 14:59:03 This is being handled effectively as an urgent task, but given what I know of it is not a release blocker. 14:59:11 do we need to do anything? sounds like they were going to do it downstream? 14:59:34 we do need to provide one or more patches 14:59:45 !propose other change to a task 14:59:45 #idea Proposed for #2323: change to a task 14:59:45 Proposed for #2323: change to a task 14:59:54 works for me 15:00:00 that would be good 15:00:05 and yes we should provide some patches 15:00:08 do we need to add to this sprint? 15:00:11 I think so 15:00:30 I could make the patches it will be easy 15:00:57 ok, im marking it as groomed also 15:01:07 !accept 15:01:07 #agreed change to a task 15:01:07 Current proposal accepted: change to a task 15:01:08 1 issues left to triage: 2326 15:01:09 #topic Publishes fail - http://pulp.plan.io/issues/2326 15:01:09 RPM Support Issue #2326 [NEW] (unassigned) - Priority: Normal | Severity: Medium | Severity: Medium 15:01:09 Publishes fail - http://pulp.plan.io/issues/2326 15:02:57 seems also related to or a dup of 2277 15:03:02 What'd we do for the last one? Skip because we don't know if it's a dupe of 2277? 15:03:16 based on comments in 2277, this is a new situation affecting 2.11+ 15:03:16 yes. And I commented on it asking if it's a dup of 2277. 15:03:32 that is the new codepath that was recently added 15:03:49 https://pulp.plan.io/issues/2277#note-7 15:03:51 Title: Issue #2277: Content published using move (instead of copy) causes 404 due to selinux denial. - Pulp (at pulp.plan.io) 15:04:11 "(Downloading published content on Pulp 2.11 still fails with an HTTP 404, but due to a different permissions issue, which I'll file a bug for shortly.)" 15:04:18 hm, ok. 15:05:08 I still think it's all probably related, and that #2326 might be a flaw in the fix for #2277. 15:05:18 But there's no hurry to mark as a dup either, so we can keep it separate. 15:05:26 That's what it looks like to me as well 15:05:36 But, y'know, from the peanut gallery. 15:05:59 * mhrivnak passes the popcorn to smyers 15:06:35 !propose skip 15:06:35 #idea Proposed for #2326: Skip this issue for this triage session. 15:06:36 Proposed for #2326: Skip this issue for this triage session. 15:06:45 !suggest mark as related to 2277 15:06:45 #idea mark as related to 2277 15:06:48 +1 15:07:08 * bmbouter grabs a handful of popcorn from smyers 15:07:19 :( 15:07:25 * pcreech holds on to his peanut bag 15:07:40 * asmacdo only has soylent :( 15:07:53 So !accept and !end? :) 15:07:56 !ccept 15:07:56 Error: "ccept" is not a valid command. 15:07:59 !accept 15:07:59 #agreed Skip this issue for this triage session. 15:07:59 Current proposal accepted: Skip this issue for this triage session. 15:08:00 #endmeeting 15:08:00 !end 15:08:00 No issues to triage.