Stuck "0 Bytes / Detached" Boot Volume on ARM Instance (Seoul Region)
in Arm Compute
Hi everyone,
I'm hitting a severe control plane metadata synchronization bug on an Always Free ARM instance in the ap-seoul-1 (Seoul) region. This appears to be a backend deadlock that I cannot resolve from my end.
The Issue:
The original boot volume was terminated, but a "ghost attachment" row is permanently stuck under the instance’s Storage -> Boot volume section.
State: Stuck in Detached. Size: Displays as 0 Bytes. Behavior: The "Replace boot volume" button is greyed out. Clicking the boot volume link itself leads to a 404 (Resource Not Found), which proves the actual storage resource is gone, but the instance attachment mapping is corrupted in the OCI DB.
Tagged:
0