OVS ports can become invalid after the instances are failed over.
If an instance lands back on the initial host and the ports are
not cleaned up, it will be left with those stale ports.
This change adds a config option, allowing those ports to be recreated.
It will be enabled by default. Deployers may consider disabling it
if the remaining ports are cleaned up when rebooting nodes or if the
network backend is not affected by this issue.
Closes-Bug: #1841778
Change-Id: I58aba53b7bc0a5e8954cf31adac6e7e106944b7e
(cherry picked from commit 7dd16950d3dea87c9853c62fea26437de0dfd814)
Reviewed: https:/ /review. opendev. org/680350 /git.openstack. org/cgit/ openstack/ compute- hyperv/ commit/ ?id=9c07fe4b59e c7a8150a88411a8 d20810dfc5bdb0
Committed: https:/
Submitter: Zuul
Branch: stable/stein
commit 9c07fe4b59ec7a8 150a88411a8d208 10dfc5bdb0
Author: Lucian Petrut <email address hidden>
Date: Wed Aug 28 13:07:46 2019 +0300
Recreate ports for failed over instances
OVS ports can become invalid after the instances are failed over.
If an instance lands back on the initial host and the ports are
not cleaned up, it will be left with those stale ports.
This change adds a config option, allowing those ports to be recreated.
It will be enabled by default. Deployers may consider disabling it
if the remaining ports are cleaned up when rebooting nodes or if the
network backend is not affected by this issue.
Closes-Bug: #1841778
Change-Id: I58aba53b7bc0a5 e8954cf31adac6e 7e106944b7e c9853c62fea2643 7de0dfd814)
(cherry picked from commit 7dd16950d3dea87