Skip to content

Fix get_backup_by_id to filter by cluster_id in cross-cluster scenarios - #1235

Open
RaunakJalan wants to merge 3 commits into
mainfrom
fix/backup-get-by-id-cluster-filter
Open

Fix get_backup_by_id to filter by cluster_id in cross-cluster scenarios#1235
RaunakJalan wants to merge 3 commits into
mainfrom
fix/backup-get-by-id-cluster-filter

Conversation

@RaunakJalan

Copy link
Copy Markdown
Collaborator

After backup import, both clusters share the same UUID in the KV store. get_backup_by_id() scanned all clusters, hitting 'Multiple values present' on restore. Add optional cluster_id parameter to scope the lookup.

After backup import, both clusters share the same UUID in the KV store.
get_backup_by_id() scanned all clusters, hitting 'Multiple values present'
on restore. Add optional cluster_id parameter to scope the lookup.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@RaunakJalan
RaunakJalan force-pushed the fix/backup-get-by-id-cluster-filter branch from 3876e9b to a3d9be4 Compare August 11, 2026 23:54
When restoring a backup on a different cluster, restore_backup() fell
back to backup.node_id which belongs to the source cluster, causing
the restored lvol to be created on the wrong cluster's nodes. Now
detect when the backup's node doesn't belong to the target cluster
and automatically select an online node from the target cluster.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Comment thread simplyblock_core/controllers/backup_controller.py Fixed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant