OnMetal Driver Does Not Handle 404s on Port Delete Gracefully

Bug #1738277 reported by MultipleCrashes
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
quark
Undecided
Unassigned

Bug Description

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 correct exception 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.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to quark (master)

Reviewed: https://review.openstack.org/527913
Committed: https://git.openstack.org/cgit/openstack/quark/commit/?id=43c8359db51d2367c6d40f9ff0b5c868547276f5
Submitter: Zuul
Branch: master

commit 43c8359db51d2367c6d40f9ff0b5c868547276f5
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
    Closes-Bug: #1738277
    Change-Id: I4ccd9be891e6c533ceb68427d47ed658bf27f4a8

Changed in neutron-quark:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers