Retry plugging ports when clustered instances start
After a while, the Failover Cluster will stop retrying when attempting
to bring back up failed instances. For example, if the CSV is down
more than a few minutes, the cluster groups will be set in "Failed"
state, while the VMs won't be registered on any Hyper-V node.
The issue is that we're only handling cluster group owner changes
(moved instances). If the admin fixes the issue and manually brings
the cluster groups back up, the instances are recreated but we aren't
handling this, so ports won't get reconnected.
This change will double check the ports when clustered instances
start.
Reviewed: https:/ /review. openstack. org/611638 /git.openstack. org/cgit/ openstack/ compute- hyperv/ commit/ ?id=d3360948f6d de1639200829a94 6a434f83a91f6e
Committed: https:/
Submitter: Zuul
Branch: master
commit d3360948f6dde16 39200829a946a43 4f83a91f6e
Author: Lucian Petrut <email address hidden>
Date: Thu Oct 18 17:49:22 2018 +0300
Retry plugging ports when clustered instances start
After a while, the Failover Cluster will stop retrying when attempting
to bring back up failed instances. For example, if the CSV is down
more than a few minutes, the cluster groups will be set in "Failed"
state, while the VMs won't be registered on any Hyper-V node.
The issue is that we're only handling cluster group owner changes
(moved instances). If the admin fixes the issue and manually brings
the cluster groups back up, the instances are recreated but we aren't
handling this, so ports won't get reconnected.
This change will double check the ports when clustered instances
start.
Closes-Bug: #1799163
Change-Id: I5caa65d7b7922d c9632b18acedaf1 aedeec3fcc3