Tuesday, 2022-02-01

*** oklhost_ is now known as oklhost07:16
opendevreviewSlawek Kaplonski proposed openstack/neutron master: Pass host parameter to the get_network_info method  https://review.opendev.org/c/openstack/neutron/+/82710107:23
opendevreviewSlawek Kaplonski proposed openstack/neutron master: Pass host parameter to the get_network_info method  https://review.opendev.org/c/openstack/neutron/+/82710107:32
*** kleini_ is now known as kleini08:13
slaweqlajoskatona: ralonsoh ykarel hi, I don't have time to look at it now but please check failure https://36d827c3b1c315f941c5-25d2473a8435e86d2da970876b6bac73.ssl.cf1.rackcdn.com/827101/3/check/neutron-ovs-tempest-multinode-full/8f28733/testr_results.html if You will have some time09:37
slaweqit seems for me that it may be some new bug in some tempest test (or maybe in job definition, IDK)09:37
slaweqthx in advance09:37
* slaweq needs to go afk now09:37
ykarelslaweq, ack will check after lunch09:38
lajoskatonaslaweq: thanks for highlight09:38
ykarellajoskatona, slaweq caused by https://review.opendev.org/c/openstack/tempest/+/82694609:42
ykarelmerged today09:42
lajoskatonaykarel: was quick, I just started to blame :-)09:42
ykarellajoskatona, you proposing fix or shall i send?09:45
lajoskatonaykarel: please, it's your finding :-)09:45
ykarelok /me sends09:46
ykarellajoskatona, slaweq  ralonsoh https://review.opendev.org/c/openstack/tempest/+/82725809:53
opendevreviewFernando Royo proposed openstack/ovn-octavia-provider stable/ussuri: Fix race condition retrieving logical router rows  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/82707710:02
ykarellajoskatona, can you +W https://review.opendev.org/c/openstack/neutron/+/82681110:14
ykarelxena gates are clear10:14
lajoskatonaykarel: done10:21
ykarelThanks lajoskatona 10:25
opendevreviewLajos Katona proposed openstack/tap-as-a-service master: Use ovs TUNNEL_ constants from new location  https://review.opendev.org/c/openstack/tap-as-a-service/+/82726310:51
fricklerlajoskatona: bcafarel: am I right in my understanding that no progress has been made yet in terms of getting n-d-r to work with OVN? the topic just came up again internally and I wonder how you folks deploy IPv6 connectivity for tenants at all without it10:53
lajoskatonafrickler: I have seen no progress, but perhaps RH folks have more insights on this topic10:55
opendevreviewLajos Katona proposed openstack/neutron master: OVN TestNBDbResources wait for NB_Global table to be present  https://review.opendev.org/c/openstack/neutron/+/82553011:10
fricklerseems I never created a bug report after adding it to the OVN gap list. I just did that and look what a nice number it received https://bugs.launchpad.net/neutron/+bug/195966611:10
ralonsohlajoskatona, sorry, I think you didn't see my last comment https://review.opendev.org/c/openstack/neutron/+/825530/7/neutron/tests/functional/plugins/ml2/drivers/ovn/mech_driver/ovsdb/test_ovn_db_resources.py11:25
opendevreviewFrode Nordahl proposed openstack/neutron master: [OVN] Off-path SmartNIC DPU Port Binding with OVN  https://review.opendev.org/c/openstack/neutron/+/80896111:47
lajoskatonaralonsoh: checking11:57
opendevreviewRodolfo Alonso proposed openstack/neutron master: [OVS] Add IPv6 ICMP RA to the default ingress rules  https://review.opendev.org/c/openstack/neutron/+/82715912:13
opendevreviewFrode Nordahl proposed openstack/neutron master: [OVN] Off-path SmartNIC DPU Port Binding with OVN  https://review.opendev.org/c/openstack/neutron/+/80896112:37
*** dasm|off is now known as dasm13:02
*** dasm is now known as dasm|rover13:02
marc-vorwerk676009243582062483Hello, we disabled today the neutron fwaas driver in our openstack environment. Is it safe to delete now all fwaas database tables? Or are these tables used for other things?13:25
opendevreviewFrode Nordahl proposed openstack/neutron master: [OVN] Off-path SmartNIC DPU Port Binding with OVN  https://review.opendev.org/c/openstack/neutron/+/80896113:26
ralonsohmarc-vorwerk676009243582062483, unused tables won't affect and I don't know if fwaas did some other change to the neutron tables referring to the fwaas ones13:38
ralonsohif you delete them, first make a DB backup13:38
lajoskatonaall: I will be perhaps a few minutes late from the team meeting (have to fetch my son from the school)13:39
opendevreviewLajos Katona proposed openstack/neutron master: OVN TestNBDbResources wait for NB_Global table to be present  https://review.opendev.org/c/openstack/neutron/+/82553013:40
marc-vorwerk676009243582062483thank you ralonsoh. Do you think its also safe to delete the neutron lbaas tables?13:50
*** marlinc is now known as Guest139313:51
ralonsohsame answer here, first make a backup. Those tables should be used only for lbaas, thus there should not be any problem13:54
opendevreviewMaor Blaustein proposed openstack/neutron-tempest-plugin master: Fix dependencies and PEP 8 new comments.  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/82729214:01
lajoskatona#startmeeting networking14:07
opendevmeetMeeting started Tue Feb  1 14:07:02 2022 UTC and is due to finish in 60 minutes.  The chair is lajoskatona. Information about MeetBot at http://wiki.debian.org/MeetBot.14:07
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:07
opendevmeetThe meeting name has been set to 'networking'14:07
lajoskatonaHi, sorry for being late....14:07
mlavalleo/14:07
ralonsohhi14:07
* mlavalle will be multitasking with a company internal meeting14:07
slaweqhi14:07
rubasovo/14:07
obondarevhi14:08
isabekHi14:08
amotokihi14:08
lajoskatonaok, let's start14:08
lajoskatona#topic Announcements14:08
lajoskatonathe usual Yoga cycle calendar: https://releases.openstack.org/yoga/schedule.html14:09
lajoskatonaWe are in week R-8, so I collected some patches that hang in the client libraries14:09
lajoskatonawe are good actually as nothing in non-client libraries, like n-lib or ovsdbapp14:10
lajoskatonaand we had recently release of them14:10
lajoskatonabut we have few things in client facing libs14:10
lajoskatonandp proxy: https://review.opendev.org/q/topic:bug%252F187730114:10
lajoskatonathe series looks quite active, so if you have time please help with reviews :-)14:11
lajoskatonaqos-minimum-guaranteed-packet-rate: https://review.opendev.org/q/topic:bp/qos-minimum-guaranteed-packet-rate+status:open14:11
opendevreviewFernando Royo proposed openstack/ovn-octavia-provider stable/victoria: Return UnsupportedOptionError() on loadbalancer failover  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/82729614:12
lajoskatonaI took over from przemek, and try to push python-openstackclient patch14:12
lajoskatonaanother one which is in quite good shape and has great progress: Local IP: https://review.opendev.org/q/topic:bug/1930200+status:open14:13
lajoskatonasmart-NIC: https://review.opendev.org/q/topic:bug%252F193215414:14
lajoskatonaand the last open topic which has client dependency: Check quota limits: https://review.opendev.org/c/openstack/python-openstackclient/+/80601614:15
lajoskatonaIf I left out anything please tell me :-)14:15
slaweqlajoskatona: I will add them to my review list and will try to go through them this week14:16
lajoskatonaIf we have to push something to be in time we can increase the priority also14:16
lajoskatonaslaweq: thanks, I try to do the same, and they are really complex and interesting features so hard work even to review them, but can learn a lot :-)14:17
lajoskatonado you have comments or questions for the announcements/ release schedule or to any of the above patch series?14:19
ralonsohno thanks14:20
lajoskatona#topic Bugs14:20
lajoskatonaI reschufled the bug deputy list: https://wiki.openstack.org/wiki/Network/Meetings#Bug_deputy14:21
lajoskatonaplease check it and if it is not ok for you tell me14:21
lajoskatonaWe have one report from obondarev: http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026897.html14:22
lajoskatonaobondarev do you have something to highlight?14:23
obondarevmaybe just one Critical - https://bugs.launchpad.net/neutron/+bug/195836314:23
obondarevnot sure what's the failure rate for this now14:24
slaweqI didn't saw it this week personally14:24
lajoskatoname neither, so perhaps not that frequent14:24
slaweqbut basically it may be hard to track e.g. in the logstash14:25
lajoskatonasadly logstash is not that useful, at least for me this week...14:25
slaweqas the visible issue is that many tests fails with instances failed to build14:25
slaweqthen you can check in neutron server logs about that disabled notification to nova in one of the workers14:26
slaweqthat's the issue :)14:26
lajoskatonarecently I started to use this tool from gibi: https://github.com/gibizer/zuul-log-search14:26
lajoskatonait can look into q-svc or any logs, but donwload them to locally, so you need net bandwidth and storage space14:27
* gibi happy to take questions about that tool in any forms14:27
lajoskatonagibi: thanks :-)14:27
ralonsohgibi thanks!14:27
fricklerthere also the issue with system scope testing being broken after recent policy changes14:28
lajoskatonathanks slaweq for adding logs to this nova notifier issue14:28
slaweqyw. I really want to understand what happens there that this is disabled permanently for one of the workers14:29
lajoskatonafrickler: you mean this one: https://bugs.launchpad.net/neutron/+bug/1959196 ?14:30
lajoskatonaNew Secure RBAC policies broke devstack-enforce-scope job14:30
frickleryes14:30
fricklerwould be good to include that job in neutron, too, I think, once it is repaired14:31
slaweqmaybe we can include it in periodic queue of neutron?14:31
fricklergood idea14:32
ralonsohthat would be better not to increase the check queue14:32
lajoskatona+114:32
slaweqI will add it to periodic queue14:33
lajoskatonaslaweq: thanks, I can do it if you have no time this week14:33
slaweqlajoskatona: no worries, I will send patch right now14:34
lajoskatona:-)14:34
lajoskatonalast week's report from isabek: http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026972.html14:34
lajoskatonaI see only a few unasigned bugs:14:35
lajoskatonahttps://bugs.launchpad.net/neutron/+bug/1959176 neutron fullstack/functional jobs TIMED_OUT randomly14:36
opendevreviewSlawek Kaplonski proposed openstack/neutron master: Add devstack-enforce-scope job to our periodic queue  https://review.opendev.org/c/openstack/neutron/+/82730214:37
lajoskatonafor this I have a question, see: #link https://bugs.launchpad.net/neutron/+bug/1959176/comments/214:37
lajoskatonacurrently OS_TEST_TIMEOUT is 600: https://opendev.org/openstack/neutron/src/branch/master/tox.ini#L7314:37
ralonsohAgree: this timeout is not needed anymore14:38
ralonsohwe solved the issues with SQL testing14:38
lajoskatonabased on comment it was changed to 600 due to an old bug14:38
lajoskatonathat was my understanding also, I will propose a patch to change that, thanks14:38
slaweq++14:38
ykarel+114:38
lajoskatonaanother unassigned from last week: https://bugs.launchpad.net/neutron/+bug/1959098 [ovn] metadata route missing on the guest14:39
slaweqI think that ykarel is on it14:39
ralonsohstill waiting for more info on this14:39
slaweqat least trying to get some more info14:39
ralonsohthis is very specific to a single network14:39
ykarelyes rodolfo and i requested some more info from reporter14:40
lajoskatonaslaweq, ralonaoh, ykarel: thanks good to know14:40
lajoskatonaAnd that's it from me for the bugs14:41
lajoskatonaThis week lajoskatona is the deputy, and next week bcafarel will be.14:41
lajoskatonaI have to check with bcafarel14:41
ralonsohhe is aware14:41
lajoskatonaralonsoh: cool, thanks14:42
lajoskatonaand actually that's all what I have for today14:42
lajoskatonaDo you have anything to discuss?14:43
ralonsohnothing from me, thanks14:43
slaweqnot from me14:43
ralonsoh(today we don't have CI meeting)14:43
obondarevack14:43
slaweqexactly :)14:43
mlavallenothing from me either14:43
ykarelnothing from me too14:44
lajoskatonaok, than let's close the meeting, thanks for participating14:44
lajoskatona#endmeeting14:44
opendevmeetMeeting ended Tue Feb  1 14:44:34 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:44
opendevmeetMinutes:        https://meetings.opendev.org/meetings/networking/2022/networking.2022-02-01-14.07.html14:44
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/networking/2022/networking.2022-02-01-14.07.txt14:44
opendevmeetLog:            https://meetings.opendev.org/meetings/networking/2022/networking.2022-02-01-14.07.log.html14:44
mlavalleo/14:44
lajoskatonao/14:44
ralonsohbye14:44
slaweqo/14:44
obondarevo/14:44
isabekbye14:44
ykarelbye14:44
opendevreviewyatin proposed openstack/neutron-tempest-plugin master: Re-enable IPv6Test in OVN scenario job  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/82730314:44
amotokio/14:44
frickleris there a CI bug for ovn failing to start in devstack like here? https://ef7f9dfdac3d80d7fe06-334c29a1db3b5ea30b4f88988d44f729.ssl.cf1.rackcdn.com/827155/4/check/devstack-ipv6/48cd888/job-output.txt14:47
ralonsohfrickler, if I'm not wrong, this is because OVN or OVS, one was installed from source and the other one not14:48
ralonsohand the directories and different14:49
ralonsohbut let me check14:49
fricklerralonsoh: it seems to be some kind of race condition, only happens like an estimated 10% of all times, I usually just recheck and it is gone14:49
ralonsohoh, that's something different then14:50
ralonsohI'll open a bug then14:50
ralonsohthat's happening in devstack-ipv6, right?14:50
fricklerralonsoh: no, it happens for all devstack jobs that deploy OVN, that is just the latest example I had at hand14:50
ralonsohok14:51
fricklerykarel: nice coincidence, I was just looking at that IPv6 bug earlier today and wondered if it was still present14:51
ykarelfrickler, yeah slawek asked me to check that today14:52
sebaShould a user be able to allocate a floatingip outside of the fip-network's allocation pool? Especially for ips like the gateway_ip of the subnet?15:02
sebaor to say it in code: I would have expected this test to fail: https://paste.debian.net/hidden/de2e633c/15:18
sebait seems like the only validation on a user specified floating-ip-address is done by the ipam module, i.e. "is the ip in use". as the gateways on our external networks don't have ports it seems that ipam deems them as being free.15:19
sebaso, is this a bug/problem for others? If so I'd create a proper bug report for this. Also, if this is a bug, I'd be curious if we should restrict fip allocation to the subnets allocation pools or just deny using the gateway ip.15:21
ralonsohseba, a FIP should belong to the range of the subnet of the external network15:22
sebayes. in my example this would be 11.0.0.0/24 with 11.0.0.1 as gw and an allocation pool 11.0.0.2-11.0.0.254. 11.0.0.1 is inside the range of the subnet, but in my case it is a bad idea for the user to be able to allocate it15:24
opendevreviewMaor Blaustein proposed openstack/neutron-tempest-plugin master: Fix dependencies and PEP 8 new comments.  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/82729215:26
ralonsohseba, let me check that case15:26
opendevreviewFrode Nordahl proposed openstack/neutron master: [OVN] Off-path SmartNIC DPU Port Binding with OVN  https://review.opendev.org/c/openstack/neutron/+/80896115:36
ralonsohseba, right, we don't check if this is the GW IP. This is because we don't assign this IP address to any Neutron port15:41
sebayeah exactly15:43
sebaI don't think this gateway ip on an external network should be allocatable for a FIP. Maybe not even for an internal OpenStack port?15:44
sebaat least it could make sense to do a check on create_floatingip() to check if the user is currently trying to allocate the external subnet's gateway ip and throw an error if they do15:45
ralonsohseba, why not? the GW could be another port15:45
ralonsohand you can redirect the traffic from there15:45
ralonsohyou can build your own GW VM15:45
sebathat's right, but does that also work for external networks?15:46
ralonsohwhy not?15:46
sebaI thought external also means "router external" i.e. "gateway not managed by openstack"15:46
seba(external as in "external networks")15:46
ralonsohI wouldn't limit that but add a warning message in the logs15:47
ralonsohthat's all15:47
ralonsohbut, of course, that could be considered15:47
ralonsohplease, open a bug to discuss this15:47
ralonsohyou can also propose a patch to be reviewed15:47
sebaokay, will do15:48
opendevreviewOleg Bondarev proposed openstack/neutron master: Make sure "dead vlan" ports cannot transmit packets  https://review.opendev.org/c/openstack/neutron/+/82731516:09
opendevreviewFernando Royo proposed openstack/ovn-octavia-provider stable/ussuri: Return UnsupportedOptionError() on loadbalancer failover  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/82731716:21
opendevreviewFernando Royo proposed openstack/ovn-octavia-provider stable/ussuri: Return UnsupportedOptionError() on loadbalancer failover  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/82731716:22
opendevreviewFernando Royo proposed openstack/ovn-octavia-provider stable/ussuri: Return UnsupportedOptionError() on loadbalancer failover  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/82732416:56
opendevreviewFrode Nordahl proposed openstack/neutron master: [OVN] Off-path SmartNIC DPU Port Binding with OVN  https://review.opendev.org/c/openstack/neutron/+/80896117:05
sebabug created: https://bugs.launchpad.net/neutron/+bug/195969917:37
opendevreviewRodolfo Alonso proposed openstack/neutron master: Use a thread local variable to store the Nova Notifier enable flag  https://review.opendev.org/c/openstack/neutron/+/82733117:47
opendevreviewFrode Nordahl proposed openstack/neutron master: [OVN] Off-path SmartNIC DPU Port Binding with OVN  https://review.opendev.org/c/openstack/neutron/+/80896118:15
opendevreviewFernando Royo proposed openstack/networking-ovn stable/train: Return UnsupportedOptionError() on loadbalancer failover  https://review.opendev.org/c/openstack/networking-ovn/+/82733218:17
opendevreviewOleg Bondarev proposed openstack/neutron master: Make sure "dead vlan" ports cannot transmit packets  https://review.opendev.org/c/openstack/neutron/+/82731518:56
opendevreviewLajos Katona proposed openstack/tap-as-a-service master: Do not try to call status setting methods in case of periodic task  https://review.opendev.org/c/openstack/tap-as-a-service/+/82529919:41
opendevreviewLajos Katona proposed openstack/tap-as-a-service master: WIP: Make ovs-taas start in VLAN only env  https://review.opendev.org/c/openstack/tap-as-a-service/+/81744919:41
*** dasm|rover is now known as dasm|off22:23

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