-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[AN-440] Add symlink to /cromwell_root in GCP Batch #7722
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice find 👍
Clearly an improvement over the current situation, and a compact change that is easy to test.
Strong candidate for a changelog entry IMO.
CHANGELOG.md
Outdated
@@ -9,6 +9,8 @@ | |||
* Add 30 GB default VM boot disk size to user-requested boot disk size; this ensures the VM has room for large user command Docker images. | |||
* Fix a bug that caused Cromwell to treat immediate preemptions as failures. | |||
* Automatically retry tasks that fail with transient Batch errors before the VM has started running (that is, before the task has cost the user money). These retries do not count against `maxRetries`. | |||
* Symlink to `/cromwell_root` - In LifeSciences, cromwell_root is located at `/cromwell_root`, but in the Batch backend it has moved to `/mnt/disk/cromwell_root`. To ensure WDLs that rely on the original |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nitpick - I would use "the Cromwell root directory that user scripts are run from" rather than "cromwell_root"
Description
Jira ticket: https://broadworkbench.atlassian.net/browse/AN-440
In LifeSciences, the
cromwell_root
is located at/cromwell_root
, but in the Batch backend it has moved to/mnt/disk/cromwell_root
. WDLs that rely on the original path break when run on the Batch. To maintain backward and forward compatibility we create a symlink between/mnt/disk/cromwell_root
and/cromwell_root
.Note: the creation of symlink does fail when run on images that don't allow root access, but in these cases the script.sh does continue to run remaining commands.
Release Notes Confirmation
CHANGELOG.md
CHANGELOG.md
in this PRCHANGELOG.md
because it doesn't impact community usersTerra Release Notes