14:30:16 #startmeeting Pulp Triage 2016-07-08 14:30:16 #info dkliban has joined triage 14:30:17 Meeting started Fri Jul 8 14:30:16 2016 UTC and is due to finish in 60 minutes. The chair is dkliban. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:30:17 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:30:17 The meeting name has been set to 'pulp_triage_2016_07_08' 14:30:17 dkliban has joined triage 14:30:27 https://pulp.plan.io/issues?query_id=30 14:30:29 Title: Un-Triaged Bugs - Pulp (at pulp.plan.io) 14:30:39 #info bmbouter has joined triage 14:30:39 !here 14:30:40 bmbouter has joined triage 14:30:46 !here 14:30:46 #info mhrivnak has joined triage 14:30:47 mhrivnak has joined triage 14:30:58 !next 14:30:59 #topic As a user, I want pulp-manage-db to show a basic progress indicator with each migration, so I can see that the migration is in progress and not hung up - http://pulp.plan.io/issues/2059 14:31:00 8 issues left to triage: 2059, 2060, 2061, 2062, 2063, 2066, 2067, 2068 14:31:01 Pulp Issue #2059 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:31:02 As a user, I want pulp-manage-db to show a basic progress indicator with each migration, so I can see that the migration is in progress and not hung up - http://pulp.plan.io/issues/2059 14:31:15 I think this is a story and not a bug 14:31:19 agreed. 14:31:54 !here 14:31:54 #info dalley has joined triage 14:31:55 dalley has joined triage 14:31:58 i am going to change it to a story and leave a comment. ready for the next one? 14:32:04 Looking ahead, that's also true for @2060 14:32:20 !here 14:32:20 #info smyers has joined triage 14:32:21 smyers has joined triage 14:32:23 ok.... are we ready for 2061 then ? 14:32:29 sure. 14:32:38 !here 14:32:38 #info ipanova has joined triage 14:32:39 ipanova has joined triage 14:32:43 !next 14:32:44 7 issues left to triage: 2060, 2061, 2062, 2063, 2066, 2067, 2068 14:32:45 #topic As a user, I want pulp-manage-db to output a message before any "known big migrations", so that I am aware that the migration could potentially be time-consuming - http://pulp.plan.io/issues/2060 14:32:45 Pulp Issue #2060 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:32:46 As a user, I want pulp-manage-db to output a message before any "known big migrations", so that I am aware that the migration could potentially be time-consuming - http://pulp.plan.io/issues/2060 14:32:50 !next 14:32:51 6 issues left to triage: 2061, 2062, 2063, 2066, 2067, 2068 14:32:53 #topic [Errno 13] Permission denied when using symlink to a different partition - http://pulp.plan.io/issues/2061 14:32:53 Pulp Issue #2061 [NEW] (unassigned) - Priority: Normal | Severity: Urgent 14:32:54 [Errno 13] Permission denied when using symlink to a different partition - http://pulp.plan.io/issues/2061 14:33:29 this was an selinux error 14:33:45 also definitely not severity urgent since a workaround exists 14:33:47 He's going to run into another error later, I think. I'm leaving a comment. 14:34:15 currently this bug is about adding a documentation note to the installer 14:34:24 but I asked him where to add it and didn't get a response 14:35:12 I guess a note right at the beginning to be aware of SELinux? Would that really be helpful, though? 14:36:24 bmbouter: so i am going to add a documentation tag to this ... right? 14:36:31 +1 doc tag 14:36:41 I like the docs tag, and tone down the severity a lot 14:36:48 !propose triage Normal medium 14:36:48 #idea Proposed for #2061: Priority: Normal, Severity: Medium 14:36:49 Proposed for #2061: Priority: Normal, Severity: Medium 14:36:59 Works for me 14:37:04 +1 14:37:30 !accept 14:37:30 #agreed Priority: Normal, Severity: Medium 14:37:31 Current proposal accepted: Priority: Normal, Severity: Medium 14:37:32 #topic Content sources refresh fails if content source name is not defined - http://pulp.plan.io/issues/2062 14:37:32 5 issues left to triage: 2062, 2063, 2066, 2067, 2068 14:37:33 Pulp Issue #2062 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:37:34 Content sources refresh fails if content source name is not defined - http://pulp.plan.io/issues/2062 14:38:13 We should just improve the docs to say which fields are required. 14:38:42 i'll documentation tag 14:38:56 !propose accept 14:38:56 #idea Proposed for #2062: Leave the issue as-is, accepting its current state. 14:38:56 Proposed for #2062: Leave the issue as-is, accepting its current state. 14:39:08 +1 14:39:17 +1 14:39:20 +1 14:39:24 !accept 14:39:24 #agreed Leave the issue as-is, accepting its current state. 14:39:24 Current proposal accepted: Leave the issue as-is, accepting its current state. 14:39:25 4 issues left to triage: 2063, 2066, 2067, 2068 14:39:25 #topic Trouble connecting to LDAP(Active Directory) Server Whole API Authentication - http://pulp.plan.io/issues/2063 14:39:26 Pulp Issue #2063 [NEW] (unassigned) - Priority: Normal | Severity: High 14:39:26 !here 14:39:26 #info jcline has joined triage 14:39:26 Trouble connecting to LDAP(Active Directory) Server Whole API Authentication - http://pulp.plan.io/issues/2063 14:39:27 jcline has joined triage 14:39:48 We need more info on this one. 14:40:01 mhrivnak: want to leave a comment? 14:41:11 sure. 14:41:57 are we ready to move on to 2066? 14:42:18 +1 14:42:20 actually, i already commented on 2066 cause it needs more info 14:42:30 !next 14:42:31 #topic rsync distributor - retry on failed rsync commands - http://pulp.plan.io/issues/2066 14:42:32 3 issues left to triage: 2066, 2067, 2068 14:42:33 !next 14:42:33 Pulp Issue #2066 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:42:34 rsync distributor - retry on failed rsync commands - http://pulp.plan.io/issues/2066 14:42:34 #topic non-ascii message to gofer segfaults httpd - http://pulp.plan.io/issues/2067 14:42:35 2 issues left to triage: 2067, 2068 14:42:36 Pulp Issue #2067 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:42:37 non-ascii message to gofer segfaults httpd - http://pulp.plan.io/issues/2067 14:43:00 should we close 2067 as closed current release? 14:43:16 I think that's true 14:43:19 Yes. 14:44:58 I agree 14:45:15 !propose triage close 14:45:15 (propose triage [target_release]) -- Propose triage values including priority, severity, and an optional target release. 14:45:21 !next 14:45:22 1 issues left to triage: 2068 14:45:22 #topic HTTP 404: When trying to run yum update from a pulp-consumer - http://pulp.plan.io/issues/2068 14:45:23 Pulp Issue #2068 [NEW] (unassigned) - Priority: Normal | Severity: High 14:45:24 HTTP 404: When trying to run yum update from a pulp-consumer - http://pulp.plan.io/issues/2068 14:46:24 is this related to the previous bug he filed about selinux? 14:46:30 seems likely. 14:47:01 agreed 14:47:07 +1 14:47:14 I'd say we ask for tracebacks from the logs to be sure, but yeah 14:47:14 i am going to leave a comment and close it as not a bug 14:47:28 ask him to reproduce with selinux in Permissive mode 14:47:31 maybe 14:47:31 ok 14:47:45 i'll leave a note and keep it open for now 14:48:00 !here 14:48:00 #info jortel has joined triage 14:48:01 jortel has joined triage 14:48:04 !next 14:48:05 No issues to triage. 14:48:10 do we have docs about bind mounting instead of symlinking? 14:48:20 hahaha, joined just in time :) 14:48:22 I thought so 14:48:25 !end 14:48:25 #endmeeting