Host deployments now detect and replace incomplete or corrupt Exasol archives.
Details
| Detail name | Value |
|---|---|
| Changelog Number | 25104 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 8.25.0, C4 4.19.4, c4 4.29.9 |
| Fix Versions | C4 4.29.10 |
| Resolution Date | 2026-09-07 |
Description
During a host deployment with c4 host play, if a data node already had a file with the same name as the Exasol archive, c4 reused that file without checking whether it was complete. If the file was empty, truncated, or corrupt (for example, left behind by an earlier upload that was interrupted), the installation failed while extracting the archive with this error:
tar: This does not look like a tar archive tar: Exiting with failure status due to previous errors
Workaround
Delete the incomplete Exasol archive from the home directory of the deployment user on the affected data nodes, then run the deployment again.
Fix
Before reusing an Exasol archive that already exists on a data node, c4 now compares its checksum with the source archive. If the archive is missing or the checksums do not match, c4 uploads it again and checks the checksum of the uploaded archive before continuing. If an upload fails or the checksum still does not match, the deployment stops with an error instead of going on with an invalid archive.
