Hi @Qovery
On our development cluster hosted on Scaleway, we cannot deploy and execute lifecycle jobs and cron jobs. It was working about 10 days ago.
There isn’t much in the logs of the deployment.
Checking Cloud provider credentials are valid
🏁 Deployment request 12d194e4-230d-4eca-b87a-7ea9906db114-639-1723896432 for stage 1 `Database schemas migrations` has been sent to the engine
⏳ Your deployment is 1 in the Queue
🚀 Qovery Engine starts to execute the deployment
🎡 Proceeding with up to 7 parallel deployment(s)
🎯 Skipping image mirroring: service and cluster registries are the same
🚀 Deployment of Job at tag airsaas/api:develop-e0eda117 is starting with a timeout/max duration of 10.00 minutes
┏━━ 📝 Deployment Status Report ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
┃ Job at tag airsaas/api:develop-e0eda117 execution is in progress ⏳, below the current status:
┃
┃ 🛰 Job at old version has 0 pods: 0 running, 0 starting, 0 terminating and 0 in error
┃ 🛰 Job at new tag airsaas/api:develop-e0eda117 has 0 pods: 0 running, 0 starting, 0 terminating and 0 in error
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
┏━━ 📝 Recap Status Report ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
❌ Deployment of job failed but we rollbacked it to previous safe/running version !
⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️ ⬇️
Look at the Deployment Status Reports above and use our troubleshooting guide to fix it https://hub.qovery.com/docs/using-qovery/troubleshoot/
⛑ Can't solve the issue? Please have a look at our forum https://discuss.qovery.com/
⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️
Qovery Engine has terminated the deployment
In the live logs we can see this:
No pods found for requested service. Retry later.
Of course there are no pods since it’s a job.
We tried it with various versions of our image, including ones that were working before. We tried it on several jobs, and they are all failing so far. We tried it for regular services and it seems to work.
We also tried to update the cluster without success.
This is blocking our release flow.
You can test the deploy yourselves here: https://console.qovery.com/organization/558f6260-d61b-47bc-bb08-f28d2d655ce9/project/70edc842-a910-4f27-9411-e3e786d39c0c/environment/12d194e4-230d-4eca-b87a-7ea9906db114/application/63326508-bae0-4342-b945-a50bad0c66b2/deployments
Thanks!
