Placement client unconditionally swallowed many exceptions. I cannot
tell why that was ever considered a good idea. I can imagine some
users wanting to ignore some of those error conditions, but it should
be the responsibility of the user to decide. The client should not
unconditionally ignore all errors, but leave this choice for the user
of the client.
Particularly this placement client will be used by later patches for
minimum-bandwidth-allocation-placement-api where we do want to know
about some of these errors and retry placement operations when they
fail.
Reviewed: https:/ /review. openstack. org/619301 /git.openstack. org/cgit/ openstack/ neutron- lib/commit/ ?id=5227491b8ab fdabe8d6c3625f2 bb544cc7cfb7e8
Committed: https:/
Submitter: Zuul
Branch: master
commit 5227491b8abfdab e8d6c3625f2bb54 4cc7cfb7e8
Author: Bence Romsics <email address hidden>
Date: Wed Nov 21 17:07:55 2018 +0100
Placement client: do not swallow exceptions
Placement client unconditionally swallowed many exceptions. I cannot
tell why that was ever considered a good idea. I can imagine some
users wanting to ignore some of those error conditions, but it should
be the responsibility of the user to decide. The client should not
unconditionally ignore all errors, but leave this choice for the user
of the client.
Particularly this placement client will be used by later patches for bandwidth- allocation- placement- api where we do want to know
minimum-
about some of these errors and retry placement operations when they
fail.
Change-Id: Ia14ba8cb273166 fe3075328229f30 d0cebae0480
Related-Bug: #1578989