Tuesday, 2020-11-24

*** tosky has quit IRC00:17
*** ralonsoh has quit IRC00:46
*** ralonsoh has joined #openstack-meeting-300:46
*** mlavalle has quit IRC01:26
*** freerunner has quit IRC02:12
*** DinaBelova has quit IRC02:12
*** DinaBelova has joined #openstack-meeting-302:13
*** freerunner has joined #openstack-meeting-302:13
*** psachin has joined #openstack-meeting-303:32
*** baojg has quit IRC05:48
*** baojg has joined #openstack-meeting-305:52
*** ralonsoh has quit IRC06:46
*** lpetrut has joined #openstack-meeting-307:53
*** slaweq has joined #openstack-meeting-308:02
*** ralonsoh has joined #openstack-meeting-308:15
*** tosky has joined #openstack-meeting-308:48
*** baojg has quit IRC08:58
*** baojg has joined #openstack-meeting-308:58
*** baojg has quit IRC09:06
*** baojg has joined #openstack-meeting-309:07
*** obondarev has joined #openstack-meeting-309:13
*** ricolin has joined #openstack-meeting-309:19
*** e0ne has joined #openstack-meeting-309:40
*** e0ne has quit IRC09:40
*** baojg has quit IRC09:42
*** baojg has joined #openstack-meeting-309:43
*** ricolin has quit IRC09:44
*** e0ne has joined #openstack-meeting-310:04
*** macz_ has joined #openstack-meeting-311:03
*** macz_ has quit IRC11:07
*** ralonsoh has quit IRC11:20
*** ralonsoh has joined #openstack-meeting-311:23
*** e0ne has quit IRC11:29
*** baojg has quit IRC11:46
*** baojg has joined #openstack-meeting-311:47
*** e0ne has joined #openstack-meeting-312:04
*** Luzi has joined #openstack-meeting-312:07
*** baojg has quit IRC12:15
*** baojg has joined #openstack-meeting-312:16
*** slaweq has quit IRC12:29
*** slaweq has joined #openstack-meeting-312:31
*** artom has joined #openstack-meeting-313:03
*** baojg has quit IRC13:05
*** baojg has joined #openstack-meeting-313:06
*** belmoreira has joined #openstack-meeting-313:07
*** obondarev has quit IRC13:19
*** lpetrut has quit IRC13:36
*** lpetrut has joined #openstack-meeting-313:38
*** obondarev has joined #openstack-meeting-313:48
*** Luzi has quit IRC13:55
*** lajoskatona has joined #openstack-meeting-313:59
slaweq#startmeeting networking14:00
openstackMeeting started Tue Nov 24 14:00:15 2020 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: networking)"14:00
openstackThe meeting name has been set to 'networking'14:00
* slaweq needs 5 minutes before we will start14:00
slaweqok, lets start14:03
*** hemanth_n has joined #openstack-meeting-314:04
slaweq#topic Announcements14:04
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:04
slaweqNext week is Wallaby-1 milestone14:05
slaweqPlease focus on reviewing opened specs - https://review.opendev.org/q/project:openstack/neutron-specs+status:open14:05
slaweqthere are some on the list which waits pretty long time to be reviewed :)14:05
slaweqnext one14:05
slaweqas You probably all already noticed, this weekend was upgrade of gerrit14:06
slaweqsome details about it can be found on  http://lists.opendev.org/pipermail/service-announce/2020-November/000014.html14:06
slaweqand that's basically all announcements from me for today14:07
slaweqanythning else anyone wants to share now?14:07
haleybAnd there is also https://etherpad.opendev.org/p/gerrit-3.2-post-upgrade-notes for the bugs14:08
lajoskatonayeah the most important is manual lp bug update as I remmeber14:08
obondarevdoes anyone know if it's possible to switch to old interface? :)14:09
bcafarelfrom that etherpad apparently no, the hooks are not there anymore :(14:09
haleybi wish it was, as my very useful tampermonkey script is not so useful14:09
bcafarel(including the CI results view that could be updated with tampermonkey)14:10
bcafarelany JS motivated folks to fix that would be most welcome I think!14:10
haleybbcafarel: yes, that is the worst thing for me, real time results14:10
slaweqobondarev: I wish it would be :)14:10
haleybthere's always gertty14:10
obondarevyeah, CI results are most annoying14:10
slaweqtrue, and it's even worst when I'm checking many patches before ci meeting :/14:11
slaweqin old gerrit I saw failed jobs immediately, now I need to read through comments to find them :/14:11
obondarevhopefully will be fixed soon!14:12
slaweqok, lets move on to the next topic14:12
slaweq#topic Blueprints14:12
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:12
slaweqWallaby-1 https://bugs.launchpad.net/neutron/+milestone/wallaby-114:12
slaweqany updates here?14:13
slaweqlajoskatona: question about https://bugs.launchpad.net/neutron/+bug/188280414:14
openstackLaunchpad bug 1882804 in neutron "RFE: allow replacing the QoS policy of bound port" [Wishlist,Confirmed] - Assigned to Lajos Katona (lajos-katona)14:14
slaweqis the only missing here the patch to tempest?14:15
lajoskatonaslaweq: yes?14:15
lajoskatonayes, I think so14:15
slaweqor there is somethig more not included on the list?14:15
lajoskatonano that's all, thanks fro reminder, I go for QA team to ask them for review14:16
slaweqI will try to look at it and also ping gmann to look at it :)14:16
lajoskatonaas I remember last time they had no objection14:16
slaweqthat's good :)14:17
slaweqfrom the other things, please review https://review.opendev.org/c/openstack/neutron/+/71531514:18
slaweqralonsoh did great job with this and it seems that it is last piece to close this long standing BP about migration to the new engine facade14:18
slaweq(even if this engine facade isn't really new anymore :P)14:18
ralonsohlet's go for it!!14:18
bcafarelthat will be wallaby cycle highlight for sure (even if it has been "new" for such long time)14:19
slaweqralonsoh: it failed functional job https://e5392d8b5c67a9e24e1f-aa881d493e66ac85e397d3a18f294794.ssl.cf5.rackcdn.com/715315/24/check/neutron-functional-with-uwsgi/a153821/testr_results.html14:19
slaweqbut it doesn't seems to be related to that patch at all14:19
ralonsohnot related, for sure14:19
ralonsohbut I'll keep an eye14:20
slaweqand that's all from my side regarding Blueprints14:20
slaweqany other updates about BPs?14:22
slaweqok, I'll take it as "no"14:23
slaweqlets move on14:23
slaweq#topic Community Goals14:23
*** openstack changes topic to "Community Goals (Meeting topic: networking)"14:23
*** lkoranda has joined #openstack-meeting-314:23
slaweqMigrate from oslo.rootwrap to oslo.privsep14:23
ralonsohwe have several patches uploaded14:24
slaweqregarding this one I worked with ralonsoh a bit and prepared etherpad https://etherpad.opendev.org/p/neutron-migration-to-privsep14:24
slaweqand ralonsoh is pushing patches for that14:24
slaweqif anyone wants to help, please ask ralonsoh about what is todo (or check in etherpad but it may not be ready fully)14:24
ralonsoh(I need to put those links there)14:24
slaweqalso - we need some volunteer to work on stadium projects regarding this goal14:25
lajoskatonaI add bagpipe later14:26
lajoskatonathere's some patches already uploaded for that14:26
slaweqlajoskatona: thx a lot14:26
slaweqregarding Migrate RBAC Policy Format from JSON to YAML - I don't know if amotoki did something already14:28
amotokiregarding the policy format to yaml, I am preparing a patch and will push it this week. it looks like simple enough and we can finish it only in the neutron repo change.14:28
slaweqamotoki: great, thx for info :)14:28
slaweqI think that we can move forward14:29
slaweq#topic Bugs14:30
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:30
slaweqjlibosva was bug deputy last week14:30
slaweqbut I didn't saw any email from him14:30
slaweqI just pinged him, maybe he will be able to join14:31
slaweqin the meantime, do You have any bugs You want to discuss today?14:33
slaweqok, I think that this means "no" :)14:35
bcafarelI don't see any in my launchpad mail folder (some fixes already merged, rest looks "normal" bug week)14:35
slaweq"normal bug week" sounds good ;)14:35
haleybyeah, there's only a lot when i'm deputy :-/14:35
slaweqhaleyb: LOL14:35
slaweqhaleyb: speaking about that, there is new round of bug deputy prepared by me14:36
slaweqit starts next week with bcafarel14:36
slaweqand haleyb's week is December 21st14:36
slaweqso I think it should be quiet week :)14:36
slaweqhaleyb: are You ok with that?14:36
*** jlibosva has joined #openstack-meeting-314:37
haleybslaweq: hmm, think i'll be on pto that week and the next14:37
slaweqhi jlibosva :)14:37
jlibosvahello :)14:37
slaweqjlibosva: any bugs You want to raise here from last week?14:37
jlibosvayes, I sent the report to openstack-discuss14:38
jlibosvathere was one critical bug that needs an assignee14:38
openstackLaunchpad bug 1904897 in neutron "Failure in test_l2_agent_restart(OVS,Flat network)" [Critical,New]14:38
jlibosvaI can't find the email in the mailman, so here is the pastebin: http://paste.openstack.org/show/800367/14:39
jlibosvaother than that, there were 3 that I left undecided14:40
jlibosvahttps://bugs.launchpad.net/neutron/+bug/1904694 - I left a comment asking for clarification as it seemed like some tempest tests are not doing cleanup, not really a Neutron bug14:40
openstackLaunchpad bug 1904694 in neutron "Enforce security group cleanup (Resources leaks)" [Medium,Incomplete] - Assigned to Abhishek Jaiswal (jkabhishek)14:40
jlibosvathen there was this https://bugs.launchpad.net/neutron/+bug/1904751 that I closed because I couldn't reproduce14:41
openstackLaunchpad bug 1904751 in neutron "Neutron – it’s possible to delete router’s port related to external gateway" [Undecided,New]14:41
jlibosvathere was a patch in the report pointing to neutron-tempest-plugin to reproduce the issue but the test is failing somewhere else and I don't think it reproduces the issue14:41
slaweqI will work with reporter of https://bugs.launchpad.net/neutron/+bug/1904751 to be sure if that is an issue in Neutron or not14:42
openstackLaunchpad bug 1904751 in neutron "Neutron – it’s possible to delete router’s port related to external gateway" [Undecided,New]14:42
jlibosvaslaweq: I quickly also checked the last patch he sent and it fails now on "list_ports" based on router_id, api complaining router_id is not a valid keyboard for filtering14:43
jlibosvalast undecided is: https://bugs.launchpad.net/neutron/+bug/1904869 - the bug is about BGP agent reporting as dead14:43
openstackLaunchpad bug 1904869 in neutron "neutron-dynamic-routing reported as not alive after adding BGP Peer to BGP Speaker" [Undecided,Incomplete]14:43
jlibosvaI asked if the RPC layer was configured well because I didn't see it in the conf, now I see the reporter replied14:44
jlibosvait was just my guess that BGP agent uses RPC too as other agents as I'm not well familiar with it14:44
slaweqjlibosva: thx14:46
jlibosvathere were other bugs that I set priority and milestone accordingly, more in the report. not sure why it's not on the ML, I got an email that moderator has to approve it, so maybe he hasn't approved the mail yet14:46
slaweqthx jlibosva for the report14:47
slaweqif there will be no other volunteers I will try to investigate this issue with fullstack test14:48
haleybjlibosva: maybe you used a different email to signup for the list?  my redhat one is always rejected14:48
jlibosvahaleyb: I actually don't remember :) I also have a RH alias so maybe that's causing the issue. I'll try to look at that, thanks for the tip14:49
slaweqI guess that with that we are done with our today's meeting14:51
*** baojg has quit IRC14:51
slaweqso I'm going to give You back few minutes14:51
slaweqsee You on the CI meeting in 9 miutes :)14:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:51
openstackMeeting ended Tue Nov 24 14:51:36 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2020/networking.2020-11-24-14.00.html14:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2020/networking.2020-11-24-14.00.txt14:51
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2020/networking.2020-11-24-14.00.log.html14:51
*** baojg has joined #openstack-meeting-314:52
*** hemanth_n has quit IRC14:53
*** e0ne has quit IRC14:57
slaweq#startmeeting neutron_ci15:00
openstackMeeting started Tue Nov 24 15:00:16 2020 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_ci)"15:00
openstackThe meeting name has been set to 'neutron_ci'15:00
* bcafarel finishes his coffee just in time15:00
gmannslaweq: lajoskatona how can I help you?15:00
slaweqwelcome (again)15:00
slaweqgmann: hi15:00
gmannplease ping me link I will review the tempest one.15:01
slaweqgmann: we were just talking about patch15:01
slaweqif You will have some time to review, that would be great :)15:01
gmannslaweq: ack, will check today15:01
slaweqthx a lot gmann15:01
lajoskatonagmann: Hi, I send it15:02
lajoskatonaslaweq was quivker15:02
gmannlajoskatona: sure, i will review it today15:02
lajoskatonagmann: thanks15:02
slaweqok, lets go with our ci meeting now :)15:03
slaweqGrafana dashboard: http://grafana.openstack.org/dashboard/db/neutron-failure-rate15:03
slaweqand agenda is on etherpad https://etherpad.opendev.org/p/neutron-ci-meetings15:03
slaweq#topic Actions from previous meetings15:03
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"15:03
slaweqfirst one was:15:03
slaweqslaweq to report bug regarding errors 500 in ovn functional tests15:03
*** macz_ has joined #openstack-meeting-315:03
slaweqit already was reported: https://bugs.launchpad.net/neutron/+bug/190300815:03
openstackLaunchpad bug 1903008 in neutron "Create network failed during functional test" [High,Confirmed]15:03
*** macz_ has quit IRC15:03
slaweqand we are actually waiting for ralonsoh's patch with engine facade migration first15:04
slaweqso this is "on hold" for now15:04
*** macz_ has joined #openstack-meeting-315:04
slaweqand next one was:15:04
slaweqralonsoh will decrease number of test workers in scenario jobs15:04
slaweqfast :)15:04
ralonsohsorry, I didn't find it15:05
slaweqI hope it will make those jobs more stable15:06
bcafarelcrossing fingers15:06
slaweqthx ralonsoh :)15:07
slaweqok, lets move on15:07
slaweq#topic Stadium projects15:07
*** openstack changes topic to "Stadium projects (Meeting topic: neutron_ci)"15:07
slaweqanything regarding stadium to discuss today?15:07
bcafarelsmall stable/stadium update, https://bugs.launchpad.net/neutron/+bug/1903689/comments/515:08
openstackLaunchpad bug 1903689 in neutron "[stable/ussuri] Functional job fails - AttributeError: module 'neutron_lib.constants' has no attribute 'DEVICE_OWNER_DISTRIBUTED'" [Medium,In progress] - Assigned to Bernard Cafarelli (bcafarel)15:08
lajoskatonanothing special, perhasp this one: https://review.opendev.org/c/openstack/networking-odl/+/76321015:08
bcafarelbasically, adding neutron to upper-constraints needs to be done manually when creating new stable branch (maybe to add to a list of steps for that?)15:09
bcafarelI will send patches for train to victoria (forgot to do it yesterday) to catch up15:09
slaweqbcafarel: can You also check https://docs.openstack.org/neutron/latest/contributor/policies/release-checklist.html if it's is up to date?15:10
slaweqand maybe update with this info if needed15:10
bcafarelooh nice, I wondered if we had something like that15:10
bcafarelslaweq: will do, and check other stuff I think of (adding branch tempest template, remove *master* jobs, etc)15:11
slaweqbcafarel++ thx a lot15:11
slaweq#action bcafarel to fix stable branches upper-constraints in stadium projects15:12
slaweq#action bcafarel to check and update doc https://docs.openstack.org/neutron/latest/contributor/policies/release-checklist.html15:12
slaweq^^ just to not forget (that bcafarel voluneer for that :P)15:12
slaweqlajoskatona: and regardig Your patch, I already +2 it15:13
slaweqso You need e.g. ralonsoh to check that15:13
lajoskatonaslaweq: thanks, just som eadvertisement for more attention :-)15:13
slaweqok, next topic15:15
slaweq#topic Stable branches15:15
*** openstack changes topic to "Stable branches (Meeting topic: neutron_ci)"15:15
slaweqVictoria dashboard: http://grafana.openstack.org/d/pM54U-Kiz/neutron-failure-rate-previous-stable-release?orgId=115:15
slaweqUssuri dashboard: http://grafana.openstack.org/d/dCFVU-Kik/neutron-failure-rate-older-stable-release?orgId=115:15
bcafarelmy unread backlog for stable is not too bad, so I'd say stble branches are good15:16
bcafarel(well except still pending https://bugs.launchpad.net/neutron/+bug/1903531 )15:16
openstackLaunchpad bug 1903531 in neutron "Update of neutron-server breaks compatibility to previous neutron-agent version" [Critical,Confirmed] - Assigned to Slawek Kaplonski (slaweq)15:16
slaweqsorry, correct links:15:16
slaweqVictoria dashboard: https://grafana.opendev.org/d/HUCHup2Gz/neutron-failure-rate-previous-stable-release?orgId=115:16
slaweqUssuri dashboard: https://grafana.opendev.org/d/smqHXphMk/neutron-failure-rate-older-stable-release?orgId=115:17
slaweqthx bcafarel - that is good topic to discuss15:18
slaweqand I forgot about it on previous meeting15:18
slaweqI don't really know what to do with it now :/15:18
slaweqthe problem is that IIUC fix should go to the agent's side15:20
slaweqand if agent will be already updated, there will be no issue at all15:20
slaweqis my understanding correct?15:20
bcafarelchecking that original commit again15:21
bcafarelslaweq: so having a fix in agent to handle both types, and note that agents should be updated first for this bug?15:22
slaweqproblem is that officially supported update path is that first server should be updated always15:23
slaweqas it should handle compatibility with older agents15:23
lajoskatonawhat I can't see what happens if the revert will be merged15:23
slaweqnot vice versa15:23
lajoskatonahow that affects these deployments15:23
slaweqlajoskatona: when we will revert that change, someone who already updated to e.g. 15.3 will have the same issue again15:24
slaweqbut in the opposite direction15:24
ralonsohexactly, they will experience the same problem15:24
slaweqbecause his server will send (ip, mac) tuple15:24
lajoskatonaok, so the fix would be better15:24
slaweqbut how to fix it?15:24
ralonsohbecause they have already rebooted the agents15:24
*** e0ne has joined #openstack-meeting-315:24
ralonsohsend a patch handling both possible RPC responses15:25
ralonsoh(IP) or (IP, MAC)15:25
slaweqralonsoh: but that patch needs to be on Agent's side, right15:25
ralonsohin both, if I'm not wrong15:25
ralonsohthis is something sent by the server15:25
slaweqralonsoh: yes, it is send by server15:28
slaweqbut how You want to send 2 things by server?15:28
ralonsohno, if the server is updated, it should send (IP,MAC)15:29
ralonsohbut, TBH, to those deployments no updated15:30
slaweqso agent should be changed that it would be able to handle both cases15:30
ralonsohif they follow the update procedures15:30
ralonsohfirst the server, then the agents15:30
ralonsohif we don't revert the original patch, then when the server is updated15:30
ralonsohthe RPC will send  (IP,MAC)15:30
ralonsohand the agents won't understand this15:30
slaweqyes, that's the problem15:31
ralonsohso maybe we should just revert the patch in stable releases15:31
slaweqbut if we will revert it in stable branches, then for deployments which already updated to latest Train (or Stein) the issue will be the same15:32
slawequpdated server will again send just IP15:32
slaweqand agent will expect (IP, MAC) as it will not have reverted change yet15:32
bcafarelI guess it will be limited number of deployments - if we cannot have fix soon it may be the "not so bad" option15:33
bcafarelfix it for people that have not updated yet, with the cost of additional trouble for those (hopefully few) who did15:33
slaweqI think that will be better but I'm not 100% sure about that15:34
slaweqok, I will try to play with it a bit more15:34
slaweqand lets discuss that on drivers meeting on Friday and decide there what to do with it15:34
slaweqare You ok with this plan?15:35
bcafarelsounds good15:35
*** lpetrut has quit IRC15:35
slaweqwe may also say that e.g. 15.3 is "broken" and maybe remove it from pypi if possible15:36
slaweqso no new people will update to that verion15:36
ralonsohthat's also an option15:36
slaweqI will ask release team for that15:36
bcafarel+1 that would be good in the meantime15:36
slaweq#action slaweq to explore options to fix https://bugs.launchpad.net/neutron/+bug/190353115:36
openstackLaunchpad bug 1903531 in neutron "Update of neutron-server breaks compatibility to previous neutron-agent version" [Critical,Confirmed] - Assigned to Slawek Kaplonski (slaweq)15:36
slaweqok, lets move on now15:37
slaweq#topic Grafana15:37
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"15:37
slaweqin overall I think that it looks not so bad this week15:37
ralonsohit's getting better, yes15:38
slaweqlooking e.g. at https://grafana.opendev.org/d/PfjNuthGz/neutron-failure-rate?viewPanel=20&orgId=115:39
slaweqall except ovn job looks pretty good this week15:39
slaweqand there is much less ssh authentication failures recently IMO15:39
bcafarelthat's nice15:40
slaweqregarding specific jobs15:40
slaweq#topic Tempest/Scenario15:40
*** openstack changes topic to "Tempest/Scenario (Meeting topic: neutron_ci)"15:40
slaweqI was looking at various failures from last week today15:41
slaweqand I didn't found many new issues15:41
slaweqI just found 2 examples of SSH failure in ovn jobs:15:41
slaweqI didn't report it yet on LP15:41
slaweqbut I will15:41
slaweqbut really https://7513009f5bff8f76e461-f83d06667d580e000031601b82c71a43.ssl.cf2.rackcdn.com/763246/1/gate/neutron-ovn-tempest-ovs-release/acf920f/testr_results.html is probably known issue with some race in paramiko15:43
slaweqbut there wasn't console output there15:43
ralonsohdid you push the patch to tempest?15:43
slaweqtempest patch is merged15:44
ralonsohthat one waiting for the VM output to mitigate the paramiko problem15:44
slaweqbut in that case it was waiting for more than 10 minutes, checking console output15:44
slaweqand it failed later :/15:45
slaweqI don't have any other examples of the failures in tempest jobs for this week15:47
slaweqlets move on15:47
slaweq#topic Rally jobs15:47
*** openstack changes topic to "Rally jobs (Meeting topic: neutron_ci)"15:47
slaweqI found today few cases with failure like:  https://zuul.opendev.org/t/openstack/build/be642647ac1e4f5993a65e5f3f91a7a5 in rally job15:47
slaweqdo You know maybe if that is known issue?15:48
slaweqI will report that agains rally as it doesn't seems to be issue in neutron really15:49
slaweq#action slaweq to report bug against rally15:50
slaweqand that's all what I had for today15:51
slaweqdo You want to talk about anything else regarding CI today?15:51
haleybi had one question, kind-of related to CI15:51
haleybI've been randomly working on fixing issues using IPv6 addresses for tunnel endpoints15:52
haleyband i sent out a WIP at https://review.opendev.org/c/openstack/neutron/+/76066815:52
haleybi was wondering if something like that should just be in one of the existing CI jobs15:52
haleybtruly making things ipv6-only15:53
slaweqhaleyb: isn't it like that in tempest-ipv6-only job?15:53
haleybi don't think it does the tunnel does it?15:54
haleybi just added that TUNNEL_IP_VERSION to devstack, it actually hasn't merged yet15:55
slaweqmaybe You can then change that tempest-ipv6-only job15:55
slaweqas it is indended to be ipv6-only :)15:55
haleybslaweq: yes, i thought about that too, just didn't want to break everyone that inherited that15:56
haleybbut maybe noone will notice with the new gerrit :)15:57
slaweqhaleyb: if You don't want to break anything for other projects You can propose new job like neutron-tempest-ipv6-only15:57
ralonsohbut slaweq is right, according to the playbooks, "ipv6-only-deployments-verification" should "Verify the IPv6-only deployments"15:57
slaweqwhich will inherit from tempest-ipv6-only and will also set this one var15:57
ralonsohand this is executed in tempest ipv615:58
slaweqthen we can run only this new job in our queue15:58
slaweqhaleyb: can You sync with tempest folks what would be better for them?15:58
haleybslaweq: sure, i can propose something there and ask them for comments15:59
slaweqhaleyb++ thx15:59
slaweqok, we are running out of time now15:59
slaweqthx for attending the meeting15:59
slaweqand see You online15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:59
openstackMeeting ended Tue Nov 24 15:59:52 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2020/neutron_ci.2020-11-24-15.00.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2020/neutron_ci.2020-11-24-15.00.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2020/neutron_ci.2020-11-24-15.00.log.html15:59
*** lajoskatona has left #openstack-meeting-316:01
*** mlavalle has joined #openstack-meeting-316:13
*** obondarev has quit IRC16:15
*** psachin has quit IRC16:16
*** lkoranda has quit IRC16:58
*** e0ne has quit IRC17:11
*** jlibosva has quit IRC18:30
*** jlibosva has joined #openstack-meeting-318:57
*** jlibosva has quit IRC19:01
*** jlibosva has joined #openstack-meeting-319:29
*** jlibosva has quit IRC19:37
*** belmoreira has quit IRC20:08
*** baojg has quit IRC20:52
*** baojg has joined #openstack-meeting-320:52
*** jlibosva has joined #openstack-meeting-320:59
*** artom has quit IRC21:00
*** artom has joined #openstack-meeting-321:01
*** artom has quit IRC21:02
*** artom has joined #openstack-meeting-321:03
*** jlibosva has quit IRC21:04
*** ralonsoh has quit IRC21:17
*** raildo has quit IRC21:17
*** jlibosva has joined #openstack-meeting-321:40
*** jlibosva has quit IRC21:45
*** baojg has quit IRC21:46
*** baojg has joined #openstack-meeting-321:47
*** baojg has quit IRC22:11
*** baojg has joined #openstack-meeting-322:12
*** slaweq has quit IRC23:09
*** jlibosva has joined #openstack-meeting-323:42
*** jlibosva has quit IRC23:50
*** tosky has quit IRC23:57

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!