14:30:19 #startmeeting Pulp Triage 2019-05-21 14:30:19 !start 14:30:19 #info asmacdo has joined triage 14:30:19 Meeting started Tue May 21 14:30:19 2019 UTC. The chair is asmacdo. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:30:19 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:30:19 The meeting name has been set to 'pulp_triage_2019-05-21' 14:30:19 asmacdo: asmacdo has joined triage 14:30:31 #info ttereshc has joined triage 14:30:31 !here 14:30:31 ttereshc: ttereshc has joined triage 14:30:35 almost all of these are rpm, so we just have 1 14:30:43 #info ipanova has joined triage 14:30:43 !here 14:30:43 ipanova: ipanova has joined triage 14:30:45 #info dkliban has joined triage 14:30:45 !here 14:30:45 dkliban: dkliban has joined triage 14:31:14 !next 14:31:15 asmacdo: 5 issues left to triage: 4835, 4850, 4856, 4857, 4858 14:31:15 #topic https://pulp.plan.io/issues/4835 14:31:16 RM 4835 - dkliban@redhat.com - NEW - RPM package can be created without specifying the 'relative_path' 14:31:17 https://pulp.plan.io/issues/4835 14:31:19 !skip 14:31:20 asmacdo: 4 issues left to triage: 4850, 4856, 4857, 4858 14:31:20 #topic https://pulp.plan.io/issues/4850 14:31:21 RM 4850 - ppicka - POST - Update autogenerated titles in API docs 14:31:22 #info daviddavis has joined triage 14:31:22 !here 14:31:23 https://pulp.plan.io/issues/4850 14:31:23 #info ppicka has joined triage 14:31:23 !here 14:31:24 daviddavis: daviddavis has joined triage 14:31:26 ppicka: ppicka has joined triage 14:31:28 !skp 14:31:28 asmacdo: Error: "skp" is not a valid command. 14:31:32 !skip 14:31:33 asmacdo: 3 issues left to triage: 4856, 4857, 4858 14:31:33 #topic https://pulp.plan.io/issues/4856 14:31:34 RM 4856 - rmcgover - NEW - Uploading ISOs of same name to a repo creates duplicates, makes repo unusable 14:31:35 https://pulp.plan.io/issues/4856 14:31:44 skip 14:31:47 !skip 14:31:48 asmacdo: 2 issues left to triage: 4857, 4858 14:31:49 #topic https://pulp.plan.io/issues/4857 14:31:49 RM 4857 - bherring - NEW - Pulp 2 Nightly Regression in test_iso_crud.ISOUpdateTestCase.test_all 14:31:51 https://pulp.plan.io/issues/4857 14:31:55 !skip 14:31:57 asmacdo: 1 issues left to triage: 4858 14:31:57 #topic https://pulp.plan.io/issues/4858 14:31:58 RM 4858 - lmayorga1980 - NEW - Running Pulp Inside a Container 14:31:59 https://pulp.plan.io/issues/4858 14:32:09 !here 14:32:09 #info bmbouter has joined triage 14:32:10 bmbouter: bmbouter has joined triage 14:33:19 asmacdo is a skip master 14:33:29 is pulp/pulp-ci still supported? 14:33:29 #info dawalker has joined triage 14:33:29 !here 14:33:29 dawalker: dawalker has joined triage 14:33:43 asmacdo: we use it on Jenkins 14:33:55 may pulp2 tag? 14:33:56 but i don't think we do anything with containers with it 14:33:59 asmacdo, that is what we used to do ci for pulp 2 on jenkins 14:34:11 but its not intended to be user-facing right? 14:34:21 i'll comment on the issue 14:34:25 i think we can close it 14:34:34 as won't fix 14:34:39 asmacdo, no 14:34:41 #idea Proposed for #4858: dkliban will comment and close 14:34:41 !propose other dkliban will comment and close 14:34:41 asmacdo: Proposed for #4858: dkliban will comment and close 14:34:56 do we have pulp2 docker instructions anywhere? 14:35:13 add Pulp2 tag as ppicka suggested 14:35:23 and remove 2.19.0 milestone please 14:35:29 dkliban, ^ 14:35:34 pulp 2 docker instructions: use pulp 3 :) 14:36:08 asmacdo, +1 14:36:09 :) 14:36:12 #agreed dkliban will comment and close 14:36:12 !accept 14:36:12 asmacdo: Current proposal accepted: dkliban will comment and close 14:36:13 asmacdo: No issues to triage. 14:36:19 open floor! 14:36:23 https://pulp.plan.io/issues/4591 14:36:29 !issue 4591 14:36:29 #topic https://pulp.plan.io/issues/4591 14:36:30 RM 4591 - ttereshc - POST - Publish of a mid-size repo is slow 14:36:31 https://pulp.plan.io/issues/4591 14:36:37 oops wrong one 14:36:39 wait 14:36:52 https://pulp.plan.io/issues/4428 14:37:10 !issue 4428 14:37:32 !issue 4428 14:37:32 #topic https://pulp.plan.io/issues/4428 14:37:33 RM 4428 - daviddavis - ASSIGNED - Upsert query raises NotUniqueError 14:37:34 https://pulp.plan.io/issues/4428 14:37:38 daviddavis daviddavis , you are not the open floor master :P 14:37:43 lol 14:37:49 (you can !propose, but you cant !issue) 14:38:08 it sounds like repo applicability regen is failing so we're going to try to add sleep statements 14:38:12 would like to add to sprint 14:38:27 this affects deferred downloads too 14:38:42 +1 to adding to sprint 14:39:47 +1 14:40:18 +1 14:40:21 seems reasonable to me, sleep is ugly but not risky 14:40:24 +1 14:40:27 yea 14:40:27 daviddavis, I'm not worried about deferred donload 14:40:44 where do you see that applicability fails 14:40:51 the only concern I have is that users see these errors 3-4+ times per day 14:41:11 dkliban reported the applicability failures https://pulp.plan.io/issues/4428#note-16 14:41:14 ttereshc: on dogfood satellite there are no consumers being managed 14:41:28 so each time a repo is synced there the regen applicability task fails 14:41:38 and it marks the sync task is katello with a warning 14:41:43 weird 14:42:09 I'm still +1 :) just curious 14:42:55 so I'll add it to the sprint if there are no objections 14:43:42 * daviddavis falls asleep 14:43:58 lol 14:44:02 daviddavis: please do 14:44:13 go for it, dkliban and I, we've got your back 14:44:37 fyi, https://pulp.plan.io/issues?query_id=30 has been updated to exclude all plugins except for pulp_file 14:44:58 * asmacdo was annoyed by skipping today 14:45:15 any other issues? 14:45:22 that's a shame :( 14:45:41 can we make a separate query either for triage or for all untriaged bugs? 14:45:50 so we can filter it by plugin as before? 14:45:53 asmacdo, ^ 14:45:54 yea https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30 no longer works 14:47:00 hmm 14:47:05 make a new Un-Triaged query and rename query 30 to "Issues to Triage" ? 14:48:17 I would do it the other way around, just because many people know what query 30 is, but this ^ works as well 14:48:37 daviddavis, I can make one if you want 14:49:14 yea, let's create a new "Issues for Triage" and revert query 30 14:49:36 i did it this way to avoid having to change pulpbot 14:49:48 but its probably not a big deal to update the query in there 14:50:11 !pirate 14:50:11 daviddavis: Error: "pirate" is not a valid command. 14:50:26 * daviddavis wasn't sure what to expect 14:50:36 aha, yeah, this should be easy https://github.com/pulp/supybot-pulptriage/blob/master/config.py#L63 14:50:45 nice find asmacdo 14:50:52 daviddavis, asmacdo, I'll create/update queries and let you know 14:51:08 ttereshc: so to confirm, we're reverting query 30? 14:51:16 +1 14:51:20 yes, I'm in favour of doing it 14:51:23 +1 14:51:29 ttereshc++ 14:51:29 daviddavis: ttereshc's karma is now 90 14:51:45 !dance 14:51:45 ♪┏(°.°)┛┗(°.°)┓┗(°.°)┛┏(°.°)┓ ♪ 14:52:03 sorry to jump the gun 14:52:14 thanks ttereshc 14:52:24 asmacdo, daviddavis, we are ignoring debian only, right? 14:52:28 this all sounds good 14:52:32 actually 14:52:37 lets not filter by project 14:53:16 then the query will be filterable for all projects using the /projects//issues?query_id=30 14:54:13 there are a bunch of issues shown under Infrastructure and Pulp CLI 14:54:51 we sitll have Pulp CLI? 14:55:28 ttereshc: IMO, the query is right, it just exposes some cleanup we need to do 14:55:35 I agree 14:55:56 ttereshc: let me know when you have a query_id, so i can make a PR to pulpbot 14:56:08 oh right 14:56:10 #endmeeting 14:56:10 !end