Comment 31 for bug 1418921

I spoke with Ryan at length about this, I don't see us having an easy time preventing this either way. However we must not allow fuel to do anything with duplicate nodes, but at the same time we must record information about duplicate nodes.

I propose that we continue to allow duplicate ip on the node entity and when a duplicate is seen on update that we set both node entity's into error state and generate a message to the notifications. This way the operator will be able to see the two duplicate nodes, their information and can address the issue. This will additionally prevent the node's from participating in activities such as deployment that would cause it to fail because the wrong node is responding to mcollective.