Comment 9 for bug 1322259

{"build_id": "2014-05-23_03-53-39", "mirantis": "yes", "build_number": "19", "ostf_sha": "5c479f04c35127576d35526650ec83b104f9a33d", "nailgun_sha": "bd09f89ef56176f64ad5decd4128933c96cb20f4", "production": "docker", "api": "1.0", "fuelmain_sha": "db2d153e62cb2b3034d33359d7e3db9d4742c811", "astute_sha": "9a0d86918724c1153b5f70bdae008dea8572fd3e", "release": "5.0", "fuellib_sha": "2ed4fbe1e04b85e83f1010ca23be7f5da34bd492"}
The same situation
Instance stack in building and deletig state. On compute nodes error about message timeouts
Also -P helps to see current conncetions with rabbit - thaks)
[root@node-4 log]# lsof -P -p 22985 | grep IPv4
nova-comp 22985 nova 20u IPv4 74323 0t0 TCP node-4:50256->node-2:5673 (ESTABLISHED)
nova-comp 22985 nova 21u IPv4 74329 0t0 TCP node-4:50258->node-2:5673 (ESTABLISHED)
nova-comp 22985 nova 22u IPv4 74596 0t0 TCP node-4:50261->node-2:5673 (ESTABLISHED)
nova-comp 22985 nova 23u IPv4 74600 0t0 TCP node-4:50263->node-2:5673 (ESTABLISHED)

So issue is reprodusable on 19 iso