nova-dhcbridge doesn't close the rabbitmq connection properly when the process dies. This results in lots of annoying error messages in the rabbit logfile:
=WARNING REPORT==== 20-Mar-2011::06:26:57 ===
exception on TCP connection <0.17629.6202> from 10.24.4.2:57025
connection_closed_abruptly
=INFO REPORT==== 20-Mar-2011::06:26:57 ===
closing TCP connection <0.17629.6202> from 10.24.4.2:57025
Since real world deploys of nova will have many such processes running, this could become an issue for large deploys (it is already annoying in Nebula).
nova-dhcbridge doesn't close the rabbitmq connection properly when the process dies. This results in lots of annoying error messages in the rabbit logfile:
=WARNING REPORT==== 20-Mar- 2011::06: 26:57 === closed_ abruptly
exception on TCP connection <0.17629.6202> from 10.24.4.2:57025
connection_
=INFO REPORT==== 20-Mar- 2011::06: 26:57 ===
closing TCP connection <0.17629.6202> from 10.24.4.2:57025
Since real world deploys of nova will have many such processes running, this could become an issue for large deploys (it is already annoying in Nebula).