I upgraded from 4.0 to 4.3.0 some time ago. I didn't restart anything and it was all working great. However, I had to perform some maintenance and had to restart everything. Now, I'm seeing packet loss on all virtuals, even ones on the same host.
sudo ping -c 500 -f 172.20.1.1 PING 172.20.1.1 (172.20.1.1) 56(84) bytes of data. ........................................ --- 172.20.1.1 ping statistics --- 500 packets transmitted, 460 received, 8% packet loss, time 864ms rtt min/avg/max/mdev = 0.069/0.218/1.290/0.139 ms, ipg/ewma 1.731/0.328 ms No interface errors reported anywhere. The host itself isn't under load at all. Doesn't matter if the instance uses e1000 or virtio for the drivers. The only thing that I'm aware of that changed was that I had to reboot all the physical servers. Could be related, but I was hit with the https://issues.apache.org/jira/browse/CLOUDSTACK-6464 bug. I did follow with Marcus' suggestion: *"This is a shot in the dark, but there have been some issues around upgrades that involve the cloud.vlan table expected contents changing. New 4.3 installs using vlan isolation don't seem to reproduce the issue. I'll see if I can reproduce anything like this with basic and/or non-vlan isolated upgrades/installs. Can anyone experiencing an issue look at their database via something like "select * from cloud.vlan" and look at the vlan_id. If you see something like "untagged" instead of "vlan://untagged", please try changing it and see if that helps."* -- Nick *'What is a human being, then?' 'A seed' 'A... seed?' 'An acorn that is unafraid to destroy itself in growing into a tree.' -David Zindell, A Requiem for Homo Sapiens*
