14:31:22 #startmeeting Pulp Triage 2020-06-30 14:31:22 #info fao89 has joined triage 14:31:22 !start 14:31:22 Meeting started Tue Jun 30 14:31:22 2020 UTC. The chair is fao89. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:31:22 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:31:22 The meeting name has been set to 'pulp_triage_2020-06-30' 14:31:22 fao89: fao89 has joined triage 14:31:40 #info ppicka has joined triage 14:31:40 !here 14:31:40 ppicka: ppicka has joined triage 14:31:45 #info x9c4 has joined triage 14:31:45 !here 14:31:45 x9c4: x9c4 has joined triage 14:32:07 #info dkliban has joined triage 14:32:07 !here 14:32:07 dkliban: dkliban has joined triage 14:32:10 #info daviddavis has joined triage 14:32:10 !here 14:32:10 daviddavis: daviddavis has joined triage 14:32:13 !next 14:32:14 fao89: 3 issues left to triage: 7060, 7052, 7003 14:32:14 #topic https://pulp.plan.io/issues/7060 14:32:15 RM 7060 - daviddavis - NEW - Redmine/BZ automation failure: ImportError: cannot import name 'RHBugzilla' from 'bugzilla.rhbugzilla' 14:32:16 https://pulp.plan.io/issues/7060 14:32:32 !propose accept and add to sprint 14:32:32 fao89: propose accept Propose accepting the current issue in its current state. 14:32:37 +1 14:32:45 #info ttereshc has joined triage 14:32:45 !here 14:32:45 ttereshc: ttereshc has joined triage 14:32:49 +1 14:32:56 +1 14:33:02 #info bmbouter has joined triage 14:33:02 !here 14:33:04 bmbouter: bmbouter has joined triage 14:33:08 !accept 14:33:08 fao89: No action proposed, nothing to accept. 14:33:08 +1 14:33:15 !propose accept and add to sprint 14:33:15 fao89: propose accept Propose accepting the current issue in its current state. 14:33:17 !accept 14:33:17 fao89: No action proposed, nothing to accept. 14:33:23 ha 14:33:26 #idea Proposed for #7060: accept and add to sprint 14:33:26 !propose other accept and add to sprint 14:33:26 dkliban: Proposed for #7060: accept and add to sprint 14:33:27 !propose other accept and add to sprint 14:33:31 #agreed accept and add to sprint 14:33:31 !accept 14:33:31 fao89: Current proposal accepted: accept and add to sprint 14:33:31 #topic https://pulp.plan.io/issues/7052 14:33:32 fao89: 2 issues left to triage: 7052, 7003 14:33:33 RM 7052 - bmbouter - NEW - As an unauthenticated user I can list pulp_file repoistories 14:33:34 https://pulp.plan.io/issues/7052 14:33:43 story 14:33:51 oh wait 14:34:00 I should read the issue first and not the title 14:34:09 yep 14:34:17 accept and add to sprint? 14:34:23 #idea Proposed for #7052: accept and add to sprint 14:34:23 !propose other accept and add to sprint 14:34:23 fao89: Proposed for #7052: accept and add to sprint 14:34:45 +1 14:34:46 wait 14:34:51 is this happening on master? We should ask for a test... 14:34:52 hahaha 14:34:55 I get a 403 14:35:07 bmbouter: yeah ... i don't think this happens on master 14:35:18 https://gist.github.com/daviddavis/b2a3c4cba6e7392ec7e3d48975093cd2 14:36:00 I was on master but it was modified 14:36:12 so we can close NOTABUT for now 14:36:18 this evidence is convincing it's not 14:36:20 or works for me? 14:36:21 did you clear permission_classes? 14:38:11 +1 worksforme 14:38:12 since it does work 14:38:37 #idea Proposed for #7052: close as worksforme 14:38:37 !propose other close as worksforme 14:38:37 fao89: Proposed for #7052: close as worksforme 14:38:41 #agreed close as worksforme 14:38:41 !accept 14:38:41 fao89: Current proposal accepted: close as worksforme 14:38:42 #topic https://pulp.plan.io/issues/7003 14:38:42 fao89: 1 issues left to triage: 7003 14:38:43 RM 7003 - dkliban@redhat.com - NEW - pulpcore-content allows for // in some parts of the URL but not others 14:38:44 https://pulp.plan.io/issues/7003 14:38:52 i commented on it after open floor 14:39:00 i still need to open up a couple of tasks related to it 14:39:05 but we can go ahead and accept now 14:39:24 +1 14:39:41 +1 14:39:43 #idea Proposed for #7003: Leave the issue as-is, accepting its current state. 14:39:43 !propose accept 14:39:43 fao89: Proposed for #7003: Leave the issue as-is, accepting its current state. 14:39:57 #agreed Leave the issue as-is, accepting its current state. 14:39:57 !accept 14:39:57 fao89: Current proposal accepted: Leave the issue as-is, accepting its current state. 14:39:58 fao89: No issues to triage. 14:40:06 Open floor! 14:40:14 https://hackmd.io/SVCMjpwXTfOMqF2OeyyLRw 14:40:24 topic: Do we want to move mdellweg/ansible_module_pulp to the pulp namespace and publish as pulp.squeezer on galaxy? 14:41:06 +1 14:41:16 +1 14:41:20 https://github.com/mdellweg/ansible_modules_pulp 14:41:31 +1 14:41:49 x9c4: i can work with you to make this happen 14:41:56 :D 14:41:58 does anyone object? 14:43:27 no objections at all 14:43:32 I think we can move to next topic 14:43:36 I dunno. I think we should wait longer. 14:43:38 jk 14:43:51 * x9c4 cheers wildly 14:43:59 * bmbouter dances 14:43:59 * daviddavis cheers crazily 14:44:04 topic: pulpcon https://hackmd.io/4dL6Eg2fSyq2MQsUydGM2A 14:44:30 can make an edit or two live? 14:44:34 small things... 14:44:41 sure 14:44:44 let's do it 14:44:57 yep 14:45:51 does getting ^ into a blog post make any sense? 14:45:55 Should we change countries to timezones? 14:46:03 yes we should 14:46:05 yep 14:46:07 ttereshc: +1 14:46:25 i didn't want to do timezones cause i wasn't sure what the eastern one was going to be called when we have the event 14:46:30 but that is not a big deal 14:46:34 let's do timezones 14:47:12 dkliban: so that would be a local instead 14:47:14 locale 14:47:38 e.g. eastern time is the locale, eastern standard or eastern daylight are the timezones 14:47:46 yeah ... 14:47:59 CET and EST ? 14:48:11 +1 that's fine 14:48:30 I was trying to figure out how the czech one is called :D 14:48:38 I know the US one 14:49:03 central eastern time probably 14:49:33 yeah, I know it as gmt+1 or +2 14:49:47 yup 14:50:18 should we mention where the dates will be announced? pulp-list? 14:50:24 include GMT so everyone can make hist own calculation? 14:50:25 or pulp-dev? 14:50:46 +1 pulp-dev 14:50:59 so I'm using this these days ... https://everytimezone.com/ 14:51:39 I just learned I'm in Papa Time Zone 14:51:52 LOL 14:52:19 Papa == pope in Portuguese 14:53:10 should we move to the next topic? 14:53:41 i think so. 14:53:46 bmbouter:? 14:54:05 yes but who is taking the next steps? 14:54:14 i'll send it out 14:54:23 or ttereshc ... did you want to do it? 14:54:27 you started this process 14:55:01 dkliban, up to you 14:55:07 I can 14:55:21 I have a meeting at 11 but I'm interested in discussing the next topics 14:55:38 let's move on, dkliban or I will send it 14:55:48 +1 14:55:55 topic: Should we relax the Repository name uniqueness accross all of Pulp to be just for a single plugin? 14:57:02 Should it be ... just for a single RepoType? 14:57:08 this question popped up again during our container meeting 14:57:27 what was the context? 14:57:39 what prevents us to change the constraint to repo name and repo type? 14:58:04 daviddavis: we have two types of repositories in pulp container 14:58:06 daviddavis: that if you have a repo 'test' created in iso plugin, you won't be able to create a test repo in any other plugin 14:58:30 I see 14:59:07 fwiw, I think soon this won't be an issue at all with RBAC ueryset restriction 14:59:23 in terms of having it "fully loosened", in fact we'll have to 15:00:59 dkliban, do you remember a user asking for a feature to use repo names instead of uuids, or am I mixing it up with something else? 15:01:42 ttereshc: the user was asking to be able to use repository names to reference resource in the bindings 15:01:49 which means that the name would be part of the URL 15:02:21 this item for open floor is not related to that though 15:02:40 ok, thanks for recalling what it was 15:03:15 let's all think about this repo name uniqueness and come back to it next tuesday 15:03:42 i can even send a note to pulp-dev if that would help? 15:03:53 i'll explain the problem statement 15:03:58 that sounds good 15:04:04 yep 15:04:18 let's talk aobut https://pulp.plan.io/issues/6899 15:04:27 i would like us to work on this asap 15:05:49 yes I agree it's important 15:06:05 I'm +1, I think it's the most useful part to automate in the whole release process 15:07:54 I can take it 15:09:14 awesome 15:09:27 +1 15:09:27 #endmeeting 15:09:27 !end