Port binding failures after failover
Bug #1795299 reported by
Lucian Petrut
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compute-hyperv |
Fix Released
|
Undecided
|
Lucian Petrut | ||
os-win |
Invalid
|
Undecided
|
Unassigned |
Bug Description
In some cases, after instances are failed over, the destination host cannot find the instance vNICs or switch ports.
It looks like the ports are not ready yet by the time we get the failover event. Adding a retry to the method that connects ports to vswitches seems to avoid this issue.
Trace: http://
Later edit: This is caused by the fact that we're not waiting for "pending" cluster groups, in which case the VMs aren't registered in Hyper-V yet.
description: | updated |
Changed in os-win: | |
status: | New → Invalid |
Changed in compute-hyperv: | |
assignee: | nobody → Lucian Petrut (petrutlucian94) |
To post a comment you must log in.
Change abandoned by Lucian Petrut (<email address hidden>) on branch: master /review. openstack. org/606893
Review: https:/
Reason: Retrying here isn't the right thing to do. We have to wait for pending cluster groups.