summaryrefslogtreecommitdiff
path: root/releasenotes/notes/ignore-port-not-found-when-unbinding-94fb63988e98cb21.yaml
diff options
context:
space:
mode:
Diffstat (limited to 'releasenotes/notes/ignore-port-not-found-when-unbinding-94fb63988e98cb21.yaml')
-rw-r--r--releasenotes/notes/ignore-port-not-found-when-unbinding-94fb63988e98cb21.yaml8
1 files changed, 8 insertions, 0 deletions
diff --git a/releasenotes/notes/ignore-port-not-found-when-unbinding-94fb63988e98cb21.yaml b/releasenotes/notes/ignore-port-not-found-when-unbinding-94fb63988e98cb21.yaml
new file mode 100644
index 000000000..30e63af7b
--- /dev/null
+++ b/releasenotes/notes/ignore-port-not-found-when-unbinding-94fb63988e98cb21.yaml
@@ -0,0 +1,8 @@
+---
+fixes:
+ - Fixes a failure when deploying a node. This happened when a port or port
+ group's internal_info['tenant_vif_port_id'] still existed after the
+ corresponding neutron port was removed and prior to deletion of the
+ instance, causing future deployments of the bare metal node to fail. The
+ situation is now logged and does not block future deployments. See
+ https://bugs.launchpad.net/ironic/+bug/1685592 for details.