14:30:01 #startmeeting Pulp Triage 2016-06-07 14:30:01 #info asmacdo has joined triage 14:30:02 Meeting started Tue Jun 7 14:30:01 2016 UTC and is due to finish in 60 minutes. The chair is asmacdo. 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_2016_06_07' 14:30:02 asmacdo has joined triage 14:30:25 #info jcline has joined triage 14:30:25 !here 14:30:26 jcline has joined triage 14:30:31 !here 14:30:31 #info mhrivnak has joined triage 14:30:31 mhrivnak has joined triage 14:30:55 !here 14:30:55 #info dkliban has joined triage 14:30:55 dkliban has joined triage 14:31:13 what did we decide was quorum? 14:31:17 !here 14:31:17 #info bmbouter has joined triage 14:31:18 bmbouter has joined triage 14:31:57 5 seems like plenty 14:31:58 !next 14:31:59 6 issues left to triage: 1967, 1971, 1977, 1978, 1979, 1980 14:32:00 #topic Duplicate instances of pulp_celerybeat on the same host will cause some tasks to be dispatched multiple times - http://pulp.plan.io/issues/1967 14:32:00 Pulp Issue #1967 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:32:01 asmacdo, it's 2. The bot knows, and won't let you !next without it 14:32:01 Duplicate instances of pulp_celerybeat on the same host will cause some tasks to be dispatched multiple times - http://pulp.plan.io/issues/1967 14:32:10 thanks smyers 14:32:28 dalley, would you like to talk about this one? 14:32:28 mhrivnak: i think that's a good suggestion 14:32:53 Ok 14:33:15 !propose accept 14:33:15 #idea Proposed for #1967: Leave the issue as-is, accepting its current state. 14:33:15 Proposed for #1967: Leave the issue as-is, accepting its current state. 14:33:22 It's fairly straightforward - we heavily discourage users from running multiple pulp celerybeats on the same machine 14:33:31 #idea Proposed for #1967: Priority: Normal, Severity: Low 14:33:31 !propose triage normal low 14:33:31 Proposed for #1967: Priority: Normal, Severity: Low 14:33:45 +1 14:33:53 +1 14:33:54 #agreed Priority: Normal, Severity: Low 14:33:54 !accept 14:33:54 Current proposal accepted: Priority: Normal, Severity: Low 14:33:56 #topic '--retain-old-count' option not retroactive - http://pulp.plan.io/issues/1971 14:33:56 5 issues left to triage: 1971, 1977, 1978, 1979, 1980 14:33:57 RPM Support Issue #1971 [NEW] (unassigned) - Priority: Normal | Severity: Low 14:33:58 '--retain-old-count' option not retroactive - http://pulp.plan.io/issues/1971 14:34:07 But if they do, both celerybeats will dispatch tasks 14:34:12 +1 14:34:19 oh sorry dally, you are the same color as dkliban 14:34:56 that's it really 14:35:05 For this one, doing similar work for the importers that we did for distributors should resolve it. Namely... 14:35:16 1) if the config changes, do a full sync next time 14:35:23 2) have an option to force a full sync any time 14:35:43 Anyone know off-hand if we have stories for those? 14:36:02 for rpm we did (2) 14:36:07 it's merged in 2.9.0 14:36:18 oh good. Have an issue #? 14:36:20 I think ipanova did them 14:36:31 https://pulp.plan.io/issues/1158 14:36:33 Title: Story #1158: As a user, I can force full/fresh publish of rpms and not do an incremental publish - RPM Support - Pulp (at pulp.plan.io) 14:36:42 and we also did (1) 14:37:10 that's publish ^ 14:37:24 https://pulp.plan.io/issues/1724 14:37:26 https://pulp.plan.io/issues/1724 14:37:31 Title: Story #1724: Publish should be a no-op if no units and no settings have changed since the last successful publish - Pulp (at pulp.plan.io) 14:37:32 Title: Story #1724: Publish should be a no-op if no units and no settings have changed since the last successful publish - Pulp (at pulp.plan.io) 14:37:49 Gotcha. So we need similar work done for sync. 14:37:57 we don't have stories 14:38:17 oic 14:38:22 what dkliban said 14:38:49 Ok. I'll add stories and make this bug related to one or both. 14:38:56 mhrivnak: thanks 14:39:07 what about prio for this one? 14:39:25 I think we could accept it as-is. 14:39:36 !propose accept 14:39:36 #idea Proposed for #1971: Leave the issue as-is, accepting its current state. 14:39:37 Proposed for #1971: Leave the issue as-is, accepting its current state. 14:39:48 +1 14:39:50 any other thoughts? 14:40:09 !accept 14:40:09 #agreed Leave the issue as-is, accepting its current state. 14:40:09 Current proposal accepted: Leave the issue as-is, accepting its current state. 14:40:11 #topic basic auth in URL fails when using authenticated proxy - http://pulp.plan.io/issues/1977 14:40:11 4 issues left to triage: 1977, 1978, 1979, 1980 14:40:12 RPM Support Issue #1977 [NEW] (unassigned) - Priority: High | Severity: High 14:40:13 basic auth in URL fails when using authenticated proxy - http://pulp.plan.io/issues/1977 14:40:56 Did this ever work before? 14:41:15 it sounds like it did 14:41:41 it's an important feature of sync I propose we accept as is 14:41:46 !propose accept 14:41:46 #idea Proposed for #1977: Leave the issue as-is, accepting its current state. 14:41:47 Proposed for #1977: Leave the issue as-is, accepting its current state. 14:41:55 +1 (obviously ;) ) 14:41:56 +1 14:42:18 #agreed Leave the issue as-is, accepting its current state. 14:42:18 !accept 14:42:18 Current proposal accepted: Leave the issue as-is, accepting its current state. 14:42:19 3 issues left to triage: 1978, 1979, 1980 14:42:19 #topic Change the name of the scheduler worker from "scheduler" to "pulp_celerybeat" - http://pulp.plan.io/issues/1978 14:42:20 Pulp Issue #1978 [NEW] (unassigned) - Priority: Low | Severity: Low | Target Release: 3.0.0 14:42:21 Change the name of the scheduler worker from "scheduler" to "pulp_celerybeat" - http://pulp.plan.io/issues/1978 14:42:51 !propose triage normal medium 14:42:51 #idea Proposed for #1978: Priority: Normal, Severity: Medium 14:42:52 Proposed for #1978: Priority: Normal, Severity: Medium 14:42:53 This looks more like a task or refactor than an issue. 14:43:04 yes a task would be good 14:43:12 it's visible to the user so it's not a refactor 14:43:21 I can switch it to a task and leave a comment 14:43:28 Works for me. 14:43:37 bmbouter, would you mark as triaged as well so we dont collide? 14:43:45 ok let's skip it, and yes 14:43:58 !skip 14:43:59 2 issues left to triage: 1979, 1980 14:44:00 #topic metadata unit copy action creates incorrect unit count on repo - http://pulp.plan.io/issues/1979 14:44:00 RPM Support Issue #1979 [NEW] (unassigned) - Priority: Normal | Severity: Low 14:44:01 metadata unit copy action creates incorrect unit count on repo - http://pulp.plan.io/issues/1979 14:44:56 bmbouter, is this new in 2.9? 14:45:10 im guessing this is because we aren't using the conduit anymore since lazy? 14:45:22 it's from whenever that code block was introduced 14:45:35 it's a 1-line fix and I propose I take it as assigned 14:45:37 mhrivnak: i guess this is because with every copy we create a new unit? 14:46:08 only in cases where the copy destination already has a unit that compares as the same against the unit being copied 14:46:28 Gotcha. I'm surprised we haven't noticed it on other types. 14:46:36 perhaps it's not that old 14:46:50 !propose high low 14:46:50 Error: "propose" is not a valid command. 14:47:07 !propose triage high low 14:47:07 #idea Proposed for #1979: Priority: High, Severity: Low 14:47:08 Proposed for #1979: Priority: High, Severity: Low 14:47:18 +1 14:47:22 +1 14:47:27 and I'll update it and take it as assigned 14:47:32 +1 14:47:33 k thanks bmbouter 14:47:37 #agreed Priority: High, Severity: Low 14:47:37 !accept 14:47:37 Current proposal accepted: Priority: High, Severity: Low 14:47:38 1 issues left to triage: 1980 14:47:39 Also please verify that it's new in 2.9 14:47:39 #topic Warning message in Langpacks upload can help - http://pulp.plan.io/issues/1980 14:47:40 RPM Support Issue #1980 [NEW] (unassigned) - Priority: Normal | Severity: Low | Target Release: master 14:47:41 Warning message in Langpacks upload can help - http://pulp.plan.io/issues/1980 14:47:44 last one 14:48:33 this is a good improvement 14:48:34 Maybe this should be a story. 14:48:37 agreed 14:48:46 As a user, I see a warning message when... 14:48:48 and it could be across several types not just langpacks 14:48:57 indeed 14:48:59 preethi: can this be rewritten as a story? 14:49:09 bmbouter: sure 14:49:19 and it can be for several types (all the metadata types) 14:49:25 which would be great! 14:49:42 asmacdo we should mark this as a resolution and also for the other skipped one, but I'm not sure how to do that 14:50:13 !prropose other Change to story 14:50:13 Error: "prropose" is not a valid command. 14:50:18 !propose other Change to story 14:50:18 #idea Proposed for #1980: Change to story 14:50:19 Proposed for #1980: Change to story 14:50:25 i guess? 14:50:47 actually here we go 14:50:53 bmbouter: making sure I understand, are you asking me to write it? ( I can try for sure) 14:51:00 #action preethi will change this to a story 14:51:00 !action preethi will change this to a story 14:51:03 :) 14:51:08 got it 14:51:18 :) 14:51:50 bmbouter, do we need to go back to the last one? 14:52:30 asmacdo: yes 1978 14:52:33 !issue 1978 14:52:34 #topic Change the name of the scheduler worker from "scheduler" to "pulp_celerybeat" - http://pulp.plan.io/issues/1978 14:52:34 Pulp Task #1978 [NEW] (unassigned) - Priority: Low | Target Release: 3.0.0 14:52:35 Change the name of the scheduler worker from "scheduler" to "pulp_celerybeat" - http://pulp.plan.io/issues/1978 14:52:45 and add a propose cahnging to type task 14:52:47 or something like that 14:52:51 !action bmbouter will change this to a task and leave a comment 14:52:51 #action bmbouter will change this to a task and leave a comment 14:53:12 !accept 14:53:12 #agreed Change to story 14:53:12 Current proposal accepted: Change to story 14:53:13 1 issues left to triage: 1980 14:53:13 #topic Warning message in Langpacks upload can help - http://pulp.plan.io/issues/1980 14:53:14 RPM Support Issue #1980 [NEW] (unassigned) - Priority: Normal | Severity: Low | Target Release: master 14:53:15 Warning message in Langpacks upload can help - http://pulp.plan.io/issues/1980 14:53:30 heh 14:53:35 hm. 14:53:45 !accept 14:53:45 No action proposed, nothing to accept. 14:54:01 i dont think "!action" is working smyers? 14:54:10 action isn't part of the proposal system 14:54:20 Just records an action item 14:54:37 !ropose other preethi will rewrite as story 14:54:37 Error: "ropose" is not a valid command. 14:54:40 !propose other preethi will rewrite as story 14:54:40 #idea Proposed for #1980: preethi will rewrite as story 14:54:41 Proposed for #1980: preethi will rewrite as story 14:54:44 #agreed preethi will rewrite as story 14:54:44 !accept 14:54:44 Current proposal accepted: preethi will rewrite as story 14:54:45 No issues to triage. 14:54:47 !end 14:54:48 #endmeeting