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

Cannot install new version: missing key "app.kubernetes.io/managed-by" #966

Closed
alex-kuzmin-hg opened this issue Dec 10, 2024 · 3 comments · Fixed by #978
Closed

Cannot install new version: missing key "app.kubernetes.io/managed-by" #966

alex-kuzmin-hg opened this issue Dec 10, 2024 · 3 comments · Fixed by #978
Assignees
Labels
Bug A error that causes the feature to behave differently than what was expected based on design docs Internal Requirement P0 An issue impacting production environments or impacting multiple releases or multiple individuals. released

Comments

@alex-kuzmin-hg
Copy link
Contributor

Describe the bug

At step "helper:solo:network:deploy", it fails:
[helper:solo:network:deploy] ✖ Check if cluster setup chart is installed [FAILED: Chart solo-cluster-setup is not installed. Run 'solo cluster setup']
task: Failed to run task "default": exit status 1

direct call shows potential culprit:

/home/cluster5/.solo/bin/helm install solo-cluster-setup oci://ghcr.io/hashgraph/solo-charts/solo-cluster-setup --version 0.35.0 -n solo-setup --create-namespace  --set cloud.prometheusStack.enabled=false --set cloud.minio.enabled=true --set cloud.certManager.enabled=false --set cert-manager.installCRDs=false
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /var/lib/teleport/credentials/k8s-pft-dal/kubeconfig.yaml
Pulled: ghcr.io/hashgraph/solo-charts/solo-cluster-setup:0.35.0
Digest: sha256:822238f9010784c9c5b579a968e95bf89afc10524e4073506366355e5ac3cab9
Error: INSTALLATION FAILED: Unable to continue with install: CustomResourceDefinition "tenants.minio.min.io" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "solo-cluster-setup"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "solo-setup"

Describe the expected behavior

must run 'task -t Taskfile.yml' fine

To Reproduce

task -t Taskfile.yml
on Latitude

Additional Context

No response

@alex-kuzmin-hg alex-kuzmin-hg added Bug A error that causes the feature to behave differently than what was expected based on design docs Pending Triage New issue that needs to be triaged by the team labels Dec 10, 2024
@alex-kuzmin-hg
Copy link
Contributor Author

alex-kuzmin-hg commented Dec 10, 2024

Nathan:
"Check if cluster setup chart is installed [FAILED: Chart solo-cluster-setup is not installed. Run 'solo cluster setup']
This is the real failure, we should not require the solo-cluster-setup chart to be installed
Preprovisioned clusters with all the necessary dependencies like the latitude cluster will not have the solo-cluster-setup chart
"

@jeromy-cannon
Copy link
Contributor

jeromy-cannon commented Dec 10, 2024

CustomResourceDefinition "tenants.minio.min.io" in namespace "" exists and cannot be imported into the current release

This means that minio already exists, try adding the --no-minio to the solo cluster setup flags.

@jeromy-cannon jeromy-cannon self-assigned this Dec 10, 2024
@jeromy-cannon jeromy-cannon added P0 An issue impacting production environments or impacting multiple releases or multiple individuals. Internal Requirement and removed Pending Triage New issue that needs to be triaged by the team labels Dec 11, 2024
@swirlds-automation
Copy link
Contributor

🎉 This issue has been resolved in version 0.32.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug A error that causes the feature to behave differently than what was expected based on design docs Internal Requirement P0 An issue impacting production environments or impacting multiple releases or multiple individuals. released
Projects
None yet
3 participants