Skip to content

fix(backuprestore): use pool UUID instead of pool name in restored PV's volume handle - #447

Open
boddumanohar wants to merge 1 commit into
mainfrom
fix/backuprestore-volumehandle-pool-uuid
Open

fix(backuprestore): use pool UUID instead of pool name in restored PV's volume handle#447
boddumanohar wants to merge 1 commit into
mainfrom
fix/backuprestore-volumehandle-pool-uuid

Conversation

@boddumanohar

Copy link
Copy Markdown
Member

Summary

  • ensurePV in the BackupRestore controller built the CSI VolumeHandle as clusterUUID:PoolName:lvolID. Every other consumer of this handle format (volumemigration_controller.go, persistentvolumeclaim_controller.go) — and every dynamically-provisioned PV — treats the middle segment as an immutable pool UUID, not the mutable pool name.
  • Switches both the handle-construction and the existing-PV drift-check in ensurePV to use restoreCR.Status.PoolUUID instead of restoreCR.Status.PoolName.

Test plan

  • go build ./...
  • go test ./internal/controller/... (full suite passes)
  • Updated TestBackupRestoreEnsurePVIncludesCSIAttributes to assert the new cluster-uuid:pool-uuid:lvol-uuid handle format

🤖 Generated with Claude Code

…'s volume handle

ensurePV built the CSI VolumeHandle as clusterUUID:PoolName:lvolID, while
every other consumer (volumemigration_controller, persistentvolumeclaim_controller)
and every dynamically-provisioned PV parse the middle segment as an immutable
pool UUID. A pool rename would silently break lookups keyed off a restored
volume's handle.
@boddumanohar boddumanohar self-assigned this Aug 21, 2026
@boddumanohar boddumanohar added the bug Something isn't working label Aug 21, 2026
@boddumanohar boddumanohar added this to the 26.4 milestone Aug 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant