14:30:02 #startmeeting Pulp Triage 2017-03-21 14:30:02 #info bizhang has joined triage 14:30:02 !start 14:30:02 Meeting started Tue Mar 21 14:30:02 2017 UTC and is due to finish in 60 minutes. The chair is bizhang. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:30:02 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:30:02 The meeting name has been set to 'pulp_triage_2017_03_21' 14:30:02 bizhang has joined triage 14:30:22 !here 14:30:22 #info mhrivnak has joined triage 14:30:23 mhrivnak has joined triage 14:30:25 #info ipanova has joined triage 14:30:25 !here 14:30:25 ipanova has joined triage 14:30:41 #info ttereshc has joined triage 14:30:41 !here 14:30:41 ttereshc has joined triage 14:30:59 !next 14:31:00 !here 14:31:02 #topic pulp not starting properly, apache pulp-manage-db throwing errors - http://pulp.plan.io/issues/2591 14:31:02 #info dkliban has joined triage 14:31:02 4 issues left to triage: 2591, 2642, 2643, 2644 14:31:03 Pulp Issue #2591 [NEW] (unassigned) - Priority: High | Severity: High 14:31:04 pulp not starting properly, apache pulp-manage-db throwing errors - http://pulp.plan.io/issues/2591 14:31:05 dkliban has joined triage 14:32:06 !here 14:32:06 #info daviddavis has joined triage 14:32:07 daviddavis has joined triage 14:32:09 This is the one Kodiak hit over the weekend. We still don't know the root cause, but we do have a reliable and simple workaround. 14:32:24 It's also not reproducible on 2.10 or 2.12. 14:32:37 #info jortel has joined triage 14:32:37 !here 14:32:37 jortel has joined triage 14:33:12 close wontfix? 14:33:13 WONTFIX until we have a reproducer? 14:33:35 I think that's reasonable. 14:33:42 !propose other close WONTFIX 14:33:42 #idea Proposed for #2591: close WONTFIX 14:33:43 Proposed for #2591: close WONTFIX 14:34:22 !accept 14:34:22 #agreed close WONTFIX 14:34:22 would not it be better worksforme? 14:34:22 Current proposal accepted: close WONTFIX 14:34:23 3 issues left to triage: 2642, 2643, 2644 14:34:24 #topic --auth-ca parameter on repo creation not working - http://pulp.plan.io/issues/2642 14:34:24 RPM Support Issue #2642 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:34:25 --auth-ca parameter on repo creation not working - http://pulp.plan.io/issues/2642 14:34:55 I've been looking at this one, but I'm not sure how to get repo auth working in pulp 14:35:07 Does anyone else want to take over? 14:35:37 It's a bit of a black art. Historically, nobody wants to use this feature except Red Hat. :) 14:36:12 well if we're all on the same page for this I can continue trying 14:36:16 #idea Proposed for #2642: needsinfo 14:36:16 !propose other needsinfo 14:36:16 Proposed for #2642: needsinfo 14:36:32 I think the biggest factor here is that there isn't enough documentation. 14:37:02 bizhang, I have a couple thoughts we could look at this afternoon. 14:37:10 yeah, I can update the docs /if/ I can figure out how to get it working with the current docs :P 14:37:15 mhrivnak, that sounds good 14:37:32 Perhaps skip it for now? 14:37:47 !skip 14:37:48 2 issues left to triage: 2643, 2644 14:37:48 #topic DKR1008: Could not find registry API at https://docker-registry.engineering.redhat.com - http://pulp.plan.io/issues/2643 14:37:49 Docker Support Issue #2643 [NEW] (unassigned) - Priority: Normal | Severity: High 14:37:50 DKR1008: Could not find registry API at https://docker-registry.engineering.redhat.com - http://pulp.plan.io/issues/2643 14:38:17 i am working on this 14:38:26 and it seems like the issue is not on the pulp side 14:38:55 ipanova, do you want to comment and close? 14:39:04 i will try to reach other engineers who could tell more details about the internal docker registry to confirm that we're safe here 14:39:09 bizhang: not yet 14:39:28 !propose other skip until ipanova confirms the root cause 14:39:28 #idea Proposed for #2643: skip until ipanova confirms the root cause 14:39:29 Proposed for #2643: skip until ipanova confirms the root cause 14:39:29 bizhang: i mean i don;t to want to close it yet 14:39:37 yup 14:39:41 +1 to skip 14:40:06 #agreed skip until ipanova confirms the root cause 14:40:06 !accept 14:40:06 Current proposal accepted: skip until ipanova confirms the root cause 14:40:08 1 issues left to triage: 2644 14:40:08 #topic pulp fails to correctly process WWW-Authenticate headers - http://pulp.plan.io/issues/2644 14:40:09 Docker Support Issue #2644 [NEW] (unassigned) - Priority: Normal | Severity: High 14:40:10 pulp fails to correctly process WWW-Authenticate headers - http://pulp.plan.io/issues/2644 14:40:34 i am working on this as well 14:40:51 this sounds familiar 14:40:57 ipanova, does it seem like a straight-forward fix? 14:41:11 i am not sure it is correct to give the scope of both push and pull when you're trying just to have read access 14:41:17 mhrivnak: it does 14:41:47 mhrivnak: but since we're having just read access i don't know if we need to forsee pull,push case 14:41:56 I think it's important that pulp can sync from artifactory, so I'd +1 adding to the sprint and getting this done. 14:42:10 mhrivnak: ok, agree 14:42:40 i am just trying to understand if it is correct from the registry side to return both read and write access when just read was requested 14:43:09 !propose other accept and add to sprint 14:43:09 #idea Proposed for #2644: accept and add to sprint 14:43:10 Proposed for #2644: accept and add to sprint 14:43:13 eh, does it matter if they give pulp extra access? 14:43:23 mhrivnak: well not for pulp 14:43:35 mhrivnak: but this way i'd report a bug for artyfactory :-P 14:43:49 Fair enough. 14:44:19 +1 to add to sprint 14:44:41 leave it as normal/high? 14:45:17 ipanova, note that their docker support is not open source, so factor that into prioritization. ;) 14:46:03 mhrivnak: gotcha 14:46:11 normal/high seems reasonable. 14:46:11 i will take care of this 14:46:18 !accept 14:46:18 #agreed accept and add to sprint 14:46:18 Current proposal accepted: accept and add to sprint 14:46:20 No issues to triage. 14:46:22 #endmeeting 14:46:22 !end