Tuesday, 2021-12-07

opendevreviewMerged openstack/neutron master: Improve DHCP RPC handler  https://review.opendev.org/c/openstack/neutron/+/81685000:23
opendevreviewMerged openstack/neutron master: [OVN] Chassis name (OVS system-id) must be a UUID formatted string  https://review.opendev.org/c/openstack/neutron/+/81963400:23
opendevreviewMerged openstack/neutron stable/xena: [OVS][FW] Initialize ConjIdMap._max_id depending on the current OFs  https://review.opendev.org/c/openstack/neutron/+/81943900:23
opendevreviewMerged openstack/neutron stable/wallaby: [OVS][FW] Initialize ConjIdMap._max_id depending on the current OFs  https://review.opendev.org/c/openstack/neutron/+/81944000:23
opendevreviewMerged openstack/neutron stable/victoria: [OVS][FW] Initialize ConjIdMap._max_id depending on the current OFs  https://review.opendev.org/c/openstack/neutron/+/81944100:23
opendevreviewMerged openstack/neutron stable/ussuri: [OVS][FW] Initialize ConjIdMap._max_id depending on the current OFs  https://review.opendev.org/c/openstack/neutron/+/81944200:23
opendevreviewTakashi Kajinami proposed openstack/neutron stable/wallaby: bw-limit: Pass int parameters to Open vSwitch  https://review.opendev.org/c/openstack/neutron/+/82061200:52
opendevreviewMerged openstack/neutron-vpnaas master: Add "update_network" implementation to "L3AgentExtension" child classes  https://review.opendev.org/c/openstack/neutron-vpnaas/+/82012602:54
fricklerlajoskatona: slaweq: we talked about this backport last week, please add to your review list https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/82009907:58
slaweqfrickler sure07:59
slaweqI will check it right after meeting which I have now07:59
lajoskatonafrickler: I will check it08:03
slaweqfrickler patch approved08:37
opendevreviewMerged openstack/neutron-dynamic-routing stable/xena: Add a StaticScheduler without automatic scheduling  https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/82009909:11
fricklerslaweq: lajoskatona: thx to both of you, next up will be the backport to wallaby. just in case you thought you were done ;)09:12
lajoskatonafrickler: no problem :-)09:33
fricklermeh, that gets merge conflicts, no easy-clicky :-(09:52
opendevreviewLajos Katona proposed openstack/neutron master: Keep binding:profile keys during placement allocation change  https://review.opendev.org/c/openstack/neutron/+/82036309:53
opendevreviewDr. Jens Harbott proposed openstack/neutron-dynamic-routing stable/wallaby: Add a StaticScheduler without automatic scheduling  https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/82068009:56
fricklerluckily 'twas only zuul config09:56
*** redrobot8 is now known as redrobot10:20
stephenfinralonsoh: I was out on Friday. What did you folks decide on for the '--force'/'--no-force' idea in OSC?10:37
ralonsohstephenfin, to open a RFE: https://bugs.launchpad.net/neutron/+bug/195317010:37
ralonsohbut the proposal was accepted10:37
ralonsohcheck the steps in the LP bug. We'll move to --force option in Neutron10:37
ralonsoh(same as Nova)10:37
ralonsoh(of course, that will take a couple of releases)10:38
stephenfinOh, so you're fixing this in the server rather than the client?10:38
ralonsohfor now we'll keep the current functionality in Neutron10:38
ralonsohand we'll write a warning message10:38
ralonsohthen we'll change the Neutron server to adopt the Nova behaviour10:39
ralonsohand then we'll remove the --check-limit parameter10:39
ralonsohso, for now, the OSC doesn't need any change10:39
ralonsohthat will make Nova and Neutron behaviour more consistent10:39
stephenfinTo be clear, I wasn't advocating for changing anything in the server. I was hoping to shim in sensible (IMO) behavior in the client alone10:40
stephenfinFixing it in the server is definitely a better option long-term but what do we do about the client in the interim10:40
stephenfin?10:40
ralonsohin the client nothing, for now10:40
ralonsohjust having --check-limit for Neutron and --force for Nova10:40
stephenfinSo we don't add '--check-limit'?10:40
ralonsohyes, we need it now10:40
ralonsohthen we'll remove it10:40
ralonsohthis is to keep the current behaviour10:41
ralonsohwe don't want to suddenly change the OSC or the Neutron server10:41
stephenfinAgreed. OSC should continue with the "force" (i.e. check_limit=false) behaviour for now. However, do we have to use the '--check-limit' terminology? Could we use '--no-force' instead?10:43
stephenfinJust because the server calls it one thing doesn't mean the client has to use the same terminology10:43
ralonsohstephenfin, that was agreed in the Neutron drivers meeting10:43
ralonsohto have this parameter name10:44
ralonsohin any case, this is temporary10:44
stephenfinexample: nova records instance actions, but OSC calls these server actions to be consistent with other server things10:44
ralonsohNeutron is ok with this term and I'm too10:45
ralonsohthat will survive 2 releases only10:45
ralonsohand is enough for the customer asking for this feature10:45
stephenfinWe can't remove that from OSC once it merges though, because we'll have to support Xena neutron deployments "forever"10:46
stephenfinThe '--forces'/'--no-forces' option seems to provide a very nice migration path to a future where neutron behaviour is the same as nova10:47
ralonsohsame as "check-limit"10:48
ralonsohthis is just a parameter name10:48
ralonsohno-forces == check-limity10:48
ralonsohI can open again this debate if needed, but really I don't want it10:49
ralonsohafter 3 Neutron drivers meeting trying to explain that I was not going to change the default behaviour10:49
stephenfinYeah, this is total bike shedding. Sorry :)10:50
stephenfinOkay, I still totally disagree but it's your project and your call :) I'll re-review that today10:51
ralonsohstephenfin, thanks a lot10:51
opendevreviewMaor Blaustein proposed openstack/neutron-tempest-plugin master: Add test_create_port_with_dns_name  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/82045611:29
opendevreviewMaor Blaustein proposed openstack/neutron-tempest-plugin master: Add test_create_port_with_dns_name  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/82045612:00
opendevreviewRodolfo Alonso proposed openstack/neutron master: Do not announce any DNS resolver if "0.0.0.0" or "::" provided  https://review.opendev.org/c/openstack/neutron/+/82085812:31
opendevreviewLajos Katona proposed openstack/neutron-tempest-plugin master: Add tap-as-a-service scenario tests  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/81487612:33
noonedeadpunkhey there! I'm wondering if there's some known issue present for neutron-server served as uwsgi and ovn?12:40
ralonsohnoonedeadpunk, there is, uwsgi is still not supported12:40
noonedeadpunkah! I jsut thought that since you test it in CI it does hehe12:41
noonedeadpunkfeels like neutron left as close to the only one service left...12:44
slaweqnoonedeadpunk there is one bug https://bugs.launchpad.net/neutron/+bug/1912359 which blocks it13:05
noonedeadpunkwell, what we see that uwsgi responds at first, but then got stuck and stop replying on requests...13:08
noonedeadpunkbut yeah, sounds like we see that as well in osa13:08
noonedeadpunkexcept that there's probably some issue with calico driver as well...13:09
noonedeadpunkbut it's quite different topic indeed13:09
ricolinlajoskatona,  FYI, Pain point discussion meeting have scheduled on 1500UTC this Wednesday(Dec. 8th) in https://meet.google.com/xsx-inbw-mos13:45
lajoskatonaricolin: thanks, I added to my calendar :-)13:46
lajoskatona#startmeeting networking14:00
opendevmeetMeeting started Tue Dec  7 14:00:58 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
mlavalleo/14:01
lajoskatonaHi14:01
slaweqhi14:01
ralonsohhi14:01
lajoskatonaI think we can start14:02
bcafarelo/14:02
obondarevhi14:02
lajoskatona#topic Announcements14:02
mlavallewith bcafarel and obondarev we have completed the ususal suspects bunch for this meeting14:02
lajoskatonamlavalle: exactly14:03
lajoskatonaThe usual cycle calendar: https://releases.openstack.org/yoga/schedule.html14:03
lajoskatonaThis is Week R-16: http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026173.html14:03
rubasovo/14:04
lajoskatonaI think we should cut  new release for n-lib at least (have to check other libs if we have enough  things merged14:05
slaweqfor neutron-lib I think we are ok as we already released it this cycle14:06
slaweqsame for os-ken iirc14:06
slaweqI'm not sure about ovsdbapp14:06
slaweqbut of course we can release new versions around X-2 milestone14:06
opendevreviewMerged openstack/neutron stable/xena: [OVN] Fix gateway_mtu option should not always be set  https://review.opendev.org/c/openstack/neutron/+/81957814:07
lajoskatonafor neutron-lib just for the regularity we should have one, and last time it was this group we waited for: https://review.opendev.org/q/topic:%2522bug/1950454%2522+(status:open+OR+status:merged)+update_network14:07
opendevreviewMerged openstack/neutron stable/wallaby: [OVN] Fix gateway_mtu option should not always be set  https://review.opendev.org/c/openstack/neutron/+/81957914:07
lajoskatonaslaweq: thanks14:07
lajoskatonaSome news for the testing runtime: 14:08
lajoskatonafull discussion: http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026175.html14:08
lajoskatonaand the summary from last week TCmeeting: "We have an agreement now on Yoga testing runtime and keeping python3.6 support in Yoga."14:08
lajoskatonaso we keep py36 in this cycle14:09
slaweq++14:10
lajoskatonaanother announcement: "Pain Points" discussion continues: http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026169.html14:10
lajoskatonaThere's an etherpad: https://etherpad.opendev.org/p/pain-point-elimination14:11
lajoskatonaand there will be a meeting: Dec. 8th, 15:00 UTC14:11
lajoskatonaAs I see OSC is the main pain point, and we are on the good side14:12
slaweqlajoskatona do You know if tomorrow it will be discussion about Neutron maybe?14:12
slaweqI'm not sure if I should join there or maybe it's not needed at all14:12
lajoskatonaslaweq: it will be openstack wide if I understand well14:12
slaweqok14:13
slaweqI will try to be there14:13
mlavalleyeah, looking at the email, it is not specific to Neutron14:13
lajoskatonaI can join tomorrow14:13
amotokilajoskatona: where does it happen?14:14
mlavalleIt's a video conference14:14
lajoskatonain the etherpad there are a few neutron related things (hostname, osc/neutronclient compatibility)14:14
amotokiI don't see the URL for it14:14
lajoskatonaamotoki: #link https://meet.google.com/xsx-inbw-mos14:14
amotokilajoskatona: thanks. I also found the link in the mailing list thread14:15
lajoskatonaso I have hopes that not Neutron will be the bad guy :-)14:15
slaweqlajoskatona it's always networking issue so it will be ;P14:16
lajoskatonaslaweq: that's true :-)14:16
bcafarel:)14:16
amotokieveryone talks over networks :)14:16
mlavallepoor Neutron guys, they are always blamed14:17
slaweqLOL14:17
lajoskatonaAny comments for announcements?14:17
lajoskatona#topic Bugs14:18
lajoskatonalajoskatona (it's me :-)) was bug deputy last week: http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026193.html14:18
lajoskatonaWe have 3 unassigned bugs:14:19
lajoskatona#link https://bugs.launchpad.net/neutron/+bug/195267514:19
lajoskatonathis one is about a db upgrade issue14:19
lajoskatona#link https://bugs.launchpad.net/neutron/+bug/194477914:20
lajoskatonaThis one is tough: VirtualInterfaceCreateException due to "Timeout waiting for [('network-vif-plugged'..."14:20
lajoskatonaAs I remember there was a long mail thread for this14:20
lajoskatonaI think this mail started it: #link http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025892.html14:21
ralonsohthere are several mixed discussions there14:21
ralonsohincluding several backend types14:21
ralonsohso when investigating those kind of errors, focus on one backend14:22
lajoskatonafrom nova perspective that is one of the problems that nova has to act based on network backend and that is not elegant, as I remember14:23
slaweqyes, and the problem is that it behaves differently in each neutron backend :/14:24
lajoskatonaI mean that nova has to use big if-else blocks to wait or not wait for event based on something that is Neutron internal thing14:24
lajoskatonaslaweq: exactly14:24
lajoskatonaI think in our downstream CI the issue was that odl and ovs send vif-pluged differently for example14:25
lajoskatonaso ti was hard to debug even what happens or not happens14:25
lajoskatonaok we had another unassigned bug from last week: #link https://bugs.launchpad.net/neutron/+bug/195316514:27
lajoskatonaand actually rubasov started to check it14:27
rubasovit may be a duplicate of https://bugs.launchpad.net/neutron/+bug/193041414:28
lajoskatonarubasov: thanks, I was looking for this14:29
slaweqrubasov so do You think we are leaking IPv6 traffic between isolated networks?14:29
haleybI would also guess it's possible that there is a second namespace with that IPv6 address, like the qrouter14:29
rubasovyes I believe so14:29
haleybrubasov: oh, that would be worse :(14:29
rubasovI think it's only a short window when ports belong to the DEAD_VLAN14:30
rubasovI'll update that bug report soon14:31
slaweqbut priteau said there that even after restarting neutron-dhcp-agent it wasn't fixed in many cases14:31
slaweqshouldn't that dead vlan tag be already removed in such case?14:32
mlavallegood point14:32
rubasovslaweq: nobody will clear dadfailed state 14:32
slaweqrubasov ahh, ok14:32
rubasovso if dadfailed happens during the short windows it stays14:32
slaweqdhcp agent will just check that interface is there and will do nothing with it after restart14:33
rubasovI also have a patch, which I'll upload, but that's at most a partial fix and not fixing the full root cause which I still don't get14:33
priteau(I am here in case you need further details)14:34
rubasovpriteau: feel free to try the reproduction in bug 1930414 to see if it's the same as you see14:35
rubasovpriteau: also after the update I'll add soon14:35
priteauI started setting up a dev environment to try and reproduce it. So far I've only seen it on a prod system14:36
lajoskatonathanks rubasov for the explanation and for working on this issue14:38
lajoskatonaThis week amotoki is the deputy, and next week mlavalle will be.14:39
mlavalleack14:39
amotokiack14:39
mlavalleThanks for the reminder14:39
lajoskatonacool14:39
mlavalleI still require a formal email....14:39
lajoskatonamlavalle: I just wanted to ask :-)14:39
mlavalleno, just kdding. slaweq spoiled me14:39
slaweqLOL14:40
lajoskatonaadvertisement: slaweq prepared something for the "reduce rechecks" topic: http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026208.html14:41
lajoskatonaso if you have ideas, or interested join please to the CI meeting from 15:00 UTC :-)14:41
slaweq++14:42
slaweqanyone's welcome there14:42
lajoskatonathanks slaweq14:43
lajoskatonawe have nothing for L3, and no changes in ryu14:43
lajoskatona#topic On Demand Agenda14:43
opendevreviewMerged openstack/neutron stable/victoria: [OVN] Fix gateway_mtu option should not always be set  https://review.opendev.org/c/openstack/neutron/+/81958014:44
lajoskatonaIf there is nothing to discuss, let's close the meeting14:45
mlavallesounds good to me14:45
lajoskatona#endmeeting14:45
opendevmeetMeeting ended Tue Dec  7 14:45:31 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:45
opendevmeetMinutes:        https://meetings.opendev.org/meetings/networking/2021/networking.2021-12-07-14.00.html14:45
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/networking/2021/networking.2021-12-07-14.00.txt14:45
opendevmeetLog:            https://meetings.opendev.org/meetings/networking/2021/networking.2021-12-07-14.00.log.html14:45
slaweq++14:45
mlavalleo/14:45
lajoskatonao/14:45
bcafarelo/14:45
slaweqsee You in 15 minutes on the ci meeting :)14:45
ralonsohbye14:45
amotokio/14:45
slaweq#startmeeting neutron_ci15:00
opendevmeetMeeting started Tue Dec  7 15:00:15 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
slaweqvideo meeting link https://meetpad.opendev.org/neutron-ci-meetings15:00
bcafarelo/ joining in a min15:02
opendevreviewBence Romsics proposed openstack/neutron master: WIP sleep to raise the chance of crosstalk between dhcp ports  https://review.opendev.org/c/openstack/neutron/+/82089615:02
opendevreviewBence Romsics proposed openstack/neutron master: A step toward making the dead vlan actually dead  https://review.opendev.org/c/openstack/neutron/+/82089715:02
slaweq#topic Actions from previous meetings15:03
slaweqlajoskatona to check why make FIP down took more than 120 seconds in the L3 agent15:03
opendevreviewBence Romsics proposed openstack/neutron master: A step toward making the dead vlan actually dead  https://review.opendev.org/c/openstack/neutron/+/82089715:03
slaweqslaweq to check failed neutron.tests.functional.agent.l3.test_keepalived_state_change.TestMonitorDaemon.test_handle_initial_state_backup15:07
slaweqlajoskatona to increase timeout of the lower-constraints job in neutron15:09
haleybotherwiseguy: can you take a look at https://bugs.launchpad.net/neutron/+bug/1953481 seems liks ovsdbapp bug (sorry to interrupt meeting)15:10
slaweqslaweq to check https://7bed286b1abc124aef60-716c2febf7f730d66787c22f3ed0da3e.ssl.cf5.rackcdn.com/818067/2/check/neutron-functional-with-uwsgi/48adb0f/testr_results.html15:11
slaweqslaweq to report bug about failing neutron_tempest_plugin.scenario.test_mac_learning.MacLearningTest15:12
slaweqDone https://bugs.launchpad.net/neutron/+bug/195206615:12
slaweq#topic Stable branches15:13
slaweq#topic Stadium projects15:14
slaweq#topic Grafana15:15
slaweq#action slaweq to check missing grafana logs for periodic jobs15:16
bcafarelykarel: testing grafana dashboards locally https://blog.cafarelli.fr/2016/12/local-testing-of-openstack-grafana-dashboard-changes/ (not sure if it still works)15:18
ykarelbcafarel, Thanks /me will tryout some time15:18
ykarelohh 2016, so will likely not work as it is15:19
ykarelbut worth a try15:19
bcafarelhopefully a few URLs updates (and maybe grafana being easier to install now) and the rest may still be OK15:20
slaweq#topic Tempest/Scenario15:21
slaweq#link https://bugs.launchpad.net/nova/+bug/195347815:21
slaweq#link https://bugs.launchpad.net/neutron/+bug/195347915:23
slaweq#link https://bugs.launchpad.net/neutron/+bug/195348015:25
slaweq#link https://565740c969459684c3b5-240d4aa44573f96d2050363ab0d496a6.ssl.cf2.rackcdn.com/820125/1/check/neutron-ovs-tempest-dvr-ha-multinode-full/d90c2a6/testr_results.html15:27
slaweq#link https://launchpad.net/bugs/181378715:27
slaweq#topic Periodic15:30
slaweqhttps://bugs.launchpad.net/neutron/+bug/195348115:30
slaweq#action ralonsoh to check  https://bugs.launchpad.net/neutron/+bug/195348115:32
slaweq#topic On Demand15:32
slaweqhttps://etherpad.opendev.org/p/neutron-ci-improvements15:32
slaweq#link https://etherpad.opendev.org/p/neutron-ci-improvements15:33
lajoskatonafor retry: https://opendev.org/zuul/zuul/src/branch/master/doc/source/reference/jobs.rst#build_status15:47
lajoskatona"The pre-run playbook failed more than the maximum number of retry attempts."15:47
opendevreviewDr. Jens Harbott proposed openstack/neutron-dynamic-routing stable/wallaby: Add a StaticScheduler without automatic scheduling  https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/82068015:50
opendevreviewDr. Jens Harbott proposed openstack/neutron-dynamic-routing stable/wallaby: Dropping lower constraints testing (stable Wallaby)  https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/82090815:50
gibihttp://status.openstack.org/elastic-recheck/15:56
gibiand you have to propose query signature here https://opendev.org/opendev/elastic-recheck/src/branch/master/queries16:01
otherwiseguyhaleyb: on PTO until Jan 416:05
slaweq#endmeeting16:06
opendevmeetMeeting ended Tue Dec  7 16:06:01 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:06
opendevmeetMinutes:        https://meetings.opendev.org/meetings/neutron_ci/2021/neutron_ci.2021-12-07-15.00.html16:06
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/neutron_ci/2021/neutron_ci.2021-12-07-15.00.txt16:06
opendevmeetLog:            https://meetings.opendev.org/meetings/neutron_ci/2021/neutron_ci.2021-12-07-15.00.log.html16:06
slaweqthx gibi for the links16:06
haleybotherwiseguy: ack, I heard, will ping jlibosva or ralonsoh to look at bug since they +2'd it16:06
ralonsohhaleyb, I'm on it now16:07
slaweqthx gibi for the links16:07
haleybralonsoh: ack, i'll stop looking then16:08
otherwiseguyhaleyb: looks like I get to have another reason to hate Mocking :D16:09
haleybotherwiseguy: yeah... i was trying to figure out if it was just the test or things could have been made compatible in ovsdbapp somehow.  but enjoy your PTO :)16:11
otherwiseguy haleyb: ralonsoh: I'd be surprised if there is anything to do in ovsdbapp. It's just that the mock.Mock() has no 'priority'. making it a magicmock will probably fix.16:18
otherwiseguyjlibosva had suggested having _get_queue take a priority and not an event, which also probably would have avoided the issue.16:19
otherwiseguyjlibosva is always right though, one day I'll learn to just do what he says. :D16:19
otherwiseguyI believe his reasoning was even "it'd make it easier to test" :D16:20
otherwiseguythough I guess you'd have to get the priority anyway, so meh. anyway, I'm going to go back to wasting my with housework. :D16:25
opendevreviewLajos Katona proposed openstack/tap-as-a-service master: WIP: Make ovs-taas start in VLAN only env  https://review.opendev.org/c/openstack/tap-as-a-service/+/81744916:42
* jlibosva reads16:43
* jlibosva knows a person with otherwiseguy nick but he should be on PTO16:44
*** otherwiseguy is now known as not_otherwiseguy16:44
opendevreviewLajos Katona proposed openstack/tap-as-a-service master: WIP: Make ovs-taas start in VLAN only env  https://review.opendev.org/c/openstack/tap-as-a-service/+/81744916:45
not_otherwiseguyjlibosva: tl;dr s/mock.Mock/mock.MagicMock/16:45
jlibosvanot_otherwiseguy: ah, I see now. the priority parameter :D16:45
haleybnot_otherwiseguy: that doesn't work directly unfortunately, assertCountEqual failure16:46
jlibosvahaleyb: ralonsoh is there anything I can help with wrt ovsdbapp bug? are you gonna send the MagicMock patch?16:51
ralonsohjlibosva, I have one ready16:51
ralonsohgive me 30 secs16:51
jlibosva2916:51
jlibosva2816:51
jlibosva2716:51
ralonsohheheh16:51
not_otherwiseguyhaleyb: ah, yeah, can't look at _watched_events :)16:57
not_otherwiseguyIT'S SECRET16:57
opendevreviewRodolfo Alonso proposed openstack/neutron master: Mock the OVN events providing a "priority" value  https://review.opendev.org/c/openstack/neutron/+/82091117:00
ralonsohjlibosva, ^^17:01
* haleyb throws-up in his mouth a little looking :)17:02
not_otherwiseguyralonsoh: Mine was similar :D https://paste.centos.org/view/6cdd04f417:06
not_otherwiseguyBut I'm definitely not working.17:07
* not_otherwiseguy hides17:07
* not_otherwiseguy remembers he is not_otherwiseugy so can work17:07
not_otherwiseguyralonsoh: haleyb: jlibosva: I guess if we had to we could do in _get_event a getattr(event, 'priority', 0)17:23
not_otherwiseguyjust to make things work regardless.17:24
ralonsohwhat is the highest priority? 0?17:24
not_otherwiseguy-infinity is lowest priority (i.e. will execute last)17:25
ralonsohby default we should assign the lowest one17:25
ralonsoh0 is the maximum17:25
ralonsohor do you consider that, if no priority is given, that means this is a high priority event?17:26
ralonsohjust asking17:27
ralonsohif so, I'm ok17:27
not_otherwiseguy0 is not the maximum.17:27
ralonsohok, you can provide negative values17:27
not_otherwiseguyand the sort order is reversed.17:27
not_otherwiseguyWaitEvent has a priority of 10, it goes after RowEvent which has a priority of 20.17:28
not_otherwiseguysort function is negative priority, i.e. highest numbers highest priority.17:29
not_otherwiseguybut in any case, you really have to pass in a subclass of RowEvent, and RowEvent defaults to priority=20 so meh. it's just testing that would not have a priority.17:32
not_otherwiseguyeh, getattr doesn't actually fix it anyway17:35
opendevreviewLajos Katona proposed openstack/neutron-tempest-plugin master: test_list_agent: pop 'alive' from agent dict  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/82092117:46
not_otherwiseguy(because mock is evil) :p17:47
*** not_otherwiseguy is now known as otherwiseguy17:48
* otherwiseguy goes back to PTOing17:48
*** jlibosva is now known as Guest788519:55
opendevreviewMerged openstack/neutron-tempest-plugin master: [stable/rocky] Regroup tests exclusion list and add new failing ones  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/81910920:33

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