** 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 + * 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). + + * This patchset introduces 'import mock' in a test unit which requires + python3-mock as a Build-Depends. + + For now, it is indirectly covered by python3-oslotest as follows: + + 18 Build-Depends-Indep: + 19 python-coverage, + 20 python-futurist, + 21 python-hacking, + 22 python-nose, + 23 python-oslosphinx, + 24 python-oslotest, + 25 python-pytest, + 26 python-requests, + 27 python-six, + 28 python-testscenarios, + 29 python-testtools, + 30 python-urllib3, + 31 python3-futurist, + 32 python3-nose, + => 33 python3-oslotest, + + ~# apt-cache depends python3-oslotest + python3-oslotest + Depends: python3-fixtures + => Depends: python3-mock + + Ideally, it would be best to have an implicit instruction for it, but + since in Stable release, adding new build dependencies is not the + preference and that python3-oslotest will unlikely be removed from the + list. It shouldn't have any effect in the future. Worse case, python- + etcd3gw will stop building, and we will have to implicitly instruct + d/control to have python3-mock as Build-Depends. [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 + Linking to related LP https://bugs.launchpad.net/ubuntu/+source/python- + etcd3gw/+bug/1820083
** 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). * This patchset introduces 'import mock' in a test unit which requires python3-mock as a Build-Depends. For now, it is indirectly covered by python3-oslotest as follows: - 18 Build-Depends-Indep: - 19 python-coverage, - 20 python-futurist, - 21 python-hacking, - 22 python-nose, - 23 python-oslosphinx, - 24 python-oslotest, - 25 python-pytest, - 26 python-requests, - 27 python-six, - 28 python-testscenarios, - 29 python-testtools, - 30 python-urllib3, - 31 python3-futurist, - 32 python3-nose, + 18 Build-Depends-Indep: + 19 python-coverage, + 20 python-futurist, + 21 python-hacking, + 22 python-nose, + 23 python-oslosphinx, + 24 python-oslotest, + 25 python-pytest, + 26 python-requests, + 27 python-six, + 28 python-testscenarios, + 29 python-testtools, + 30 python-urllib3, + 31 python3-futurist, + 32 python3-nose, => 33 python3-oslotest, ~# apt-cache depends python3-oslotest python3-oslotest - Depends: python3-fixtures + Depends: python3-fixtures => Depends: python3-mock Ideally, it would be best to have an implicit instruction for it, but since in Stable release, adding new build dependencies is not the preference and that python3-oslotest will unlikely be removed from the list. It shouldn't have any effect in the future. Worse case, python- etcd3gw will stop building, and we will have to implicitly instruct d/control to have python3-mock as Build-Depends. [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 ** 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). * This patchset introduces 'import mock' in a test unit which requires python3-mock as a Build-Depends. For now, it is indirectly covered by python3-oslotest as follows: + d/control: 18 Build-Depends-Indep: 19 python-coverage, 20 python-futurist, 21 python-hacking, 22 python-nose, 23 python-oslosphinx, 24 python-oslotest, 25 python-pytest, 26 python-requests, 27 python-six, 28 python-testscenarios, 29 python-testtools, 30 python-urllib3, 31 python3-futurist, 32 python3-nose, => 33 python3-oslotest, ~# apt-cache depends python3-oslotest python3-oslotest Depends: python3-fixtures => Depends: python3-mock Ideally, it would be best to have an implicit instruction for it, but since in Stable release, adding new build dependencies is not the preference and that python3-oslotest will unlikely be removed from the list. It shouldn't have any effect in the future. Worse case, python- etcd3gw will stop building, and we will have to implicitly instruct d/control to have python3-mock as Build-Depends. [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
