Comment 4 for bug 1826472

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to nova (master)

Reviewed: https://review.opendev.org/678301
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9cbedea0bf5535fc45d78c80e6d7499512e4c5f5
Submitter: Zuul
Branch: master

commit 9cbedea0bf5535fc45d78c80e6d7499512e4c5f5
Author: Matt Riedemann <email address hidden>
Date: Fri Aug 23 16:03:41 2019 -0400

    Trap and log errors from _update_inst_info_cache_for_disassociated_fip

    When associating a floating IP to instance A and the floating IP is
    already associated to instance B, the associate_floating_ip method
    updates the floating IP to be associated with instance A then tries
    to update the network info cache for instance B. That network info
    cache update is best effort and could fail in different ways, e.g.
    the original associated port or instance could be gone. Failing to
    refresh the cache for instance B should not affect the association
    operation for instance A, so this change traps any errors during the
    refresh and just logs them as a warning.

    Change-Id: Ib5a44e4fd2ec2bf43b761db29403810d8b730429
    Related-Bug: #1826472