Activity log for bug #1795299

Date Who What changed Old value New value Message
2018-10-01 06:38:27 Lucian Petrut bug added bug
2018-10-18 09:36:35 Lucian Petrut 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://paste.openstack.org/raw/730451/ 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://paste.openstack.org/raw/730451/ 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.
2018-10-18 09:40:30 Lucian Petrut os-win: status New Invalid
2018-10-18 09:40:49 Lucian Petrut bug task added compute-hyperv
2018-10-18 09:40:59 Lucian Petrut compute-hyperv: assignee Lucian Petrut (petrutlucian94)
2018-10-18 09:48:08 OpenStack Infra compute-hyperv: status New In Progress
2018-11-19 15:32:33 OpenStack Infra compute-hyperv: status In Progress Fix Released