Fixed a reboot breaking on-prem deployments that added a new node

Detail name	Value
Changelog Number	22353
Type	Bug
Status	Resolved
Affected Versions	Exasol 8.0.0
Fix Versions	Exasol 8.33.0, C4 4.24.2
Resolution Date	2025-02-27

Description

Documentation page Add Reserve Nodes to Existing Deployment explains how to add a new node to on-prem deployments.

Database is able to start and work right after performing these steps.

However, c4_cloud_command service won’t start after one or more machines of that deployment are rebooted.

Workaround

Workaround for versions where the bug is not fixed requires manual changes to configuration files.

Please contact Exasol Support to guide you through the needed steps.

Fix

c4_cloud_command service starts normally after one or more machines of deployment extended according to Add Reserve Nodes to Existing Deployment are rebooted.