When quark tries to delete an onmetal port that no longer
exists downstream, it should happily ignore the 404 and
move on.Instead, it complains and retries before eventually
giving up. This is due to not catching the correctexception
from the neutron client.This doesn't present as a 500 to
any clients, as the exception is caught and ignored,
but it gums up the logs and wastes time making requests
multiple times.
Reviewed: https:/ /review. openstack. org/527913 /git.openstack. org/cgit/ openstack/ quark/commit/ ?id=43c8359db51 d2367c6d40f9ff0 b5c868547276f5
Committed: https:/
Submitter: Zuul
Branch: master
commit 43c8359db51d236 7c6d40f9ff0b5c8 68547276f5
Author: inimitableharish <email address hidden>
Date: Tue Dec 12 00:04:31 2017 +0530
OnMetal Driver Can't Handle 404s on Port Delete
When quark tries to delete an onmetal port that no longer
exists downstream, it should happily ignore the 404 and
move on.Instead, it complains and retries before eventually
giving up. This is due to not catching the correctexception
from the neutron client.This doesn't present as a 500 to
any clients, as the exception is caught and ignored,
but it gums up the logs and wastes time making requests
multiple times.
Implements: Exception handling 33ceb68427d47ed 658bf27f4a8
Closes-Bug: #1738277
Change-Id: I4ccd9be891e6c5