14:30:36 #startmeeting Pulp Triage 2020-09-22 14:30:36 #info fao89 has joined triage 14:30:36 !start 14:30:36 Meeting started Tue Sep 22 14:30:36 2020 UTC. The chair is fao89. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:30:36 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:30:36 The meeting name has been set to 'pulp_triage_2020-09-22' 14:30:36 fao89: fao89 has joined triage 14:30:53 #info daviddavis has joined triage 14:30:53 !here 14:30:54 daviddavis: daviddavis has joined triage 14:30:54 #info dkliban has joined triage 14:30:54 !here 14:30:55 dkliban: dkliban has joined triage 14:31:16 #info ppicka has joined triage 14:31:16 !here 14:31:16 ppicka: ppicka has joined triage 14:31:18 !next 14:31:19 #topic https://pulp.plan.io/issues/7543 14:31:19 fao89: 4 issues left to triage: 7543, 7542, 7532, 7513 14:31:20 RM 7543 - wibbit - NEW - "reserved_resources_record" missing from tasks (python client) 14:31:21 https://pulp.plan.io/issues/7543 14:31:59 I think it was already addressed 14:32:26 fao89: do you mean there is already a fix for this on master branch? 14:32:37 yes, I'm checking it 14:32:41 #info ipanova has joined triage 14:32:41 !here 14:32:41 ipanova: ipanova has joined triage 14:33:12 dkliban, https://pulp.plan.io/issues/7347 14:33:36 so we should close as a duplicate then 14:33:42 i'll add the relationship 14:33:55 issues is reported against 3.6.0 14:33:59 I'll check the openapi schema 14:34:03 the fix was released in 3.6.1 14:34:10 he is using 3.6.0 14:34:30 it is there: https://docs.pulpproject.org/pulpcore/api.json 14:34:35 yes, this is what i said 14:34:43 we should close and say it is fixed in 3.6.1 14:35:01 #info bmbouter has joined triage 14:35:01 !here 14:35:01 bmbouter: bmbouter has joined triage 14:35:13 #info x9c4 has joined triage 14:35:13 !here 14:35:13 x9c4: x9c4 has joined triage 14:35:16 fao89: i closed it 14:35:22 +1 14:35:24 #idea Proposed for #7543: close as duplicated 14:35:24 !propose other close as duplicated 14:35:24 fao89: Proposed for #7543: close as duplicated 14:35:29 #agreed close as duplicated 14:35:29 !accept 14:35:29 fao89: Current proposal accepted: close as duplicated 14:35:30 #topic https://pulp.plan.io/issues/7542 14:35:30 fao89: 3 issues left to triage: 7542, 7532, 7513 14:35:31 RM 7542 - wilful - NEW - Can't upload artifacts and filter artifacts does't work 14:35:32 https://pulp.plan.io/issues/7542 14:36:03 he needs to use == in the filter 14:36:08 I just commented 14:36:13 daviddavis++ 14:36:13 dkliban: daviddavis's karma is now 365 14:36:39 close as not a bug? 14:36:42 +1 14:36:43 sure 14:36:55 +1 14:36:55 #idea Proposed for #7542: close as notabug 14:36:55 !propose other close as notabug 14:36:55 fao89: Proposed for #7542: close as notabug 14:36:59 #agreed close as notabug 14:36:59 !accept 14:36:59 fao89: Current proposal accepted: close as notabug 14:37:00 #topic https://pulp.plan.io/issues/7532 14:37:00 fao89: 2 issues left to triage: 7532, 7513 14:37:01 RM 7532 - mdepaulo@redhat.com - NEW - pulpcore-selinux fails to build due to unknown type pulpcore_etc_t 14:37:02 https://pulp.plan.io/issues/7532 14:37:27 selinux tag 14:37:33 accept and add to sprint 14:37:42 and add selinux tag 14:37:47 yes yes 14:37:58 +1 14:38:04 #idea Proposed for #7532: accept and add to sprint 14:38:04 !propose other accept and add to sprint 14:38:04 fao89: Proposed for #7532: accept and add to sprint 14:38:07 #agreed accept and add to sprint 14:38:07 !accept 14:38:08 #topic https://pulp.plan.io/issues/7513 14:38:08 fao89: Current proposal accepted: accept and add to sprint 14:38:09 fao89: 1 issues left to triage: 7513 14:38:10 RM 7513 - thm - NEW - bulk-delete tasks 14:38:11 https://pulp.plan.io/issues/7513 14:38:16 convert to story 14:38:18 +1 14:38:30 +1 14:38:39 #idea Proposed for #7513: convert to story 14:38:39 !propose other convert to story 14:38:39 fao89: Proposed for #7513: convert to story 14:38:44 #agreed convert to story 14:38:44 !accept 14:38:44 fao89: Current proposal accepted: convert to story 14:38:45 fao89: No issues to triage. 14:39:00 open floor! 14:39:09 https://hackmd.io/@pulp/triage/edit 14:39:13 CI status 14:39:16 pulp CI is failing due to the docs publishing changes 14:39:22 pulp and pulplift are failing 14:39:24 i will update the 2-master branch 14:39:36 with the new username that should be used 14:39:44 great 14:40:06 pulplift is failing due to fedora vagrant boxes being old ... or that's my theory 14:40:37 actually, it's gettinga 500 error from vagrant cloud trying to download F 31 and F32 boxes 14:40:46 ah so intermittent error 14:41:02 i think so 14:41:09 let's monitor then to see if it keeps happening 14:41:09 let's see what happens next time it runs 14:41:19 !topic Flip triage will open floor. It is easier to advertise and get attention for open floor then triage 14:41:19 fao89: (topic []) -- Returns the topic for . is only necessary if the message isn't sent in the channel itself. 14:41:29 topic: Flip triage will open floor. It is easier to advertise and get attention for open floor then triage 14:42:16 this came as suggestion during pulpcon 14:43:32 open floor is one of the ways to get interaction with our community, however because it does not have an exact time when it starts it is not possible to advertise it 14:43:33 thoughts? 14:43:45 open floor can take a long time 14:43:51 and we would need to timebox it 14:43:51 that's true 14:44:08 what about time boxing it for 30 mins? 14:44:23 what about doing a video call with users once a month 14:44:28 ? 14:44:45 people who would have the intention to join i would expect to do so in the first 30 mins 14:44:51 dkliban: yeah we could 14:45:02 dkliban: good idea, but with chat as backup, I think not everyone wan't to video 14:45:03 the benefit of open floor is that it is twice a week 14:45:29 I like chat for this meeting but I'm in favor of a once a month video call 14:45:43 so let's go back to the original suggestion 14:46:22 my concern with making open floor 30 mins at the begining is that it sometimes doesnt' take 30 mins 14:46:23 bmbouter: what would be the program of that meeting, how do you see it advertised? 14:46:45 we could timebox the triage 14:46:54 we can plan it for 30 minutes, and if no topics wait 10mins for user and then skip to triage 14:46:54 dkliban: i share that concern 14:47:00 we generally do it in 10-20 minutes 14:47:23 ipanova: it's not related to this meeting really, let me put it as it's own idea at the end of open floor for today on the agenda 14:47:49 and we can: skip to discuss at open floor 14:49:19 so who is in favor of having open floor be 30 minutes at the begining of this meeting/ 14:49:21 ? 14:50:04 bmbouter: the benefit i see to keep this in the open floor is that people can come twice a week and have "clinic hours", having this once a month might be too seldom 14:50:05 +1 if option to skip if no topics/users available 14:50:38 I'm in favor of tying the switch. We can always go back if doesnot work out 14:50:46 bmbouter: also having this as a separate meeting might lead to no topics at all, while having this combined with open floor we will always gather together and have things to get discussed 14:51:22 it doesn't have to be video 14:51:29 my idea and dennis' are not really related actually at all 14:51:35 lol 14:51:47 so let's finish this topic though 14:52:26 i am in favor of trying to switch 14:52:29 i don't see much value in switching open floor to the begining of the meeting ... however, if there are others that see the value, i am not going to oppose it 14:52:29 I want this to stay as written because chat meetings promote inclusivity both in terms of record and for english as second language folks who are more comfortable in a written format (what I've learned from osas) 14:52:39 switching the order is fine w/ me 14:52:56 I don't have a strong opinion but am happy to try out the switch 14:53:01 cool 14:53:06 it sounds like we are going to try it out 14:53:10 when we start the switch? 14:53:14 friday! 14:53:20 !friday 14:53:20 ♪ It's Friday, Friday, gotta get down on Friday ♪ 14:53:21 dkliban: i think i care more of the open floor having an exact time to start, whether this is before or after triage i do not really care 14:53:50 topic: Proposal: disable merging by commit for pulpcore and pulp_file 14:54:06 bmbouter: agreed on the written format 14:54:32 i think this change will require us to change how we checkout Required PRs 14:54:42 will it? 14:54:48 daviddavis: i was about to ask you 14:54:50 I've not used merge by commit in 3 years 14:54:50 lol 14:55:08 I think everything should work 14:55:23 here's a great illustration of merge by commit vs not using merge by commit https://imgur.com/a/uiIa0Mr 14:55:27 are we going to disable creating of a merge commit? 14:55:39 yes exactly 14:55:46 just use rebase and merge 14:56:03 that's what I've been using now for years 14:56:17 i am for this 14:56:28 me too 14:56:47 I am also +1 14:56:53 cool, I make this change to pulpcore and pulp_file 14:56:58 yes please! 14:57:28 daviddavis: can you share where this change will happen? 14:57:34 in the repo settings? 14:58:07 ipanova: yea go to https://github.com/pulp/pulpcore/settings and scroll down to merge button 14:58:47 done. 14:58:47 daviddavis: i see,thanks 14:58:51 np :) 14:59:08 I'll send out a quick email too 14:59:27 sounds good 14:59:51 topic: What about a "Pulp, what the heck?" invite, maybe with video (or not)? 15:00:42 i like this 15:00:57 +1 15:01:03 the thing is - most of the users will come from pulp2 experience 15:01:05 maybe we could also demo stuff too 15:01:16 we can do it on IRC, but i also see value of doing it on a different platfrom that people that avoid IRC might be more willing to participate in 15:01:23 are we going to highlight that this is pulp3 only? 15:01:41 ipanova: it doesn't matter ... we will just tell them to use pulp 3 15:01:47 lol 15:01:58 dkliban: well i am not sure this kind of answer will be helpful for them 15:02:09 expecially if migration wise are not production ready 15:02:33 "I can't sync from puppet forge" 15:02:36 "use pulp 3!!" 15:02:43 nope ... switch to ansible 15:02:46 lol 15:02:49 lol 15:03:11 yeah so this what the heck idea 15:03:16 we used to have the demo session on youtube, why it stopped? 15:03:38 we stopped because we weren't getting demo's recorded by developers 15:03:47 if i come to share my pain points my hope/expectations that i will be provided some sort of workaround/fix. if the answer will be - switch to pulp3 this will not help my today's pain 15:04:35 i am in favor of having this sessions however i would at least try to highlight that this is pulp3 targeted. 15:04:38 thoughts? 15:04:55 pulp2 is in maintenance mode so we can't fix there, but I still want them to express their pain 15:05:01 I agree with you ipanova 15:05:04 here is the hass.io invite on their WTH https://www.home-assistant.io/blog/2020/08/18/the-month-of-what-the-heck/ 15:06:05 I like this idea 15:06:26 bmbouter: i am +1 on hearing the pain points independent of the version they use 15:06:54 what will be the next steps? shall we draft a blogpost? 15:07:02 i agree ... we want to hear about user experience 15:08:21 we should mention to mcorr somewhere/somehow I think 15:08:33 speaking of the format - video or written form I think we should start with a written form 15:09:05 people could share their experience in an email and we would then work towards a blogpost in a format: problem ---> solution 15:09:47 how does it differ from using pulp-list? 15:09:58 bmbouter: what about putting this among headlines at our pulpteam meeting 15:10:32 fao89: it will be i guess better articulated and targeted to cover bigger audience 15:10:51 plus not everyone as it turns out are subscribed to our lists 15:12:04 does the user need be subscribed to send an email to pulp-list? 15:12:10 fao89: yes 15:12:16 otherwise spammers send 15:12:24 also users wouldn't receive a reply 15:13:17 =/ 15:13:18 ipanova: I'll add to a headline 15:13:37 sounds good, thank you 15:13:51 so we'll discuss the format on Monday/? 15:14:17 dkliban: i think so, plus get some input from mcorr 15:16:02 sounds good 15:16:44 #endmeeting 15:16:44 !end