ID 486833 - Connecting a node downstream of a deleted node results in a disembodied input port

Problem summary
Using the Python API, deleting a node and then connecting its output port to another node's input port causes said input port to become disembodied from its node.

This also does not produce a warning or error that the user is attempting to connect to a deleted node/port.

Customer reported version
Katana N/A

Customer reported platform
Windows 10

Steps to reproduce

1) Run the following script from the Python tab:


rootNode = NodegraphAPI.GetRootNode()cameraCreateNode = NodegraphAPI.CreateNode('CameraCreate', rootNode)cameraCreateNode.delete() transform3dNode = NodegraphAPI.CreateNode('Transform3D', rootNode)cameraCreateNodePosition = NodegraphAPI.GetNodePosition(cameraCreateNode)NodegraphAPI.SetNodePosition(transform3dNode,                             (cameraCreateNodePosition[0] + 75,                              cameraCreateNodePosition[1] - 75))cameraCreateNode.getOutputPort('out').connect(transform3dNode.getInputPort('in'))

Expected behaviour
The downstream node has its input port intact

Actual behaviour
The node's input port become disembodied and is located where the output port was for the connected and deleted node

Workaround
Undo (Ctrl+Z) the connection

Reproduced by support
This bug has been reproduced in:
Katana 4.0v5 - Windows 10
Katana 4.0v1 - Windows 10
Katana 3.6v5 - Windows 10
Katana 3.6v1 - Windows 10
Katana 3.5v5 - Windows 10
Katana 3.5v1 - Windows 10
Katana 3.2v6 - Windows 10
Katana 3.2v1 - Windows 10
Katana 3.1v7 - Windows 10
Katana 3.1v1 - Windows 10
Katana 3.0v9 - Windows 10
Katana 3.0v1 - Windows 10
Katana 2.6v4 - Windows 10
Katana 2.6v1 - Windows 10
Katana 2.5v2 - Windows 10
Katana 2.5v1 - Windows 10

Earliest version tested
Guidance: List earliest version you've tested and the reason you stopped there. Reasons can be:
2.5v2 - This issue appears to be in all versions of the product

We're sorry to hear that

Please tell us why