Symptoms

When you manually add a node with an identical address or name as a node that already exists, you receive a confusing error: 01020036:3: The requested Node (/Common/mynode) was not found.

Impact

The error actually means that the node already exists, so is confusing.

Conditions

This occurs when adding a node to the proxy where either the node name or the node address already exists. For example, if a proxy already has a node with this name and address: mynode/10.1.20.11 Later if you add a node with the same name but different address: mynode/10.1.20.12 The error will be generated

Workaround

None

Fix Information

In the 1.0.1 release the error will be similar to the following: ERROR: 409 Invalid Node, mynode or the IP address 10.1.20.11 already exists. When using the REST API, the same error will be a 403 code similar to the following: {"errors":{"status":403,"title":"Forbidden","detail":"{\"message\":\"SC: mynode was previously added in auto Mode, cannot add this node in Auto Discovery mode\"}","meta":{"id":"257ea791-f326-47dd-9f83-7cf4f5c9003d","action":"post","type":"node","statusCode":403}}}

Behavior Change