ID 587009 - OCIODisplay node fails to load colorspaces correctly when different display groups contain different views

Problem summary
OCIODisplay node fails to load colorspaces correctly when different display groups contain different views
 
This can happen with both OCIO v1 and OCIO v2, the below reproduction steps are for OCIO v2, but the attached OCIO config (ocioDisplayBug.zip) works in OCIO v1
 
Customer reported version
nuke.15.0v4
 
Customer reported platform
windows10
 
Steps to reproduce
 
1) Make a copy of Nuke's Nuke15.1v3\plugins\OCIOConfigs\configs\fn-nuke_cg-config-v1.0.0_aces-v1.3_ocio-v2.1.ocio config file on your desktop

2) Open the new config in a text editor

3) In line 46, change the name from Raw to Test, and save the config:

 
4) Launch Nuke
 
5) In Edit>Project Settings...>Color tab, set color management to OCIO, OCIO config to custom, and set the custom OCIO config path to the edited config
 
6) Create an OCIODisplay node, set the display device to P3-D65 - Display, and the view transform to Raw
 
7) Copy and paste the node, or Save>Close>Open the Nuke script, an error will appear, and the view transform will change from Raw to ACES 1.0 - SDR Cinema
 

On load error ^

Copy/Paste error ^
 
Expected behaviour
For the Raw colorspace to still work
 
Actual behaviour
The OCIODispaly node errors when either being pasted or loaded in a Nuke script
 
Workaround
Unknown. 
 
Reproduced by support
This bug has been reproduced in:
Nuke 15.1v3 - Windows 10, macOS Sonoma
Nuke 12.0v1 - Windows 10, macOS Sonoma
 
Earliest version tested
Nuke 12.0v1 - This issue appears to be in all tested versions of the product