15:40:27 #startmeeting Pulp Triage 2016-09-23 15:40:27 #info pcreech has joined triage 15:40:27 Meeting started Fri Sep 23 15:40:27 2016 UTC and is due to finish in 60 minutes. The chair is pcreech. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:40:27 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:40:27 The meeting name has been set to 'pulp_triage_2016_09_23' 15:40:27 pcreech has joined triage 15:40:40 !here 15:40:40 #info dkliban has joined triage 15:40:40 dkliban has joined triage 15:40:43 !here 15:40:43 #info mhrivnak has joined triage 15:40:44 mhrivnak has joined triage 15:41:09 !here 15:41:09 #info bmbouter has joined triage 15:41:10 bmbouter has joined triage 15:41:23 !next 15:41:29 8 issues left to triage: 2252, 2272, 2274, 2276, 2277, 2278, 2279, 2280 15:41:34 #topic Repo sync with "epoch" related error message. - http://pulp.plan.io/issues/2252 15:41:35 RPM Support Issue #2252 [NEW] (unassigned) - Priority: Normal | Severity: Medium | Severity: Medium 15:41:35 Repo sync with "epoch" related error message. - http://pulp.plan.io/issues/2252 15:41:40 ipanova, jortel preethi smyers ttereshc ^ in case you didn't see triage starting 15:41:59 #info ipanova has joined triage 15:41:59 !here 15:41:59 ipanova has joined triage 15:42:03 !here 15:42:03 #info ttereshc has joined triage 15:42:03 ttereshc has joined triage 15:42:04 looks like this one seems to be user environemtn, and his last comment was that it's resolved 15:42:13 !propose other CLOSED 15:42:13 #idea Proposed for #2252: CLOSED 15:42:13 Proposed for #2252: CLOSED 15:42:21 agreed 15:42:23 +1 15:42:29 WONTFIX? 15:42:33 !here 15:42:33 #info jortel has joined triage 15:42:34 jortel has joined triage 15:42:39 or WORKSFORME ? 15:42:41 it is a bug and we aren't fixing it 15:42:47 i'd vote for worksforme 15:42:50 Is it a bug? 15:43:03 if you upgraded from old versions of pulp 15:43:11 and synced with an old version, I'm not sure how old 15:43:33 before mongoengine it was the wild west in the database 15:44:05 yes, but these unit types have always had an epoch. 15:44:09 Ok. So, did he just go from "too old version" to "too new version" without intermediates? 15:44:21 yes but pulp failed to store it at some point in time 15:44:28 we cannot really be sure if it is a bug or the user just screwed up the db 15:44:30 do we know that for sure? 15:44:38 we do know that he didn't mess up his db 15:44:48 let;s close it as works for me and if that happens again we can re-open it 15:44:49 and has backups 15:44:54 Ok, so, we can discuss the finer points later. accepting 15:45:02 !accept 15:45:02 #agreed CLOSED 15:45:02 Current proposal accepted: CLOSED 15:45:02 !here 15:45:08 7 issues left to triage: 2272, 2274, 2276, 2277, 2278, 2279, 2280 15:45:13 #topic Downloading on_demand repositories silently fails - http://pulp.plan.io/issues/2272 15:45:13 #info fdobrovo has joined triage 15:45:13 RPM Support Issue #2272 [NEW] (unassigned) - Priority: Normal | Severity: Medium | Target Release: 2.10.1 15:45:13 Downloading on_demand repositories silently fails - http://pulp.plan.io/issues/2272 15:45:14 fdobrovo has joined triage 15:45:53 This one seems to be an issue with the on_demand failing 15:46:06 we've been working on this a lot today 15:46:22 jortel is working on it it's a recent regression 15:46:39 Is this also caused by the move vs copy selinux issue? 15:46:40 urgent, high 15:46:43 regression? === so blocker? 15:46:58 !propose triage ugent high 15:46:58 Error: Unknown Priority 15:47:06 oh we have two of them? 15:47:22 !propose triage urgent high 15:47:22 #idea Proposed for #2272: Priority: Urgent, Severity: High 15:47:23 Proposed for #2272: Priority: Urgent, Severity: High 15:47:46 I'm not sure if it's been reported twice. But the smash failures we looked at yesterday were about accessing published yum repos. 15:48:04 +1 15:48:20 assign to jortel? 15:48:27 no this looks different 15:48:35 yeah, this looks different 15:48:43 I thought this was the selinux one ichimonji filed 15:48:59 no, that's 2277 15:49:07 this does look serious though 15:49:56 yep. urgent/high is appropriate I think. 15:50:04 +1 15:50:09 +1 15:50:14 !accept 15:50:14 #agreed Priority: Urgent, Severity: High 15:50:14 Current proposal accepted: Priority: Urgent, Severity: High 15:50:21 6 issues left to triage: 2274, 2276, 2277, 2278, 2279, 2280 15:50:26 #topic Uploading duplicate content results in ambiguous error message - http://pulp.plan.io/issues/2274 15:50:26 Pulp Issue #2274 [NEW] (unassigned) - Priority: Normal | Severity: Medium | Severity: Medium 15:50:26 Uploading duplicate content results in ambiguous error message - http://pulp.plan.io/issues/2274 15:51:08 i filed this 15:51:35 ttereshc points out in the comments that if you look at the API output, you can actually tell that it's a duplicate content 15:51:57 so, it just sounds like some pulp-admin error reporting robustness is needed? 15:52:18 Or the "summary" should go where the "description" is. 15:52:41 I think it is not only the iso case, this way error reported for upload of rpm/drpm/srpm as well 15:52:58 either way, it's just a change to how the error is presented. 15:53:06 Normal medium is good with me 15:53:11 sounds good. 15:53:19 !propose accept 15:53:19 #idea Proposed for #2274: Leave the issue as-is, accepting its current state. 15:53:19 Proposed for #2274: Leave the issue as-is, accepting its current state. 15:53:49 +1 15:53:59 !accept 15:53:59 #agreed Leave the issue as-is, accepting its current state. 15:53:59 Current proposal accepted: Leave the issue as-is, accepting its current state. 15:54:11 5 issues left to triage: 2276, 2277, 2278, 2279, 2280 15:54:16 #topic Can't kickstart against an on_demand file:// repo - http://pulp.plan.io/issues/2276 15:54:16 RPM Support Issue #2276 [NEW] (unassigned) - Priority: Normal | Severity: Medium | Severity: Medium 15:54:16 Can't kickstart against an on_demand file:// repo - http://pulp.plan.io/issues/2276 15:54:46 This is a somewhat unusual use case, but it would be good to make sure we handle it more gracefully. 15:56:13 !propose triage normal high 15:56:13 #idea Proposed for #2276: Priority: Normal, Severity: High 15:56:13 Proposed for #2276: Priority: Normal, Severity: High 15:57:07 +1 15:57:46 any other +1 ? 15:58:11 +1 15:58:18 !accept 15:58:18 #agreed Priority: Normal, Severity: High 15:58:18 Current proposal accepted: Priority: Normal, Severity: High 15:58:24 4 issues left to triage: 2277, 2278, 2279, 2280 15:58:29 #topic Repository publishes silently fail - http://pulp.plan.io/issues/2277 15:58:30 Pulp Issue #2277 [NEW] (unassigned) - Priority: High | Severity: High | Severity: High 15:58:30 Repository publishes silently fail - http://pulp.plan.io/issues/2277 15:58:47 I was confused by the name similarity 15:58:55 this is the bug that jortel is working on 15:59:08 !propose triage urgent high 15:59:08 #idea Proposed for #2277: Priority: Urgent, Severity: High 15:59:09 Proposed for #2277: Priority: Urgent, Severity: High 15:59:10 yes 15:59:17 +1 15:59:55 +1 15:59:55 assuming silence = +1 15:59:55 maybe it is also worth to rename it a little bit? 16:00:18 +1 16:00:24 +1 for urgent 16:00:32 !suggest Renaming 2277 for clarity 16:00:32 #idea Renaming 2277 for clarity 16:00:39 Good point. Since we know more about it now, adding something about selinux to the title would be valuable. 16:01:11 jortel, want to handle renaming it? 16:01:19 mhrivnak: sure 16:01:22 thanks! 16:01:25 !accept 16:01:25 #agreed Priority: Urgent, Severity: High 16:01:25 Current proposal accepted: Priority: Urgent, Severity: High 16:01:32 3 issues left to triage: 2278, 2279, 2280 16:01:37 #topic 2.7 -> 2.8 Validation - http://pulp.plan.io/issues/2278 16:01:38 Pulp Issue #2278 [NEW] (unassigned) - Priority: Normal | Severity: Medium | Severity: Medium 16:01:38 2.7 -> 2.8 Validation - http://pulp.plan.io/issues/2278 16:01:57 It's nice that this person took the time to file a report! 16:02:20 * smyers finds it funny that a ticket dealing with 2.7 -> 2.8 is number 2278 16:02:29 However it looks like something went wrong in either the DB dump or restore. The error appears to be for duplicate repo_id entries in the repo collection. 16:02:45 !propose accept 16:02:45 #idea Proposed for #2278: Leave the issue as-is, accepting its current state. 16:02:45 Proposed for #2278: Leave the issue as-is, accepting its current state. 16:02:51 scientific linux :) 16:03:08 I don't think we have anything here we can take action on. 16:03:43 what if we don't triage this 16:03:47 and ask some questions 16:03:52 Looks like he's just looking for some help with what went wrong, at least. how about skipping and someone follows up? 16:04:09 But he is doing exactly what we said to do in the readme, and it'd be nice to help a brotha out. So if we need more info to take action... 16:04:12 !propose needinfo 16:04:12 #idea Proposed for #2278: This issue cannot be triaged without more info. 16:04:12 #info smyers has joined triage 16:04:13 smyers has joined triage 16:04:14 Proposed for #2278: This issue cannot be triaged without more info. 16:04:16 yeah needs info 16:04:20 Sounds good. 16:04:39 +1 16:04:42 +1 16:04:59 someone want to volunteer? 16:05:33 I wanted to write but don't know what to say 16:05:44 we can come back to this 16:05:58 do we need a who before accepting? 16:06:08 needsinfo would be to not accept 16:06:21 was more on "accepting the needinfo proposal" 16:06:22 or in terms of accepting deferment maybe 16:06:24 he means to !accept the needinfo proposal :) 16:06:50 accepting, we can figure out who after triage 16:06:54 I accept your definition of accept ;) 16:07:06 !accept 16:07:06 #agreed This issue cannot be triaged without more info. 16:07:06 Current proposal accepted: This issue cannot be triaged without more info. 16:07:19 2 issues left to triage: 2279, 2280 16:07:23 Those of you not sitting near pcreech unfortunately can't appreciate the audible vigor with which he is hitting to accept issues. ;) 16:07:24 #topic Pulp yum_importer fails when syncing SuSE repositories - http://pulp.plan.io/issues/2279 16:07:25 Pulp Issue #2279 [NEW] (unassigned) - Priority: Normal | Severity: Medium | Severity: Medium 16:07:25 Pulp yum_importer fails when syncing SuSE repositories - http://pulp.plan.io/issues/2279 16:07:44 that's just more my commanding control over my keyboard 16:08:05 gotta keep it in line! ok back on task... 16:08:46 looks like we need to investigate this for sure. 16:09:04 This one's a little weird. I'd think it wouldn't try to download srpms unless they're listed in the repodata, but why are the in the repodata if they aren't in the repo? Also you can't --skip srpm? 16:09:07 sounds like a 2.9-2.10 regression maybe? In the sense of "SuSE worked, now it doesn't" 16:09:13 agreed 16:09:31 I'm thinking... 16:09:35 !propose needinfo 16:09:35 #idea Proposed for #2279: This issue cannot be triaged without more info. 16:09:35 yep, it does seem like it could be a regression based on the description. 16:09:35 Proposed for #2279: This issue cannot be triaged without more info. 16:09:44 +1 16:09:44 And I can ask some questions 16:09:48 +1 16:09:49 +1 16:09:55 +1 16:09:57 Thanks smyers . 16:09:57 +1 and thank smyers 16:09:58 !suggest smeyers follows up on 2279 16:09:58 #idea smeyers follows up on 2279 16:10:07 !accept 16:10:07 #agreed This issue cannot be triaged without more info. 16:10:07 Current proposal accepted: This issue cannot be triaged without more info. 16:10:11 * smyers does not know this smeyers person 16:10:13 1 issues left to triage: 2280 16:10:18 #topic Error is not reported correctly when size verification for DRPM unit fails - http://pulp.plan.io/issues/2280 16:10:18 RPM Support Issue #2280 [NEW] (unassigned) - Priority: Normal | Severity: Medium | Severity: Medium 16:10:18 Error is not reported correctly when size verification for DRPM unit fails - http://pulp.plan.io/issues/2280 16:10:39 oops... i do that a lot actually, and usually tend to catch it 16:10:59 16:12:01 !propose accept 16:12:01 #idea Proposed for #2280: Leave the issue as-is, accepting its current state. 16:12:01 Proposed for #2280: Leave the issue as-is, accepting its current state. 16:12:49 +1 16:12:54 +1 16:12:57 +1 16:13:13 Brno is in agreement here :) 16:13:18 heh 16:13:20 \0/ 16:13:28 The Brnobles have spoken. 16:13:34 !accept 16:13:34 #agreed Leave the issue as-is, accepting its current state. 16:13:34 Current proposal accepted: Leave the issue as-is, accepting its current state. 16:13:40 No issues to triage. 16:13:53 pcreech++ 16:13:53 pcreech's karma is now 7 16:13:56 Thanks everyone! Sorry if it felt rushed 16:14:03 jortel, I assigned 2277 to you. 16:14:03 nope 16:14:06 pcreech++ 16:14:06 pcreech's karma is now 8 16:14:10 don't forget to !end it, though 16:14:13 Thanks for driving. 16:14:14 !end 16:14:14 #endmeeting