Revision history [back]

Hi,

This was fixed in Queens, Mitaka is no longer supported. We were considering configuring neutron-ovs-cleanup as a Nova and Neutron agent dependency, running once per boot but we found some Windows ovs limitations. When neutron-ovs-cleanup runs, it will remove all the vm ovs ports, which will then be recreated when Nova starts. The issue is that some recreated ovs ports will become invalid. The next Windows OVS release will probably provide a fix.

For now, you could either: * remove all ports (e.g. by recreating the bridge) and restart Nova so that it will add them back. The downside is that some ports may become invalid due to the above mentioned bug and if you have running instances, those will become temporarily unavailable, which is the reason why neutron-ovs-cleanup is usually run once at startup. It's probably easier if there aren't any running instances (i.e. those have already been moved to a different host). * write a script that selectively removes stale ports. Make sure you don't remove ports that are currently in-use. You can get a list of vm hyper-v switch ports by using get-vmswitchport.

Regards, Lucian

Hi,

This was fixed in Queens, Mitaka is no longer supported. We were considering configuring neutron-ovs-cleanup as a Nova and Neutron agent dependency, running once per boot but we found some Windows ovs limitations. When neutron-ovs-cleanup runs, it will remove all the vm ovs ports, which will then be recreated when Nova starts. The issue is that some recreated ovs ports will become invalid. The next Windows OVS release will probably provide a fix.

For now, you could either: * either:

• remove all ports (e.g. by recreating the bridge) and restart Nova so that it will add them back. The downside is that some ports may become invalid due to the above mentioned bug and if you have running instances, those will become temporarily unavailable, which is the reason why neutron-ovs-cleanup is usually run once at startup. It's probably easier if there aren't any running instances (i.e. those have already been moved to a different host). * host).

• write a script that selectively removes stale ports. Make sure you don't remove ports that are currently in-use. You can get a list of vm hyper-v switch ports by using get-vmswitchport.

  Regards,

Regards,

Lucian