Tuesday, 2021-11-02

opendevreviewMerged openstack/neutron master: Add shared field to SG API response and filter  https://review.opendev.org/c/openstack/neutron/+/81124201:20
opendevreviewDaniel Speichert proposed openstack/neutron master: Make OVN PG ACL sync compare known fields  https://review.opendev.org/c/openstack/neutron/+/81388301:43
opendevreviewMerged openstack/neutron master: [DVR] Set arp entries only for IPs from the correct subnet  https://review.opendev.org/c/openstack/neutron/+/80203703:24
opendevreviewBalazs Gibizer proposed openstack/neutron master: Do not block qos for direct-physical ports  https://review.opendev.org/c/openstack/neutron/+/81596207:20
opendevreviewOleg Bondarev proposed openstack/neutron master: Add Local IP L2 extension flows  https://review.opendev.org/c/openstack/neutron/+/81510207:23
slaweqlajoskatona hi, just FYI, bcafarel told me that he remembers about his bug deputy this week. He is off today but will start triaging bugs tomorrow :)08:05
lajoskatonaslaweq: Hi, than I will not send mail :-) thanks08:06
opendevreviewPrzemyslaw Szczerbik proposed openstack/neutron-lib master: Move QosPlacementAllocationUpdateConflict to neutron-lib  https://review.opendev.org/c/openstack/neutron-lib/+/81630608:34
opendevreviewSlawek Kaplonski proposed openstack/neutron master: Remove some scenario jobs from the check and gate queues  https://review.opendev.org/c/openstack/neutron/+/81546508:39
opendevreviewSlawek Kaplonski proposed openstack/neutron master: Cleaning of the zuul's project.yaml file  https://review.opendev.org/c/openstack/neutron/+/81546608:39
slaweqlajoskatona gibi: hi, I'm checking neutron CI from last week and I noticed few times failures with min_bw_allocation tests, like e.g. https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_50e/801470/11/check/neutron-ovs-tempest-multinode-full/50e5327/testr_results.html08:45
slaweqdid You maybe saw such issue already? Or should I open bug for it?08:45
lajoskatonaslaweq: thanks for highlight, perhaps its due to some change was not merged to recent pps things, and tempest already expects it: https://review.opendev.org/c/openstack/tempest/+/80916808:56
slaweqlajoskatona but it don't happens all the time, it's intermittent08:56
lajoskatonaslaweq: that's strange08:57
slaweqlajoskatona yes, that's why I asked :)08:57
EugenMayerslaweq i might have reproduced the meta-data issue on wallaby, but i'am not sure. At least the meta-data service is no longer available for any VM i spawn. Are you interested in guiding me in debugging it? I can see there is a namespace, but booting a (debian) generic cloud box ends with :[   11.437648] cloud-init[310]: 2021-11-02 08:57:13,605 -08:59
EugenMayerutil.py[WARNING]: No active metadata service found08:59
slaweqEugenMayer that's great that You can reproduce it there too08:59
slaweqwhat You can check first is the ovn-meta... namespace on the compute node where vm is spawned09:00
slaweqin that namespace there should be haproxy spawned09:00
slaweqthis haproxy should be bound to 169.254.169.254 IP address in that namespace09:00
slaweqmaybe there is something missing there09:00
EugenMayerhttps://gist.github.com/EugenMayer/3708c679f207d0185d4d485f8c9f36e709:00
EugenMayerwhat shall i do /query in the namespace?09:01
slaweqcheck if there is this IP address configured there, and if there is haproxy process running09:01
slaweqif it is, You need to debug if requests are reaching that haproxy or not09:01
slaweqbasically You should debug step by step where connectivity is broken09:02
EugenMayerslaweq https://gist.github.com/EugenMayer/3708c679f207d0185d4d485f8c9f36e709:02
EugenMayerslaweq are you aware that we tcpdumped that under xena? https://gist.github.com/EugenMayer/3b7d1fc4a42d7fc911229f38eec891dd09:03
EugenMayer(this is not my current stack, but that was the same thing)09:03
EugenMayerso you want me to tcpdump that tap interface i have right now while bootstrapping that instance?09:04
EugenMayer`and if there is haproxy process running` <- how to check that/09:04
slaweqYou can grep for haproxy service in the output of "ps" command for example09:05
EugenMayerinside that ns?09:06
slaweqfrom tcpdump it seems that something replies to the metadata requests09:06
slaweqprocess will be visible both in namespace and outside namespace09:06
EugenMayerip netns exec ovnmeta-6975b4e7-f0fa-411a-8a69-dac1614ce84f nmap 10.10.0.131 (which is the interface of that tap device) does not show any open ports09:07
EugenMayerslaweq https://gist.github.com/EugenMayer/3708c679f207d0185d4d485f8c9f36e7#file-gistfile1-txt-L2209:07
EugenMayer'a' haproxy is running, not sure how to determine it is 'the haproxy routing metadata requests'09:08
slaweqso You have haproxy, now You can check in syslog if it receives any requests from VM09:08
EugenMayerthat wont be that easy, need to find the right docker container running that one, sec09:08
slaweqbasically it is simple http service which You have to debug where communication is broken - I don't think I will be able to guide You through whole process step by step :)09:09
EugenMayeri know what a haproxy is, but you expect me to know all the internals of neutron, which i really do not know about :)09:10
EugenMayerfound /var/log/kolla/neutron/neutron-ovn-metadata-agent.log09:10
slaweqEugenMayer Neutron internals here are pretty easy. HTTP request should go like that: "VM -> tapXXX in br-int -> OF rules in br-int --> tap interface in the ovn namespace -> haproxy -> nova metadata api"09:12
slaweqhaproxy is logging directly in the journal log IIRC09:12
slaweqso You can check there also09:12
slaweqand You can do "curl http://169.254.169.254/" from the instance and then track where it's dropped in the compute node09:13
EugenMayeri found the container the haproxy is running in, looking for the log locations right now09:13
EugenMayercannot find those to answer your questions if the haproxy could not proxy / upstream the request09:15
EugenMayersince it is a docker container, there as no systemd thus no journal09:16
EugenMayeri see that the haproxy is running on 169.254.169.254:80 - trying a wget on that from the container haproxy is running on leads to a stuck request. This should no be happening, right?09:20
EugenMayerusing ip netns exec ovnmeta-6975b4e7-f0fa-411a-8a69-dac1614ce84f curl 169.254.169.254 -v (so from withing the namespace) leads to a 404 which seems to be better and might be the expected thing09:22
slaweqyes, 404 is expected in that case09:42
EugenMayerslaweq running ` ip netns exec ovnmeta-6975b4e7-f0fa-411a-8a69-dac1614ce84f curl http://169.254.169.254/2009-04-04/instance-id -v` which is what i see that cirros is requesting, leads to 40409:42
EugenMayerso i would suggest that the HAproxy is there and answers. The questions is, what shall be the response if it works?09:43
EugenMayerslaweq on my working (lab) wallaby box, spinning up a cirros instance, where i see the same request, using the namespce there, running this request - returns a 404 too09:46
EugenMayerslaweq those are the requests https://gist.github.com/EugenMayer/bed2b7f27f5cd70db688ba29300e13f909:48
EugenMayerto former is the current working wallaby, the latter the broken one, both cirros 0.5.209:49
slaweqon working one it returns instance-id from nova09:53
slaweqnot 40409:53
EugenMayerslaweq interesttingly doing ip netns exec ovnmeta-6975b4e7-f0fa-411a-8a69-dac1614ce84f tcpdump -i tap6975b4e7-f1 -n port 80 on the broken box i cannot see any traeffic09:53
EugenMayerslaweq it does within cirros, but the curl request does not do that09:53
slaweqif You are doing request from the ovn-meta namespace, it returns 404 because there is no instance id identified09:53
EugenMayerunderstood09:53
slaweqso You need to check what is the routing table in the vm in broken setup and then check vm's tap interface if requests are there09:54
EugenMayercould it be, that instead the meta-data service being borked, that the booting instance cannot talk to 169.254.169.254?09:54
slaweqif yes, check OF rule where it may be dropped09:54
slaweqcan be09:55
EugenMayerwhat is an OF rule?09:55
EugenMayerwell i have to wait about 10m to let the cirros instance finish it's bootstrap to check the routing table09:55
EugenMayeri have spun up a debian nocloud node. Looking at the routing table, default is via 10.10.0.129 which is the default gw09:57
EugenMayerinterestingly trying to curl from that box to 169 does stuck.09:58
EugenMayerExactly, the working box has a route to 169 specifically via etho, while broken box is missing that route09:59
EugenMayerwhat/who is responsible to push that route?09:59
slaweqIIRC You should have that route set by DHCP10:15
slaweqand OF is open flow rule in br-int10:15
EugenMayerslaweq AFAIU i'am not able to configure this route or disable it, it is core api? so there is an issue in dhcp?10:24
opendevreviewFederico Ressi proposed openstack/neutron master: Change tobiko CI job in the periodic queue  https://review.opendev.org/c/openstack/neutron/+/81397710:25
lajoskatona1slaweq: for min_bw_allocation tests failure: https://review.opendev.org/c/openstack/tempest/+/81631510:27
slaweqEugenMayer: maybe there is an issue with DHCP in OVN, idk10:28
slaweqI don't have ovn based env now to test it really10:28
lajoskatona1slaweq: not sure if we have some misconfiguration or similar in the failing case10:29
slaweqlajoskatona1: thx for the patch, I just gave +1 to it :)10:30
EugenMayeri really ask myself how widely OVN is actually used10:33
EugenMayerslaweq is OVN considered rather 'beta' level right now, or should one / can one use it for production grade. In other words, is it used for production setups?10:35
opendevreviewLajos Katona proposed openstack/networking-bgpvpn master: DNM: check master  https://review.opendev.org/c/openstack/networking-bgpvpn/+/80609610:36
slaweqEugenMayer:  it is used for production in many deployments for sure10:43
slaweqin fact it is default backend e.g. in the Red Hat OpenStack since some time10:43
slaweqand it is also default backend in the devstack - so it is used in most of the tempest jobs around OpenStack projects10:43
EugenMayerinteresting, i think we can reproduce it in wallaby the following way10:44
EugenMayercreate a network with e.g. one subnet, then under ports you will see `network:distributed` under ports for that network10:45
EugenMayerwhen you now remove that one, remove the subnet and create one or 2 new subnets, it will not get readded.10:45
EugenMayerIf you now restart the controller, it is added, but only with one IP in the second subnet. This ip is the gateway for the 169 address and that is, since it is missing, most probably the route is not added10:46
EugenMayerinterestingly, under xena, it is not working at all10:46
EugenMayerso network:distributed might not be added at all10:46
EugenMayerwhen removing the network entirely, adding 2 subnets right away one can see network:distributed with fixed ips from both subnets. So that is how it should be10:47
ralonsohI told you to check if https://review.opendev.org/c/openstack/neutron/+/813408 is there10:47
ralonsohthis is a problem with dhcp subnets and metadata port10:48
EugenMayerralonsoh i was not remotely aware of anything i was just writing (until 20 minutes ago) - so i might just not have understood your question10:49
ralonsohI told you this last week10:49
EugenMayeri was neither aware of this special port, that it is used as gateway for 169 and nor that metadata haproxy is running on that address. And i have never read about those internals anywhere10:49
EugenMayerif you did - i did not understand it. Sorry10:50
EugenMayeri guess that merge is very recent and has not yet been released right?10:51
slaweqEugenMayer: yes, it isn't in released version yet11:10
slaweqYou need to apply it manually in Your env11:11
EugenMayerslaweq thank you11:33
EugenMayerralonsoh slaweq i can confirm that xena is working when creating the subnets via the CLI, so the bug report i created is either no longer valid or only valid if those subnets are created via the GUI11:39
slaweqI think it's no longer valid11:40
slaweqGUI (horizon) is using same API calls as CLI11:40
EugenMayerwell i tested i way after 20 oct - and i could 100% reproduce it. So i let you do what you think, but that bug cannot be resolved due to that. Close the issue to your liking though, i will use the cli for that purpose11:46
opendevreviewMerged openstack/os-ken master: Choose the highest TLS version  https://review.opendev.org/c/openstack/os-ken/+/81383011:49
opendevreviewSlawek Kaplonski proposed openstack/neutron master: Add functional and fullstack jobs with FIPS enabled  https://review.opendev.org/c/openstack/neutron/+/81400911:51
opendevreviewOleg Bondarev proposed openstack/neutron master: Add Local IP fullstack test case  https://review.opendev.org/c/openstack/neutron/+/81632712:08
opendevreviewCong Nguyen Thanh proposed openstack/neutron master: [OVN] Fix port disable security dead when run neutron-ovn-db-sync-util  https://review.opendev.org/c/openstack/neutron/+/81632812:10
opendevreviewRodolfo Alonso proposed openstack/neutron stable/xena: Allow to set the OpenFlow protocol when needed  https://review.opendev.org/c/openstack/neutron/+/81216212:14
opendevreviewOleg Bondarev proposed openstack/neutron master: Add Local IP Extension and DB  https://review.opendev.org/c/openstack/neutron/+/80452312:24
opendevreviewOleg Bondarev proposed openstack/neutron master: Add Local IP L2 extension  https://review.opendev.org/c/openstack/neutron/+/80711612:24
opendevreviewOleg Bondarev proposed openstack/neutron master: Add Local IP L2 extension flows  https://review.opendev.org/c/openstack/neutron/+/81510212:24
opendevreviewOleg Bondarev proposed openstack/neutron master: Add Local IP fullstack test case  https://review.opendev.org/c/openstack/neutron/+/81632712:24
opendevreviewMerged openstack/neutron-tempest-plugin master: [stable/stein] Regroup tests exclusion list and add new failing ones  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/81545812:42
opendevreviewSlawek Kaplonski proposed openstack/neutron master: Remove run-devstack role from run_functional_job playbook  https://review.opendev.org/c/openstack/neutron/+/81635413:06
opendevreviewOleg Bondarev proposed openstack/neutron master: [WIP] Add Local IP fullstack test case  https://review.opendev.org/c/openstack/neutron/+/81632713:26
opendevreviewOleg Bondarev proposed openstack/neutron master: [WIP] Add Local IP fullstack test case  https://review.opendev.org/c/openstack/neutron/+/81632713:58
lajoskatona1#startmeeting networking14:00
opendevmeetMeeting started Tue Nov  2 14:00:09 2021 UTC and is due to finish in 60 minutes.  The chair is lajoskatona1. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
opendevmeetThe meeting name has been set to 'networking'14:00
mlavalleo/14:00
lajoskatona1o/14:00
ralonsohhi14:00
isabekHi!14:00
obondarev_hi14:00
haleybo/14:00
slaweqhi14:00
lajoskatona1I think we can start14:01
lajoskatona1You can check the agenda here: https://wiki.openstack.org/wiki/Network/Meetings14:01
lajoskatona1#topic Announcements14:02
rubasovo/14:02
lajoskatona1Yoga cycle calendar https://releases.openstack.org/yoga/schedule.html14:02
lajoskatona1in 2 weeks we reach yoga-1 milestone14:03
dmitriiso/14:03
lajoskatona1Any announcements which we can discuss?14:04
lajoskatona1ok, let's move on14:04
lajoskatona1#topic Bugs14:04
lajoskatona1obondarev was bug deputy last week: http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025624.html14:05
lajoskatona1obondarev: do you have anything to highlight?14:05
obondarev_not really, all details are in the report I think14:06
lajoskatona1I listed the bugs without owner to https://wiki.openstack.org/wiki/Network/Meetings14:06
lajoskatona1Ok, Do you have any bug to discuss here?14:08
lajoskatona1Personally I have the feeling that some from the list could be an RFE, like https://bugs.launchpad.net/neutron/+bug/1948891 ([ovn] Using ovsdb-client for MAC_Binding could theoretically block indefinitely) or https://bugs.launchpad.net/neutron/+bug/1949202 (ovn-controllers are listed as agents but cannot be disabled )14:09
lajoskatona1or more a support request at current  state like https://bugs.launchpad.net/neutron/+bug/194909714:09
slaweqthat last one I think can be closed IMO14:10
lajoskatona1this one was discussed on  #neutron channel today, no?14:10
slaweqwe discussed it with ralonsoh and EugenMayer last week and today14:10
ralonsohyes, it is already solved14:10
slaweqhttps://bugs.launchpad.net/neutron/+bug/1949059 this one worries me14:11
slaweqI will try to take a look at it this week14:11
slaweqbut I'm not ovn-octavia-provider expert so it will for sure take me some time to catch up with it :)14:11
slaweqregarding https://bugs.launchpad.net/neutron/+bug/1949202 - I have a question14:12
slaweqis it really possible to disable e.g. neutron-ovs-agent?14:12
lajoskatona1yeah this comment is hard: https://bugs.launchpad.net/neutron/+bug/1949059/comments/114:12
ralonsohI can try to ping redhat folks about OVN octavia bug14:13
lajoskatona1slaweq: the admin_state_up can be updated to true, but not sure what that really do in the background14:14
lajoskatona1I mean false14:14
slaweqexactly that's why I asked because I'm not sure if that has any real effect14:15
slaweqI know that for dhcp/L3 agent it will not schedule networks/routers to such agents but for L2 agent I don't think it really do anything14:15
ralonsohI'll check it14:16
ralonsohif that affects the agent, we should do the same for OVN agents14:16
ralonsohif not, I'll document it in the bug14:16
slaweqthx ralonsoh :)14:17
lajoskatona1As I see no port will be scheduled to the agent if admin state is false14:18
slaweqlajoskatona1: You mean ports will not be bound to the host where ovs-agent is disabled?14:19
lajoskatona1yes, exactly: https://opendev.org/openstack/neutron/src/branch/master/neutron/plugins/ml2/drivers/mech_agent.py#L18214:20
slaweqok, so we should probably to the same for ovn-controller "agents"14:21
ralonsohI don't know if we can replicate this behaviour in those agents14:21
ralonsohbut I'll check it14:21
lajoskatona1yes, and perhaps check how other l2 agents work and try to "standardize" it and/or document what we have now14:22
ralonsohsure14:22
lajoskatona1thanks ralonsoh14:22
slaweq++14:22
lajoskatona1I check if this is something common for all l2 agents and if we have documentation for it14:23
lajoskatona1ok, if nothing more for bugs......14:23
lajoskatona1This week bcafarel is the deputy, and next week slaweq will be.14:23
lajoskatona1Is that ok for you?14:24
slaweqsure14:24
lajoskatona1ok, thanks14:24
lajoskatona1#topic L3 subteam14:24
lajoskatona1To tell the truth I forgot to ping Liu the day before.....14:25
mlavalleLOL14:25
lajoskatona1ping liuyulong14:25
dasp_Sorry, on the topic of bugs, I have interest in https://bugs.launchpad.net/neutron/+bug/1670666 (and resurrecting https://review.opendev.org/c/openstack/neutron/+/708011). Can I get some comments if that solution is still okay today or what to change?14:26
lajoskatona1mlavalle: due to timezone (and perhaps irc availability) constraints sending a mail seems to be working :-)14:26
opendevreviewMerged openstack/neutron-specs master: Neutron VLAN networks with QinQ enabled  https://review.opendev.org/c/openstack/neutron-specs/+/79870414:28
lajoskatona1dasp_: if I understand from last comments there was no general issue with it, so restore it and we can contiune the review after the things fixed in last comments14:30
slaweqdasp_: I abandoned it automatically some time ago, but feel free to restore that patch and work on it14:31
slaweqif You can't restore it in gerrit, I can do it for You14:31
dasp_I don't think I can14:32
slaweqIt's restored now :)14:32
dasp_thanks! I'll see what I can do.14:33
lajoskatona1I think we can skip l3 section as there's no topics for it14:33
lajoskatona1#topic ryu and os-ken14:33
ralonsohno updates from "parent" project, ryu14:34
ralonsohthree patches to review14:34
ralonsohhttps://review.opendev.org/c/openstack/os-ken/+/81578414:34
lajoskatona1https://review.opendev.org/q/project:openstack%252Fos-ken+status:open14:34
lajoskatona1thanks ralonsoh14:34
ralonsohthat's all today14:34
slaweqtonight I will rebase my patches there to resolve conflicts14:34
slaweqand when all will be merged I think we can do new os-ken release14:35
slaweqwdyt?14:35
ralonsohsure thanks14:35
ralonsohcheck https://review.opendev.org/c/openstack/os-ken/+/81560114:35
lajoskatona1slaweq: +114:35
lajoskatona1ralonsoh: eventlet 0.26.1 is what we use in Neutron for example?14:37
ralonsohlet ne check14:38
ralonsoh0.25.114:38
lajoskatona1yeah we have eventlet>=0.25.114:38
ralonsohbut we install the last one14:38
ralonsoh0.32.014:38
lajoskatona1ralonsoh: ok14:39
lajoskatona1If noting more for ryu/os-ken we can move on14:40
lajoskatona1#topic On Demand Agenda14:40
lajoskatona1Do you have anything in mind to discuss?14:41
slaweqjust a short reminder if someone missed my email - today's CI meeting will be a video meeting14:42
slaweqif someone is interested, please join :)14:42
slaweqit will be in 18 minutes (after that one)14:42
dmitriishttps://blueprints.launchpad.net/neutron/+spec/off-path-smartnic-dpu-port-binding-with-ovn14:42
slaweqahh, and also, I prepared doodle https://doodle.com/poll/3n2im4ebyxhs45ne?utm_source=poll&utm_medium=link to choose the best time slot for ci meeting14:43
dmitriisLooking for reviews on this spec https://review.opendev.org/c/openstack/neutron-specs/+/78882114:43
lajoskatona1slaweq: cool14:43
lajoskatona1dmitriis: there's a nova spec for it as well: https://review.opendev.org/c/openstack/nova-specs/+/787458 14:45
dmitriisIf anybody has bandwidth, it would be much appreciated. At the Nova side, this spec https://review.opendev.org/c/openstack/nova-specs/+/787458 was gated on the approval of the Neutron spec by the core devs.14:45
frickleranother review on https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/815294 would also be nice14:46
dmitriislajoskatona1: yes, here is the pointer to Nova cores wanting a review from Neutron first https://etherpad.opendev.org/p/nova-yoga-ptg#L56114:46
lajoskatona1dmitriis: ok, thanks, I will check it14:47
dmitriisas such, the Nova spec have went through several iterations ~April - May 202114:47
lajoskatona1frickler: I will check it14:47
dmitriisso, there isn't much left to agree on there from what I can tell, just trying to get ordering right14:47
dmitriislajoskatona1: tyvm14:47
lajoskatona1dmitriis: np14:48
lajoskatona1ok, if nothing more for today's meeting we can close here and prepare for the video CI meeting :-)14:49
dmitriislajoskatona1: feel free to ping me or fnordahl if any questions arise. There is a WIP review for it already which may make it easier to see what's in it for Neutron https://review.opendev.org/c/openstack/neutron/+/808961 (likewise, there is code for Nova here https://review.opendev.org/c/openstack/nova/+/812111/)14:49
lajoskatona1 dmitriis: ack, I saw the link to the patch as comment :-)14:50
lajoskatona1#endmeeting14:50
opendevmeetMeeting ended Tue Nov  2 14:50:39 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:50
opendevmeetMinutes:        https://meetings.opendev.org/meetings/networking/2021/networking.2021-11-02-14.00.html14:50
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/networking/2021/networking.2021-11-02-14.00.txt14:50
opendevmeetLog:            https://meetings.opendev.org/meetings/networking/2021/networking.2021-11-02-14.00.log.html14:50
dmitriislajoskatona1: 👍14:50
ralonsohbye14:50
lajoskatona1bye14:50
mlavalleo/14:50
dmitriiso/14:50
slaweqbye14:51
rubasovo/14:52
opendevreviewSlawek Kaplonski proposed openstack/neutron master: Add functional and fullstack jobs with FIPS enabled  https://review.opendev.org/c/openstack/neutron/+/81400914:54
slaweq#startmeeting neutron_ci15:00
opendevmeetMeeting started Tue Nov  2 15:00:16 2021 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
opendevmeetThe meeting name has been set to 'neutron_ci'15:00
slaweqhi15:00
slaweqplease remember that this week's meeting is on video15:01
slaweq#link https://meetpad.opendev.org/neutron-ci-meetings15:01
slaweqralonsoh: lajoskatona1 are You joining?15:01
obondarev_hi15:03
slaweq#topic Actions from previous meetings15:03
slaweqbcafarel to switch to use regular ubuntu image in the train jobs, related to https://bugs.launchpad.net/neutron/+bug/194880415:03
lajoskatona1yes, sorry15:03
slaweqralonsoh to open LP bug and check functional failure with missing snat namespace15:04
slaweq#link https://bugs.launchpad.net/neutron/+bug/194883215:04
slaweq#action slaweq to work on https://bugs.launchpad.net/neutron/+bug/194883215:09
slaweqslaweq to prepare doodle with question about new time slot for CI meetings15:09
slaweqhttps://doodle.com/poll/3n2im4ebyxhs45ne?utm_source=poll&utm_medium=link15:09
slaweqslaweq to prepare ci meeting on tue 2.11 as video call15:11
slaweq#topic Stadium projects15:11
slaweq#topic Stable branches15:12
slaweq#link https://etherpad.opendev.org/p/neutron-stable-ussuri-em15:13
slaweq#topic Grafana15:14
slaweqhttps://grafana.opendev.org/d/BmiopeEMz/neutron-failure-rate?orgId=115:14
slaweq#topic fullstack/functional15:19
slaweqhttps://review.opendev.org/c/openstack/neutron/+/81635415:19
slaweq#topic Tempest/Scenario15:22
slaweqhttps://1bdefef51603346d84af-53302f911195502b1bb2d87ad2b01ca2.ssl.cf5.rackcdn.com/814807/4/check/neutron-tempest-plugin-scenario-openvswitch/3de2195/testr_results.html15:24
slaweq#link https://launchpad.net/bugs/194799315:27
slaweq#action ralonsoh to check metadata issue https://1bdefef51603346d84af-53302f911195502b1bb2d87ad2b01ca2.ssl.cf5.rackcdn.com/814807/4/check/neutron-tempest-plugin-scenario-openvswitch/3de2195/testr_results.html15:29
slaweqhttps://5a5cde44dedb81c8bd48-91d0b9dca863bf6ffc8b1718d062319a.ssl.cf5.rackcdn.com/805391/13/check/neutron-tempest-plugin-scenario-ovn/84283cb/testr_results.html15:29
slaweq#action slaweq to check https://5a5cde44dedb81c8bd48-91d0b9dca863bf6ffc8b1718d062319a.ssl.cf5.rackcdn.com/805391/13/check/neutron-tempest-plugin-scenario-ovn/84283cb/testr_results.html15:32
slaweqhttps://581819ea67919485b97e-6002fae613cad806f99007086c39ea60.ssl.cf2.rackcdn.com/813977/5/gate/neutron-tempest-plugin-scenario-linuxbridge/8fdcf6f/testr_results.html15:32
slaweq#action lajoskatona1 to check https://581819ea67919485b97e-6002fae613cad806f99007086c39ea60.ssl.cf2.rackcdn.com/813977/5/gate/neutron-tempest-plugin-scenario-linuxbridge/8fdcf6f/testr_results.html15:33
slaweq#endmeeting15:49
opendevmeetMeeting ended Tue Nov  2 15:49:45 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:49
opendevmeetMinutes:        https://meetings.opendev.org/meetings/neutron_ci/2021/neutron_ci.2021-11-02-15.00.html15:49
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/neutron_ci/2021/neutron_ci.2021-11-02-15.00.txt15:49
opendevmeetLog:            https://meetings.opendev.org/meetings/neutron_ci/2021/neutron_ci.2021-11-02-15.00.log.html15:49
opendevreviewRodolfo Alonso proposed openstack/neutron master: Use the DB object when listing the SG rules  https://review.opendev.org/c/openstack/neutron/+/81637316:37
nmk94Team: with security group with attached remote_security_group  I can see two  flows with different cookies one with default ovs cookie and another new cookie with conjunction flows , is it expected ?17:06
nmk94ubuntu@req-generic-65-d012-mn:~$ sudo ovs-ofctl dump-flows br-int | awk '{print $1}' | sort -n | uniq cookie=0x12b7adbe73614620, cookie=0x207d02d6bbcf499e, NXST_FLOW ubuntu@req-generic-65-d012-mn:~$ sudo ovs-ofctl dump-flows br-int |  grep "0x207d02d6bbcf499e"  cookie=0x207d02d6bbcf499e, duration=335.421s, table=82, n_packets=0, n_bytes=0, idle_age=335, priority=70,ct_state=+est-rel-rpl,ipv6,reg6=0x1,ipv6_src=fdd8:a3ce:31ae:0:f816:17:07
opendevreviewRodolfo Alonso proposed openstack/neutron master: [OVN] Check if OVN NB supports stateless NAT rules  https://review.opendev.org/c/openstack/neutron/+/81637617:12
opendevreviewRodolfo Alonso proposed openstack/neutron master: [OVN] Check if OVN NB supports stateless NAT rules  https://review.opendev.org/c/openstack/neutron/+/81637617:33
opendevreviewRodolfo Alonso proposed openstack/neutron master: [OVN] Check if OVN SB supports virtual ports  https://review.opendev.org/c/openstack/neutron/+/81638317:47
opendevreviewMerged openstack/os-ken master: Msgpack version upgrade to 1.0.0  https://review.opendev.org/c/openstack/os-ken/+/81578417:50
opendevreviewRodolfo Alonso proposed openstack/neutron master: Remove "get_logical_port_chassis_and_datapath"  https://review.opendev.org/c/openstack/neutron/+/81346217:51
opendevreviewMerged openstack/neutron-lib master: Add qos-pps-minimum-rule-alias api-def and api-ref  https://review.opendev.org/c/openstack/neutron-lib/+/81511618:47
*** ianw_pto is now known as ianw19:00
opendevreviewSlawek Kaplonski proposed openstack/os-ken master: Bugfix now multiple switches can connect with TLS  https://review.opendev.org/c/openstack/os-ken/+/81383320:42
opendevreviewSlawek Kaplonski proposed openstack/os-ken master: Allow user to set cipher list.  https://review.opendev.org/c/openstack/os-ken/+/81383520:43
opendevreviewSlawek Kaplonski proposed openstack/os-ken master: Add support for the MTU ND option.  https://review.opendev.org/c/openstack/os-ken/+/81383620:45
opendevreviewSlawek Kaplonski proposed openstack/os-ken master: Bump min eventlet version to 0.26.1  https://review.opendev.org/c/openstack/os-ken/+/81560120:56
opendevreviewSlawek Kaplonski proposed openstack/neutron master: Add functional and fullstack jobs with FIPS enabled  https://review.opendev.org/c/openstack/neutron/+/81400921:39
opendevreviewMerged openstack/neutron-tempest-plugin master: Add a config option for BGP speaker scheduling  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/81529422:31
opendevreviewMerged openstack/neutron-lib master: Move QosPlacementAllocationUpdateConflict to neutron-lib  https://review.opendev.org/c/openstack/neutron-lib/+/81630622:35

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