Tuesday, 2021-11-09

opendevreviewliuyulong proposed openstack/neutron master: Meter flows and ovsdb action for ovs bridge  https://review.opendev.org/c/openstack/neutron/+/81680003:35
opendevreviewliuyulong proposed openstack/neutron master: Add QoS pps limit rule to support list  https://review.opendev.org/c/openstack/neutron/+/81680103:35
opendevreviewliuyulong proposed openstack/neutron master: Support pps limitation for openvswitch agent  https://review.opendev.org/c/openstack/neutron/+/81680203:35
opendevreviewManu B proposed openstack/neutron-dynamic-routing master: BGPaaS server side implementation  https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/80244505:29
opendevreviewManu B proposed openstack/neutron-dynamic-routing master: BGP speaker route handling  https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/80917305:35
opendevreviewManu B proposed openstack/neutron-dynamic-routing master: Updating status, name field and handling reboot operation  https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/81130005:43
opendevreviewManu B proposed openstack/neutron-dynamic-routing master: Updating status, name field and handling reboot operation  https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/81130005:49
opendevreviewSlawek Kaplonski proposed openstack/neutron master: [OVN] Execute OVN migration transactions independently  https://review.opendev.org/c/openstack/neutron/+/81418108:25
opendevreviewSlawek Kaplonski proposed openstack/neutron master: Remove not used parameter from migrate_neutron_database_to_ovn function  https://review.opendev.org/c/openstack/neutron/+/81716208:25
ralonsohslaweq, ^^ I don't understand08:27
ralonsohI did in https://review.opendev.org/c/openstack/neutron/+/814181/608:27
opendevreviewliuyulong proposed openstack/neutron master: Meter flows and ovsdb action for ovs bridge  https://review.opendev.org/c/openstack/neutron/+/81680009:09
opendevreviewliuyulong proposed openstack/neutron master: Add QoS pps limit rule to support list  https://review.opendev.org/c/openstack/neutron/+/81680109:09
opendevreviewliuyulong proposed openstack/neutron master: Support pps limitation for openvswitch agent  https://review.opendev.org/c/openstack/neutron/+/81680209:09
*** gthiemon1e is now known as gthiemonge09:14
opendevreviewLajos Katona proposed openstack/neutron master: Change QosRuleType object version id  https://review.opendev.org/c/openstack/neutron/+/81717810:24
opendevreviewLajos Katona proposed openstack/networking-odl master: CI: Make tempest and rally jobs non-OVN based  https://review.opendev.org/c/openstack/networking-odl/+/81718610:48
kevkohi, is there any issue in neutron wallaby ? when trying to spawn several instances at once via heat ..getting this in nova ->  Timeout waiting for [('network-vif-plugged', ......12:58
kevkoml2/ovs12:59
opendevreviewLajos Katona proposed openstack/networking-odl master: CI: Make tempest and rally jobs non-OVN based  https://review.opendev.org/c/openstack/networking-odl/+/81718613:02
opendevreviewLajos Katona proposed openstack/networking-bgpvpn stable/victoria: [stable/victoria] Dropping lower-constraints testing  https://review.opendev.org/c/openstack/networking-bgpvpn/+/81650013:12
opendevreviewLajos Katona proposed openstack/networking-bgpvpn stable/victoria: [stable/victoria] Dropping lower-constraints testing  https://review.opendev.org/c/openstack/networking-bgpvpn/+/81650013:17
lajoskatona#startmeeting networking14:00
opendevmeetMeeting started Tue Nov  9 14:00:29 2021 UTC and is due to finish in 60 minutes.  The chair is lajoskatona. 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
lajoskatonaHi14:00
obondarevhi14:00
mlavalleo/14:00
isabekHi14:00
bcafarelhi14:00
rubasovo/14:00
lajoskatonaLet's start14:02
lajoskatona#topic Announcements14:02
lajoskatonaYoga cycle calendar #link https://releases.openstack.org/yoga/schedule.html14:02
slaweqhi14:02
lajoskatonaThis week is the final week for Ussuri, so if you have anything to merge and release for ussuri please push that14:03
amotokihi14:03
lajoskatonawe have one patch series hanging: https://review.opendev.org/q/I409bc674b65e4f495ebd42d03e97a09d5148233914:03
lajoskatonaHi slaweq & amotoki :-)14:04
bcafarelyes apart from it it looks good: https://review.opendev.org/q/project:openstack/neutron+branch:stable/ussuri+status:open14:04
*** jlibosva is now known as Guest542614:04
lajoskatonabcafarel: thanks14:04
lajoskatonaWe have to propose last release patch for ussuri ( Iahve to check if isn't there an automatic one already)14:05
lajoskatonaand actually that's all announcements from me, do you have anything in mind or questions for announcements?14:06
lajoskatonaohh, no I have few more lines....14:06
lajoskatonaCI meeting time slot: #link http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025578.html please vote, if you a fan of the CI meeting ;)14:06
slaweq++14:07
lajoskatonaAnd I sent out a vote for the team meeting as well: #link http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025702.html14:07
lajoskatonaand for the drivers meeting: #link http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025705.html14:07
lajoskatonaI thought that next week we can discuss the results for the last 214:07
lajoskatonaslaweq: whan we will have final result for CI meeting slot?14:08
slaweqI though to summarize it this week14:08
slaweqso let's say that deadline is end of this week14:08
lajoskatonaslaweq: ok, thanks, 14:08
lajoskatonaok, so if nothing more for announcements.....14:09
lajoskatona# topic Community Goals14:09
mlavalleso no meeting times change this week, right?14:10
lajoskatonaon this meeting we have't discussed community goals recently, but RBAC was a hot and long topic on the PTG....14:10
lajoskatonamlavalle: next weeks meeting will be the same time14:10
mlavalleack14:11
lajoskatonaso for communit goals there was a mail from last meeting of TC: #link http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025693.html14:11
lajoskatonaand they linked the etherpad for RBAC discussion an etherpad with notes: #link https://etherpad.opendev.org/p/policy-popup-yoga-ptg14:11
lajoskatonato tell the truth I haven't read it in details, so it is more a headsup that there should be finally some outcome of how to handle system scopes and related things.....14:12
lajoskatonaDo you have some comments, question for the RBAC and community goal for Yoga cycle?14:13
amotokiperhaps we can focus on improving system-scope related things in neutron side.14:14
mlavalleso hold for now, right?14:14
lajoskatonaamotoki: sure, but to tell the truth I lost what is the direction....14:14
amotokiand we can reflect openstack-wide discussion results to our implementations if needed14:14
amotokilajoskatona: the last week discussion was mainly focused on how to handle project-specific resources with system-scoped token, but it is still unclear to me....14:15
lajoskatonaamotoki: +1, that makes things easier for sure, and we have painpoints  where nova-neutron interaction is in question for example14:15
slaweqamotoki: I wanted to do that but I'm still not sure how new rules should looks like14:16
lajoskatonaamotoki: you saved my day, I thought I am the last one who understands half of this whole topic :-)14:16
amotokislaweq: me neither :(14:16
slaweqIIUC we should have system_scope only for APIs like for agents or logs maybe14:17
slaweqonly things which don't really have project_id14:17
slaweqbut there should be also some new persona IIUC14:17
slaweqso I would like to change all at once and that's why I didn't moving on with this yet14:17
lajoskatonaslaweq, amotoki: thanks for keeping an eye on this topic14:18
amotokislaweq: my undrestanding is same (though I am not sure I caught the discusion fully) but I agree we should wait till the direction is clear.14:19
slaweq++14:19
lajoskatonaok, so as mlavalle said: hold for now, till we have clear direction14:20
lajoskatonaok if nothing more for RBAC and community goals, let's move on14:20
lajoskatona#topic Bugs14:21
lajoskatonabcfarel was bug deputy last week: http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025703.html14:21
lajoskatonaFrom the mail it seems that every bug is handled, bcafarel: do you have anything to add?14:22
bcafarelno, all bugs have good progress or assignee in that week :)14:23
lajoskatonabcafarel: thanks for the report :-)14:23
lajoskatonaThis week slaweq is the deputy, and next week hongbin will be.14:23
slaweqI'm on it already :)14:24
lajoskatonaslaweq: thanks14:24
lajoskatonaI will write a mail to hongbin to be sure14:24
lajoskatonaok next topic14:24
lajoskatona#topic L3 subteam14:24
lajoskatona#link https://wiki.openstack.org/wiki/Network/Meetings#L3_subteam14:24
lajoskatonaliuyulong collected a lot of blueprints to the wiki, but I can't see him14:25
lajoskatonasome of them are already finished, like ECMP support....14:27
lajoskatonaas liuyulong is not here, I think we can move forward14:29
lajoskatona#topic ryu and os-ken14:29
lajoskatona#link https://etherpad.opendev.org/p/make_os-ken_and_ryu_sync14:29
slaweqthere is no ralonsoh  today so I guess no update14:29
lajoskatonano new patches in ryu this week, so we can close this14:29
slaweqbut good news is that we merged all backports from ryu to os-ken last week14:29
lajoskatonayes exactly and we have an os-ken release with them14:30
slaweqyes14:30
lajoskatona#topic On Demand Agenda14:30
lajoskatonaI added a topic, but I am more the post man for it:14:31
lajoskatonaWhat to move to neutron-lib?14:31
lajoskatonaThere is an interesting debate over few patches what code parts/ constants etc to move to n-lib:14:31
lajoskatonahttps://review.opendev.org/c/openstack/neutron/+/79712114:31
lajoskatonahttps://review.opendev.org/c/openstack/neutron/+/79712014:32
lajoskatonahttps://review.opendev.org/c/openstack/neutron-lib/+/80722414:32
lajoskatonaI hope I collected all of the relevant patches :-)14:32
slaweqyes, thx14:32
slaweqactually https://review.opendev.org/c/openstack/neutron/+/797120 and https://review.opendev.org/c/openstack/neutron-lib/+/807224 are important in that discussion14:32
slaweqbasically I wanted to move all ovs constants to the neutron-lib14:33
lajoskatonaliuyulong is on this discussion so sad that we can't have him14:33
slaweqas e.g. some of them were (are) used by networking-bagpipe IIRC14:33
slaweqand all of them are rehomed already14:33
slaweqnow liuyulong wants to keep *ALL_TABLES lists in the neutron14:33
slaweqas it may "speed" development process in some cases14:34
slaweqbut obondarev had IMO very good point that if we will keep those lists separately, in the future we will forget to add new tables to it14:34
slaweqso it's better to move all to neutron-lib and use it from neutron-lib14:34
slaweqand now I think we need some more votes to judge which approach would be better :)14:35
obondarevslaweq: do you know which constants are used by networking-bagpipe? Maybe we should move only those constants that are known to be used by 2+ projects?14:36
lajoskatonaI think this is that comment and discussion under it: https://review.opendev.org/c/openstack/neutron/+/797120/comment/41ae240e_35fcd1b2/14:36
slaweqyes14:37
obondarevsuch "common" constants will be saved in lib and used by other projects. Specific constants may stay in specific repos until needed by someone else14:38
obondarevI think that was the workflow for neutron-lib originally14:39
lajoskatonaobondarev: +114:39
amotokiyeah, that is the principle. in case of OF tables, we need to avoid conflicts among table numbers. I think that's the point.14:39
slaweqyes14:40
obondarevgood point14:41
mlavalle+114:41
slaweqif You'll have some time, please comment on that patch14:42
slaweqso I can move on with it in one or another way :)14:42
slaweqthx a lot14:43
lajoskatonaso let's revisit these changes and follow the "old" rule: move only things that used by multiple projects, otherwise avoid conflicts in places like OF tables.14:43
lajoskatonaCan that be the summary?14:43
slaweqyes14:43
lajoskatonaok, than I think we can close this dicussion here, and continue under the reviews, I will point it to ralonsoh and liuyulong to have all of us on the same page14:44
slaweq++ thx14:45
lajoskatonaIf no more topics for the On Demand agenda.....14:45
dmitriislooking for a second core review on https://review.opendev.org/c/openstack/neutron-specs/+/788821/ if anybody has cycles for it.14:45
dmitriisLiu looked at it but only gave a +1 so I guess it has to be somebody else14:47
lajoskatonayes, please if you have time to review this spec, check it, as it is again a cross-project effort with Nova and with OVN (out of our control) and nova waits for the neutron-spec review14:48
mlavalleI'll look at it later today14:48
dmitriistyvm14:48
lajoskatonamlavalle: thanks14:48
lajoskatonaif nothing more.....14:48
lajoskatona#endmeeting14:49
opendevmeetMeeting ended Tue Nov  9 14:49:26 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:49
opendevmeetMinutes:        https://meetings.opendev.org/meetings/networking/2021/networking.2021-11-09-14.00.html14:49
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/networking/2021/networking.2021-11-09-14.00.txt14:49
opendevmeetLog:            https://meetings.opendev.org/meetings/networking/2021/networking.2021-11-09-14.00.log.html14:49
slaweqo/14:49
lajoskatonathanks for attending, Bye14:49
amotokio/14:49
dmitriiso/14:49
mlavalleo/14:49
rubasovo/14:50
rubasovzigo: I see you asked about v6-only metadata14:51
rubasovwe do not have a v6-only tempest test for it, because these tests use huge images and are very costly14:52
rubasovbut I just checked manually in my environment and it was working14:53
rubasovwe intended to cover the v6-only case and if that's not working that's definitely a bug14:53
rubasovregarding the namespaces: depending on whether your network is an isolated network or one with a router please check both the qrouter and the qdhcp namespaces14:54
rubasovand for a tests sake it may be worth to create a net with both v4 and v6 subnest and check if metadata works over ipv4 in the same environment14:55
jrosser_some cloud images arent configured to try the v6 metadata service at all14:55
rubasovjrosser_: yes, probably most of them are not using it by default, but the service itself should be available14:56
jrosser_yeah, we found the metadata service worked but stock images were tricky to use14:58
rubasovI remember that some older OSes (for example ubuntu 16.04) had even problems with general IPv6 link local addresses (though I don't remember the details)14:59
slaweq#startmeeting neutron_ci15:00
opendevmeetMeeting started Tue Nov  9 15:00:11 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
slaweqGrafana dashboard: http://grafana.openstack.org/dashboard/db/neutron-failure-rate15:00
opendevreviewMerged openstack/neutron master: Bump OVN version for functional job to 21.06  https://review.opendev.org/c/openstack/neutron/+/81661415:00
slaweqbcafarel: lajoskatona obondarev CI meeting is starting  :)15:00
obondarevhi15:00
slaweqhi15:00
bcafarelo/15:00
lajoskatonaHi15:02
slaweqok, I think we can start15:02
slaweqthis week is just on IRC15:02
slaweq#topic Actions from previous meetings15:02
slaweqslaweq to work on https://bugs.launchpad.net/neutron/+bug/194883215:03
slaweqI was checking it today15:03
slaweqand TBH I don't think it's the same bug as mentioned by ralonsoh in the LP15:03
slaweqI wrote my findings in the comment there15:04
slaweqI will try to investigate it little bit more this week15:04
slaweq#action slaweq to check more deeply https://bugs.launchpad.net/neutron/+bug/194883215:05
slaweqnext one15:05
slaweqralonsoh to check metadata issue https://1bdefef51603346d84af-53302f911195502b1bb2d87ad2b01ca2.ssl.cf5.rackcdn.com/814807/4/check/neutron-tempest-plugin-scenario-openvswitch/3de2195/testr_results.html15:05
slaweqI guess we need to move that one for next week as ralonsoh is not here today15:06
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:07
slaweqnext one15:07
slaweqslaweq to check https://5a5cde44dedb81c8bd48-91d0b9dca863bf6ffc8b1718d062319a.ssl.cf5.rackcdn.com/805391/13/check/neutron-tempest-plugin-scenario-ovn/84283cb/testr_results.html15:07
slaweq    It seems for me that the issue is similar to https://launchpad.net/bugs/189286115:07
slaweq    The problem is that "login: " message in console log appears pretty quickly but cloud-init is still doing some things on the node, so maybe SSH isn't working yet and we hit the same bug.15:07
lajoskatonathis happens with cirros?15:09
slaweqno, it's with Ubuntu15:09
lajoskatonaok15:09
slaweqmaybe we should find better way to check if guest OS is really booted before doing SSH15:09
bcafareladvanced OS wanting to show that login prompt too fast :)15:09
slaweqit seems like that for me15:10
bcafarelthe problem is that sounds OS-dependant? though maybe systemd check for advanced + login: for cirros would be good enough15:10
slaweqbecause I didn't saw anything else wrong there really15:10
slaweqanyway, I will keep an eye on that. If it will happen more often I will report bug and try to figure out something :)15:12
slaweqfor now let's move on to the last one15:12
slaweqlajoskatona to check https://581819ea67919485b97e-6002fae613cad806f99007086c39ea60.ssl.cf2.rackcdn.com/813977/5/gate/neutron-tempest-plugin-scenario-linuxbridge/8fdcf6f/testr_results.html15:12
lajoskatonayeah I checked this one, and the startnge is that the FIP goes UP but too late (~few secs)15:12
slaweqto UP or to DOWN?15:13
lajoskatonaslaweq: I mean down, thanks....15:13
slaweqerror message says "attached port status failed to transition to DOWN "15:13
slaweqahh, ok15:13
slaweqhow long we are waiting for that transition?15:14
lajoskatona120sec15:14
obondarevshould be more than enough..15:15
slaweqyeah15:15
lajoskatonatempest stoppes waiting at: 2021-10-21 08:09:14.58399415:15
lajoskatonaand q-svc reports it's down: Oct 21 08:09:17.015995 ubuntu-focal-iweb-mtl01-0027033075 neutron-server[81347]: DEBUG neutron.api.rpc.handlers.l3_rpc [None req-ca3c8a33-07ab-41b7-b946-2411e666af30 None None] New status for floating IP aa555045-e872-47f5-a5f4-b4b59017b474: DOWN {{(pid=81347) update_floatingip_statuses /opt/stack/neutron/neutron/api/rpc/handlers/l3_rpc.py:270}}15:15
lajoskatonafrom https://581819ea67919485b97e-6002fae613cad806f99007086c39ea60.ssl.cf2.rackcdn.com/813977/5/gate/neutron-tempest-plugin-scenario-linuxbridge/8fdcf6f/job-output.txt and https://581819ea67919485b97e-6002fae613cad806f99007086c39ea60.ssl.cf2.rackcdn.com/813977/5/gate/neutron-tempest-plugin-scenario-linuxbridge/8fdcf6f/controller/logs/screen-q-svc.txt15:16
slaweqwas L3 agent very busy during that time?15:16
lajoskatonayeah it was refreshing continuusly the iptables rules15:16
lajoskatonamy question: do we need ha router enabled for this for example?15:17
slaweqmaybe there is some issue in the L3 agent then?15:17
lajoskatonathis is a singlenode job as I see15:18
slaweqlajoskatona: we enabled HA for those routers to have at least some HA test coverage15:18
slaweqas we don't have any other jobs with HA routers15:18
slaweqand even if that job is singlenode, when router is HA, all HA codepath is tested15:18
slaweqlike keepalived and other stuff15:19
slaweqit's just that router is always transitioned to be primary on that single node :)15:19
lajoskatonaslaweq: ok15:19
lajoskatonaI can check l3-agent if I can see something why it took so long to make the fip down15:20
slaweq++15:21
slaweq#action lajoskatona to check why make FIP down took more than 120 seconds in the L3 agent15:21
slaweqthx lajoskatona 15:21
slaweqok, that are all actions from last week15:21
slaweqlet's move on15:21
slaweq#topic Stadium projects15:21
lajoskatonanothing new15:22
lajoskatonaThis week I realized that odl tempest jobs try to run with ovn15:22
lajoskatonaso I fight against that, but the jobs will still fail, but at least we have services up and tempest/rally started15:23
lajoskatonathat's it for stadiums15:24
slaweqdo You have patch for that?15:24
slaweqI can review it if You want15:24
lajoskatonathanks15:24
lajoskatonait's not fully ready yet by zuul  as I see: https://review.opendev.org/c/openstack/networking-odl/+/81718615:24
slaweqok15:26
lajoskatonaohh, no tempest is ok at least. It's failing bu with the usual way which is due to ODL is slow behind it....15:26
lajoskatonaok, so I have to tune rally job15:27
lajoskatonaI will send it on IRC when that is ok15:27
slaweqI added it to my review list for tomorrow morning :)15:27
lajoskatonaslaweq: thanks15:27
slaweqok, next topic then15:28
slaweq#topic Stable branches15:28
bcafareloverall good this week, as mentioned ussuri has only https://review.opendev.org/c/openstack/neutron/+/816661 left (before EM transition)15:28
bcafarelthough functional test failing in it looks related15:29
bcafareland I found just before meeting train has neutron-tempest-plugin-designate-scenario-train failing :( https://zuul.opendev.org/t/openstack/build/a6a1142368b742248be710f902f541f515:29
slaweqyes, indeed15:29
slaweqI will check it tomorrow15:29
bcafarelI will fill a bug for that designate train one after meetings15:29
bcafarelbut at least full support branches are good :)15:30
slaweqok, thx bcafarel 15:30
slaweqI think we can move on then15:30
slaweq#topic Grafana15:30
slaweqhttp://grafana.openstack.org/dashboard/db/neutron-failure-rate15:31
slaweqrally was broken last week15:31
slaweqbut it's I guess due to that missing service endpoint in keystone, right?15:32
slaweqand it's already fixed15:32
lajoskatonayes15:32
lajoskatonaactually it's funny, in devstack the endpoint creation was deleted and now we create it from the job15:32
lajoskatonaand seems like neutron runs mostly as voting job rally15:33
slaweqso only rally job needs it?15:33
lajoskatonayes as I remember15:33
slaweqhmm, ok15:34
slaweqthx for fixing that issue quickly15:34
lajoskatonaand the proper fix should be in rally, but I checked and not clear for first view where to fix it.....15:34
lajoskatonait was ralonsoh actually, I just run another "alternative" path, but that was not enough....15:34
slaweq:)15:34
slaweqfrom other things I see that neutron-tempest-plugin-scenario-linuxbridge job is failing pretty often (more than other similar jobs)15:35
slaweqI'm not sure why it is like that really15:35
slaweqprobably some timeouts which I saw pretty often in the scenario jobs last week15:35
slaweqlike e.g. https://zuul.opendev.org/t/openstack/build/7a2bc299305249c5911e7107bb4d4a3715:36
slaweqI think we need to investigate why so often our tests are so slow recently15:38
slaweqI doubt I will have time for that this week but maybe there is anyone who could check that15:39
obondarevalso neutron-tempest-plugin-scenario-ovn started failing I think15:40
obondarevexample: https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_330/807116/23/check/neutron-tempest-plugin-scenario-ovn/330ce5c/testr_results.html15:40
slaweqobondarev: You mean with timeouts?15:40
obondarevnope15:40
obondareva couple of tests failing with ssh I believe15:40
slaweqhmm, in those 2 tests for example we are missing console log from instance15:41
slaweqso it's hard to say15:41
slaweqbut it may be the same issue like in  https://5a5cde44dedb81c8bd48-91d0b9dca863bf6ffc8b1718d062319a.ssl.cf5.rackcdn.com/805391/13/check/neutron-tempest-plugin-scenario-ovn/84283cb/testr_results.html15:41
slaweqwhich I spoke about at the begining of the meeting15:42
slaweqlet's observe it and if someone will have some time, maybe investigate it a bit more :)15:44
obondarevI'll keep an eye on it and report a bug if it continue to fail with similar symptoms15:44
slaweqobondarev: sounds good, thx15:44
slaweqok, I think we can move on quickly15:44
slaweqwe already spoke about most urgent issues in our jobs, at least those which I had prepared for today15:45
slaweq#topic tempest/scenario15:45
slaweqhere I have one more thing to mention15:45
slaweqthis time, good news I think15:45
slaweqour CI job found bug :)15:45
slaweqhttps://bugs.launchpad.net/neutron/+bug/1950273 15:45
slaweqso sometimes those jobs seems to be useful ;)15:46
obondarevnice! :)15:46
slaweqit seems to be some race condition or something else but even in such case we shouldn't return error 500 to the user15:46
lajoskatona+115:47
slaweqso at least we should properly handle that error15:47
slaweqthat's why I marked it as "Higt"15:47
slaweq*High15:47
slaweqok, and last topic from me for today15:47
slaweq#topic Periodic15:47
slaweqhere all except UT with neutron-lib master looks good15:48
slaweqI opened bug https://bugs.launchpad.net/neutron/+bug/1950275 today15:48
lajoskatonaFor that I pushed a patch: https://review.opendev.org/c/openstack/neutron/+/81717815:48
slaweqthx lajoskatona 15:49
slaweqbut my question is: why some change in neutron-lib caused that failure?15:49
slaweqas OVO object is defined in the Neutron repo, isn't it?15:49
lajoskatonabut that breaks unit test with n-lib 2.16.0, and what I can't consume:15:49
obondarevI believe order of constants on which OVO depends - changed15:49
lajoskatonaseems like this patch brings the failure: https://review.opendev.org/c/openstack/neutron-lib/+/81644715:49
lajoskatonayeah, possible, but that can change the hash for ovo?15:50
obondarevI think we faced similar issues in the past15:50
lajoskatonaso If I understand it we have to release n-lib with constants change and bump n-lib for neutron?15:51
obondarevI think so too15:51
lajoskatonaok15:51
slaweqbut the problem may be that in the release patches it runs some UT job for neutron, no?15:51
slaweqand this job will fail then15:51
slaweqor am I missing something?15:52
lajoskatonathat's possible15:52
lajoskatonaI push release patch and that will tell us if this way can work15:53
slaweq++15:53
slaweqmaybe I'm wrong here15:54
slaweqin the releases it don't runs UT probably15:54
slaweqI hope so at least :)15:54
slaweqok, so that's all what I had for today15:54
slaweqanything else You want to discuss regarding CI?15:54
obondarevlajoskatona: I would appreciate if you check https://review.opendev.org/c/openstack/neutron-lib/+/816468 before lib release :)15:54
lajoskatonaobondarev: I will15:55
obondarevlajoskatona:thanks a lot!15:55
slaweqok, so I think we can finish our meeting for today15:56
slaweqhave a great week and see You all next week on the video call again :)15:56
slaweqo/15:56
slaweq#endmeeting15:56
opendevmeetMeeting ended Tue Nov  9 15:56:58 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:56
opendevmeetMinutes:        https://meetings.opendev.org/meetings/neutron_ci/2021/neutron_ci.2021-11-09-15.00.html15:56
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/neutron_ci/2021/neutron_ci.2021-11-09-15.00.txt15:56
opendevmeetLog:            https://meetings.opendev.org/meetings/neutron_ci/2021/neutron_ci.2021-11-09-15.00.log.html15:56
lajoskatonao/15:57
obondarevo/15:57
opendevreviewMerged openstack/neutron master: Revert "[Fullstack] Mark TestHAL3Agent fip_qos test as unstable"  https://review.opendev.org/c/openstack/neutron/+/81523516:06
opendevreviewMerged openstack/neutron stable/xena: [DVR] Fix update of the MTU in the DVR HA routers  https://review.opendev.org/c/openstack/neutron/+/81665816:06
opendevreviewSlawek Kaplonski proposed openstack/neutron master: Add functional and fullstack jobs with FIPS enabled  https://review.opendev.org/c/openstack/neutron/+/81400916:10
opendevreviewMerged openstack/neutron master: Remove todo's in Y release  https://review.opendev.org/c/openstack/neutron/+/81585316:11
kevkoslaweq: I've read today meeting, and maybe I have different issue ..but my openstack wallaby is somehow slow when starting instances ..17:16
kevkowhen I run heat stack ..sometimes it is in minute ..sometimes it is running and running and completed after several minutes ..17:17
kevkoit looks like sometimes event about vif plugged from neutron is sent and received by nova...and in other cases I am waiting for event for a long time ..17:18
kevkocould you please advice me ? 17:18
slaweqkevko: You should check when port is transitioned to be up. And what is preventing that transition. Usually it's L2 or DHCP agent17:20
slaweqSorry but now I'm off for the day so i will not be able to response to your questions17:21
opendevreviewLajos Katona proposed openstack/networking-odl master: CI: Make tempest and rally jobs non-OVN based  https://review.opendev.org/c/openstack/networking-odl/+/81718617:21
kevkoslaweq: ok, thanks, just quick question -> 2021-11-09 16:40:42.749 8 ERROR neutron.agent.dhcp.agent [-] Unexpected number of DHCP interfaces for metadata proxy, expected 1, got 2 17:22
kevkothis is normal ? 17:22
slaweqNope. I don't think it's normal17:23
kevkohmm17:23
slaweqBut i don't know why it's like that17:23
slaweqI would need to look into code where that error comes from17:24
opendevreviewLajos Katona proposed openstack/networking-odl master: CI: Make tempest and rally jobs non-OVN based  https://review.opendev.org/c/openstack/networking-odl/+/81718619:15
opendevreviewSeena Fallah proposed openstack/ovsdbapp master: ovn-sb: remove chassis from Chassis_Private on ChassisDelCommand  https://review.opendev.org/c/openstack/ovsdbapp/+/81730019:51
opendevreviewSeena Fallah proposed openstack/ovsdbapp master: ovn-sb: remove chassis from Chassis_Private on ChassisDelCommand  https://review.opendev.org/c/openstack/ovsdbapp/+/81730021:35
opendevreviewMerged openstack/neutron-specs master: Off-path SmartNIC Port Binding with OVN  https://review.opendev.org/c/openstack/neutron-specs/+/78882121:57

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