claude-botandClaude Opus 5
4938f8f5a2
The removal has been applied: Apply complete! Resources: 0 added, 0 changed, 0 destroyed, 1 forgotten. `tofu state list` now returns no Proxmox resources at all, and a full plan with refresh enabled produces no Proxmox errors — the "no route to host" against 10.2.40.201:8006 that failed every infrastructure plan since the conversion is gone. The block was always one-shot. Left in place it refers to a state entry that no longer exists, which is harmless but misleading: it reads as pending work. Worth recording for the next time this shape comes up, because it cost a failed merge to learn. A `removed` block alone does not fix an unreachable provider: OpenTofu still refreshes the resource before it can forget it, and that refresh is exactly what cannot succeed. It takes one run with `-refresh=false` to process. `-target` does not help — targeting does not reach `removed` blocks, so a targeted plan reports "No changes" while the state entry sits there untouched. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>