Repository navigation
Move the remaining provider-backed platform volumes to Longhorn V2 #6009
Description
🤖 Generated by the Agentic Engineer
Objective
Move the platform’s remaining provider-backed persistent data to Longhorn V2 while preserving recoverability.
Details
Qualify durable capacity for the complete three-replica target. Prove that essential services can start during cold recovery and that their data can be restored from an independent copy. Move each workload through its reviewed cutover, retain the original during verification, and retire the provider copy after the rollback decision.
Checklist
- Account for every source claim and retained data set, including inactive sources.
- Verify the target capacity, recovery order, and independent restores before the first cutover.
- Verify each workload or retained recovery copy on Longhorn V2 and account for every original provider volume.
- Verify that future platform provisioning uses Longhorn V2 for these workloads.
Part of #5582
Reacted by coderabbitai
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
Priority
None yet
Projects
- Status
Activity
coderabbitai commentedon Nov 10, 2026
🔗 Related PRs
#5713 - feat(storage): inventory native V1 replica directories [merged]
#5698 - feat(storage): release the warm spare ahead of the Longhorn V2 worker [merged]
#5584 - chore(storage): prepare worker capacity for Longhorn V2 [merged]
#5726 - feat(storage): add the fixed Longhorn V2 migration worker [merged]
#5969 - fix(storage): restore capacity for missing V1 replicas [merged]
#5828 - fix(storage): observe host memory during replica replacement [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
devantler commentedon Nov 11, 2026
The reviewed provider-capacity observation passed on a first-attempt main dispatch at
ecfa914dd797b77548d22a236dcb281320ec463c. It accounted for all 17 source claims. Allocated source capacity totals 220 GiB, fourteen mounted claims measured up to 56 GiB used, and the three unmounted claims retain a full 30 GiB allowance. The observer bound the source claims, provider devices and host epochs before and after the measurement. Native runNext gates cover independent restores, durable V2 capacity and workload cutover.
chore: agent-claim #6009 nonce=543848b472d8b4fdec43a6f707694cc9
chore: agent-claim #6009 nonce=5fda9c400f8ff92a138c61de9b06cd62
chore: agent-claim #6009 nonce=e1df33c9d2bcc2893598cd1a25646e60
chore: agent-claim #6009 nonce=7dd89a030d22fd8bbb14df67aed26a8a
chore: agent-claim #6009 nonce=ff5500c36cad1bef360703f237def6b8
chore: agent-claim #6009 nonce=cbf95340341ac239696f68a69d655e7f
chore: agent-claim #6009 nonce=09d78dcfa9e2c3e35cf537a796a1804d
chore: agent-claim #6009 nonce=f68f551a47b7540e8561cfd0ffe0ea35
chore: agent-claim #6009 nonce=d2ee0082ffe1d60d177b54dcfde5a878
chore: agent-claim #6009 nonce=3bdf40e5e9aef979d4f07641454e1d1c
chore: agent-claim #6009 nonce=b52eb9c7e37c303588ba46e7ef704e55
devantler commentedon Nov 11, 2026
The provider-source protection phase is complete. Fresh native readback confirms all 17 original provider-backed volumes now use
Retain, with every original claim, volume and backend binding unchanged. All 17 deliberately mismatched identity confirmations were refused; the readback performed no writes. The guarded operations and their exact attempts are retained in the private operator record.This preserves the originals while migration proceeds. It is not a V2 cutover, independent-restore acceptance or permission to retire a source. This issue remains open for the capacity, recovery-order, restore, per-workload migration and future-provisioning criteria above.