[Bug 1948666] [NEW] Misleading behavior when enabling hardware offloads
Public bug reported: According to the documentation(1) the following setting: ovs-vsctl set Open_vSwitch . other_config:hw-offload=true|false/unset should have effects only after vswitchd is restarted. However, flipping the value on will have the following effect: Hardware offloads will be enabled for newly created ports, but not on the ports prior enabling the TC offloads. If hw-offload got enabled, qdisc configured, hw-offload disabled --> ovs restarted. This sequence might not delete the qdisc, and vswitchd on restart might not touch existing ones. As a side effect you will have to delete them manually. (1) https://github.com/openvswitch/ovs/blob/v2.16.1/vswitchd/vswitch.xml#L225-L248 ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948666 Title: Misleading behavior when enabling hardware offloads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1948666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774249] Re: update_available_resource will raise DiskNotFound after resize but before confirm
** Tags added: verification-done-bionic verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774249 Title: update_available_resource will raise DiskNotFound after resize but before confirm To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1774249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774249] Re: update_available_resource will raise DiskNotFound after resize but before confirm
Hello Robie, I have tested the proposed package using the test case. We need to keep in mind that this patch does not allow the exception to be raised, but we still the error as a WARNING. I am adding the packages used for testing together with the logs. ubuntu@test:~/home$ juju run -a nova-compute -- "apt list nova*" | grep installed nova-api-metadata/bionic-proposed,now 2:17.0.13-0ubuntu4 all [installed] nova-common/bionic-proposed,now 2:17.0.13-0ubuntu4 all [installed,automatic] nova-compute/bionic-proposed,now 2:17.0.13-0ubuntu4 all [installed] nova-compute-kvm/bionic-proposed,now 2:17.0.13-0ubuntu4 all [installed] nova-compute-libvirt/bionic-proposed,now 2:17.0.13-0ubuntu4 all [installed,automatic] ubuntu@test:~/home$ juju run -a nova-compute -- grep "DiskNotFound" /var/log/nova/nova-compute.log 2021-10-19 09:22:11.422 19060 WARNING nova.virt.libvirt.driver [req-60b887da-6da1-4463-b754-6d389d7f5df3 - - - - -] Periodic task is updating the host stats, it is trying to get disk info for instance-0001, but the backing disk storage was removed by a concurrent operation such as resize. Error: No disk at /var/lib/nova/instances/5f5d2c95-afb0-4e8c-9fd1-fc3f29d3a5f8/disk: DiskNotFound: No disk at /var/lib/nova/instances/5f5d2c95-afb0-4e8c-9fd1-fc3f29d3a5f8/disk ** Tags removed: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774249 Title: update_available_resource will raise DiskNotFound after resize but before confirm To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1774249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915480] Re: DeviceManager's fill_dhcp_udp_checksums assumes IPv6 available
** Description changed: The following code in DeviceManager's fill_dhcp_udp_checksums assumes IPv6 is always enabled: iptables_mgr = iptables_manager.IptablesManager(use_ipv6=True, namespace=namespace) When iptables_mgr.apply() is later called, an attempt to add the UDP checksum rule for DHCP is done via iptables-save/iptables-restore and if IPv6 has been disabled on a hypervisor (eg, by setting `ipv6.disable=1` on the kernel command line) then an many-line error occurs in the DHCP agent logfile. There should be a way of telling the agent that IPv6 is disabled and as such, it should ignore trying to set up the UDP checksum rule for IPv6. This can be easily achieved given that IptablesManager already has support for disabling it. We've seen this on Rocky on Ubuntu Bionic but it appears the issue still exists on the master branch. = Ubuntu SRU details: - [Impact] - See above. + + [Impact] - [Test Case] - Deploy openstack on a hypervisor with IPv6 disabled. - Create a network which has a subnetwork with DHCP enabled. - Search the `neutron-dhcp-agent.log` (with debug log enabled) and check if there are any `ip6tables-restore` commands. + See above - [Regression Potential] - Minimal. - Users which were relying on the setting to always be true could be affected. + + [Test Plan] + + Disable IPv6 on a hypervisor. + sudo sysctl -w net.ipv6.conf.all.disable_ipv6=1 + sudo sysctl -w net.ipv6.conf.default.disable_ipv6=1 + sudo sysctl -w net.ipv6.conf.lo.disable_ipv6=1 + Deploy Openstack Ussuri or Victoria with one compute node, using the hypervisor which has IPv6 disabled as a neutron gateway. + Create a network which has a subnetwork with DHCP enabled. Eg: + openstack network create net1 + openstack subnet create subnet1 --network net1 --subnet-range 192.0.2.0/24 --dhcp + Search the `/var/log/neutron/neutron-dhcp-agent.log` (with debug log enabled) and check if there are any `ip6tables-restore` commands. Eg: + sudo grep ip6tables-restore /var/log/neutron/neutron-dhcp-agent.log + + [Where problems could occur] + + Users which were relying on the setting to always be true could be + affected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915480 Title: DeviceManager's fill_dhcp_udp_checksums assumes IPv6 available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1915480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915480] Re: DeviceManager's fill_dhcp_udp_checksums assumes IPv6 available
** Patch added: "neutron-focal-victoria.debdiff" https://bugs.launchpad.net/neutron/+bug/1915480/+attachment/5525960/+files/neutron-focal-victoria.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915480 Title: DeviceManager's fill_dhcp_udp_checksums assumes IPv6 available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1915480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915480] Re: DeviceManager's fill_dhcp_udp_checksums assumes IPv6 available
** Patch added: "neutron-focal-ussuri.debdiff" https://bugs.launchpad.net/neutron/+bug/1915480/+attachment/5525933/+files/neutron-focal-ussuri.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915480 Title: DeviceManager's fill_dhcp_udp_checksums assumes IPv6 available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1915480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915480] Re: DeviceManager's fill_dhcp_udp_checksums assumes IPv6 available
** Description changed: The following code in DeviceManager's fill_dhcp_udp_checksums assumes IPv6 is always enabled: iptables_mgr = iptables_manager.IptablesManager(use_ipv6=True, - namespace=namespace) + namespace=namespace) When iptables_mgr.apply() is later called, an attempt to add the UDP checksum rule for DHCP is done via iptables-save/iptables-restore and if IPv6 has been disabled on a hypervisor (eg, by setting `ipv6.disable=1` on the kernel command line) then an many-line error occurs in the DHCP agent logfile. There should be a way of telling the agent that IPv6 is disabled and as such, it should ignore trying to set up the UDP checksum rule for IPv6. This can be easily achieved given that IptablesManager already has support for disabling it. We've seen this on Rocky on Ubuntu Bionic but it appears the issue still exists on the master branch. + + = + Ubuntu SRU details: + + [Impact] + See above. + + [Test Case] + Deploy openstack on a hypervisor with IPv6 disabled. + Create a network which has a subnetwork with DHCP enabled. + Search the `neutron-dhcp-agent.log` (with debug log enabled) and check if there are any `ip6tables-restore` commands. + + [Regression Potential] + Minimal. + Users which were relying on the setting to always be true could be affected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915480 Title: DeviceManager's fill_dhcp_udp_checksums assumes IPv6 available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1915480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915480] Re: DeviceManager's fill_dhcp_udp_checksums assumes IPv6 available
** No longer affects: cloud-archive/victoria -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915480 Title: DeviceManager's fill_dhcp_udp_checksums assumes IPv6 available To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1915480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
Verified bionic-ussuri/proposed and bionic-ussuri/train proposed using [Test Case] ** Tags removed: verification-train-needed ** Tags added: verification-bionic-done verification-train-done ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
Verified hirtsue/proposed, focal-ussuri/proposed, focal- victoria/proposed, focal-wallaby/proposed using [Test Case] ** Tags removed: verification-needed-focal verification-victoria-needed verification-wallaby-needed ** Tags added: verification-focal-done verification-victoria-done verification-wallaby-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
** Tags removed: verification-needed-hirsute ** Tags added: verification-hirsute-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
