ID 480721 - Render resolution table is not recreated for every render

Problem summary
During a render, renderboot is provided with an XML with the table:

Running command: /opt/Foundry/Katana4.0v4/bin/renderboot -geolib3OpTree /tmp/katana_tmpdir_56246/geolib3000001.optree -renderer dl -renderMethodType previewRender -renderMethodName previewRender -renderTime 1 -t 1 -useID True -sequenceID 1 -katanaRoot /opt/Foundry/Katana4.0v4 -tempDir /tmp/katana_tmpdir_56246 -pluginDsoPath /usr/local/3delight-2.3.7/Linux-x86_64/3DelightForKatana/Libs -assetPlugin File -fileSequencePlugin FileSeq -geolib3RuntimeMode sync -resolutionsTable /tmp/katana_tmpdir_56246/Resolutions/FoundryResolutions.xml -verbose 1 -threads 8 -host FWP55306:15900 -interactivePrecision float -geolibRuntime Geolib3-MT -opTreeOptimizations True -sceneTraversalVerboseLogging False -cacheEviction True -cacheSoftLimit 1048576 -cacheCollectionFrequency 10000

 However, the table is not recreated for every render; Katana fails to correctly write the XML that renderboot is fed off.

Customer reported version
katana.4.0v2

Customer reported platform

Steps to reproduce

1. Launch Katana.
2. Load the Hello World example project.
3. Start a Preview Render from the Merge mode.
4. Run the following snippet in a Python tab to add a custom resolution to the ResolutionTable:

   
   rt = ResolutionTable.GetResolutionTable()entry = rt.createResolution(222,                            111,                            'my_custom_resolution',                            groupName='Miscellaneous',                            pixelAspect=1.0)rt.addEntries([entry])

5. Set the edit flag on the RenderSettings node.
6. Set its resolution parameter to my_custom_resolution.
7. Set its adjustScreenWindow parameter to Adjust width to match resolution.
8. Start another Preview Render from the RenderSettings node.

Expected behavior
A sphere should be seen:

​



Actual behavior
The render won't be adjusted to the window, resulting in an oval instead of a sphere:

​
Workaround
As a workaround, users could run the following snippet in a Python tab to delete the Resolutions/ directory, therefore ensuring that the XML file would be regenerated when the next render is started:

shutil.rmtree(    os.path.dirname(        RenderManager.ResolutionTableUtils.GetTempResolutionTablePath()))

Reproduced by support
This bug has been reproduced in:
Katana 4.0v4 - CentOS 7
Katana 4.0v1 - CentOS 7

Unable to reproduce bug in:
Katana 3.6v4 - CentOS 7
Katana 3.5v4 - CentOS 7


Earliest version tested
Katana 3.6v4 - This issue doesn't appear in this version and has regressed