Core 0.4.4 absolute filepaths breaking multilayer publishes

Hey! We’re having artist reports of Lighting and Layout renders from blender / houdini-redshift failing to publish on the farm (deadline). The error given is: ayon_core.pipeline.publish.publish_plugins.KnownPublishError: Given file names contain full paths

Looking at the metadata.json submitted with a core 0.4.4 job, the filepath looks like this:

"files": [
              "Y:/projects/ayon_dev/101/sq001/sh010/work/Layout/renders/blender/ad_sh010_Layout_v013/sh010_renderLayoutMain_beauty.1001.exr",
              "Y:/projects/ayon_dev/101/sq001/sh010/work/Layout/renders/blender/ad_sh010_Layout_v013/sh010_renderLayoutMain_beauty.1002.exr",
              etc

And in the json from a core 0.4.3 job, the filepath looks like this:

"files": [
              "sh010_renderLayoutMain_beauty.1001.exr",
              "sh010_renderLayoutMain_beauty.1002.exr",
              etc

And here’s a bunch more details in case they’re helpful:

metadata JSON from ayon-core 0.4.3, up until filepath section

{
“comment”: “”,
“deadline_publish_job_id”: “66eb8136671c3571c5fd3777”,
“folderPath”: “/101/sq001/sh010”,
“fps”: 24.0,
“frameEnd”: 1100,
“frameStart”: 1001,
“instances”: [
{
“colorspace”: null,
“comment”: “”,
“deadline”: {
“auth”: null,
“require_authentication”: false,
“url”: “http://10.0.4.5:8081”,
“verify”: true
},
“extendFrames”: null,
“families”: [
“render”,
“review”
],
“folderPath”: “/101/sq001/sh010”,
“fps”: 24.0,
“frameEnd”: 1100,
“frameEndHandle”: 1100,
“frameStart”: 1001,
“frameStartHandle”: 1001,
“handleEnd”: 0,
“handleStart”: 0,
“inputVersions”: ,
“jobBatchName”: “”,
“multipartExr”: true,
“overrideExistingFrame”: null,
“pixelAspect”: 1,
“productGroup”: “renderLayoutMain”,
“productName”: “renderLayoutMain_beauty”,
“productType”: “render”,
“representations”: [
{
“colorspaceData”: {
“colorspace”: “”,
“config”: {
“path”: “”,
“template”: “”
},
“display”: “sRGB”,
“view”: “ACES 1.0 SDR-video”
},
“ext”: “exr”,
“files”: [
“sh010_renderLayoutMain_beauty.1001.exr”,
“sh010_renderLayoutMain_beauty.1002.exr”,

metadata JSON from ayon-core 0.4.4, up until filepath section

{
“comment”: “”,
“deadline_publish_job_id”: “66eb866a671c3571c5fd3783”,
“folderPath”: “/101/sq001/sh010”,
“fps”: 24.0,
“frameEnd”: 1100,
“frameStart”: 1001,
“instances”: [
{
“aov”: “beauty”,
“colorspace”: null,
“comment”: “”,
“deadline”: {
“auth”: null,
“require_authentication”: false,
“url”: “http://10.0.4.5:8081”,
“verify”: true
},
“extendFrames”: null,
“families”: [
“render”,
“review”
],
“folderPath”: “/101/sq001/sh010”,
“fps”: 24.0,
“frameEnd”: 1100,
“frameEndHandle”: 1100,
“frameStart”: 1001,
“frameStartHandle”: 1001,
“handleEnd”: 0,
“handleStart”: 0,
“inputVersions”: ,
“jobBatchName”: “”,
“multipartExr”: true,
“overrideExistingFrame”: null,
“pixelAspect”: 1,
“productGroup”: “renderLayoutMain”,
“productName”: “renderLayoutMain_beauty”,
“productType”: “render”,
“representations”: [
{
“colorspaceData”: {
“colorspace”: “”,
“config”: {
“path”: “”,
“template”: “”
},
“display”: “sRGB”,
“view”: “ACES 1.0 SDR-video”
},
“ext”: “exr”,
“files”: [
“Y:/projects/ayon_dev/101/sq001/sh010/work/Layout/renders/blender/ad_sh010_Layout_v013/sh010_renderLayoutMain_beauty.1001.exr”,
“Y:/projects/ayon_dev/101/sq001/sh010/work/Layout/renders/blender/ad_sh010_Layout_v013/sh010_renderLayoutMain_beauty.1002.exr”,

I’ve had a look through the changelogs and the only semi related change I can find is Use product name for render templates by antirotor · Pull Request #841 · ynput/ayon-core · GitHub, but using legacy or new behaviour has no impact

Is anyone aware of a potential cause, or failing that, able to reproduce this? It happens for every published render with AOVs (which for us is all of them) from blender and houdini-redshift, and presumably maya renders also. But not Nuke render publishes, curiously.

That’s interesting!
I was able to replicate your job file on my side.
I’m on the latest:

  • core: 0.4.5-dev.1
  • Deadline: 0.2.5-dev.1
  • Houdini: 03.13-dev.1
"files": [
    "//storage/work/ayon_projects/Robo/Assets/Character/roboangry/work/cfx/pyblish/renders/mantra_ropTest/mantra_ropTest.1001.beauty.exr",
    "//storage/work/ayon_projects/Robo/Assets/Character/roboangry/work/cfx/pyblish/renders/mantra_ropTest/mantra_ropTest.1002.beauty.exr",
    "//storage/work/ayon_projects/Robo/Assets/Character/roboangry/work/cfx/pyblish/renders/mantra_ropTest/mantra_ropTest.1003.beauty.exr"
],
.
.
"files": [
    "//storage/work/ayon_projects/Robo/Assets/Character/roboangry/work/cfx/pyblish/renders/mantra_ropTest/mantra_ropTest.1001.N.exr",
    "//storage/work/ayon_projects/Robo/Assets/Character/roboangry/work/cfx/pyblish/renders/mantra_ropTest/mantra_ropTest.1002.N.exr",
    "//storage/work/ayon_projects/Robo/Assets/Character/roboangry/work/cfx/pyblish/renders/mantra_ropTest/mantra_ropTest.1003.N.exr"
],

But, surprisingly my publish went fine!

Gonna close this, as it seems to not happen in Core 1.0.0 :slight_smile: