question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"Copying directories not supported" on AWS

See original GitHub issue

Ran a workflow using V40 Cromwell on AWSBATCH that had as outputs (one outputfile.vcf for each of the shards in the workflow):

output {
    Array[File] outputs = task.outputvcf
}

I used the following workflow options:

{
    "workflow_failure_mode": "NoNewCalls",
    "default_runtime_attributes": {
        "maxRetries": 1
    },
    "final_workflow_outputs_dir": "s3://bucket/Cromwell/results",
    "use_relative_output_paths": "false",
    "final_workflow_log_dir": "s3://bucket/Cromwell/workflowLogs",
    "final_call_logs_dir": "s3://bucket/Cromwell/workflowLogs"
}

All calls of the workflow completed successfully but the workflow itself failed.

Error Message I got: "copying directories is not yet supported: s3://s3.amazonaws.com/bucket/Cromwell/results/workflowName/1ec38d0b-afc4-4cd5-90f1-f015395d6e36/call-task/shard-0/outputfile.vcf"

Oddly enough, the correct prefixes for the output files were created in the correct S3 bucket, they just don’t have an object there, and via the CLI they appear as directories. ???

For the logs, a prefix was made that is empty, and the log file was written successfully to one level higher than the prefix it is supposed to be in. So instead of:

s3://bucket/Cromwell/workflowLogs/workflowName/<workflowid>.log

there is:

s3://bucket/Cromwell/workflowLogs/workflowName/ (empty prefix)
s3://bucket/Cromwell/workflowLogs/<workflowid>.log (successfully written file)

Thoughts?

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:19 (14 by maintainers)

github_iconTop GitHub Comments

2reactions
svitkovsergeycommented, Aug 20, 2019

@wleepang @geoffjentry Any updates about PR #5110 ? 😄

2reactions
robthompsonwebcommented, Jul 31, 2019

@TimurKustov correct (apart from the trailing slash on output.txt… not sure if that is a typo but that will break it on s3. it would copy output.txt to s3://3-bucket/WGS_BAM_to_GVCF/workflow/call-MergeGVCFs/output.txt. ie aws s3 cp localpath/WGS_BAM_to_GVCF/workflow/call-MergeGVCFs/output.txt s3://3-bucket/WGS_BAM_to_GVCF/workflow/call-MergeGVCFs/output.txt

I would expect it to copy every file from the output into the path specified by final_workflow_outputs_dir. if use_relative_output_paths is false it would be: s3://3-bucket/output.txt

Read more comments on GitHub >

github_iconTop Results From Across the Web

Troubleshoot issues copying an object between S3 buckets
I'm trying to copy an object from one Amazon Simple Storage Service (Amazon S3) bucket to another, but it's not working.
Read more >
Links and directories copied by AWS DataSync
AWS DataSync handles copied hard links, symbolic links, and directories differently depending on the storage locations involved in your transfer. Hard links.
Read more >
Transferring files using a client - AWS Documentation
Set up and use clients with AWS Transfer Family to perform file operations.
Read more >
Manage directories for WorkSpaces - AWS Documentation
Learn how to manage directories for your WorkSpaces. ... Shared directories are not currently supported for use with Amazon WorkSpaces.
Read more >
Troubleshoot AWS Glue error "Temporary directory not ...
The most common reason for this error is the missing temporary S3 bucket that's used by the AWS Glue job as a staging...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found