Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Installing devtron/devtron-operator Helm chart with cicd module fails #6138

Open
2 tasks done
OctavianHome opened this issue Nov 28, 2024 · 6 comments
Open
2 tasks done
Assignees
Labels
bug Something isn't working

Comments

@OctavianHome
Copy link

OctavianHome commented Nov 28, 2024

📜 Description

If you install (upgrade) Devtron Hem Chart with cicd install module enabled the Helm is raising an error (CustomResourceDefinition workflows.argoproj.io).
If you install (upgrade) Devtron Hem Chart without cicd install module it is working fine.

👟 Reproduction steps

Add Helm Repo:

helm repo add devtron https://helm.devtron.ai

Update Helm Repo:

helm repo update devtron

Install Helm Dashboard by Devtron (devtron-operator-0.22.78.tgz):

helm upgrade \
    --install "devtron" \
    --namespace "devtroncd" --create-namespace \
    devtron/devtron-operator \
    --set installer.modules={cicd} \
    --wait \
    --debug

👍 Expected behavior

The Helm installation to be successful.

👎 Actual Behavior

Helm error:

Error: Unable to continue with install: CustomResourceDefinition "workflows.argoproj.io" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-name" must equal "devtron": current value is "argo"; annotation validation error: key "meta.helm.sh/release-namespace" must equal "devtroncd": current value is "argo" 

☸ Kubernetes version

AKS 1.30.5

Cloud provider

Azure - AKS

🌍 Browser

Chrome

🧱 Your Environment

No response

✅ Proposed Solution

No response

👀 Have you spent some time to check if this issue has been raised before?

  • I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

@OctavianHome OctavianHome added the bug Something isn't working label Nov 28, 2024
@pawan-mehta-dt
Copy link
Contributor

@OctavianHome Devtron installs argo-workflows with the configurations that it requires, if you already have it installed, helm will raise an error because it restricts overwriting the current configurations. Can you try installing it on any cluster where any component related to argo isn't installed?

@OctavianHome
Copy link
Author

@pawan-mehta-dt
There is no argo or argo-workflows releases installed on this cluster.
Indeed initially I installed devtron into a cluster with argo installed.
But after that I suspected the same so I switched the context to a "green" AKS cluster but the error was still there.

@OctavianHome
Copy link
Author

OctavianHome commented Nov 28, 2024

@pawan-mehta-dt
It seems that even if I tried to install devtron on a "green" AKS cluster since I tried twice that error showed up.
So I tried to install to a new AKS cluster and the above error (CustomResourceDefinition "workflows.argoproj.io") disappeared.
But now I've got another error:

wait.go:87: 2024-11-28 17:14:55.0504291 +0200 EET m=+318.745903801 [debug] Error received when checking status of resource postgresql-postgresql-metrics. Error: 'client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline', Resource details: 'Resource: "/v1, Resource=services", GroupVersionKind: "/v1, Kind=Service"
Name: "postgresql-postgresql-metrics", Namespace: "devtroncd"'
wait.go:94: 2024-11-28 17:14:55.0510009 +0200 EET m=+318.746475601 [debug] Retryable error? true
wait.go:71: 2024-11-28 17:14:55.0510009 +0200 EET m=+318.746475601 [debug] Retrying as current number of retries 0 less than max number of retries 30
Error: context deadline exceeded
helm.go:86: 2024-11-28 17:14:55.411784 +0200 EET m=+319.107258701 [debug] context deadline exceeded

@pawan-mehta-dt
Copy link
Contributor

@OctavianHome Can you join our discord community? https://discord.devtron.ai so that we can Debug and resolve your issue

@OctavianHome
Copy link
Author

@pawan-mehta-dt
I have no access to https://discord.devtron.ai/ due to company laptop restrictions.
Could we debug it "offline"?
Thanks

@pawan-mehta-dt
Copy link
Contributor

@OctavianHome Can you share few details like? K8s version
is it Airgapped?

Output of kubectl get po -n devtroncd

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants