ovs-agent.log error after host ip changed
I had to rebuild a vm server and assign a new ip to it. The host name remained the same.
Seeing the following error in the ovs-agent.log file.
[2013-03-01 13:50:35 7587] ERROR (ha:34) Failed to get VM list on 192.168.0.40: (113, 'No route to host')
[2013-03-01 13:50:48 7615] ERROR (ha:34) Failed to get VM list on 192.168.0.40: (113, 'No route to host')
[2013-03-01 13:51:02 7639] ERROR (ha:34) Failed to get VM list on 192.168.0.40: (113, 'No route to host')
[2013-03-01 13:51:15 7658] ERROR (ha:34) Failed to get VM list on 192.168.0.40: (113, 'No route to host')
192.168.0.40 was the old address.
VM Server is 3.2.2 and VM Manager is at version 3.2.2
I think the ip address is hanging around in some config file.
Seeing the following error in the ovs-agent.log file.
[2013-03-01 13:50:35 7587] ERROR (ha:34) Failed to get VM list on 192.168.0.40: (113, 'No route to host')
[2013-03-01 13:50:48 7615] ERROR (ha:34) Failed to get VM list on 192.168.0.40: (113, 'No route to host')
[2013-03-01 13:51:02 7639] ERROR (ha:34) Failed to get VM list on 192.168.0.40: (113, 'No route to host')
[2013-03-01 13:51:15 7658] ERROR (ha:34) Failed to get VM list on 192.168.0.40: (113, 'No route to host')
192.168.0.40 was the old address.
VM Server is 3.2.2 and VM Manager is at version 3.2.2
I think the ip address is hanging around in some config file.
0