14:29:58 #startmeeting Pulp Triage 2017-03-24 14:29:58 Meeting started Fri Mar 24 14:29:58 2017 UTC and is due to finish in 60 minutes. The chair is bizhang. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:29:58 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:29:58 The meeting name has been set to 'pulp_triage_2017_03_24' 14:29:58 #info bizhang has joined triage 14:29:58 bizhang has joined triage 14:30:02 !here 14:30:02 #info smyers has joined triage 14:30:02 smyers has joined triage 14:30:08 !here 14:30:08 #info ipanova has joined triage 14:30:08 ipanova has joined triage 14:30:13 !here 14:30:13 #info ttereshc has joined triage 14:30:14 ttereshc has joined triage 14:30:20 !here 14:30:20 #info mhrivnak has joined triage 14:30:20 mhrivnak has joined triage 14:30:24 !next 14:30:25 #topic Broker reconnect support broken - http://pulp.plan.io/issues/2613 14:30:26 6 issues left to triage: 2613, 2642, 2654, 2655, 2657, 2659 14:30:27 Pulp Issue #2613 [ASSIGNED] (dalley) - Priority: Normal | Severity: Medium 14:30:28 Broker reconnect support broken - http://pulp.plan.io/issues/2613 14:30:41 !here 14:30:41 #info bmbouter has joined triage 14:30:42 bmbouter has joined triage 14:31:16 ASSIGNED and already on the sprint 14:31:31 I think it was untriaged to discuss if it should be a 2.13 blocker 14:31:32 !here 14:31:32 #info dalley_ has joined triage 14:31:32 dalley_ has joined triage 14:31:40 correct bizhang 14:32:38 !propose other triage high/normal keep 2.13 blocker status 14:32:38 #idea Proposed for #2613: triage high/normal keep 2.13 blocker status 14:32:39 I have no reason to change ichimonji10's decision in #9 14:32:39 Proposed for #2613: triage high/normal keep 2.13 blocker status 14:32:43 =1 14:32:46 also +1 14:32:46 +1 14:32:49 Is there anything specific to discuss? 14:32:50 thomasmckay: not for now 14:32:53 I'm not sure what changed. 14:33:20 !accept 14:33:20 #agreed triage high/normal keep 2.13 blocker status 14:33:20 Current proposal accepted: triage high/normal keep 2.13 blocker status 14:33:21 #topic --auth-ca parameter on repo creation not working - http://pulp.plan.io/issues/2642 14:33:22 5 issues left to triage: 2642, 2654, 2655, 2657, 2659 14:33:23 RPM Support Issue #2642 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:33:24 --auth-ca parameter on repo creation not working - http://pulp.plan.io/issues/2642 14:33:29 mhrivnak, when the issue was first discussed it was completely different than it is now 14:33:39 it was thought to be an issue only w/ Celery 4 14:34:10 the actual issue is that some new celery functionality we're using in 2.13 has a defect to where broker reconnect support is broken with both Celery 3 & 4 14:34:31 it was untriaged also because I rewrote the issue with that new info 14:34:42 Gotcha, ok. 14:35:13 #2642 looks rough, can anyone tell for sure if it's broken, or just a super confusing workflow that's easy to mess up (and got messed up)? 14:35:35 bizhang has looked at this one a lot. 14:35:44 Looks like it might be a legit bug. 14:35:55 Yeah, that's the sense I'm getting 14:36:38 Yeah I think it's our pulp_content.conf's sslverifyclient not checking the client cert 14:37:02 setting it to optional_no_ca fixes the issues 14:37:03 !propose accept 14:37:03 #idea Proposed for #2642: Leave the issue as-is, accepting its current state. 14:37:03 Proposed for #2642: Leave the issue as-is, accepting its current state. 14:37:43 but I'm not sure if that's the correct resolution, anyways +1 accept 14:38:23 !accept 14:38:23 #agreed Leave the issue as-is, accepting its current state. 14:38:23 Current proposal accepted: Leave the issue as-is, accepting its current state. 14:38:24 4 issues left to triage: 2654, 2655, 2657, 2659 14:38:25 I don't think they're mutually exclusive, maybe get on the mailing list to ofer that as a workaround, but still fix the bug :) 14:38:25 #topic Pulp3 isn't logging the first 8 characters of a task id in every log statement emitted from a running task - http://pulp.plan.io/issues/2654 14:38:26 Pulp Issue #2654 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:38:27 Pulp3 isn't logging the first 8 characters of a task id in every log statement emitted from a running task - http://pulp.plan.io/issues/2654 14:38:35 heh 14:38:42 smyers, that sounds like a good plan :) 14:39:04 This one is a fix made in pulp2 that was not merged forward to pulp3 14:39:07 !propose accept 14:39:07 #idea Proposed for #2654: Leave the issue as-is, accepting its current state. 14:39:08 Proposed for #2654: Leave the issue as-is, accepting its current state. 14:39:10 That's not a bug, imo 14:39:14 agreed. 14:39:38 Convert to story, "pulp 2 does this, pulp 3 should too, merging forward didn't work so we have to do it the hard way" 14:39:45 I'm glad we have something in redmine to track it, but I wouldn't call it a bug. 14:39:52 agree 14:39:56 !propose other convert to story 14:39:56 #idea Proposed for #2654: convert to story 14:39:57 Proposed for #2654: convert to story 14:40:05 +1 14:40:06 +1 14:40:09 !accept 14:40:09 #agreed convert to story 14:40:09 Current proposal accepted: convert to story 14:40:11 #topic units_successful is empty for successful ISO assocaiting task - http://pulp.plan.io/issues/2655 14:40:11 3 issues left to triage: 2655, 2657, 2659 14:40:12 RPM Support Issue #2655 [ASSIGNED] (ipanova@redhat.com) - Priority: Normal | Severity: High 14:40:13 units_successful is empty for successful ISO assocaiting task - http://pulp.plan.io/issues/2655 14:40:34 while i was looking into it i found the issue and the fix 14:40:54 mind triaging it and adding to the sprint? 14:41:01 +1 14:41:17 I question the high severity... 14:41:29 !propose other normal/medium add to sprint 17 14:41:29 #idea Proposed for #2655: normal/medium add to sprint 17 14:41:29 Proposed for #2655: normal/medium add to sprint 17 14:41:49 +1 14:41:56 This is a blocker to upgrade for a key user, because they depend on that field being populated. 14:42:13 So I suppose they consider it "severe" since it blocks them. 14:42:29 But otherwise I agree that medium seems appropriate. 14:42:37 +1 14:42:50 the fix is 1 line, let's move ^_^ 14:42:54 !accept 14:42:54 #agreed normal/medium add to sprint 17 14:42:54 Current proposal accepted: normal/medium add to sprint 17 14:42:56 #topic Publishing iso_rsync_distributor fails when iso_distributor is published with serve_https==False - http://pulp.plan.io/issues/2657 14:42:56 2 issues left to triage: 2657, 2659 14:42:57 RPM Support Issue #2657 [ASSIGNED] (ipanova@redhat.com) - Priority: Normal | Severity: Medium 14:42:58 Publishing iso_rsync_distributor fails when iso_distributor is published with serve_https==False - http://pulp.plan.io/issues/2657 14:43:04 ipanova++ 14:43:04 ipanova's karma is now 34 14:43:05 same here 14:43:22 prio and sev are used by QE, for example, after the bug is fixed. They still matter even after we fix the bug. 14:43:57 !propose other accept and add to sprint 14:43:57 #idea Proposed for #2657: accept and add to sprint 14:43:57 Proposed for #2657: accept and add to sprint 14:44:26 +1 14:44:31 +1 14:44:38 !accept 14:44:38 #agreed accept and add to sprint 14:44:38 Current proposal accepted: accept and add to sprint 14:44:39 +1 14:44:41 1 issues left to triage: 2659 14:44:41 #topic Stale worker documents present in the db for Pulp3 - http://pulp.plan.io/issues/2659 14:44:42 Pulp Issue #2659 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:44:43 Stale worker documents present in the db for Pulp3 - http://pulp.plan.io/issues/2659 14:44:48 !propose other convert to story 14:44:48 #idea Proposed for #2659: convert to story 14:44:49 Proposed for #2659: convert to story 14:44:54 +1 14:44:58 this is another pulp2->3 merge issue 14:45:08 !accept 14:45:08 #agreed convert to story 14:45:08 Current proposal accepted: convert to story 14:45:10 No issues to triage. 14:45:15 !end 14:45:15 #endmeeting