ID 383997 - Rename node operates on pruned locations

Follow

Problem summary

Locations deleted by Prune nodes can wrongly be resurrected when targeted by Rename nodes.

Customer reported version
Katana 3.0v7

Customer reported platform
CentOS 7

Steps to reproduce:

  1. Use a LocationCreate node to create two locations underneath /root/world/geo named ASSET and ASSETCOPY.
  2. Use a Prune node to delete /root/world/geo/ASSETCOPY.
  3. Use a Rename node to rename /root/world/geo/ASSET to /root/world/geo/ASSETCOPY.

Expected result:

The scene graph consists of a single location: /root/world/geo/ASSETCOPY.

Actual result:

The scene graph consists of a single location: /root/world/geo/ASSETCOPYCOPY.

Workaround:
No known workaround.

Tested versions/platforms:

  • Katana 3.1v3 - Windows 10 -- Affected
  • Katana 3.1v1 - Windows 10 -- Affected
  • Katana 3.0v8 - Windows 10 -- Affected
  • Katana 3.0v1 - Windows 10 -- Affected
  • Katana 2.5v1 - Linux CentOS RHEL 6.3 -- Affected
  • Katana 2.0v1 - Linux CentOS RHEL 6.3 -- Affected -- REGRESSION
  • Katana 1.6v1 - Linux CentOS RHEL 6.3 -- Unaffected
  • Katana 1.5v1 - Linux CentOS RHEL 6.3 -- Unaffected
  • Katana 1.0v1 - Linux CentOS RHEL 6.3 -- Unaffected

    We're sorry to hear that

    Please tell us why