Fusion v2.6.9
Fusion v2.6.9 fixes three ways a healthy task could be lost in NFS service mode or on EC2: failed output uploads reported as success, a short EC2 instance metadata outage blocking S3 access, and remote I/O errors on a task relaunched from a clean start.
How to pin this version
fusion {
enabled = true
containerConfigUrl = 'https://fusionfs.seqera.io/releases/v2.6.9-amd64.json'
}
info
For ARM64 CPU architecture, use containerConfigUrl = 'https://fusionfs.seqera.io/releases/v2.6.9-arm64.json'.
Bug fixes
NFS service mode
- Fixed a task exiting with
0when the final upload of its work directory failed. Fusion now retries the upload for about five minutes, then exits with174. See Fusion exit codes. - Fixed a
Remote I/O errorwhen a task relaunched from a clean start recreated a path the clean had removed.
AWS
- Fixed a short gap in the EC2 instance metadata service leaving Fusion with anonymous S3 access for the rest of the task. If the work directory is still unreachable, Fusion exits with
173, which Intelligent Compute relocates to another host.
Dependencies
- Updated dependencies and CI.
Upgrade notes
- Drop-in replacement for v2.6.8. No configuration changes required.
- In NFS service mode, a task whose command succeeded but whose final work directory upload failed now exits with
174instead of0. A task whose command failed keeps its original exit code. - On EC2, a host with no instance profile keeps using anonymous S3 access. If a host has an instance profile but no reachable instance metadata service and should use anonymous access, set
AWS_EC2_METADATA_DISABLED=true.