14:30:35 #startmeeting Pulp Triage 2019-08-23 14:30:35 #info asmacdo has joined triage 14:30:35 !start 14:30:35 Meeting started Fri Aug 23 14:30:35 2019 UTC. The chair is asmacdo. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:30:35 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:30:35 The meeting name has been set to 'pulp_triage_2019-08-23' 14:30:35 asmacdo: asmacdo has joined triage 14:31:06 #info dawalker has joined triage 14:31:06 !here 14:31:06 dawalker: dawalker has joined triage 14:32:00 #info ggainey has joined triage 14:32:00 !here 14:32:03 !next 14:32:04 #topic https://pulp.plan.io/issues/5329 14:32:07 ggainey: ggainey has joined triage 14:32:08 asmacdo: 6 issues left to triage: 5329, 5327, 5321, 5311, 5308, 5304 14:32:09 RM 5329 - Poil - NEW - Pulp 2.20 upgrade chown -R on /var/lib/pulp failed due to NFS mountpoint with Netapp snapshot 14:32:10 https://pulp.plan.io/issues/5329 14:32:26 #info ppicka has joined triage 14:32:26 !here 14:32:26 ppicka: ppicka has joined triage 14:32:49 does the suggestion make sense? maybe we can ask for a PR 14:33:10 is this the chown that we decided to revert? 14:33:17 dkliban: ^^ 14:33:51 #info bmbouter has joined triage 14:33:51 !here 14:33:51 bmbouter: bmbouter has joined triage 14:34:33 i guess lets skip and come back to it 14:34:37 k 14:34:40 !skip 14:34:41 #topic https://pulp.plan.io/issues/5327 14:34:41 asmacdo: 5 issues left to triage: 5327, 5321, 5311, 5308, 5304 14:34:42 RM 5327 - ttereshc - NEW - psql doesn't work on the pulp2-nightly-pulp3-source-centos7 box 14:34:42 I'm digging, will see what i find 14:34:43 https://pulp.plan.io/issues/5327 14:35:09 well this must be irritating 14:35:13 heh 14:35:15 #idea Proposed for #5327: accept and add to sprint 14:35:15 !propose other accept and add to sprint 14:35:15 asmacdo: Proposed for #5327: accept and add to sprint 14:35:22 concur 14:35:47 #agreed accept and add to sprint 14:35:47 !accept 14:35:47 asmacdo: Current proposal accepted: accept and add to sprint 14:35:48 #topic https://pulp.plan.io/issues/5321 14:35:48 asmacdo: 4 issues left to triage: 5321, 5311, 5308, 5304 14:35:49 RM 5321 - daviddavis - NEW - Stop having the installer call makemigrations 14:35:50 https://pulp.plan.io/issues/5321 14:36:45 #idea Proposed for #5321: accept, add to sprint 14:36:45 !propose other accept, add to sprint 14:36:45 asmacdo: Proposed for #5321: accept, add to sprint 14:36:52 +1 14:36:54 ow, painful - concur 14:36:55 +1 14:37:02 #agreed accept, add to sprint 14:37:02 !accept 14:37:02 asmacdo: Current proposal accepted: accept, add to sprint 14:37:03 #topic https://pulp.plan.io/issues/5339 14:37:03 asmacdo: 4 issues left to triage: 5339, 5311, 5308, 5304 14:37:05 RM 5339 - lmjachky - NEW - Add support for role based access control 14:37:06 https://pulp.plan.io/issues/5339 14:37:37 is this is a story? 14:37:50 yes 14:37:52 i think so 14:37:54 more of an epic really 14:38:01 also that ^ 14:38:12 #idea Proposed for #5339: convert to story 14:38:12 !propose other convert to story 14:38:12 asmacdo: Proposed for #5339: convert to story 14:38:34 don't think further action can be taken without a decently large effort to plan 14:38:38 concur, both to story and epic - adding role-based ACLs is...big 14:38:42 concur 14:38:59 #agreed convert to story 14:38:59 !accept 14:38:59 asmacdo: Current proposal accepted: convert to story 14:39:00 #topic https://pulp.plan.io/issues/5311 14:39:00 asmacdo: 3 issues left to triage: 5311, 5308, 5304 14:39:01 yes, it was just an idea; to implement ACL 14:39:02 does this need to be taken to the list? 14:39:02 RM 5311 - daviddavis - NEW - Hitting /pulp/api/v3/ raises a 500 error 14:39:03 https://pulp.plan.io/issues/5311 14:39:22 #info fabricioo0 has joined triage 14:39:22 !here 14:39:22 fabricioo0: fabricioo0 has joined triage 14:39:30 i just replicated this 14:39:36 #idea Proposed for #5311: accept and add to sprint 14:39:36 !propose other accept and add to sprint 14:39:37 asmacdo: Proposed for #5311: accept and add to sprint 14:39:38 concur 14:39:41 +1 14:40:07 #agreed accept and add to sprint 14:40:07 !accept 14:40:07 asmacdo: Current proposal accepted: accept and add to sprint 14:40:08 #topic https://pulp.plan.io/issues/5308 14:40:08 asmacdo: 2 issues left to triage: 5308, 5304 14:40:09 RM 5308 - dkliban@redhat.com - NEW - pulp can't handle update version as a string in updateinfo.xml 14:40:10 https://pulp.plan.io/issues/5308 14:40:26 #idea Proposed for #5308: move to rpm 14:40:26 !propose other move to rpm 14:40:26 asmacdo: Proposed for #5308: move to rpm 14:41:04 +1 14:41:19 yeah, that makes sense - and accept? because versions in rpm-land are historically...filthy. Alas. 14:41:21 #info dkliban has joined triage 14:41:21 !here 14:41:21 dkliban: dkliban has joined triage 14:41:28 that issue is a regression 14:41:33 it needs to be added to the sprint 14:41:35 even more reason to accept :) 14:41:39 concur 14:41:42 #idea Proposed for #5308: accept, add to sprint, change to rpm 14:41:42 !propose other accept, add to sprint, change to rpm 14:41:42 asmacdo: Proposed for #5308: accept, add to sprint, change to rpm 14:41:58 #agreed accept, add to sprint, change to rpm 14:41:58 !accept 14:41:58 asmacdo: Current proposal accepted: accept, add to sprint, change to rpm 14:41:59 #topic https://pulp.plan.io/issues/5304 14:42:00 asmacdo: 1 issues left to triage: 5304 14:42:01 RM 5304 - dkliban@redhat.com - NEW - Pulp 3 can't publish metadata when installed together with Pulp 2 14:42:02 https://pulp.plan.io/issues/5304 14:42:15 i was supposed to comment on this 14:42:20 and i did not 14:42:31 we will change how publishing works 14:42:34 in pulp 3 14:43:12 skip or accept? 14:43:20 accept 14:43:27 #idea Proposed for #5304: Leave the issue as-is, accepting its current state. 14:43:27 !propose accept 14:43:27 asmacdo: Proposed for #5304: Leave the issue as-is, accepting its current state. 14:43:30 +1 14:43:54 #agreed Leave the issue as-is, accepting its current state. 14:43:54 !accept 14:43:54 asmacdo: Current proposal accepted: Leave the issue as-is, accepting its current state. 14:43:55 asmacdo: No issues to triage. 14:44:01 open floor 14:44:22 dkliban: question - is https://pulp.plan.io/issues/5329 the result of the chown we/you reverted? 14:46:47 we can shift back to ^ whenever. in the meantime, would it be helpful to add a 2to3 migration redmine tag? seems like a large enough effort that might be useful to see on its own. 14:47:15 ttereshc^ 14:47:21 makes sense to me 14:47:52 ggainey: i am not sure 14:47:56 * dkliban looks 14:48:04 dkliban: I can't remember where that chown was 14:48:18 asmacdo: new tag sounds reasonable to me? 14:48:33 ggainey: yeah ... we reverted this 14:48:39 ggainey: but we never released another version 14:48:57 gotcha - so this will be fixed when 2.21 goes out? 14:49:03 i beieve so 14:49:26 i'll comment on the issue 14:49:41 we should have released a 2.20.1 14:51:00 ahhh, interesting, ok 14:51:25 any other topics? 14:51:40 Not sure if there's enough folks around right now, but I added this to the headlines for next team meeting and could start talking now 14:52:12 Now that we're not supporting Mariadb, what do we think of changing TextField to JSONField where appropriate in pulpcore? 14:52:21 We have a ticket to do so in pulp_rpm now: https://pulp.plan.io/issues/5326 14:52:25 dawalker: looks like the title is backwards 14:52:32 but wanted to have a wider discussion to address this elsewhere 14:53:01 oh nevermind, just read it backwards 14:53:24 :) 14:53:53 Thoughts? 14:54:05 Can also table this until Monday when more folks are around 14:54:08 dawalker: we arleady have a story filed to change to JSON fields 14:54:19 dalley: didn't you find one the other day? 14:54:24 yeah I've had to go to conflicting meeting so I couldn't be here for much 14:54:35 dawalker, there's one for RPM at least 14:54:47 i think this would be more useful as individual issues for specific fields that should hcnage 14:54:47 ..oh, you posted it :) 14:55:03 dkliban, I don't know if there's one for core 14:55:30 oh ok 14:55:32 dalley, yup :) 14:56:05 dawalker: where is it needed in pulpcore? 14:56:20 asmacdo, I prefer consistency in handling it if possible, but addressing individually is fine too 14:56:49 dkliban, not sure. I ran into it with comps.xml where we were dumping lists and dictionaries into TextField. 14:57:00 dawalker: thats fine, then we need to list those fields on the issue. at the moment, its not really actionable 14:57:01 If you don't need to manipulate them further, JSONField would be better 14:57:11 but if you do need to manipulate them further, it's a moot point 14:57:17 dawalker, that's what I get for responding to the last 5 lines of conversation instead of reading first :) 14:58:24 asmacdo, we can hunt up each case, but first let's decide if the consistency in changing over is even a goal? 14:58:42 If it's not, no reason to take the time listing them on tickets. 14:59:08 dawalker: by "consistency" do you mean to change all text fields? 14:59:20 no, not all 14:59:49 more of a consistent strategy in how to handle the ones that had been dumped lists/dictionaries. 15:00:21 models where you see: models.TextField(default='[]') 15:00:59 but again, not all, I'm only just learning about this, but it appears to depend on what we intend to do with the data 15:01:08 if we need to manipulate it further or not 15:02:48 +1 to change all "text fields storing json dumps" to json fields 15:03:01 a reasonable proposition :) 15:03:30 we've got some of those in Pulp Python also I think 15:04:08 so maybe this issue should be a "contributor docs" issue 15:04:15 +1 to change (less and nicer code) 15:04:15 possibly? 15:05:35 more on that? or other issues? 15:06:33 i'm ready to move on 15:07:06 :q 15:07:10 erm no 15:07:12 #endmeeting 15:07:12 !end