15:30:13 #startmeeting Pulp Triage 2018-02-13 15:30:13 Meeting started Tue Feb 13 15:30:13 2018 UTC and is due to finish in 60 minutes. The chair is dalley. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:30:13 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:30:13 The meeting name has been set to 'pulp_triage_2018_02_13' 15:30:13 #info dalley has joined triage 15:30:13 dalley: dalley has joined triage 15:30:34 !here 15:30:34 #info daviddavis has joined triage 15:30:34 daviddavis: daviddavis has joined triage 15:30:37 !here 15:30:37 #info milan_ has joined triage 15:30:38 milan_: milan_ has joined triage 15:30:39 !here 15:30:39 #info dkliban has joined triage 15:30:39 dkliban: dkliban has joined triage 15:30:40 !here 15:30:40 #info ttereshc has joined triage 15:30:41 ttereshc: ttereshc has joined triage 15:31:04 !next 15:31:05 #topic Can't delete a publication - http://pulp.plan.io/issues/3354 15:31:06 dalley: 7 issues left to triage: 3354, 3355, 3357, 3358, 3362, 3365, 3366 15:31:07 Issue #3354 [POST] (daviddavis@redhat.com) - Priority: Normal | Severity: Medium 15:31:08 Can't delete a publication - http://pulp.plan.io/issues/3354 15:31:15 !here 15:31:15 #info bizhang has joined triage 15:31:15 bizhang: bizhang has joined triage 15:31:19 already in POST. accept & add to sprint? 15:31:30 +1 15:31:35 !propose other accept and add to sprint 15:31:35 #idea Proposed for #3354: accept and add to sprint 15:31:35 dalley: Proposed for #3354: accept and add to sprint 15:31:54 +1 15:31:57 +1 15:32:00 !accept 15:32:00 #agreed accept and add to sprint 15:32:00 dalley: Current proposal accepted: accept and add to sprint 15:32:02 #topic Getting an error building docs with Sphinx 1.7 - http://pulp.plan.io/issues/3355 15:32:02 dalley: 6 issues left to triage: 3355, 3357, 3358, 3362, 3365, 3366 15:32:03 Issue #3355 [NEW] (unassigned) - Priority: Normal | Severity: Medium 15:32:04 Getting an error building docs with Sphinx 1.7 - http://pulp.plan.io/issues/3355 15:32:41 add to sprint 15:32:45 +1 15:32:50 +1 15:32:59 !propose other accept and add to sprint 15:32:59 #idea Proposed for #3355: accept and add to sprint 15:32:59 dalley: Proposed for #3355: accept and add to sprint 15:33:03 !accept 15:33:03 #agreed accept and add to sprint 15:33:03 dalley: Current proposal accepted: accept and add to sprint 15:33:04 dalley: 5 issues left to triage: 3357, 3358, 3362, 3365, 3366 15:33:04 #topic docker_distributor_web is racy, not atomic - http://pulp.plan.io/issues/3357 15:33:05 Issue #3357 [NEW] (unassigned) - Priority: Normal | Severity: Medium 15:33:06 docker_distributor_web is racy, not atomic - http://pulp.plan.io/issues/3357 15:34:39 !propose other high / normal add to sprint 15:34:39 #idea Proposed for #3357: high / normal add to sprint 15:34:40 dalley: Proposed for #3357: high / normal add to sprint 15:36:48 it seems like a bad issue though it's not that urgent I think... 15:36:56 and we have sprint planning this week 15:37:15 let's discuss at sprint planning? 15:37:37 !propose triage h n 15:37:37 ttereshc: Error: Unknown Severity 15:37:42 !propose triage h m 15:37:42 #idea Proposed for #3357: Priority: High, Severity: Medium 15:37:42 ttereshc: Proposed for #3357: Priority: High, Severity: Medium 15:37:45 just accept for now then and evaluate at planning? 15:37:56 yeah 15:38:19 h/m works for me 15:38:31 +1 15:38:37 !accept 15:38:37 #agreed Priority: High, Severity: Medium 15:38:37 dalley: Current proposal accepted: Priority: High, Severity: Medium 15:38:38 dalley: 4 issues left to triage: 3358, 3362, 3365, 3366 15:38:39 #topic Very occasionally, a task will be processed and have a 'worker_name' of None - http://pulp.plan.io/issues/3358 15:38:39 Issue #3358 [NEW] (unassigned) - Priority: Normal | Severity: High 15:38:40 Very occasionally, a task will be processed and have a 'worker_name' of None - http://pulp.plan.io/issues/3358 15:38:58 I suspect this is another race condition 15:39:00 dalley, maybe add sprint candidate flag to rm #3357? 15:39:08 ttereshc, ack 15:41:19 seems like it happens quite infrequently but it caused a random task failure and a bunch of others without a record of what worker processed them 15:41:32 why update throws dup key error? if index is only by task id? (if I understood the traceback correctly) 15:42:02 here https://pulp.plan.io/issues/3358#note-3 15:42:29 hm 15:45:00 for triage purposes I think we can accept it 15:45:00 should we add to the sprint? 15:46:20 we can accept it for now and then discuss it at sprint planning perhaps. but I will probably spend some time looking at it today anyways 15:46:28 sounds good 15:46:34 let's accept and go to next issue 15:46:34 * milan_ cofeee sry, falling asleep triaging O:-) 15:46:54 dalley, do you still have this installation and DB data? 15:47:00 ttereshc, yes 15:47:13 cool 15:47:19 !propose accept 15:47:19 #idea Proposed for #3358: Leave the issue as-is, accepting its current state. 15:47:19 ttereshc: Proposed for #3358: Leave the issue as-is, accepting its current state. 15:47:36 I just checked and it happened again about 20 minutes ago 15:48:10 +1 accept 15:48:18 +1 15:48:38 !accept 15:48:38 #agreed Leave the issue as-is, accepting its current state. 15:48:38 dalley: Current proposal accepted: Leave the issue as-is, accepting its current state. 15:48:39 #topic Pypi install commands are missing the migrations and they produce broken installations - http://pulp.plan.io/issues/3362 15:48:40 dalley: 3 issues left to triage: 3362, 3365, 3366 15:48:41 Issue #3362 [NEW] (unassigned) - Priority: Normal | Severity: Medium 15:48:42 Pypi install commands are missing the migrations and they produce broken installations - http://pulp.plan.io/issues/3362 15:50:05 is this because we're not shipping migrations with the pypi packages and we need to generate them? 15:50:14 i think so 15:50:29 accept and make sprint candidate for next sprint? 15:50:34 that's what Brian's email said 15:50:39 yeah 15:51:20 I think migrations should be shipped with pypi when they're commited to github 15:51:46 bizhang: let's discuss on the ticket 15:51:54 dkliban, will do 15:51:57 yeah, I think we had this discussion somewhere, /me is trying to find it 15:53:12 there was a discussion last year on pulp-dev: Is it time to commit our migrations? 15:53:28 !propose accept and make candidate 15:53:28 dalley: propose accept Propose accepting the current issue in its current state. 15:53:37 !propose other accept and make candidate 15:53:37 #idea Proposed for #3362: accept and make candidate 15:53:37 dalley: Proposed for #3362: accept and make candidate 15:54:43 !propose skip 15:54:43 #idea Proposed for #3362: Skip this issue for this triage session. 15:54:43 dalley: Proposed for #3362: Skip this issue for this triage session. 15:54:53 if we are discussing on the ticket 15:55:10 works for me 15:55:20 +1 15:55:22 +1 15:55:40 !skip 15:55:41 dalley: 2 issues left to triage: 3365, 3366 15:55:42 #topic @id@ on the inherited content unit conflicts with a content unit which also uses @id@ - http://pulp.plan.io/issues/3365 15:55:42 Issue #3365 [NEW] (unassigned) - Priority: Normal | Severity: Low 15:55:43 @id@ on the inherited content unit conflicts with a content unit which also uses @id@ - http://pulp.plan.io/issues/3365 15:56:27 not sure I understand the conflict? 15:57:06 oh, plugin writers are trying to add 'id' columns to their content units? 15:57:22 I guess more information on the issue will be helpful 15:57:36 I can comment 15:57:38 let's skip 15:58:05 +1 15:58:08 +1, skip. need for info 15:58:17 +1 15:58:20 !skip 15:58:21 dalley: 1 issues left to triage: 3366 15:58:22 #topic settings.yaml states the default broker to be Qpid but settings.py requires Rabbitmq - http://pulp.plan.io/issues/3366 15:58:22 Issue #3366 [NEW] (unassigned) - Priority: Normal | Severity: Medium 15:58:24 settings.yaml states the default broker to be Qpid but settings.py requires Rabbitmq - http://pulp.plan.io/issues/3366 15:58:59 !propose accept + add to sprint + easy fix flag 15:58:59 dalley: propose accept Propose accepting the current issue in its current state. 15:59:11 +1 15:59:18 +1 15:59:34 +1 15:59:40 !accept 15:59:40 #agreed Skip this issue for this triage session. 15:59:40 dalley: Current proposal accepted: Skip this issue for this triage session. 15:59:42 dalley: No issues to triage. 15:59:44 !end 15:59:44 #endmeeting