Comment 15 for bug 1333143

Ok, as far as I can see this issue is a dup indeed and it is not l3agent location related, byt vips location and rmq clustering instead.
Here is full log could be found for steps was done to ensure it is a dup http://pastebin.com/qqCVj7i1
Some notes:
1) After the failover of vips, SYN-SYNT sessions keep going on for ever (see step 3). So, looks like it is not an issue?..
2) Looks like the issue was resolved by rmq service restart *which have caused the compute service to reestablish its amqp sessions* and is a dup of 1323277, indeed
3) OSTF tests for RabbitMQ HA should verify if rmq services are gracefully restartable as well (restarting it one by one will allow to detect some hang glithes)