15:30:12 #startmeeting Pulp Triage 2017-02-14 15:30:12 #info bizhang has joined triage 15:30:13 Meeting started Tue Feb 14 15:30:12 2017 UTC and is due to finish in 60 minutes. The chair is bizhang. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:30:13 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:30:13 The meeting name has been set to 'pulp_triage_2017_02_14' 15:30:13 bizhang has joined triage 15:30:32 !here 15:30:32 #info ttereshc has joined triage 15:30:33 ttereshc has joined triage 15:30:35 !here 15:30:35 #info preethi has joined triage 15:30:36 preethi has joined triage 15:30:44 !here 15:30:44 #info dkliban has joined triage 15:30:45 dkliban has joined triage 15:30:48 !next 15:30:49 3 issues left to triage: 2544, 2585, 2586 15:30:49 #topic copy always matches every unit in the repo - http://pulp.plan.io/issues/2544 15:30:50 OSTree Support Issue #2544 [NEW] (unassigned) - Priority: Normal | Severity: Medium 15:30:50 copy always matches every unit in the repo - http://pulp.plan.io/issues/2544 15:31:01 !here 15:31:01 #info ipanova has joined triage 15:31:01 ipanova has joined triage 15:31:01 !here 15:31:01 #info mhrivnak has joined triage 15:31:02 mhrivnak has joined triage 15:31:06 !propose other accept and add to sprint 15:31:06 #idea Proposed for #2544: accept and add to sprint 15:31:07 Proposed for #2544: accept and add to sprint 15:31:10 +1 15:31:20 +1 15:31:27 +1 to add to the sprint 15:31:33 +1 15:31:36 !accept 15:31:36 #agreed accept and add to sprint 15:31:36 Current proposal accepted: accept and add to sprint 15:31:37 #topic Bugs fixed in version link is not correct for plugins - http://pulp.plan.io/issues/2585 15:31:38 2 issues left to triage: 2585, 2586 15:31:38 Pulp Issue #2585 [NEW] (unassigned) - Priority: Normal | Severity: Medium 15:31:39 Bugs fixed in version link is not correct for plugins - http://pulp.plan.io/issues/2585 15:32:26 add to the sprint as well? 15:32:57 does this need to be filed individually for each plugin? 15:33:21 bizhang: if we make it a task, we can make a generic one 15:33:24 It's likely going to get fixed in one place (platform) 15:33:41 I think it's an easyfix and it can be done all at once 15:33:45 +1 15:33:52 !propose other accept and add to sprint 15:33:52 #idea Proposed for #2585: accept and add to sprint 15:33:52 Proposed for #2585: accept and add to sprint 15:34:00 +1 15:34:00 +1 15:34:03 +1 15:34:09 !accept 15:34:09 #agreed accept and add to sprint 15:34:09 Current proposal accepted: accept and add to sprint 15:34:11 #topic Pulp workers/beat/resource_manager go missing - http://pulp.plan.io/issues/2586 15:34:11 1 issues left to triage: 2586 15:34:11 Pulp Issue #2586 [NEW] (unassigned) - Priority: Normal | Severity: High 15:34:12 Pulp workers/beat/resource_manager go missing - http://pulp.plan.io/issues/2586 15:35:20 !here 15:35:20 #info dalley has joined triage 15:35:20 dalley has joined triage 15:35:26 !here 15:35:26 #info bmbouter has joined triage 15:35:27 bmbouter has joined triage 15:35:42 we should look into this to help support katello's effort 15:35:50 yep 15:35:57 let's add it to the sprint 15:35:59 I talked w/ ehelms when this was filed and he provided the reproducer 15:36:04 +1 to adding to sprint 15:36:31 works for me 15:36:40 it's very likely an environmental issue, but one we can help identify 15:36:44 !propose other accept and add to sprint 15:36:44 #idea Proposed for #2586: accept and add to sprint 15:36:45 Proposed for #2586: accept and add to sprint 15:37:14 should sev be high? 15:37:34 bizhang: it's doesn't matter. as long as we add to sprint 15:37:53 I don't have an opinion on the sev 15:38:07 It sorta does, since that's for more than just triage (ideally?) 15:38:37 fair enough 15:38:51 I don't see anything in the issue that says it should be high, but upon reproducing it, maybe we revisit it 15:38:53 I dunno 15:38:56 I think high severity is appropriate. 15:39:07 workers going missing is real bad. 15:39:19 that sounds fine 15:39:26 I still think it's environmental so it's severe for this 1 user 15:39:33 I would say prio should be high 15:39:38 is it a development environment issue or one that shows up uiversally? 15:39:42 ^^ 15:39:50 only in this 1 environment have I heard about it 15:40:05 with a clear reproducer but no hint as to what's going on, severity is almost undefined. Priority should be high to resolve severity asap :) 15:40:12 and 2.10.z has been out a while so if it was really this severe I think we would be hearing about it all the time 15:40:28 yeah I would say prio to high, sev to med or high 15:40:40 !propose other triage high/? add to sprint 15:40:40 #idea Proposed for #2586: triage high/? add to sprint 15:40:41 Maybe even urgent 15:40:41 Proposed for #2586: triage high/? add to sprint 15:40:54 Because, as mhrivnak, if workers are going missing, that's bad. 15:40:57 (said) 15:41:06 +1 urgent prio, high sev 15:41:11 +1 15:41:18 The problem the user experienced is severe. If we can identify the cause is already fixed, environmental, etc. that's great, but I don't think it changes the severity of what's reported. 15:41:25 that is fine 15:41:30 !propose triage other Urgent/High, add to sprint 15:41:31 (propose triage [target_release]) -- Propose triage values including priority, severity, and an optional target release. 15:41:38 Iw rote this thing. I'm terrible. 15:41:44 I don't know for certain that it is environmental so that sounds good 15:41:47 !propose other Urgent/High, add to sprint 15:41:47 #idea Proposed for #2586: Urgent/High, add to sprint 15:41:47 #info smyers has joined triage 15:41:47 smyers has joined triage 15:41:48 Proposed for #2586: Urgent/High, add to sprint 15:41:54 +1 15:42:02 !accept 15:42:02 #agreed Urgent/High, add to sprint 15:42:02 Current proposal accepted: Urgent/High, add to sprint 15:42:04 No issues to triage. 15:42:06 !end 15:42:06 #endmeeting