14:30:13 #startmeeting Pulp Triage 2016-09-13 14:30:13 #info asmacdo has joined triage 14:30:13 !start 14:30:13 Meeting started Tue Sep 13 14:30:13 2016 UTC and is due to finish in 60 minutes. The chair is asmacdo. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:30:13 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:30:13 The meeting name has been set to 'pulp_triage_2016_09_13' 14:30:13 asmacdo has joined triage 14:30:20 !here 14:30:20 #info mhrivnak has joined triage 14:30:21 mhrivnak has joined triage 14:30:23 !here 14:30:23 #info pcreech has joined triage 14:30:23 pcreech has joined triage 14:30:23 !here 14:30:23 #info ipanova has joined triage 14:30:23 ipanova has joined triage 14:30:45 !here 14:30:45 #info jcline has joined triage 14:30:46 jcline has joined triage 14:30:50 !here 14:30:50 #info ttereshc has joined triage 14:30:51 ttereshc has joined triage 14:31:14 !next 14:31:15 #topic last_published field should not be updated when the publish is skipped - http://pulp.plan.io/issues/2244 14:31:16 5 issues left to triage: 2244, 2248, 2249, 2250, 2251 14:31:17 Pulp Issue #2244 [NEW] (unassigned) - Priority: Normal | Severity: Medium | Severity: Medium 14:31:17 !here 14:31:17 #info fdobrovo has joined triage 14:31:17 last_published field should not be updated when the publish is skipped - http://pulp.plan.io/issues/2244 14:31:18 fdobrovo has joined triage 14:31:59 dkliban, is this a regression? 14:32:31 asmacdo: not really 14:33:05 i think this somehow infuencies rsync logic, dkliban is it a requirement for rcm? 14:33:08 Is it blocking the rsync distributor's completion? 14:33:35 !here 14:33:35 #info bmbouter has joined triage 14:33:35 bmbouter has joined triage 14:34:19 can we skip it and return to it later? 14:34:22 dkliban knows better, but I believe it is blocking them 14:34:31 !propose skip 14:34:31 #idea Proposed for #2244: Skip this issue for this triage session. 14:34:31 Proposed for #2244: Skip this issue for this triage session. 14:34:38 +1 to skip 14:34:41 works for me. 14:34:41 +1 14:34:42 +1 14:34:42 !accept 14:34:42 #agreed Skip this issue for this triage session. 14:34:42 Current proposal accepted: Skip this issue for this triage session. 14:34:44 #topic metadata file copy results in error 'Content import of FILENAME failed - must be an existing file' - http://pulp.plan.io/issues/2248 14:34:44 4 issues left to triage: 2248, 2249, 2250, 2251 14:34:45 RPM Support Issue #2248 [NEW] (unassigned) - Priority: Normal | Severity: High | Severity: High 14:34:46 metadata file copy results in error 'Content import of FILENAME failed - must be an existing file' - http://pulp.plan.io/issues/2248 14:35:24 !here 14:35:24 #info dkliban has joined triage 14:35:25 dkliban has joined triage 14:35:51 I have seen this error before, but I think we need a reproducer to triage 14:36:03 asmacdo: i left a comment 14:36:09 reproducer is listed 14:36:11 looks like ipanova added reproducer steps. 14:36:19 O.o 14:36:24 ipanova++ 14:36:24 ipanova's karma is now 21 14:36:35 !propose accept 14:36:35 #idea Proposed for #2248: Leave the issue as-is, accepting its current state. 14:36:36 Proposed for #2248: Leave the issue as-is, accepting its current state. 14:36:55 +1 14:37:05 i am not sure what to do about that, because i do not see any solution for that 14:37:27 Right. 14:37:47 Seems like we at least need to provide guidance on how to get out of that situation. 14:38:08 mhrivnak: yeah, re-sync if repo with feed 14:38:19 if repo without feed than user is screwed up 14:38:51 jsherrill, any guidance? 14:39:02 is it hard to add a storage path check in the orphan cleanup? 14:39:10 reading 14:39:26 pcreech, I'm not sure what it would check. 14:39:41 pcreech, maybe it could check to see if any other units reference the same file path. 14:39:49 that was my thinking 14:39:49 But that could get expensive quickly. 14:40:17 pcreech: if the user got upgraded to 2.8. no check of storage path would help i gues 14:40:20 guess 14:40:21 mhrivnak: ipanova so the reproducer steps seems to conflict slightly with what the user claimed. they said that they were able to do step 9 successfully after step 7 14:40:23 theoretically expensive or real-world expensive? (I'm not familiar enough, but this is also digressing into details of a solution not neccissarily appropriate for triate) 14:40:37 mhrivnak: ipanova but then later on it failed with this error 14:40:39 triage* 14:40:42 pcreech: 2.8.6 14:41:17 jsherrill: there could be successful copies for units that before the upgrade where not copied, then copy removed and orphans cleaned 14:41:21 pcreech, I think it theoretically would be n^2 performance. 14:41:26 jsherrill: or successful copied for newly arrived content into pulp after upgrade 14:42:09 !propose other skip for now and discuss with jsherrill more specifically what can be done for users who encounter this 14:42:09 #idea Proposed for #2248: skip for now and discuss with jsherrill more specifically what can be done for users who encounter this 14:42:10 Proposed for #2248: skip for now and discuss with jsherrill more specifically what can be done for users who encounter this 14:42:18 +1 14:42:30 !accept 14:42:30 #agreed skip for now and discuss with jsherrill more specifically what can be done for users who encounter this 14:42:31 Current proposal accepted: skip for now and discuss with jsherrill more specifically what can be done for users who encounter this 14:42:32 #topic Document platform Django app layout - http://pulp.plan.io/issues/2249 14:42:32 3 issues left to triage: 2249, 2250, 2251 14:42:32 Pulp Issue #2249 [NEW] (unassigned) - Priority: Normal | Severity: Medium | Severity: Medium 14:42:33 Document platform Django app layout - http://pulp.plan.io/issues/2249 14:42:43 jsherrill: not sure if what i said makes sense 14:42:54 sounds like a task, and not an issue? 14:43:06 ipanova: not sure i quite understand it, but that is likely not your fault :) 14:43:26 bmbouter, do you agree this should be a task? 14:43:26 mhrivnak, i agree 14:43:28 +1 for the task 14:43:31 !propose other make it a task 14:43:31 #idea Proposed for #2249: make it a task 14:43:32 Proposed for #2249: make it a task 14:43:43 jsherrill: we will discuss that later 14:43:50 +1 14:44:36 !accept 14:44:36 #agreed make it a task 14:44:37 Current proposal accepted: make it a task 14:44:37 #topic Add a new Jenkins job to run pulp-smash against Fedora-provided packages - http://pulp.plan.io/issues/2250 14:44:38 2 issues left to triage: 2250, 2251 14:44:39 Packaging Issue #2250 [NEW] (unassigned) - Priority: Normal | Severity: Medium | Severity: Medium 14:44:40 Add a new Jenkins job to run pulp-smash against Fedora-provided packages - http://pulp.plan.io/issues/2250 14:45:00 !propose other make it a task 14:45:00 #idea Proposed for #2250: make it a task 14:45:00 also a task? 14:45:00 Proposed for #2250: make it a task 14:45:15 +1 14:45:32 +1 14:45:46 +1 14:45:54 !accept 14:45:54 #agreed make it a task 14:45:54 Current proposal accepted: make it a task 14:45:55 1 issues left to triage: 2251 14:45:56 #topic Error on sync: sequence item 0: expected string, NoneType found - http://pulp.plan.io/issues/2251 14:45:56 Pulp Issue #2251 [NEW] (unassigned) - Priority: Normal | Severity: Medium | Severity: Medium 14:45:57 Error on sync: sequence item 0: expected string, NoneType found - http://pulp.plan.io/issues/2251 14:46:42 * mhrivnak scrolls forever to the right 14:47:16 sounds like maybe the proxy isn't configured correctly. 14:47:24 traceback leads to proxy issue 14:47:31 _add_proxy(session, config)\n File \"/usr/lib/python2.7/site-packages/nectar/downloaders/threaded.py\", line 400, in _add_proxy\n url = ':'.join((host, str(config.proxy_port)))\nTypeError: sequence item 0: expected string, NoneType found\n" 14:47:50 That code path is dead on the master branch 14:48:23 So it's fixed. It sounds like a work around would be to explicitly define a proxy port 14:48:37 Sounds good. 14:49:13 Should we put the issue at MODIFIED? 14:49:20 I'll leave a comment on the work-around 14:49:27 !suggest jcline closes and adds comment for work around 14:49:27 #idea jcline closes and adds comment for work around 14:49:38 I don't think it should be MODIFIED 14:49:52 closed as a duplicate? 14:50:05 or maybe worksforme ? 14:50:10 No, the code is still broken, it's just not used by us anymore 14:50:17 ok, what do you suggest? 14:50:18 CLOSED - WONTFIX 14:50:36 the bug is filed against pulp, the problem is in nectar 14:50:39 I left the function as the nectar API isn't really defined 14:50:44 the pulp code no longer uses this nectar code 14:50:49 so i think closed-current realease 14:50:52 I'll fix that as well 14:50:56 jcline, am I wrong? 14:51:44 The bug in the code is still there. We just aren't going to fix it because we don't use that function or any function that does use it. 14:51:50 I see. Either of those seems reasonable. 14:51:55 !propose other close-wontfix 14:51:55 #idea Proposed for #2251: close-wontfix 14:51:56 Proposed for #2251: close-wontfix 14:52:33 !accept 14:52:33 #agreed close-wontfix 14:52:33 Current proposal accepted: close-wontfix 14:52:35 No issues to triage. 14:52:52 !issue 2244 14:53:01 !issue 2244 14:53:01 #topic last_published field should not be updated when the publish is skipped - http://pulp.plan.io/issues/2244 14:53:02 Pulp Issue #2244 [NEW] (unassigned) - Priority: Normal | Severity: Medium | Severity: Medium 14:53:03 last_published field should not be updated when the publish is skipped - http://pulp.plan.io/issues/2244 14:54:06 i filed this issue because jluza was experiencing a problem related to this ... however, i was not able to actually reproduce a problem with this 14:54:27 ah, suggestion? 14:54:45 asmacdo: we can close it as not a bug 14:54:46 dkliban: i think it would be good if jluza would provide some exact steps and context 14:55:02 ipanova: he emailed me yesterday saying that he could not reproduce the problem on 2.10 14:55:10 Sounds good. 14:55:19 !propose other close-notabug 14:55:19 #idea Proposed for #2244: close-notabug 14:55:20 Proposed for #2244: close-notabug 14:55:45 dkliban: if he was not able to reproduce it then let's close it 14:55:56 !accept 14:55:56 Current proposal accepted: close-notabug 14:55:56 #agreed close-notabug 14:55:57 No issues to triage. 14:56:05 ipanova: i agree 14:57:12 thanks everyone! 14:57:23 ttereshc: back to you https://github.com/pulp/pulp_rpm/pull/985 14:57:24 Title: Fix unit association if unit was downloaded for the second time by goosemania · Pull Request #985 · pulp/pulp_rpm · GitHub (at github.com) 14:57:28 !end 14:57:28 #endmeeting