=== E_Eickmeyer is now known as Eickmeyer === Rhvs is now known as MeltedLux === MeltedLux is now known as md_5 === md_5 is now known as Rhvs [08:06] sarnold_: Somebody replied already on the bug, and I got the answer. Thank you! === utkarsh210225 is now known as utkarsh2102 [11:56] coreycb: Do you know if its possible to pull Neutron 16.3.0 from any Ubuntu repositories? I hit that nasty 16.3.1 bug which causes all L3 agents to remain in standby so I managed to find and install some .deb's for I think Focal for 16.0.0 and that's working but I think it may be the cause of some other less serious issues now [12:21] shubjero: hey, also consider opening a bug, preferably? [12:28] utkarsh2102: yeah there's already a bug submitted from early may, I marked bug as im affected and added comments [12:28] oh perfect, thank you! [12:28] at this point id just like 16.3.0 published somewhere so i can use it instead of some random 16.0.0 deb [12:28] I'm using this now: neutron-common 2:16.0.0~b3~git2020041516.5f42488a9a-0ubuntu2 [12:30] utkarsh2102: this is the bug I hit: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1927868 [12:30] Launchpad bug 1927868 in neutron (Ubuntu) "vRouter not working after update to 16.3.1" [Undecided, Confirmed] [12:30] Real ugly. Takes the whole openstack deployment offline [12:32] I had tested my openstack upgrade over a month ago which at the time was 16.3.0 and then we had some further scheduling delays so by the time i got to do prod, 16.3.1 was out and I forgot to re-test.. my fault there but since for some reason old versions are not retained I was not able to just easily specify a version of neutron and thus had to scramble during our upgrade to try and find a [12:32] version that was available and worked. === Poster` is now known as Poster === ikonia_ is now known as ikonia [14:44] shubjero: this one? https://bugs.launchpad.net/cloud-archive/+bug/1832021 [14:44] Launchpad bug 1832021 in neutron (Ubuntu Bionic) "Checksum drop of metadata traffic on isolated networks with DPDK" [Medium, Fix Committed] === Serge is now known as hallyn [15:09] fnordahl: Is there an option to get newer OVN packages in UCA? I'm interested in 21.06 which has this commit - https://github.com/ovn-org/ovn/commit/127bf166ccf4a2509f670c48a00b0340039f20d2 [15:09] Commit 127bf16 in ovn-org/ovn "northd: Support flow offloading for logical switches with no ACLs." === smoser1 is now known as smoser [17:00] Hi all , Anyone knows if the future version of Ubuntu server will be having ZFS as the root level of file system as a default or option during the installation ? Right now it is possible but the out of the box experience is pretty ish regarding this option. Right now the version of Ubuntu 21.04 now support ZFS on root by default. [17:17] coreycb: Sorry, was away for a bit. No not that one, this one: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1927868 [17:17] Launchpad bug 1927868 in neutron (Ubuntu) "vRouter not working after update to 16.3.1" [Undecided, Confirmed] [17:17] way nastier [17:44] coreycb: Do you know how I can install via apt or perhaps download deb files for Neutron 16.3.0 for bionic Ussuri? 16.3.1 and 16.3.2 take down my entire openstack deployment [17:47] shubjero: that's not fixed by this by any chance is it? [17:48] https://bugs.launchpad.net/neutron/+bug/1929832 [17:48] Launchpad bug 1929832 in neutron "stable/ussuri py38 support for keepalived-state-change monitor" [High, In Progress] [17:51] coreycb: I don't think so. Symptoms seem different, but definitely in same ballpark. The issue I have is none of the L3 agents for a router enter an active state. So I'll have 3 L3 agents for a router all in standby and therefore is unreachable from a network perspective. I did try installing the neutron packages from the proposed repo '16.3.2-0ubuntu3~cloud0' but the issue persisted. === sarnold_ is now known as sarnold [19:37] shubjero: does this appear to be related? https://bugs.launchpad.net/neutron/+bug/1928466 I'm just trying to see if anything upstream has already dealt with this. [19:37] Launchpad bug 1928466 in neutron "Allowed address pairs aren't populated to the new host with DVR router" [Medium, Fix Released] [19:38] I'll move discussion over to the bug [19:45] coreycb: i dont think so, we dont even use DVR