** Description changed: [impact] when the gateway reports an error, it is not passed along in the exception raised by python-etcd3gw [test case] Upstream added unit tests for this bug, which are included in the backport, so a successful package build (which runs the unit tests at build time) is enough to verify the fix. [regression potential] any regression would likely occur in handling errors sent from the gateway to python-etcd3gw, or in handling or later processing the exception(s) generated from the gateway error(s). [scope] three commits are needed for b/f/g, and one commit is needed in h. this is fixed upstream with commits: 483a37e28a59e29239dcae7eeabf6f24c1f0b440 19abd85b710682b326702e2290a30d084fb0af71 which are included in v2.5, and commit: 5a3157a122368c2314c7a961f61722e47355f981 which is included in v2.6 Debian currently has v2.5, and MR to add the last commit needed is: https://salsa.debian.org/openstack-team/python/python-etcd3gw/-/merge_requests/1 + + + Linking to related LP https://bugs.launchpad.net/ubuntu/+source/python-etcd3gw/+bug/1820083
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900617 Title: gateway error detail is not passed along in raised exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-etcd3gw/+bug/1900617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
