The patch for jammy looks reasonable, and certain a great deal more minimal than the upstream commit, thank you! The test plan in the SRU template could probably do with a bit more detail, however. Specifically:
1. Ideally a test plan should reproduce the buggy behaviour (from the existing version), then upgrade to the proposed version, and demonstrate the buggy behaviour no longer occurs (to demonstrate that the error definitely occurs on the target release, and is fixed by the proposed version, and not something else). That said, I've no idea how feasible it is to upgrade a cluster of this sort. 2. The test plan is (I'm guessing) fine for someone well versed in openstack / octavia, but I'm not and I wouldn't have the first clue how to set it all up. Acknowledging this is a non-trivial area, could the test plan be written in such a way that one could follow it by rote? I may be asking too much here; if an idealised test plan requires pages upon pages of content, then there's no point, but I do consider it important to try and enable as many users as possible to participate in the testing. Still, the patch as it stands is good: sponsoring for jammy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2117280 Title: [SRU] Asymmetric routing issue on amphorae in ACTIVE_STANDBY topology To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2117280/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
