Fixed next_stage_for_slave failing on reboot in some cases

Detail name	Value
Changelog Number	24183
Type	Bug
Status	Resolved
Affected Versions	Exasol 8.0.0
Fix Versions	Exasol 8.34.0, Exasol 8.29.10
Resolution Date	2025-04-16

Description

If a user stopped the nodes with infra_instances_stop (or infra_db_stop), the nodes' state was set to “disabled” in EXAConf permanently. The state was not reset back to “enabled” after the nodes were started up again.

The issue only occurred when all the nodes (including master) were rebooted at the same time, at some later point in time. In that case, the slave nodes that were marked as “disabled” failed to sync with master, as master was considering them as disabled.

Workaround

Restart “c4_cloud_command” service on the slave nodes that encounter the issue by running sudo systemctl restart c4_cloud_command.

Fix

Nodes are now always marked as “enabled” during register_node (i.e., when nodes initialize).