"CreateError - Invalid container registry information" after updating mirror registry

First of all, refer to Failed to pull image error on mirror images #2488 where I describe an issue with Scaleway registry used as mirror registry.

We discussed with @Pierre_Mavro about the issue linked previously and he advised to change the registry provider because it’s kind of known that there are issues with Scaleway registries.
And that’s what we tried to do.

First of all, it looks like we can’t use a different registry provider when using Scaleway as cloud provider (after updating mirror registry config, an error notification shows up to tell that).

Now, the real issue after rollbacking that editions, the clusters can’t deploy any apps/environments with the following error message:

CreateError - Invalid container registry information

Both of my clusters are now stuck in this situation.

How to deal with it?

And additional question: how can I use a different registry for mirror images when using Scaleway as cloud provider?

Thanks for your help!

I’m not fan of “UP” replies, sorry then, but some help would be really appreciated since I can’t perform any update nor deployment on my clusters right now.

Hello @Sryther
I’m taking a look

Can you update your cluster credentials linked to your scaleway cluster ? (Cluster Settings > Credentias > “Edit”)

Internally I can see the scaleway project id is missing on our side.

I see only 1 of your cluster in error, the other one seems fine ?

Hello @Melvin_Zottola,

I edited and update the credentials but same issue. Is the project id still missing?

Both of my clusters have the issue.

Can you send me the Qovery console URL of your clusters ?

Sure! Here you are:

Production: https://console.qovery.com/organization/558f6260-d61b-47bc-bb08-f28d2d655ce9/cluster/df0e7f28-5da0-4fbe-a9dc-24054c4a656f/

Development/Staging: https://console.qovery.com/organization/558f6260-d61b-47bc-bb08-f28d2d655ce9/cluster/0b1f0c0c-3f16-4847-a329-34f44e043c71/

Thank you, I’m digging to check why this is not updated

I’ve updated and redeployed your clusters to apply the changements regarding the container registries.
Can you try to redeploy some of your envs that had issues linked to the container registry error ?

It looks like we can dploy on every clusters. Thanks!

1 Like

Hello @Melvin_Zottola,
I’m not sure the issue is related but it looks like because it’s about mirror registries.

On my production cluster, for containers, lifecycle jobs and cronjobs I got this error message:

🔓 Login to registry rg.fr-par.scw.cloud as user nologin
🪞 Mirroring image to private cluster registry to ensure reproducibility
🪞 Retrying Mirroring image due to error...
🪞 Retrying Mirroring image due to error...
🪞 Retrying Mirroring image due to error...
🪞 Retrying Mirroring image due to error...
┏━━ 📝 Recap Status Report ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
❌ Deployment of cron-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/
⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️

For this specific logs, here is the URL: https://console.qovery.com/organization/558f6260-d61b-47bc-bb08-f28d2d655ce9/project/70edc842-a910-4f27-9411-e3e786d39c0c/environment/e993949f-97d7-440b-bb5a-f82a2c6bb88d/logs/4e0028b4-32fb-4f32-907b-a76947f5691d/deployment-logs if it helps.


This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.