14:30:58 #startmeeting Pulp Triage 2019-04-12 14:30:58 #info asmacdo has joined triage 14:30:58 !start 14:30:58 Meeting started Fri Apr 12 14:30:58 2019 UTC. The chair is asmacdo. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:30:58 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:30:58 The meeting name has been set to 'pulp_triage_2019-04-12' 14:30:58 asmacdo: asmacdo has joined triage 14:31:12 #info daviddavis has joined triage 14:31:12 !here 14:31:12 daviddavis: daviddavis has joined triage 14:31:18 #info dkliban has joined triage 14:31:18 !here 14:31:18 dkliban: dkliban has joined triage 14:31:29 daviddavis++ 14:31:29 asmacdo: daviddavis's karma is now 184 14:31:31 #info bmbouter has joined triage 14:31:31 !here 14:31:31 bmbouter: bmbouter has joined triage 14:31:35 so frequently first in :) 14:31:41 #info ppicka has joined triage 14:31:41 !here 14:31:41 ppicka: ppicka has joined triage 14:31:42 !next 14:31:43 asmacdo: 7 issues left to triage: 4602, 4648, 4662, 4665, 4672, 4676, 4679 14:31:43 #topic https://pulp.plan.io/issues/4602 14:31:44 RM 4602 - mdepaulo@redhat.com - NEW - /var/lib/pulp/tmp/ seems to violate the FHS 14:31:45 https://pulp.plan.io/issues/4602 14:31:52 skip? 14:32:02 yea, who is this waiting on? 14:32:11 I think we can accept now 14:32:14 ok 14:32:15 ok 14:32:16 it'll be a docs thing 14:32:20 accept 14:32:23 and I can try to work on it today and get mike to review 14:32:26 +1 14:32:39 #idea Proposed for #4602: Leave the issue as-is, accepting its current state. 14:32:39 !propose accept 14:32:39 asmacdo: Proposed for #4602: Leave the issue as-is, accepting its current state. 14:32:40 accept and add to sprint 14:32:42 #info dawalker has joined triage 14:32:42 !here 14:32:42 dawalker: dawalker has joined triage 14:32:44 !here (a wizard arrives precisely when he means to) 14:32:44 mikedep333: (here mark yourself present for triage) -- Records a note in the meeting minutes that you are present for this triage session. The meeting chair and anyone participating using triage bot commands should be automatically added. 14:32:49 #idea Proposed for #4602: accept and add to the sprint 14:32:49 !propose other accept and add to the sprint 14:32:49 asmacdo: Proposed for #4602: accept and add to the sprint 14:32:55 #info mikedep333 has joined triage 14:32:55 !here 14:32:55 mikedep333: mikedep333 has joined triage 14:33:11 lol, glad to have a wizard in here 14:33:17 #info ttereshc has joined triage 14:33:17 !here 14:33:17 ttereshc: ttereshc has joined triage 14:33:21 me too 14:33:23 mikedep333: all good to accept this? 14:34:10 4602? Yes, on the docs update. 14:34:18 #agreed accept and add to the sprint 14:34:18 !accept 14:34:18 asmacdo: Current proposal accepted: accept and add to the sprint 14:34:19 asmacdo: 6 issues left to triage: 4648, 4662, 4665, 4672, 4676, 4679 14:34:19 #topic https://pulp.plan.io/issues/4648 14:34:20 RM 4648 - dkliban@redhat.com - NEW - 'reset-admin-password' django-admin command is listed under 'app' section of help text 14:34:21 https://pulp.plan.io/issues/4648 14:35:25 i updated the description 14:35:32 i think we should accept 14:35:47 #idea Proposed for #4648: Leave the issue as-is, accepting its current state. 14:35:47 !propose accept 14:35:47 asmacdo: Proposed for #4648: Leave the issue as-is, accepting its current state. 14:35:51 +1 14:35:53 +1 14:36:12 tag as 3.0 14:36:25 sprint/milestone = 3.0 14:36:29 +1 14:37:01 #agreed Leave the issue as-is, accepting its current state. 14:37:01 !accept 14:37:01 asmacdo: Current proposal accepted: Leave the issue as-is, accepting its current state. 14:37:02 asmacdo: 5 issues left to triage: 4662, 4665, 4672, 4676, 4679 14:37:02 !here 14:37:02 #topic https://pulp.plan.io/issues/4662 14:37:02 #info dalley has joined triage 14:37:03 RM 4662 - kersom - NEW - Few fields returned by task reported by orphans endpoint set as None 14:37:04 https://pulp.plan.io/issues/4662 14:37:05 dalley: dalley has joined triage 14:37:16 I think this is a legit issue 14:37:24 and we should put onto sprint + accept 14:37:28 yp ... accept and add to sprint 14:37:31 +1 14:37:31 +1 14:37:36 +1 14:37:56 #idea Proposed for #4662: accept and add to sprint 14:37:56 !propose other accept and add to sprint 14:37:56 asmacdo: Proposed for #4662: accept and add to sprint 14:38:22 ill also add 3.0 milestone 14:38:34 great 14:38:47 #agreed accept and add to sprint 14:38:47 !accept 14:38:47 asmacdo: Current proposal accepted: accept and add to sprint 14:38:48 +1 14:38:48 #topic https://pulp.plan.io/issues/4665 14:38:49 asmacdo: 4 issues left to triage: 4665, 4672, 4676, 4679 14:38:50 RM 4665 - kersom - NEW - Field base_version set as none even when repo has multiple versions 14:38:51 https://pulp.plan.io/issues/4665 14:39:13 accept 14:39:15 +1 to accept 14:39:15 +1 14:39:17 im not sure if this does make sense for mirror=True 14:39:33 this feature only makes sense if the version was created from another version right? 14:39:46 every version (except the first) is made from another version 14:39:48 but every version except 1 is 14:39:50 yeap 14:39:56 +1 14:39:58 the packages could change significantly version to version 14:40:11 ok thats cool 14:40:19 #idea Proposed for #4665: Leave the issue as-is, accepting its current state. 14:40:19 !propose accept 14:40:19 asmacdo: Proposed for #4665: Leave the issue as-is, accepting its current state. 14:40:23 wait 14:40:24 3.0? 14:40:28 +1 3.0 14:40:28 should we add the 3.0 milestone 14:40:30 yes 14:40:30 yea ok 14:40:34 will be a pain to migrate 14:40:54 lol right 14:41:02 #agreed Leave the issue as-is, accepting its current state. 14:41:02 !accept 14:41:02 asmacdo: Current proposal accepted: Leave the issue as-is, accepting its current state. 14:41:04 asmacdo: 3 issues left to triage: 4672, 4676, 4679 14:41:04 #topic https://pulp.plan.io/issues/4672 14:41:05 RM 4672 - kersom - NEW - Actions over task system missing documentation 14:41:06 https://pulp.plan.io/issues/4672 14:41:27 I also wonder if we should be showing a user error message 14:41:31 409 could mean anything 14:41:36 the issue #4665 does not make sense to me. Later if someone can explain to me, I appreciate it. 14:42:14 kersom: sure, ping me after 14:42:19 we should add docs 14:42:26 asmacdo, thanks. 14:42:28 daviddavis: this is a docs issue 14:42:34 daviddavis: I think if we include 409 in the REST docs, that should be fine 14:42:38 yeap 14:42:49 I think we could do both tho? 14:42:49 asmacdo: add documentation tag on this 14:42:54 +1 docs tag 14:43:03 it already has a docs tag 14:43:08 #idea Proposed for #4672: accept +documentation +3.0milestone and add to sprint 14:43:08 !propose other accept +documentation +3.0milestone and add to sprint 14:43:08 asmacdo: Proposed for #4672: accept +documentation +3.0milestone and add to sprint 14:43:12 +1 14:43:18 I agree with daviddavis , "reason" can be better 14:43:23 than just Conflict 14:43:24 agreed also 14:43:28 conflict does not seem right 14:43:34 I'll file a separate issue 14:43:41 related to http status code, do you have standards around them? 14:43:45 we* 14:43:55 generally we try to follow the standard 14:44:01 daviddavis: can we do it on the same issue? it would be not ideal to add docs for 409 and then change it 14:44:03 yes it's called rfc2616 14:44:06 this is the only 209 that I recorded seen 14:44:09 asmacdo: +1 14:44:12 there is a bit of interpretation here and there, but generally we let drf do the work 14:44:13 I mean for pulp endpoints 14:44:22 ah I see 14:44:31 bmbouter, I think 409 is our addition 14:44:36 delete always produces 204, for instance? 14:44:40 strange 14:45:01 daviddavis: i'm going to accept, any concerns, please comment on the issue 14:45:06 bmbouter, we specifically added 409 instead of general 400 for specific cases 14:45:11 asmacdo: ok 14:45:12 I was trying to compare and I could not find a doc explained this for pulp 3 14:45:21 ttereshc: where does this happen? 14:45:35 bmbouter, I'll try to find an issue 14:45:36 we can answer later also 14:45:38 ty 14:45:46 #agreed accept +documentation +3.0milestone and add to sprint 14:45:46 !accept 14:45:46 asmacdo: Current proposal accepted: accept +documentation +3.0milestone and add to sprint 14:45:47 #topic https://pulp.plan.io/issues/4676 14:45:47 asmacdo: 2 issues left to triage: 4676, 4679 14:45:48 RM 4676 - jdjeffers - NEW - Documentation for PATCH /pulp/api/v3/remotes/file/file/:ref doesn't match behavior 14:45:49 https://pulp.plan.io/issues/4676 14:45:59 we can come back to that one during open floor if anyone is interested 14:46:14 this is a problem iwth the bindings 14:46:21 agreed 14:46:21 let's accept and add to sprint 14:46:23 +1 14:46:27 +1 14:46:29 3.0 milestone 14:46:48 #idea Proposed for #4676: accept +add to sprint +3.0milestone 14:46:48 !propose other accept +add to sprint +3.0milestone 14:46:48 asmacdo: Proposed for #4676: accept +add to sprint +3.0milestone 14:47:06 do we want to change this to "File Support" or should this be treated as a pulpcore issue 14:47:28 I'm a bit confused by this issue 14:47:33 I tried to reproduce but couldn't 14:47:37 see my comment 14:47:43 is it a bindings issue? 14:47:45 I talked with rochacbruno about bindings testing, more than use a diff to compare json files, it will require a drastic change in the way that we are currently writing tests. Not sure if we are going to be able to do this now. 14:47:46 yes 14:47:54 ok we should add the bindings tag then 14:48:18 I think this could be pulpcore since the serializer and fields exist in core 14:48:23 yeah 14:48:27 makes sense 14:49:08 #agreed accept +add to sprint +3.0milestone 14:49:08 !accept 14:49:08 asmacdo: Current proposal accepted: accept +add to sprint +3.0milestone 14:49:09 #topic https://pulp.plan.io/issues/4679 14:49:09 asmacdo: 1 issues left to triage: 4679 14:49:10 RM 4679 - tustvold - NEW - Custom settings not propogating 14:49:11 https://pulp.plan.io/issues/4679 14:49:43 we already hav ea PR that's going to fix it 14:49:58 rochacbruno made a PR for the latest version of DynaConf integration 14:50:06 so let's accept and add to sprint 14:50:14 +1 14:50:23 #idea Proposed for #4679: accept, add to sprint, rochacbruno to take as assigned 14:50:23 !propose other accept, add to sprint, rochacbruno to take as assigned 14:50:23 asmacdo: Proposed for #4679: accept, add to sprint, rochacbruno to take as assigned 14:50:25 +1 14:50:51 #agreed accept, add to sprint, rochacbruno to take as assigned 14:50:51 !accept 14:50:52 asmacdo: Current proposal accepted: accept, add to sprint, rochacbruno to take as assigned 14:50:53 asmacdo: No issues to triage. 14:51:13 rochacbruno: i went ahead and assigned you. feel free to correct that if you disagree 14:51:19 Open floor! 14:51:22 bmbouter, re 409 code, I remember a lot of discussion about it next to my desk :), it turned out the PR was not merged and issues was closed https://pulp.plan.io/issues/3846 14:51:29 https://pulp.plan.io/issues/3527 that is the issue that introduced the 409 14:51:43 !issue 4672 14:51:43 #topic https://pulp.plan.io/issues/4672 14:51:44 RM 4672 - kersom - NEW - Actions over task system missing documentation 14:51:45 https://pulp.plan.io/issues/4672 14:51:57 I just responded to this btw 14:52:22 I think 400 is right and 409 is not what I expected 14:52:41 asmacdo: cool, I'll try to reproduce that problem and if needed I update my opened PR 14:52:56 409: The request could not be completed due to a conflict with the current 14:52:57 state of the resource. 14:53:14 that sounds correct to me, the task state prevents it from getting deleted 14:53:33 and a error message explaining why would be great as well 14:53:35 so the delete works if it's in completed? 14:53:45 * bmbouter rereads 14:53:48 correct 14:53:54 that is another part of the documentation missing 14:54:16 ic 14:54:27 asmacdo: I think you're right then about the 409 14:54:37 and kersom you are right about the missing docs 14:54:39 I just want to point out that rfc2616 says "The response body SHOULD include enough information for the user to recognize the source of the conflict." 14:54:41 and perhaps the error message too 14:54:51 yeah we are not doing that part 14:54:55 let's do that part 14:54:55 daviddavis, +1 14:55:15 +1. if the error message is clear, then the other part is also true :This code is only allowed in situations where 14:55:15 it is expected that the user might be able to resolve the conflict 14:55:15 and resubmit the request. 14:55:26 ok, I am fine with 409 14:55:35 if the user sees a descriptive 409, they can cancel the task, and then delete it 14:55:41 +1 14:55:47 I wrote tests for the task system covering those topics 14:55:49 https://github.com/pulp/pulpcore/pull/80 14:55:57 I can update them later 14:56:07 anyone want to update this issue with what we discussed here? 14:57:00 ill grab do it then 14:57:16 anyone else got an issue they'd like to discuss? 14:57:23 I do 14:57:25 does it have to be a bug? 14:57:33 https://pulp.plan.io/issues/4678 14:57:36 daviddavis: na, i think it can be anything 14:57:41 !issue 4678 14:57:42 #topic https://pulp.plan.io/issues/4678 14:57:42 RM 4678 - bmbouter - NEW - As a plugin writer, I have Master/Detail Publications 14:57:43 https://pulp.plan.io/issues/4678 14:57:50 oh, yes 14:58:23 bmbouter: ive been wondering about this one, and whether we actually should delete the publishers 14:58:36 IMO many plugins should for sure delete the publishers 14:58:45 they only create a 2-step workflow I've realized 14:58:53 but some plugins might have values that they want to repeat 14:59:03 I need to read this I suppose 14:59:10 * daviddavis just saw we're removing publishers 14:59:13 it would be irritating to have to enter them in for every POST Publication request 14:59:22 asmacdo: I see your point 14:59:34 I think pulpcore should leave in Publisher for any plugins that it helps 14:59:34 would it be possible for a plugin to create a publisher? 14:59:38 without it being in core? 14:59:58 I guess we can leave it core as well if it helps plugins 15:00:00 asmacdo: I can see the use case you are talking about 15:00:13 we can revise this to leave publishers as-is 15:00:19 awesome 15:00:22 which also makes this a simpler change 15:00:28 generally, I really like this 15:00:50 hopefully those who use publishers will record the actual options used on the publication but that is up to them 15:00:51 does GET /pulp/api/v3/publications/ go away? 15:00:57 yes 15:01:04 I see 15:01:05 so this won't be backwards compatible 15:01:11 that's true 15:01:17 bmbouter: IIRC you said it could be done backwards compatible somehwere? 15:01:28 I was focusing on the plugin interface mainly 15:01:33 ah ok 15:01:48 so this will be a little bit awkward 15:02:02 can we bring this up next week? I'd like time to review it more. 15:02:09 yes this is not decision time 15:02:15 ok cool 15:02:15 it's advertisement and discussion time 15:02:24 please comment w/ ideas/concerns etc 15:02:44 next? 15:02:46 I like this change but I hate master detail 15:02:54 #4487 15:03:02 !issue 4487 15:03:03 #topic https://pulp.plan.io/issues/4487 15:03:03 RM 4487 - daviddavis - NEW - As a user, I can spin up Pulp in a FIPS enabled environment with pulplift 15:03:04 https://pulp.plan.io/issues/4487 15:03:20 I just wanted to advertise this issue because there's a lot of FIPS work slated for 3.0 and this is blocking it 15:03:34 btw, it is 11:03, so we can keep going, but people may drop off 15:04:14 daviddavis: is this blocked by installing on RHEL? 15:04:16 we should put this onto the sprint 15:04:27 CentOS has fips right? 15:04:35 asmacdo: no, we can use centos. there's a centos-fips box in forklift as well. 15:04:38 yea 15:04:44 sweet 15:04:50 let's get this onto the sprint we should do this 15:04:52 #idea Proposed for #4487: add to sprint 15:04:52 !propose other add to sprint 15:04:53 asmacdo: Proposed for #4487: add to sprint 15:04:57 +1 15:05:14 I'd love to help with this, but im super ignorant with FIPs 15:05:31 so whoever picks up, feel free to discuss with me 15:05:44 #agreed add to sprint 15:05:44 !accept 15:05:44 asmacdo: Current proposal accepted: add to sprint 15:05:45 asmacdo: No issues to triage. 15:06:05 +1 15:06:06 thats our time, so im going to end 15:06:08 #endmeeting 15:06:08 !end