Cant redeploy Qovery managed cluster on Scaleway

Questions and Answers
1

Hey, once redeploy is initiated it stuck for 1 hour in this state

Create - Infrastructure 'scw-staging (zd62ee903)' deployment is in progress...

And after 1 hour it fails with error

CreateError - Helm timed out for release `promtail` during helm UPGRADE: Name: "promtail", Namespace: "kube-system"'Name: "promtail", Namespace: "kube-system"'Error: UPGRADE FAILED: an error occurred while rolling back the release. original upgrade error: context deadline exceeded: release promtail failed: context deadline exceededrelease promtail failedhelm.sh/helm/v3/pkg/action.(*Rollback).performRollback	helm.sh/helm/v3/pkg/action/rollback.go:239helm.sh/helm/v3/pkg/action.(*Rollback).Run	helm.sh/helm/v3/pkg/action/rollback.go:79helm.sh/helm/v3/pkg/action.(*Upgrade).failRelease	helm.sh/helm/v3/pkg/action/upgrade.go:524helm.sh/helm/v3/pkg/action.(*Upgrade).reportToPerformUpgrade	helm.sh/helm/v3/pkg/action/upgrade.go:388helm.sh/helm/v3/pkg/action.(*Upgrade).releasingUpgrade	helm.sh/helm/v3/pkg/action/upgrade.go:448runtime.goexit	runtime/asm_amd64.s:1695an error occurred while rolling back the release. original upgrade error: context deadline exceededhelm.sh/helm/v3/pkg/action.(*Upgrade).failRelease	helm.sh/helm/v3/pkg/action/upgrade.go:525helm.sh/helm/v3/pkg/action.(*Upgrade).reportToPerformUpgrade	helm.sh/helm/v3/pkg/action/upgrade.go:388helm.sh/helm/v3/pkg/action.(*Upgrade).releasingUpgrade	helm.sh/helm/v3/pkg/action/upgrade.go:448runtime.goexit	runtime/asm_amd64.s:1695UPGRADE FAILEDmain.newUpgradeCmd.func2	helm.sh/helm/v3/cmd/helm/upgrade.go:240github.com/spf13/cobra.(*Command).execute	github.com/spf13/cobra@v1.8.0/command.go:983github.com/spf13/cobra.(*Command).ExecuteC	github.com/spf13/cobra@v1.8.0/command.go:1115github.com/spf13/cobra.(*Command).Execute	github.com/spf13/cobra@v1.8.0/command.go:1039main.main	helm.sh/helm/v3/cmd/helm/helm.go:83runtime.main	runtime/proc.go:271runtime.goexit	runtime/asm_amd64.s:1695: Command terminated with a non success exit status code: exit status: 1
Terminated - Qovery Engine has terminated the infrastructure deployment

Can someone assist me with redeploying our cluster? Or better deleting it, because I cant delete it my self, it says all environments must be deleted before deleting cluster though i dont have any environments active inside cluster.

3

Hello @markkkkas !

Looking at your cluster, it seems promtail was late ingesting old logs, not sure why, still looking. Giving a bit of fresh air to promtail allowing it to ingest it all unlock the situation.

I triggered a cluster update, everything is ok now.

As for other issue you are facing (every envs must be deleted before deleting cluster) it’s a bug on our side, we are working on it and it should lands within this week.

Let me know if you need further assistance.

Cheers

4

Hi @bchastanier, we expect that you will not charge us for this cluster since we can’t get rid of it due to a Qovery bug, right?

5

Hey @markkkkas, I can confirm that you will obviously not be charged for this cluster, due to the situation.
Please let us know if you have any further questions.
Best,
Morgan

6

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