| ralonsoh | slaweq, hello! I have a question about https://bugs.launchpad.net/neutron/+bug/1939558 | 07:57 |
|---|---|---|
| ralonsoh | this is related to "test_log_lifecycle", that is failing periodically and I think I could know the problem | 07:57 |
| ralonsoh | what happens if you create a log not related to a SG? | 07:57 |
| ralonsoh | with https://review.opendev.org/c/openstack/neutron/+/804237 all logs will be deleted | 07:58 |
| ralonsoh | those logs with and without target=sg | 07:58 |
| slaweq | ralonsoh: hmm, tbh I don't remember what will happen if You create log not related to any SG | 08:01 |
| slaweq | do You have link to the failed test? | 08:02 |
| ralonsoh | https://00b9edcb114e0ac8e05a-b611493cf8fd4459149d00d14c03b361.ssl.cf5.rackcdn.com/812334/1/check/neutron-tempest-plugin-api/bb2f986/testr_results.html | 08:02 |
| ralonsoh | I saw that the SG was deleted before the second check | 08:02 |
| ralonsoh | and the log was deleted too | 08:02 |
| ralonsoh | the point is that if a log has a SG as target, we should delete it | 08:02 |
| ralonsoh | but if not (that means this log is for all SGs) | 08:03 |
| ralonsoh | this log should not be deleted | 08:03 |
| slaweq | ralonsoh: so I probably made it wrong :/ | 08:03 |
| ralonsoh | slaweq, let me check it before merging the cherry-picks | 08:03 |
| slaweq | ralonsoh++ thx | 08:04 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron master: [WIP] Delete log entries when SG or port is deleted https://review.opendev.org/c/openstack/neutron/+/812459 | 08:55 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron master: [OVN] Check if OVN NB supports "Port_Group" https://review.opendev.org/c/openstack/neutron/+/812176 | 09:16 |
| opendevreview | Rodolfo Alonso proposed openstack/networking-ovn stable/train: [OVN] Set NB/SB "connection" inactivity probe https://review.opendev.org/c/openstack/networking-ovn/+/812304 | 09:43 |
| slaweq | ralonsoh: lajoskatona: hi | 10:13 |
| ralonsoh | hi | 10:14 |
| slaweq | qq about doc https://docs.openstack.org/neutron/latest/admin/config-ipv6.html#ipv6-ra-mode-and-ipv6-address-mode-combinations | 10:14 |
| slaweq | do You know what exactly columns "radvd A,M,O" and "External router A,M,O" means there? | 10:14 |
| ralonsoh | the radvd mode, one sec | 10:15 |
| ralonsoh | https://docs.opnsense.org/manual/radvd.html | 10:15 |
| ralonsoh | if I'm not wrong, A assisted, M managed, O router only | 10:16 |
| slaweq | ok, thx a lot | 10:17 |
| ralonsoh | slaweq, O stands for "other consifguration flag" | 10:17 |
| slaweq | ralonsoh: ok, but where did You found it? :) | 10:19 |
| ralonsoh | scroll down in this doc | 10:19 |
| ralonsoh | on the description of the three configuration modes available | 10:20 |
| ralonsoh | Auto Configuration Flag = 1 | 10:20 |
| ralonsoh | Managed Configuration Flag = 0 | 10:20 |
| ralonsoh | Other Configuration Flag = 0 | 10:20 |
| ralonsoh | for example | 10:20 |
| lajoskatona | slaweq: Hi | 10:33 |
| lajoskatona | I have a downstream meeting, but will check it | 10:33 |
| slaweq | ralonsoh++ thx | 10:33 |
| slaweq | lajoskatona: no worries, ralonsoh already replied me :) | 10:33 |
| slaweq | but thx anyway for willing to help :) | 10:34 |
| frickler | slaweq: ralonsoh: one could consider also replacing the "radvd" part there with something more descriptive, like "neutron-generated advertisements", since "radvd" is more of an implementation detail | 10:45 |
| slaweq | frickler: good idea | 10:46 |
| slaweq | I will propose update to that document today | 10:46 |
| ralonsoh | ok then | 10:46 |
| opendevreview | Merged openstack/neutron stable/victoria: Remove dhcp_extra_opt name after first newline character https://review.opendev.org/c/openstack/neutron/+/810876 | 10:54 |
| opendevreview | Anton Vazhnetsov proposed openstack/ovsdbapp master: nb: fix route.output_port name https://review.opendev.org/c/openstack/ovsdbapp/+/807749 | 11:01 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron master: [WIP] Delete log entries when SG or port is deleted https://review.opendev.org/c/openstack/neutron/+/812459 | 11:02 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron master: Delete log entries when SG or port is deleted https://review.opendev.org/c/openstack/neutron/+/812459 | 11:02 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron master: Execute "migrate_neutron_database_to_ovn" inside the same DB ctx https://review.opendev.org/c/openstack/neutron/+/812481 | 11:12 |
| opendevreview | Anton Vazhnetsov proposed openstack/ovsdbapp master: nb: provide 'discard' value for nexthop https://review.opendev.org/c/openstack/ovsdbapp/+/812484 | 11:37 |
| jawad-axd_ | Hi, with limited floating IPs, how can we avoid using two floating IPs per teanat for internet acccess, one for instance and one for router? Shared router is not technically possible as far as I know, what else can we look into. Thanks | 11:39 |
| opendevreview | Szymon Wróblewski proposed openstack/neutron master: Log OvsdbAppException as warnings https://review.opendev.org/c/openstack/neutron/+/812485 | 11:42 |
| *** elvira2 is now known as elvira | 11:44 | |
| opendevreview | Anton Vazhnetsov proposed openstack/ovsdbapp master: nb: provide 'discard' value for nexthop https://review.opendev.org/c/openstack/ovsdbapp/+/812484 | 11:47 |
| zigo | Hi there! I've been strugling getting the tip of stable/rocky to build in Debian Buster, and when up to bissect to find out what commit broke the Debian package. | 11:52 |
| zigo | Finally, I was able to point out that this patch : https://review.opendev.org/c/openstack/neutron/+/783544 | 11:52 |
| zigo | completely broke the Debian unit tests at package build time. | 11:52 |
| zigo | Example failure (among many others): | 11:54 |
| zigo | https://paste.opendev.org/show/809787/ | 11:54 |
| zigo | That's 225 failures that I'm talking about. | 11:54 |
| zigo | ralonsoh: slaweq: ^ | 11:54 |
| zigo | Currently, I have Neutron 13.0.7+git.2021.09.27.bace3d1890 ready to be uploaded to buster-security with that patch revert. Should I go ahead ? | 11:55 |
| opendevreview | Lajos Katona proposed openstack/networking-odl master: DNM: Check master status https://review.opendev.org/c/openstack/networking-odl/+/806095 | 11:55 |
| opendevreview | Lajos Katona proposed openstack/networking-bagpipe master: DNM: check master https://review.opendev.org/c/openstack/networking-bagpipe/+/806097 | 11:56 |
| opendevreview | Lajos Katona proposed openstack/networking-bgpvpn master: DNM: check master https://review.opendev.org/c/openstack/networking-bgpvpn/+/806096 | 11:56 |
| opendevreview | Lajos Katona proposed openstack/neutron-dynamic-routing master: DNM: test master https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/806177 | 12:03 |
| opendevreview | Lajos Katona proposed openstack/networking-sfc master: DNM: test master https://review.opendev.org/c/openstack/networking-sfc/+/812491 | 12:05 |
| opendevreview | Lajos Katona proposed openstack/neutron-vpnaas master: DNM: check master https://review.opendev.org/c/openstack/neutron-vpnaas/+/812492 | 12:21 |
| opendevreview | Slawek Kaplonski proposed openstack/neutron master: [Docs] Small improvements to the IPv6 config guide https://review.opendev.org/c/openstack/neutron/+/812497 | 12:42 |
| slaweq | zigo: what python version are You using there? I see that this patch was ok on py35 on Ubuntu | 12:47 |
| zigo | slaweq: That's Python 3.7 in Buster. | 12:47 |
| slaweq | zigo: but Rocky wasn't never tested on py37 | 12:48 |
| slaweq | u/s at least | 12:48 |
| slaweq | if You want to revert that patch in Debian, then it's up to You | 12:48 |
| zigo | slaweq: Do you think it's an interpreter issue ? | 12:48 |
| slaweq | u/s it was working fine | 12:48 |
| zigo | slaweq: Well, I have no idea if that patch is important or not, which is why I'm asking for your advice. | 12:49 |
| slaweq | zigo: that's my first guess | 12:49 |
| slaweq | that patch fixes High bug so it is pretty important | 12:50 |
| zigo | :/ | 12:50 |
| slaweq | maybe You can adjust Your UT in that version instead of reverting whole patch | 12:51 |
| zigo | slaweq: As in, maybe only the unit test is making things fail? | 12:51 |
| slaweq | zigo: but how You found out that this patch is the culprit as I see e.g. failuires in test neutron.tests.unit.plugins.ml2.extensions.test_dns_integration.DNSIntegrationTestCaseDefaultDomain.test_dns_driver_loaded_after_server_restart which wasn't touched at all by that patch | 12:52 |
| frickler | jawad-axd: you can define a service subnet that is used only for the router external IPs | 12:53 |
| zigo | slaweq: It took me a long long time, I bissected to that patch and built like 15 times the package ... | 12:55 |
| zigo | (30 mins each build ...) | 12:55 |
| slaweq | can You try to run same tests with e.g. python 3.5 ? | 12:56 |
| zigo | No, I can't. | 12:56 |
| slaweq | just to make sure if this is or isn't interpreter related | 12:56 |
| zigo | Buster comes with Python 3.7 ... | 12:56 |
| slaweq | why? | 12:56 |
| zigo | I wouldn't know how to install it. | 12:56 |
| zigo | Oh, hang on ... | 12:57 |
| zigo | slaweq: I can try to build in Stretch, as I have Rocky there. | 12:57 |
| zigo | Easy enough, I have all the dependencies for it. | 12:58 |
| zigo | slaweq: Let me try. | 12:58 |
| slaweq | sure | 12:58 |
| slaweq | but please look, u/s UT are fine: https://zuul.opendev.org/t/openstack/build/3b583c988403472da1792e7e0ce40cb3 | 12:58 |
| slaweq | but they run on py35 | 12:59 |
| slaweq | on Ubuntu 16.04 | 12:59 |
| zigo | Unit tests are now running ... I'll know in a bit. | 13:13 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron master: [OVN] Check if OVN NB supports "Port_Group" https://review.opendev.org/c/openstack/neutron/+/812176 | 13:17 |
| zigo | slaweq: Same thing with Python 3.5: 1113 unit failures ... :/ | 13:41 |
| * zigo tries to build removing that UT | 13:42 | |
| lajoskatona | zigo: it is strange because the patch You pointed was backported from train and there py36 and py37 is used for testing (https://review.opendev.org/c/openstack/neutron/+/783923 ) | 13:43 |
| slaweq | zigo: then maybe it's some dependency installed/missing - I really don't know how it runs on Debian | 13:43 |
| bcafarel | ack I would be surprised if that ovs neutron agent restart UT change had an impact on mock in other tests | 13:50 |
| lajoskatona | #startmeeting networking | 14:00 |
| opendevmeet | Meeting started Tue Oct 5 14:00:08 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 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
| opendevmeet | The meeting name has been set to 'networking' | 14:00 |
| mlavalle | o/ | 14:00 |
| lajoskatona | o/ | 14:00 |
| ralonsoh | hi | 14:00 |
| slaweq | hi | 14:00 |
| amotoki | hi | 14:00 |
| lajoskatona | Ok, I think we can start | 14:01 |
| lajoskatona | #topic Announcements | 14:01 |
| lajoskatona | Xena cycle calendar: https://releases.openstack.org/xena/schedule.html | 14:01 |
| lajoskatona | This week is Xena release week: http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025158.html :-) | 14:01 |
| bcafarel | o/ | 14:01 |
| lajoskatona | so we are older one cycle again :-) | 14:02 |
| rubasov | o/ | 14:02 |
| bcafarel | We are getting close to the end of the alphabet | 14:02 |
| isabek | o/ | 14:02 |
| lajoskatona | I think we finally have every patch merged to xena, thanks everybody for that | 14:02 |
| lajoskatona | bcafarel: true | 14:03 |
| slaweq | congrats everyone :) | 14:03 |
| lajoskatona | bcafarel: don't remember if there was any plan for that already how to continue, start from "a" again? | 14:03 |
| mlavalle | so we are in Yoga now? | 14:04 |
| lajoskatona | mlavalle: officially this week is R-0 of xena | 14:04 |
| lajoskatona | so not yet | 14:04 |
| bcafarel | lajoskatona: I guess it will loop yes | 14:05 |
| mlavalle | but for practical purposes, like reviewing and merging, we are, aren't we? | 14:05 |
| slaweq | but technically master branch is already for Yoga since couple of weeks | 14:05 |
| bcafarel | I think so, stable/xena branches exist everywhere now (and RC2 is out) | 14:05 |
| mlavalle | yeah, that's what I meant | 14:05 |
| lajoskatona | mlavalle: yes, as xena is cut, and master can go forward | 14:05 |
| lajoskatona | ok, I have 2 small highlights: | 14:06 |
| opendevreview | Alex Kavanagh proposed openstack/neutron stable/wallaby: Move dns-integration extension to the ML2_SUPPORTED_API_EXTENSIONS list https://review.opendev.org/c/openstack/neutron/+/812509 | 14:06 |
| lajoskatona | Openinfra episode this Thursday: OpenInfra Live Ep. 25: OpenStack Xena- Open Source Integration and Hardware Diversity | 14:06 |
| lajoskatona | https://www.youtube.com/watch?v=aqilhEmkEBw&ab_channel=OpenInfrastructureFoundation | 14:06 |
| lajoskatona | Neutron has few minutes to talk about cyborg integration together with Nova and Cyborg | 14:07 |
| lajoskatona | and ot tell about technical debt reduction in Neutron (and other projects will be on stag as well) | 14:07 |
| lajoskatona | slides for it (please check Cyborg integration and technical debt reduction) | 14:08 |
| lajoskatona | please check if you have few minutes and tell me what I missed what to include | 14:08 |
| lajoskatona | Next Thursday the openinfra episode will be around Neutron scaling: https://www.youtube.com/watch?v=4ZLqILbLIpQ&ab_channel=OpenInfrastructureFoundation | 14:08 |
| lajoskatona | That will be mostly the production of slaweq :-) | 14:09 |
| slaweq | lajoskatona: really? :) | 14:09 |
| lajoskatona | but if you have scaling stories, that would be helpful | 14:09 |
| slaweq | I though we will be together there ;) | 14:10 |
| lajoskatona | slaweq: Yeah, but ttx asked you first :P | 14:10 |
| slaweq | :D | 14:10 |
| slaweq | ok | 14:10 |
| slaweq | and You all are more than welcome there | 14:10 |
| slaweq | You can help answering questions e.g. on chat etc. | 14:11 |
| lajoskatona | yeah, the live chat will be open | 14:11 |
| lajoskatona | Ok, is there anything more to announce or for announcements? | 14:12 |
| mlavalle | not from me | 14:12 |
| slaweq | me neighter | 14:12 |
| zigo | slaweq: Removing the UT (but not the rest of the patch which is a one-liner) fixes it in Stretch (and I guess in Buster too, will build right away now ...). | 14:12 |
| lajoskatona | ok next topic | 14:12 |
| lajoskatona | #topic Bugs | 14:13 |
| slaweq | zigo++ | 14:13 |
| zigo | Oh, sorry. | 14:13 |
| lajoskatona | rubasov was bug deputy last week: http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025177.html | 14:13 |
| lajoskatona | I found 2 unassigned bugs from the report: | 14:13 |
| lajoskatona | https://bugs.launchpad.net/neutron/+bug/1945283 test_overlapping_sec_grp_rules from neutron_tempest_plugin.scenario is failing intermittently | 14:14 |
| lajoskatona | https://bugs.launchpad.net/neutron/+bug/1945306 [dvr+l3ha] north-south traffic not working when VM and main router are not on the same host | 14:14 |
| lajoskatona | rubasov: anything to add to the report? | 14:14 |
| rubasov | the dvr+l3ha kombo may be broken for some time, if we analyzed it correctly | 14:14 |
| rubasov | the reporter indentified the bugfix that introduced the regression | 14:15 |
| rubasov | so I hope dvr experts have some ground to start from | 14:15 |
| rubasov | regarding the 'still being triaged' metering bug | 14:16 |
| slaweq | this would be good if liuyulong could take a look | 14:16 |
| rubasov | it turned out it wasn't really in an ovn environment (was a typo between ovs and ovn) | 14:16 |
| lajoskatona | I think this week liuyulong is still on PTO, but not sure | 14:17 |
| rubasov | however as I looked into our docs, they are quite ambiguous about if ovn supports metering or not, so that could be fixed in the support matrix regardless | 14:17 |
| lajoskatona | this is the metering bug just for the log: https://bugs.launchpad.net/neutron/+bug/1945560 | 14:18 |
| rubasov | lajoskatona: thanks | 14:18 |
| rubasov | that bug report is probably more like a support request now (knowing it's about ovs env) | 14:19 |
| lajoskatona | thanks rubasov for the report and for the triaging | 14:20 |
| rubasov | of course | 14:20 |
| lajoskatona | This week ralonsoh is the deputy, and next week lucasgomes will be, is that ok? | 14:20 |
| ralonsoh | ok | 14:20 |
| mlavalle | cool, we are in good hands | 14:21 |
| lajoskatona | ok I will contact lucasgomes to be sure :-) | 14:21 |
| lajoskatona | mlavalle: true :-) | 14:21 |
| mlavalle | ralonsoh: estuve tentando a decir que estamos jodidos | 14:21 |
| ralonsoh | hehehehe | 14:22 |
| ralonsoh | (don't translate that) | 14:22 |
| mlavalle | I won't | 14:22 |
| slaweq | LOL | 14:23 |
| bcafarel | :) | 14:23 |
| * slaweq had to translate that when ralonsoh said not to do this :D | 14:23 | |
| lajoskatona | ok, liuyulong is not here, do you have anything for L3? | 14:23 |
| ralonsoh | not from me | 14:23 |
| lajoskatona | ok, last topic then | 14:24 |
| lajoskatona | #topic On Demand Agenda | 14:24 |
| lajoskatona | There's nothing on the meeting wiki | 14:25 |
| lajoskatona | I had 1 question though, which I just started to dicsuss with Heat team | 14:26 |
| lajoskatona | Heat is now using neutronclient as client | 14:26 |
| lajoskatona | for me it is double work to have everything in openstacksdk and in neutronclient as well, shall I hear your opinion on this? | 14:27 |
| lajoskatona | Perhaps I dig into this a little more and we can discuss it during the PTG | 14:27 |
| ralonsoh | neutronclient was deprecated 2 years ago, if I'm not wrong | 14:27 |
| mlavalle | what direction do you lean towards? | 14:27 |
| mlavalle | getting rid of neutronclient? | 14:28 |
| mlavalle | yeah, it has been deprecated for a long time | 14:28 |
| ralonsoh | but we are still merging code | 14:28 |
| mlavalle | I think even longer than 2 years | 14:28 |
| rubasov | ralonsoh: I guess this is about the python bindings part, which wasn't deprecated (only the cli iirc) | 14:28 |
| lajoskatona | ralonsoh: yeah but we deprecated the CLI part, not the python api part, am I right? | 14:28 |
| amotoki | IMHO it is better to implement the python bidnings in SDK and implement CLI in OSC and OSC plugin (in neutornclient repo for the stadium projects) | 14:28 |
| slaweq | AFAIK neutronclient is actually 2 things - CLI and "lib" and that lib part isn't deprecated | 14:28 |
| lajoskatona | rubasov: exactly | 14:28 |
| ralonsoh | yes, the CLI, not the API | 14:28 |
| slaweq | amotoki: correct me if I'm wrong but for now I think we have it actually like that | 14:29 |
| frickler | so is heat using the neutron cli? or the python bindings? | 14:29 |
| lajoskatona | but to have cli in python-openstackclient we have to have binding in openstacksdk, or am I wrong? | 14:29 |
| slaweq | of course we have also python bindings for core neutron things in neutronclient | 14:29 |
| ralonsoh | lajoskatona, yes, we need SDK first | 14:29 |
| rubasov | frickler: the python bindings | 14:29 |
| lajoskatona | frickler: just the python bindings from neutronclient (I think at least) | 14:30 |
| lajoskatona | on the python bindings level there should be no diff between neutronclient and sdk, am I right? | 14:31 |
| amotoki | we have python bindings for two purposes: the one is for the core feature used by otherr projects like nova and the other is for OSC plugin for stadium projects | 14:31 |
| amotoki | I think there are ambiguous points on the current status | 14:32 |
| lajoskatona | amotoki: in neutronclient you mean? | 14:32 |
| amotoki | lajoskatona: yes | 14:32 |
| amotoki | in neutronclient | 14:32 |
| ralonsoh | and is it possible to move all to SDK? | 14:32 |
| ralonsoh | just asking | 14:32 |
| amotoki | I think so | 14:32 |
| lajoskatona | yeah, ambiguous is good word for it :-) | 14:32 |
| amotoki | I can summarize the current status of the neutronclient repo. there are some ambigous points on the repo. | 14:33 |
| mlavalle | lajoskatona: is that what you intended when bringing up the topic? Consolidate and have one less repo to support? | 14:33 |
| lajoskatona | ralonsoh: I hope yes | 14:33 |
| frickler | are there plans to actually drop the CLI part from neutronclient soonish? (assuming that feature-parity with OSC has been reached) | 14:34 |
| lajoskatona | mlavalle: that could be the outcome, now I just realized that for new features the python bindings must be done in 2 repos, and I hate double work :-) | 14:34 |
| lajoskatona | firckler: you mean to even delete the code, not just print warning if somebody use neutron net-list? | 14:35 |
| frickler | lajoskatona: yes | 14:35 |
| frickler | because the warning was there a long time when actually ignoring it was the only option | 14:36 |
| lajoskatona | frickler: I think that was not discussed yet, and not sure if we have to wail after we reached the feature parity | 14:36 |
| frickler | so people are used to ignoring it and will continue to do so | 14:36 |
| lajoskatona | frickler: that's true | 14:36 |
| amotoki | xena neutron CLI emmits "neutron CLI is deprecated and will be removed in the Z cycle. Use openstack CLI instead." though we haven't discussed the exact cycle yet. | 14:36 |
| slaweq | frickler: lajoskatona: actually we merged https://review.opendev.org/c/openstack/python-neutronclient/+/793366 some time ago | 14:36 |
| slaweq | and we agreed to remove it completly in Z cycle | 14:37 |
| lajoskatona | slaweq: thanks, so we discussed, and set it to Z | 14:37 |
| slaweq | as we merged in OSC possibility to pass custom parameters to Neutron | 14:37 |
| mlavalle | amotoki: that message has been there way longer that 2 cycles | 14:37 |
| frickler | ah, I hadn't seen that, but that looks like a good path forward | 14:37 |
| slaweq | which was last missing thing AFAIR | 14:37 |
| slaweq | mlavalle: nope, it was slightly different and said that it will be removed "in the future" | 14:38 |
| amotoki | mlavalle: the message was updated in Xena cycle and it now contains when it plans to be dropped. | 14:38 |
| slaweq | not it says that it will be removed in "Z cycle" | 14:38 |
| lajoskatona | ok, so in Z we can remove the CLI code from neutronclient | 14:38 |
| slaweq | ++ | 14:38 |
| ralonsoh | +1 | 14:38 |
| mlavalle | cool | 14:38 |
| lajoskatona | ok, for now I think I will ask heat folks if it is possible to have sdk as client for some feature, and come back with result for that | 14:40 |
| lajoskatona | thanks for the discussion | 14:40 |
| lajoskatona | any other topics to discuss? | 14:40 |
| frickler | well I added a topic to the CI meeting, but if we have time now we can discuss here | 14:41 |
| frickler | about neutron-trunk testing in grenade | 14:41 |
| lajoskatona | yeah, that is interesting | 14:42 |
| frickler | where I argue that it would make sense to move the service definition for that from neutron's devstack plugin into devstack proper | 14:42 |
| lajoskatona | gmann is working on some patches to have trunk enabled | 14:42 |
| frickler | iiuc that has already been merged | 14:42 |
| lajoskatona | frickler: ok, I missed that | 14:43 |
| slaweq | frickler are You saying to move https://github.com/openstack/neutron/blob/master/devstack/lib/trunk to devstack repo? | 14:43 |
| gmann | frickler: lajoskatona those are merged on master but not for stable | 14:43 |
| frickler | but I would like to get grenade away from using the neutron devstack plugin | 14:43 |
| frickler | slaweq: yes, that and some wrapping code | 14:43 |
| gmann | https://review.opendev.org/q/topic:%22bug%252F1945346%22+(status:open%20OR%20status:merged) | 14:43 |
| gmann | and those are WIP due to nova bug https://bugs.launchpad.net/nova/+bug/1912310 | 14:44 |
| lajoskatona | gmann: thanks | 14:44 |
| frickler | one question is: what about the other new features, will more of them become "standard" soon? | 14:44 |
| frickler | then this may be a lost cause anyway | 14:44 |
| lajoskatona | not sure when feature become standard :-) | 14:46 |
| gmann | frickler: lajoskatona slaweq and on master we run trunk test as extensions is set as 'All' (enable everything) | 14:46 |
| slaweq | frickler: tbh I don't know about any discussion to make it "standard feature" | 14:46 |
| gmann | to me too, it make sense to move to lib/trunk to devstack side | 14:46 |
| frickler | lajoskatona: my definition would be: "when other projects want to test them in the default grenade job" | 14:46 |
| frickler | or possibly default tempest job even | 14:47 |
| gmann | +1 | 14:47 |
| lajoskatona | frickler: ok, that makes sense | 14:47 |
| slaweq | gmann: but wasn't that "ALL" in extensions list kind of bug? | 14:47 |
| lajoskatona | that should be part of the interop dicsussion perhaps | 14:47 |
| slaweq | if we will have it like that we would need to move also other things to devstack repo as they would all be "standard features" | 14:47 |
| slaweq | no? | 14:48 |
| gmann | slaweq: well, on master we want to test everything while development/release itself right? | 14:48 |
| frickler | slaweq: either move them, too, or accept that the neutron plugin is part of the standard setup | 14:48 |
| gmann | and anything under-development can be added in disable list | 14:48 |
| frickler | but then the question would be: what goes into devstack/lib/neutron* at all? | 14:49 |
| slaweq | frickler: we can move things which are there for at least couple of cycles and are considered as "stable" to devstack repo | 14:50 |
| lajoskatona | frickler: that's a good question | 14:50 |
| slaweq | like trunk, qos | 14:50 |
| slaweq | port_forwarding etc. | 14:50 |
| amotoki | agree. perhaps once a feature is complete it is better to move their testing from neutron-specific to tempest/devstack. | 14:50 |
| lajoskatona | I can't say where the border should be as neutron CI is quite big | 14:50 |
| slaweq | in fact I think that we are adding things to neutron devstack plugin as it's easier and faster for us | 14:51 |
| lajoskatona | but now tempest runs tests wit ovn only, no? | 14:51 |
| gmann | and due to that (mgiht be) we kept trunk disabled in all stable for no reason and testing on master only | 14:51 |
| slaweq | but we can consider moving things to devstack repo once they are finished, e.g. next cycle after something was introduced | 14:51 |
| gmann | lajoskatona: yes, whatever devstack is default | 14:51 |
| lajoskatona | and neutron-tempest-lugin has jobs for other backend, ovs, linuxbridge? | 14:51 |
| frickler | there was some issue with debian and ovn iirc | 14:52 |
| amotoki | lajoskatona: I think we are discussing tests themselves rather than job definitions | 14:52 |
| lajoskatona | yeah if we move part of neutron devstavk-plugin to core devstack we should still has specific job definitons for not-ovn jobs.... | 14:52 |
| lajoskatona | amotoki: true | 14:53 |
| frickler | https://review.opendev.org/c/openstack/devstack/+/789083/20/.zuul.yaml#90 | 14:53 |
| slaweq | lajoskatona: I think that those are unrelated things really | 14:54 |
| lajoskatona | So the suggestion is to move trunk related code from neutron devstack plugin to devstack itself ? | 14:55 |
| frickler | o.k., so does someone want to do the neutron-trunk move as a first step? | 14:55 |
| slaweq | I can do this | 14:56 |
| lajoskatona | That can be a good start and based on that we can see if we need to move anything else | 14:56 |
| lajoskatona | slaweq: thanks | 14:56 |
| frickler | and then maybe have a topic at the ptg to see what other things should be moved next | 14:56 |
| gmann | +1, indeed | 14:56 |
| slaweq | ++ | 14:56 |
| lajoskatona | +1 | 14:56 |
| amotoki | +1 | 14:56 |
| ralonsoh | +1 | 14:57 |
| amotoki | gmann: is there any criteria to have backend-specific things in devstack? | 14:57 |
| amotoki | we already have several backend-specific things in devstack like linuxbridge. | 14:57 |
| gmann | amotoki: nothing as such as long we as we are testing those somewhere | 14:57 |
| slaweq | ovn, ovs too | 14:57 |
| amotoki | thanks | 14:58 |
| gmann | I remember we have for cinder too | 14:58 |
| frickler | maybe one could actually move lb back into the neutron plugin, now that it isn't widely tested anymore? | 14:58 |
| slaweq | frickler: I can add it to my todo list but not with high priority for sure | 14:59 |
| lajoskatona | those can be checked | 14:59 |
| lajoskatona | ok we can close the meeting I think | 14:59 |
| lajoskatona | See you next week | 14:59 |
| lajoskatona | #endmeeting | 14:59 |
| opendevmeet | Meeting ended Tue Oct 5 14:59:40 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:59 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/networking/2021/networking.2021-10-05-14.00.html | 14:59 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/networking/2021/networking.2021-10-05-14.00.txt | 14:59 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/networking/2021/networking.2021-10-05-14.00.log.html | 14:59 |
| mlavalle | o/ | 14:59 |
| ralonsoh | bye | 14:59 |
| amotoki | o/ | 14:59 |
| slaweq | #startmeeting neutron_ci | 15:00 |
| opendevmeet | Meeting started Tue Oct 5 15:00:27 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 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:00 |
| opendevmeet | The meeting name has been set to 'neutron_ci' | 15:00 |
| ralonsoh | hi | 15:00 |
| slaweq | hi | 15:00 |
| slaweq | let's wait few more minutes for others to join and we will start | 15:02 |
| lajoskatona | Hi | 15:03 |
| slaweq | Grafana dashboard: http://grafana.openstack.org/dashboard/db/neutron-failure-rate | 15:03 |
| bcafarel | o/ (sorry was wrapping up a downstream meeting) | 15:03 |
| slaweq | #topic Actions from previous meetings | 15:04 |
| slaweq | slaweq to check vpnaas stable/train patch https://review.opendev.org/c/openstack/neutron-vpnaas/+/805969/10 | 15:04 |
| slaweq | this is done, with huge help from gmann :) | 15:04 |
| bcafarel | yes gmann++ indeed | 15:04 |
| bcafarel | that passing CI job made me smile :) | 15:05 |
| gmann | np! | 15:05 |
| slaweq | we missed to define tempest_plugins there :) | 15:05 |
| slaweq | next one | 15:05 |
| slaweq | alonsoh to check functional tests issue with router's state transition | 15:05 |
| ralonsoh | yes, I have a patch, one sec | 15:06 |
| ralonsoh | #link https://review.opendev.org/c/openstack/neutron/+/811751 | 15:06 |
| slaweq | thx ralonsoh | 15:08 |
| slaweq | ok, next one | 15:08 |
| slaweq | slaweq to check api extensions list in ovs based jobs, how it was generated | 15:08 |
| slaweq | I didn't check it but I think that gibi and gmann found the solution for that issue already | 15:08 |
| lajoskatona | I added the link to that checklist to our checklist for relase | 15:09 |
| lajoskatona | https://review.opendev.org/c/openstack/neutron/+/812112 | 15:10 |
| slaweq | thx lajoskatona | 15:10 |
| slaweq | and that are all actions from last week | 15:11 |
| slaweq | #topic Stadium projects | 15:11 |
| slaweq | any updates? | 15:11 |
| lajoskatona | all is green, except vpnaas | 15:11 |
| lajoskatona | fix is here: https://review.opendev.org/c/openstack/neutron-vpnaas/+/811731 | 15:11 |
| bcafarel | autumn cleanup time there I guess | 15:12 |
| lajoskatona | some news for vpnaas (half stable topic): p, q, r, s branches are deleted so no more failures from periodic jobs | 15:12 |
| slaweq | sorry that I missed that one | 15:12 |
| bcafarel | +train and newer fixed :) | 15:13 |
| ralonsoh | cool! | 15:13 |
| *** whoami-rajat__ is now known as whoami-rajat | 15:13 | |
| lajoskatona | and I have a question: for bgpvpn theres patches for centos8 : https://review.opendev.org/q/owner:bshewale%2540redhat.com+project:%2522%255Eopenstack/networking.*%2522+intopic:%2522%255Ec7-to-c8.*%2522 | 15:13 |
| lajoskatona | with redhat hat (:P) could you help me if those are ok? | 15:14 |
| slaweq | LOL | 15:14 |
| slaweq | sure | 15:14 |
| bcafarel | interesting, added to the list | 15:15 |
| slaweq | I added it for my tomorrow's todo list | 15:15 |
| lajoskatona | thanks | 15:15 |
| lajoskatona | that's it for stadium from me | 15:16 |
| slaweq | thx lajoskatona | 15:16 |
| slaweq | I think we can move on | 15:16 |
| slaweq | #topic Stable branches | 15:16 |
| bcafarel | I have a few pending backports to check but overall all good | 15:17 |
| bcafarel | we got the needed fixes in xena just in time for rc2 | 15:17 |
| ralonsoh | +1 to this | 15:18 |
| slaweq | yeah, that were "last minute" patches | 15:19 |
| ralonsoh | I don't know what you are talking about... | 15:19 |
| bcafarel | :) | 15:19 |
| slaweq | btw. speaking about xena | 15:19 |
| bcafarel | ralonsoh++ | 15:19 |
| slaweq | I proposed https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/811003 some time ago | 15:20 |
| slaweq | please review it | 15:20 |
| ralonsoh | suer | 15:20 |
| ralonsoh | sure | 15:20 |
| bcafarel | thanks yes time to add xena to the list | 15:21 |
| slaweq | ok, I think we can move on to the next topic then | 15:22 |
| slaweq | #topic Grafana | 15:22 |
| slaweq | I don't see anything critically wrong there | 15:24 |
| lajoskatona | it seems that after the release week the gods of CI are more merciful | 15:24 |
| slaweq | :D | 15:24 |
| slaweq | well said lajoskatona :) | 15:24 |
| slaweq | there was some short spike yesterday but it was on most of the jobs (or all even) so I think it was something outside neutron | 15:25 |
| slaweq | and it is gone already | 15:25 |
| slaweq | lets talk about some specific jobs and issues there :) | 15:26 |
| slaweq | #topic fullstack/functional | 15:27 |
| slaweq | I found one fullstack failure: | 15:27 |
| slaweq | https://8d5ef598bba78b1573a4-7dfe055f87ad090ed1b50745545f409a.ssl.cf1.rackcdn.com/805391/10/check/neutron-fullstack-with-uwsgi/6e03086/testr_results.html | 15:27 |
| slaweq | it was failed neutron.tests.fullstack.test_l3_agent.TestHAL3Agent.test_router_fip_qos_after_admin_state_down_up test | 15:27 |
| slaweq | and I saw in logs "Network unreachable" errors | 15:27 |
| slaweq | so IMO this may be some issue with test itself, not in the Neutron code really | 15:28 |
| slaweq | I will report bug for that | 15:28 |
| slaweq | but I don't think I will have time to check it really this week | 15:28 |
| slaweq | #action slaweq to report fullstack issue with neutron.tests.fullstack.test_l3_agent.TestHAL3Agent.test_router_fip_qos_after_admin_state_down_up test | 15:28 |
| slaweq | #topic Tempest/Scenario | 15:30 |
| slaweq | here I saw something interesting | 15:30 |
| slaweq | at least 3 times scenario jobs failed with errors like e.g. in: https://6599da62140c9583e14a-cd7f53ffbb0b86c69deae453da021fe8.ssl.cf5.rackcdn.com/811746/4/check/neutron-tempest-plugin-scenario-openvswitch/3cafcd7/testr_results.html | 15:30 |
| slaweq | basically all HA routers were in backup state but non of them were transitioned to master | 15:31 |
| slaweq | I wonder if that could be the same issue as the one which ralonsoh fixed with https://review.opendev.org/c/openstack/neutron/+/811751 | 15:31 |
| ralonsoh | I think so | 15:31 |
| ralonsoh | I was checking that | 15:31 |
| ralonsoh | because are those routers created only for those tests? | 15:32 |
| slaweq | yes, each test is creating router | 15:32 |
| slaweq | and deleting it on cleanup | 15:32 |
| ralonsoh | if so, they initial "primary" state could be delayed unnecessarily | 15:32 |
| slaweq | but can this delay actually cause the issue that it will never later be switched? | 15:33 |
| slaweq | to be primary | 15:33 |
| ralonsoh | no, this delay is by design | 15:34 |
| ralonsoh | to avoid histeresis during the transitions to master | 15:34 |
| ralonsoh | *primary | 15:34 |
| slaweq | so that is likely different issue probably | 15:34 |
| ralonsoh | could be, yes | 15:35 |
| slaweq | as in this case routers aren't switched to primary at all | 15:35 |
| slaweq | I will report bug and will try to investigate in the logs | 15:35 |
| slaweq | but help is welcome with that one :) | 15:35 |
| ralonsoh | sure, I'll check it once we have the other patch merged | 15:35 |
| slaweq | #action slaweq to report bug regarding ha routers not going to be primary never | 15:36 |
| slaweq | ralonsoh++ thx | 15:36 |
| slaweq | ok, next one | 15:36 |
| slaweq | we still have some issues with ovs agent crashing, like https://04824dc10f811bf71cc7-f60cbd2bdbb8b5648c0b0982a5f4272f.ssl.cf1.rackcdn.com/805391/10/check/neutron-ovs-tempest-slow/cd391db/compute1/logs/screen-q-agt.txt | 15:36 |
| slaweq | but I hope that recent backports to os-ken will solve that issue | 15:36 |
| slaweq | the bad thing is that we need to have new os-ken release for that | 15:37 |
| ralonsoh | yes but we need the new branches in "releases" | 15:37 |
| slaweq | and releases repo isn't ready for yoga yet | 15:37 |
| ralonsoh | and then create a new tag there | 15:37 |
| ralonsoh | nope | 15:37 |
| lajoskatona | side note: I tried to reach directly some ryu developers (most active ones in last months) to have some discussion with them | 15:38 |
| ralonsoh | can we add a topic in Neutron meetings? to track weekly any change in ryu that should be backported to os-ken | 15:40 |
| ralonsoh | that could take 5 secs (if nothing is merged) | 15:40 |
| ralonsoh | or a couple of links to be reviewed | 15:40 |
| ralonsoh | I can take care of it | 15:40 |
| slaweq | sounds good | 15:40 |
| lajoskatona | sure, that;s a good idea, to follow ehat happens there | 15:41 |
| slaweq | maybe we can also propose some simple script in https://github.com/openstack/neutron/tree/master/tools to list such changes | 15:42 |
| slaweq | and maybe even to backport such patches to os-ken | 15:43 |
| slaweq | wdyt? | 15:43 |
| lajoskatona | I can check it before the meeting and we can triage if there's anything during the meeting to include or not | 15:43 |
| lajoskatona | yeah, that's a good idea | 15:43 |
| ralonsoh | the first triage will be the worst, I'll check on friday what we should migrate | 15:43 |
| ralonsoh | and I'll propose the needed patches | 15:43 |
| lajoskatona | as I see not much activity (weekly 1-2 patches) in ryu | 15:43 |
| slaweq | ok, thx ralonsoh for that | 15:44 |
| slaweq | #action ralonsoh will come up with list of ryu patches which we should backport to os-ken | 15:44 |
| slaweq | #action lajoskatona will add ryu - os-ken sync topic to the neutron weekly meeting's agenda | 15:44 |
| lajoskatona | +1 | 15:45 |
| slaweq | is that ok for You ^^ ? | 15:45 |
| lajoskatona | yes it's ok for me | 15:45 |
| ralonsoh | perfect for me too | 15:45 |
| slaweq | thx | 15:45 |
| slaweq | that was the last topic from me for today | 15:46 |
| slaweq | btw. periodic jobs are fine - even fedora one :) | 15:46 |
| slaweq | thx ralonsoh | 15:46 |
| bcafarel | nice CI status for release week then | 15:46 |
| lajoskatona | yeah suprisingly few failures this week, and we can get rid of old vpnaas jobs now | 15:46 |
| slaweq | yeah, I just need to check tobiko job there but that's not urgent | 15:47 |
| ralonsoh | I don't know how the error in the compute test is passing now in fedora | 15:47 |
| slaweq | me neighter but it's green :) | 15:47 |
| ralonsoh | I'll close the bug (half of it) | 15:47 |
| slaweq | so I don't want to worry about it | 15:47 |
| slaweq | thx ralonsoh :) | 15:47 |
| slaweq | ok, anything else You want to discuss today? | 15:47 |
| bcafarel | all good here | 15:48 |
| lajoskatona | nothing from me | 15:49 |
| ralonsoh | I'm ok | 15:49 |
| slaweq | so thx for attending the meeting | 15:49 |
| slaweq | and have a great evening | 15:49 |
| slaweq | o/ | 15:49 |
| slaweq | #endmeeting | 15:49 |
| opendevmeet | Meeting ended Tue Oct 5 15:49:53 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:49 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/neutron_ci/2021/neutron_ci.2021-10-05-15.00.html | 15:49 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/neutron_ci/2021/neutron_ci.2021-10-05-15.00.txt | 15:49 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/neutron_ci/2021/neutron_ci.2021-10-05-15.00.log.html | 15:49 |
| ralonsoh | bye | 15:50 |
| lajoskatona | o/ | 15:50 |
| bcafarel | o/ | 15:50 |
| opendevreview | Merged openstack/networking-odl stable/train: Try deinit odl_features in TestOdlFeaturesNoFixture setUpClass https://review.opendev.org/c/openstack/networking-odl/+/695365 | 16:00 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron master: Delete log entries when SG or port is deleted https://review.opendev.org/c/openstack/neutron/+/812459 | 16:27 |
| opendevreview | Rodolfo Alonso proposed openstack/networking-ovn stable/train: [OVN] Set NB/SB "connection" inactivity probe https://review.opendev.org/c/openstack/networking-ovn/+/812304 | 16:34 |
| opendevreview | Merged openstack/neutron stable/wallaby: [DVR] Check if SNAT iptables manager is initialized https://review.opendev.org/c/openstack/neutron/+/812285 | 17:06 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron master: [OVN] Update the DHCP options when the metadata port is modified https://review.opendev.org/c/openstack/neutron/+/807692 | 17:25 |
| opendevreview | Slawek Kaplonski proposed openstack/neutron master: Make configure_for_func_testing compatible with e.g. Centos https://review.opendev.org/c/openstack/neutron/+/799625 | 18:49 |
| opendevreview | Slawek Kaplonski proposed openstack/neutron master: WIP/DNM - Add FIPS enabled jobs https://review.opendev.org/c/openstack/neutron/+/797537 | 18:49 |
| *** tamas_erdei is now known as terdei | 20:32 | |
| opendevreview | Hang Yang proposed openstack/neutron-lib master: Add API extension "security-groups-shared-filtering" https://review.opendev.org/c/openstack/neutron-lib/+/812617 | 22:05 |
| opendevreview | Hang Yang proposed openstack/neutron master: Add shared field to SG API response and filter https://review.opendev.org/c/openstack/neutron/+/811242 | 22:11 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!