Skip to content

fix: log explicit messages when bootstrap.dcs.standby_cluster can't parse#108

Merged
Tvion merged 1 commit into
Netcracker:mainfrom
vlsi:bootstrap_dcs_logs
Jun 24, 2026
Merged

fix: log explicit messages when bootstrap.dcs.standby_cluster can't parse#108
Tvion merged 1 commit into
Netcracker:mainfrom
vlsi:bootstrap_dcs_logs

Conversation

@vlsi

@vlsi vlsi commented Oct 9, 2025

Copy link
Copy Markdown
Collaborator

Previously, a generic panic was logged, so it was hard to figure out the cause

@Tvion

Tvion commented Jan 8, 2026

Copy link
Copy Markdown
Collaborator

Hi, thank you, this looks right to handle each field separately.

However we have to follow the old logic and stop execution if one of the fields incorrect or not found. So here we have to send the error and stop reconcile.

…arse

Return errors from updateStandbyClusterSettings and propagate them to
the reconciler so that reconciliation stops on invalid config instead of
silently continuing with an unmodified configmap.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@vlsi

vlsi commented Mar 26, 2026

Copy link
Copy Markdown
Collaborator Author

@Tvion , right you are. I've updated the code so it returns the error. Could you review again?

@Tvion Tvion merged commit 88b68e8 into Netcracker:main Jun 24, 2026
8 of 14 checks passed
@github-actions github-actions Bot locked and limited conversation to collaborators Jun 24, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants