Hello Guillaume, or anyone else affected, Accepted ovn-octavia-provider into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ovn- octavia-provider/6.0.1-0ubuntu1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Description changed: [Impact] This release sports mostly bug-fixes and we would like to make sure all of our supported customers have access to these improvements. The update contains the following package updates: ovn-octavia-provider 6.0.1 + The Ovn Octavia provider is the second most used provider used in Canonical solutions, the most used provider being Amphora, not being affected by this package. + In charmed openstack, OVN is not the default provider. In sunbeam, the LoadBalancer feature (underlying octavia) is not enabled by default, and when it is, ovn is the default provider if Amphora is not enabled. + + The main motivation is broken IPv6 health monitoring with the OVN + provider: health monitors can be created, but OVN does not correctly + check the members (LP #2055876). + [Test Case] The following SRU process was followed: - https://wiki.ubuntu.com/OpenStackUpdates + https://ubuntu.com/project/docs/SRU/reference/exception-OpenStack-Updates/ In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. + + Testing of the locally built candidate on Noble/Caracal includes: + - The regress-stack selection: 170 passed, 16 skipped, no failures; this includes eight passing Octavia tests. + - The full Octavia Tempest selection configured for OVN: 52 passed, 647 skipped and four class-setup failures. Those failures report a missing eth0 interface in backend guests and prevented the affected traffic tests from running. + + The OVN octavia provider has a dedicated suite in the octavia-tempest- + test to ensure minimal functionality. + + The testing will be repeated with the -proposed packages. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] The main regression risks are changes to existing health-monitor mappings during startup, member/port cleanup, and OVSDB connection handling. In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. [Discussion] - The Ovn Octavia provider is the second most used provider used in Canonical solutions, the most used provider being Amphora, not being affected by this package. - In charmed openstack, OVN is not the default provider. In sunbeam, the LoadBalancer feature (underlying octavia) is not enabled by default, and when it is, ovn is the default provider if Amphora is not enabled. - - The OVN octavia provider has a dedicated suite in the octavia-tempest- - test to ensure minimal functionality. - - The main motivation is broken IPv6 health monitoring with the OVN - provider: health monitors can be created, but OVN does not correctly - check the members (LP #2055876). We are proposing the Caracal maintenance release rather than the IPv6 fix alone because the release also includes a correction preventing its startup maintenance from clearing existing IPv4 health-monitor mappings (LP #2072754). Other user-facing fixes include orphaned health-monitor ports preventing subnet deletion and incorrect member subnet selection when creating fully populated load balancers. The linked commit inventory distinguishes these runtime fixes from changes confined to upstream CI and tests. - - Testing of the locally built candidate on Noble/Caracal includes: - - The regress-stack selection: 170 passed, 16 skipped, no failures; this includes eight passing Octavia tests. - - The full Octavia Tempest selection configured for OVN: 52 passed, 647 skipped and four class-setup failures. Those failures report a missing eth0 interface in backend guests and prevented the affected traffic tests from running. ** Changed in: ovn-octavia-provider (Ubuntu Noble) Status: Triaged => Fix Committed ** Tags added: verification-needed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2172343 Title: [SRU] caracal stable release ovn-octavia-provider To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2172343/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
