New Question

Revision history [back]

click to hide/show revision 1
initial version

OVS set_manager failed

Hi, Trying to add Hyper-V with OVS as OpenStack compute Node. I have a Devstack machine as the control node, with OpenDaylight as the network controller. I followed the OVS for Hyper-V installation instructions but I never get to the state where the OVS shows is_connected to the Manager ( OpenDaylight in this case).

OVS set_manager failed

Hi, Trying to add Hyper-V with OVS as OpenStack compute Node. I have a Devstack machine as the control node, with OpenDaylight as the network controller. I followed the OVS for Hyper-V installation instructions but I never get to the state where the OVS shows is_connected to the Manager ( OpenDaylight in this case).

I get the following errors all over the log: 2016-12-13T18:02:53.259Z|200207|netdev_windows|ERR|Call to GetAdaptersAddresses failed with error: The file name is too long.

2016-12-13T18:02:53.259Z|200208|inband|WARN|br-port1: cannot find route for controller (10.0.43.69): No such device or address 2016-12-13T18:02:53.261Z|200209|netdevwindows|ERR|Call to GetAdaptersAddresses failed with error: The file name is too long.

2016-12-13T18:02:53.261Z|200210|in_band|WARN|br-int: cannot find route for controller (10.0.43.69): No such device or address co

OVS set_manager failed

Hi, Trying to add Hyper-V with OVS as OpenStack compute Node. I have a Devstack machine as the control node, with OpenDaylight as the network controller. I followed the OVS for Hyper-V installation instructions but I never get to the state where the OVS shows is_connected to the Manager ( OpenDaylight in this case).

I get the following errors all over the log: log:

2016-12-13T18:02:53.259Z|200207|netdev_windows|ERR|Call to GetAdaptersAddresses failed with error: The file name is too long.

2016-12-13T18:02:53.259Z|200208|inband|WARN|br-port1: cannot find route for controller (10.0.43.69): No such device or address 2016-12-13T18:02:53.261Z|200209|netdevwindows|ERR|Call to GetAdaptersAddresses failed with error: The file name is too long.

2016-12-13T18:02:53.261Z|200210|in_band|WARN|br-int: cannot find route for controller (10.0.43.69): No such device or address co