Fix c4 not finding the Exasol archive when adding a new node
Details
| Detail name | Value |
|---|---|
| Changelog Number | 21688 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 8.0.0 |
| Fix Versions | C4 4.19.8, Exasol 2025.1.0, C4 4.27.0, Exasol 8.29.11 |
| Resolution Date | 2025-06-03 |
Description
Adding a new node involves invoking confd_client infra_instances_add command which internally invokes c4 to add the new node. However, if the installation had at least a single update in the past, c4 would fail to find the Exasol archive that is expected to be located in the home directory of the current node.
Workaround
c4 connect -i PLAY_ID -s host -n 11 VERSION=8.34.0 ALIAS=$(c4 config -e .play.working_copy) mv $HOME/exasol-$VERSION.tar.gz $HOME/$ALIAS.tar.gz
Fix
c4 will now correctly identify the expected name of the archive, even if the deployment was updated in the past.