Pod stuck on "Waiting for connection data..." — runtime/ports null, critical data at risk
Hi,
My pod u4f9qu4sm8i7m0 ("AWA Project", RTX A6000) is stuck in a broken state.
Problem: desiredStatus is RUNNING, container starts successfully (logs show "Start script(s) finished, pod is ready to use"), but runtime remains null or ports stay null — no ports are assigned, SSH and web terminal are unavailable. The Connect tab shows "Waiting for connection data..." indefinitely.
What I've tried:
- Stop/Start via UI and API multiple times
- Hard refresh, different browsers
- Waited 15+ minutes after each restart
- It briefly came up once with ports assigned, then went back to null after some time
After every restart the logs are clean but runtime/ports keep dropping.
I cannot terminate this pod — it has critical data on pod storage (/workspace, 400GB) with no network volume attached.
Could you please either:
1. Migrate the pod to a healthy node while preserving the disk, or
2. Restore network/port assignment on the current node?
Pod ID: u4f9qu4sm8i7m0
Thank you.
My pod u4f9qu4sm8i7m0 ("AWA Project", RTX A6000) is stuck in a broken state.
Problem: desiredStatus is RUNNING, container starts successfully (logs show "Start script(s) finished, pod is ready to use"), but runtime remains null or ports stay null — no ports are assigned, SSH and web terminal are unavailable. The Connect tab shows "Waiting for connection data..." indefinitely.
What I've tried:
- Stop/Start via UI and API multiple times
- Hard refresh, different browsers
- Waited 15+ minutes after each restart
- It briefly came up once with ports assigned, then went back to null after some time
After every restart the logs are clean but runtime/ports keep dropping.
I cannot terminate this pod — it has critical data on pod storage (/workspace, 400GB) with no network volume attached.
Could you please either:
1. Migrate the pod to a healthy node while preserving the disk, or
2. Restore network/port assignment on the current node?
Pod ID: u4f9qu4sm8i7m0
Thank you.
