fbda1b4beb
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands - CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround - CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check - NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere - MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates - LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference Co-authored-by: Cursor <cursoragent@cursor.com>
5.5 KiB
5.5 KiB
RPC VMID Migration - Progress Report
Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation
Date: 2025-01-20
Time: Current Status Check
Overall Progress: 🔄 2 of 12 migrations in progress
Current Status Summary
✅ Completed Migrations
None yet - Clones are still in progress
🔄 In Progress (2 clones running)
-
2504 → 2304 (besu-rpc-ali-0x1)
- Status: Cloning in progress
- New VMID: 2304 (stopped, "create" state)
- Old VMID: 2504 (stopped for cloning)
- Clone Process: Running
-
2507 → 2307 (besu-rpc-putu-0x8a)
- Status: Cloning in progress
- New VMID: 2307 (stopped, "create" state)
- Old VMID: 2507 (stopped for cloning)
- Clone Process: Running
⏳ Pending Migrations (10 remaining)
- ⏳ 2500 → 2101 (besu-rpc-core-1)
- ⏳ 2501 → 2201 (besu-rpc-public-1)
- ⏳ 2502 → 2301 (besu-rpc-private-1)
- ⏳ 2400 → 2401 (besu-rpc-thirdweb-0x8a-1) ⚠️ CONFLICT DETECTED
- ⏳ 2401 → 2402 (besu-rpc-thirdweb-0x8a-2) ⚠️ CONFLICT DETECTED
- ⏳ 2402 → 2403 (besu-rpc-thirdweb-0x8a-3)
- ⏳ 2503 → 2303 (besu-rpc-ali-0x8a)
- ⏳ 2505 → 2305 (besu-rpc-luis-0x8a)
- ⏳ 2506 → 2306 (besu-rpc-luis-0x1)
- ⏳ 2508 → 2308 (besu-rpc-putu-0x1)
⚠️ Important Issue Detected
VMID Conflicts for Thirdweb RPC Nodes
Problem: Old VMIDs 2401 and 2402 already exist as running containers:
- VMID 2401: thirdweb-rpc-2 (running)
- VMID 2402: thirdweb-rpc-3 (running)
Impact: The migration script cannot clone:
- 2400 → 2401 (because 2401 already exists)
- 2401 → 2402 (because 2402 already exists)
Solution Required:
- Option A: Rename/stop old 2401 and 2402 first, then proceed
- Option B: Use different target VMIDs for thirdweb migrations
- Option C: Migrate thirdweb nodes in a different order
Recommended: Handle thirdweb migrations separately after other migrations complete.
Old VMIDs Status
| VMID | Status | Name | Notes |
|---|---|---|---|
| 2500 | running | besu-rpc-1 | Will be cloned to 2101 |
| 2501 | running | besu-rpc-2 | Will be cloned to 2201 |
| 2502 | running | besu-rpc-3 | Will be cloned to 2301 |
| 2503 | running | besu-rpc-ali-0x8a | Will be cloned to 2303 |
| 2504 | stopped | besu-rpc-ali-0x1 | Currently being cloned to 2304 |
| 2505 | running | besu-rpc-luis-0x8a | Will be cloned to 2305 |
| 2506 | running | besu-rpc-luis-0x1 | Will be cloned to 2306 |
| 2507 | stopped | besu-rpc-putu-0x8a | Currently being cloned to 2307 |
| 2508 | running | besu-rpc-putu-0x1 | Will be cloned to 2308 |
| 2400 | running | thirdweb-rpc-1 | Will be cloned to 2401 (conflict) |
| 2401 | running | thirdweb-rpc-2 | CONFLICT - already exists |
| 2402 | running | thirdweb-rpc-3 | CONFLICT - already exists |
New VMIDs Status
| VMID | Status | Name | Source |
|---|---|---|---|
| 2101 | not found | besu-rpc-core-1 | From 2500 (pending) |
| 2201 | not found | besu-rpc-public-1 | From 2501 (pending) |
| 2301 | not found | besu-rpc-private-1 | From 2502 (pending) |
| 2303 | not found | besu-rpc-ali-0x8a | From 2503 (pending) |
| 2304 | stopped (create) | besu-rpc-ali-0x1 | From 2504 (in progress) |
| 2305 | not found | besu-rpc-luis-0x8a | From 2505 (pending) |
| 2306 | not found | besu-rpc-luis-0x1 | From 2506 (pending) |
| 2307 | stopped (create) | besu-rpc-putu-0x8a | From 2507 (in progress) |
| 2308 | not found | besu-rpc-putu-0x1 | From 2508 (pending) |
| 2401 | running | thirdweb-rpc-2 | CONFLICT - old container |
| 2402 | running | thirdweb-rpc-3 | CONFLICT - old container |
| 2403 | not found | besu-rpc-thirdweb-0x8a-3 | From 2402 (pending) |
Active Clone Processes
Currently Running: 2 clone processes
pct clone 2504 2304 --hostname besu-rpc-ali-0x1 --storage local-lvmpct clone 2507 2307 --hostname besu-rpc-putu-0x8a --storage local-lvm
Estimated Time Remaining: 5-15 minutes per clone (depending on container size)
Progress Metrics
- Total Migrations: 12
- Completed: 0 (clones still in progress)
- In Progress: 2
- Pending: 10
- Blocked/Conflicts: 2 (thirdweb VMIDs 2401, 2402)
Completion: ~17% (2 of 12 started, 0 fully completed)
Next Steps
Immediate
- ✅ Wait for current clones (2304, 2307) to complete
- ✅ Migration script will continue with next migrations automatically
- ⚠️ Address thirdweb VMID conflicts before those migrations
After Current Clones Complete
- Network configuration will be updated for 2304 and 2307
- Script will proceed with remaining migrations (2500, 2501, 2502, 2503, 2505, 2506, 2508)
- Thirdweb migrations (2400, 2401, 2402) need conflict resolution
Conflict Resolution for Thirdweb
Recommended Approach:
- Stop old 2401 and 2402 containers
- Rename them to temporary VMIDs (e.g., 2401→2491, 2402→2492)
- Proceed with migrations: 2400→2401, 2401→2402, 2402→2403
- Or use different target VMIDs for thirdweb (e.g., 2411, 2412, 2413)
Monitoring Commands
# Check new VMIDs
ssh root@192.168.11.10 "pct list | grep -E '^(2101|2201|2301|2303|2304|2305|2306|2307|2308|2401|2402|2403)'"
# Check clone processes
ssh root@192.168.11.10 "ps aux | grep 'pct clone' | grep -v grep"
# Check old VMIDs
ssh root@192.168.11.10 "pct list | grep -E '^(2500|2501|2502|2503|2504|2505|2506|2507|2508|2400|2401|2402)'"
Last Updated: 2025-01-20
Next Check: Monitor clone completion