Currently, xcengine-created application packages fail to run on a ZOO + DRU deployment, for reasons that are unclear but seem to be connected with the stage-out process:
Unable to run the Service. The message returned back by the Service was the following: Exception during execution...
Traceback (most recent call last):
File "/opt/zooservices_user/anonymous/main/service.py", line 458, in main
exit_status = runner.execute()
File "/usr/local/lib/python3.8/dist-packages/zoo_calrissian_runner/__init__.py", line 542, in execute
self.handler.post_execution_hook(
File "/opt/zooservices_user/anonymous/main/service.py", line 296, in post_execution_hook
raise(e)
File "/opt/zooservices_user/anonymous/main/service.py", line 219, in post_execution_hook
logger.info(f"Read catalog => STAC Catalog URI: {output['StacCatalogUri']}")
KeyError: 'StacCatalogUri'
We have a known-good, working, fairly minimal example: the EOEPCA convert-url package. While xcengine output validates as conformant CWL, it would be a good first debugging step to get it as close as possible to the working example, both semantically and syntactically.
Currently, xcengine-created application packages fail to run on a ZOO + DRU deployment, for reasons that are unclear but seem to be connected with the stage-out process:
We have a known-good, working, fairly minimal example: the EOEPCA convert-url package. While xcengine output validates as conformant CWL, it would be a good first debugging step to get it as close as possible to the working example, both semantically and syntactically.