14:43:19 #startmeeting Pulp Triage 2016-08-09 14:43:19 !start 14:43:19 #info asmacdo has joined triage 14:43:19 Meeting started Tue Aug 9 14:43:19 2016 UTC and is due to finish in 60 minutes. The chair is asmacdo. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:43:19 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:43:19 The meeting name has been set to 'pulp_triage_2016_08_09' 14:43:19 asmacdo has joined triage 14:43:35 My opinion is it would make my life /slightly/ easier if everyone chipped in with their specfile changes, but not that much easier. I mean, in the time we've had this discussion, I probably could have reconciled whatever changes needed to be reconciled. 14:43:58 !here 14:43:58 #info jcline has joined triage 14:43:59 jcline has joined triage 14:44:02 good point, jcline 14:44:03 !here 14:44:03 #info pcreech has joined triage 14:44:03 pcreech has joined triage 14:44:05 #info fdobrovo|wfh has joined triage 14:44:05 !here 14:44:05 fdobrovo|wfh has joined triage 14:44:28 #info mhrivnak has joined triage 14:44:28 !here 14:44:28 mhrivnak has joined triage 14:45:05 !next 14:45:07 #topic Permissions docs should include some info on /v2/ - http://pulp.plan.io/issues/2133 14:45:07 5 issues left to triage: 2133, 2134, 2136, 2137, 2142 14:45:08 Pulp Issue #2133 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:45:09 Permissions docs should include some info on /v2/ - http://pulp.plan.io/issues/2133 14:45:25 !propose accept 14:45:25 #idea Proposed for #2133: Leave the issue as-is, accepting its current state. 14:45:26 Proposed for #2133: Leave the issue as-is, accepting its current state. 14:45:38 +1 14:46:04 works for me 14:46:21 !accept 14:46:21 #agreed Leave the issue as-is, accepting its current state. 14:46:22 Current proposal accepted: Leave the issue as-is, accepting its current state. 14:46:23 #topic Updating a repo without specifying checksum_type causes KeyError - http://pulp.plan.io/issues/2134 14:46:23 4 issues left to triage: 2134, 2136, 2137, 2142 14:46:24 RPM Support Issue #2134 [ASSIGNED] (fdobrovo) - Priority: High | Severity: Medium 14:46:25 Updating a repo without specifying checksum_type causes KeyError - http://pulp.plan.io/issues/2134 14:47:26 #info dalley has joined triage 14:47:26 !here 14:47:26 dalley has joined triage 14:47:31 It's from bugzilla and there is not enough info to reproduce it ... 14:48:02 mhrivnak: it states from bugzilla, is there a BZ to associate? 14:48:10 Seems like a regression with the REST API so high/medium or high/high? 14:48:13 pcreech, it's associated. maybe you're not logged in? 14:48:22 (ah, that could be) 14:48:33 * pcreech shakes fist at 'stay logged in' 14:49:06 There is a straight-forward work-around, so I think severity can be medium or low. But I do like high priority. 14:49:27 Or we could wait a few days for more info on reproducibility. 14:49:48 any preference on waiting vs. triaging now? I'm happy either way. 14:49:48 _ 14:49:57 !here 14:49:57 #info jortel has joined triage 14:49:58 I'm for waiting 14:49:58 jortel has joined triage 14:50:01 !propose skip 14:50:01 #idea Proposed for #2134: Skip this issue for this triage session. 14:50:02 Proposed for #2134: Skip this issue for this triage session. 14:50:33 skip, or needinfo? 14:50:52 needinfo I'd think 14:50:57 i think we could needinfo 14:51:24 BZ already has needinfo. 14:51:52 id like to see the pulp apicalls 14:52:17 elyezer: https://github.com/PulpQE/pulp-fixtures/pull/24#issuecomment-238578609 14:52:18 Title: Sign all RPMs with Pulp QE GPG key by elyezer · Pull Request #24 · PulpQE/pulp-fixtures · GitHub (at github.com) 14:52:19 so, looking at the code, the cause is that the config being passed into update(...) contains keys not included in the distributor config 14:52:29 and there's no handling for that 14:52:33 ichimonji10++ 14:52:33 ichimonji10's karma is now 34 14:52:39 (: 14:53:03 !accept 14:53:03 #agreed Skip this issue for this triage session. 14:53:04 Current proposal accepted: Skip this issue for this triage session. 14:53:05 #topic publish step error handling incorrectly assumes open file - http://pulp.plan.io/issues/2136 14:53:05 3 issues left to triage: 2136, 2137, 2142 14:53:06 Pulp Issue #2136 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:53:07 publish step error handling incorrectly assumes open file - http://pulp.plan.io/issues/2136 14:53:43 jsherrill, any guidance on priority from your side? 14:55:18 I think this is largely a case of unclear error reporting. 14:55:25 from the user perspective. 14:55:48 The bug is only triggered if some other problem already occurred. 14:56:25 !propose skip 14:56:25 #idea Proposed for #2136: Skip this issue for this triage session. 14:56:26 Proposed for #2136: Skip this issue for this triage session. 14:56:42 I in-person-pinged jsherrill :) 14:57:07 who is looking at it now. 14:57:09 ah, ok, ill hold off then 14:57:41 mhrivnak: has 2 customer issues attached, but got moved to backlog as well.. so medium? 14:58:19 #idea Proposed for #2136: Leave the issue as-is, accepting its current state. 14:58:19 !propose accept 14:58:19 Proposed for #2136: Leave the issue as-is, accepting its current state. 14:58:56 im not opposed to accepting 14:59:09 +1 14:59:09 but im not sure that there is enough here to reproduce it 15:00:00 unless there are other thoughts, ill accept it 15:00:32 !acceot 15:00:32 Error: "acceot" is not a valid command. 15:00:36 !accept 15:00:36 #agreed Leave the issue as-is, accepting its current state. 15:00:36 Current proposal accepted: Leave the issue as-is, accepting its current state. 15:00:38 #topic Can't delete task agent_unbind - http://pulp.plan.io/issues/2137 15:00:38 2 issues left to triage: 2137, 2142 15:00:39 Pulp Issue #2137 [NEW] (unassigned) - Priority: Normal | Severity: Medium 15:00:40 Can't delete task agent_unbind - http://pulp.plan.io/issues/2137 15:01:03 This is pretty unfortunate. 15:01:29 Cancellation shouldn't require the consumer to still exist. 15:01:45 agreed 15:02:04 workaround is probably to create a consumer of the same name 15:02:06 I thought there was a --force? 15:02:27 I think there is, but maybe in this case they already did unbind without the --force option? 15:02:28 That told pulp to not sync up with the consumer when unbinding, but maybe not 15:03:06 Oh yeah I see. That's not good. 15:03:25 Maybe I'm just uninspired regarding consumer stuff, but I'm not sure this is worth prioritizing. 15:04:15 Any other thoughts on priority? 15:04:35 * jortel thinking on how it would affect satellite 15:04:36 Yeah. It's surprising you can get uncancelable tasks, though, maybe that should be the real issue 15:05:06 It's worth noting that these are not celery tasks. 15:05:20 So at least it's not impacting that whole system. 15:05:43 right, they are agent tasks. this will not affect satellite because they don't use bind/unbind 15:05:45 It's just an annoying record in the DB at this point I think. 15:06:00 rather, the katello agent does not impl bind/unbind. 15:06:32 I think I agree this is just annoying. 15:06:38 med/low sounds good to me from what you all have said 15:06:47 works for me. 15:06:52 works for me, too 15:07:06 !propose triage normal low 15:07:06 #idea Proposed for #2137: Priority: Normal, Severity: Low 15:07:07 Proposed for #2137: Priority: Normal, Severity: Low 15:07:37 +1 15:07:42 #agreed Priority: Normal, Severity: Low 15:07:42 !accept 15:07:42 Current proposal accepted: Priority: Normal, Severity: Low 15:07:43 1 issues left to triage: 2142 15:07:44 #topic Units created with 0-byte files when sync runs out of disk space - http://pulp.plan.io/issues/2142 15:07:44 Docker Support Issue #2142 [NEW] (unassigned) - Priority: High | Severity: High 15:07:45 Units created with 0-byte files when sync runs out of disk space - http://pulp.plan.io/issues/2142 15:08:23 I think this one is pretty bad. 15:08:30 i agree 15:08:47 It caused jluza a lot of pain yesterday. 15:08:58 it has caused him a lot of pain for over a week 15:09:36 there is a related issue https://pulp.plan.io/issues/753 15:09:38 Title: Issue #753: Sync just hangs when running out of diskspace - Pulp (at pulp.plan.io) 15:09:54 I tried reproducing 753 the same way and could not. 15:10:01 oh ok 15:10:19 High/High I guess? Or Urgent? Serving corrupt files seems bad. 15:10:34 mhrivnak, dkliban, I'm used to pain from pulp, but Tim was all bad from this 15:11:37 i think this one should be urgent 15:11:42 ichimonji10: that PR is ready for final review, will flip the labels on it 15:11:45 Since we're using "urgent" to signify release blockers, and I don't think this should block a release necessarily, I'd stick with high/high. 15:12:15 It seems likely that this bug has existed for a lot of releases. 15:12:15 +1 15:12:20 Yep 15:12:26 I do think we should fix it ASAP though. 15:12:27 dkliban, do you think this should block a release? 15:12:32 asmacdo: no 15:12:39 !propose triage high high 15:12:39 #idea Proposed for #2142: Priority: High, Severity: High 15:12:40 Proposed for #2142: Priority: High, Severity: High 15:13:10 mhrivnak: we don't have to set the release on it now, but I think we should try to release it was part of 2.8.8 15:13:38 dkliban, sounds reasonable. Let's add a note that a fix should go on 2.8-dev. 15:13:47 er, I guess it's 2.0-dev 15:14:07 which is the only option for pulp_docker, so we don't need a note. :) 15:14:30 !accept 15:14:30 #agreed Priority: High, Severity: High 15:14:30 Current proposal accepted: Priority: High, Severity: High 15:14:32 No issues to triage. 15:14:44 \o/ 15:15:07 !end 15:15:07 #endmeeting