Gracefully handle fetch network fail in qos extend port
When the qos plugin is handling a port resource request through it's
port resource request extension, sometimes the network a port is
attached to is looked up and returns None. It may happen like that
if network will be deleted in concurrent API request.
Reviewed: https:/ /review. openstack. org/628492 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=65a2f86aafa 7637ec07aa0a313 ea0fae39758608
Committed: https:/
Submitter: Zuul
Branch: master
commit 65a2f86aafa7637 ec07aa0a313ea0f ae39758608
Author: Nate Johnston <email address hidden>
Date: Fri Jan 4 10:28:01 2019 -0500
Gracefully handle fetch network fail in qos extend port
When the qos plugin is handling a port resource request through it's
port resource request extension, sometimes the network a port is
attached to is looked up and returns None. It may happen like that
if network will be deleted in concurrent API request.
Change-Id: Ide4acdf4c37371 3968f9d43274fb0 c7550283c11
Closes-Bug: #1810504