Forum

Hello, we have identified the issue.

Root Cause: You just launched a new Tencent Seoul server (Mede-DEV). You initiated cloneProject 38 seconds after the server init was completed, but the backend server status cache had not yet synchronized. It was incorrectly identified as "provisioning," causing the namespace creation step to fail. We checked other Tencent servers created in the same batch at the same time, and clone/deploy operations were normal, confirming that your server itself is fine and k3s is healthy.

Current Status: The previous attempts left two empty shell projects on the new server: esim-aria and esim-olic (they only have a production env and no services).

Action Required:

1. Delete the empty esim-aria and esim-olic projects from the Dashboard (to avoid confusion later).
2. Run the Clone Project process again, selecting Mede-DEV as the target.

If it still fails after retrying, please paste the new Trace ID, and we will take another look.