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
Error: release kubevious failed, and has been uninstalled due to atomic being set: timed out waiting for the condition #59
Comments
@maorkuriel, lets try adding Please include more details from helm install and pods that are failing. |
Hi @rubenhak history.go:56: [debug] getting history for release kubevious client.go:128: [debug] creating 16 resource(s) COMPUTED VALUES:
HOOKS:Source: kubevious/templates/tests/test-connection.yamlapiVersion: v1
|
@maorkuriel, did you check "kubevious" Deployment and the "kubevious-mysql" StatefulSet? Are the corresponding pods up and running? Are they ready? Any errors in the logs? |
@rubenhak They were running. I will spin up another deployment and test it again. |
@maorkuriel, that's odd. There is not much information for me to troubleshoot. Want to have a live call to debug? I've sent you an invite on LinkedIn. |
@maorkuriel, we've released a new version that could resolve this issue. Could you please give it a try and reopen the issue if it still persists. kubectl create namespace kubevious
helm repo add kubevious https://helm.kubevious.io
helm repo update
helm upgrade --atomic -i kubevious kubevious/kubevious --version 0.9.27 -n kubevious For more details on installation options, visit Deployment Repository. |
Describe the bug
I am trying to run the tool on Minikube on my Macbook pro M1 and failing to install it with an error message
❯ helm upgrade --atomic -i kubevious kubevious/kubevious --version 0.8.15 -n kubevious
Release "kubevious" does not exist. Installing it now.
Error: release kubevious failed, and has been uninstalled due to atomic being set: timed out waiting for the condition
~ took 5m3s
To Reproduce
Steps to reproduce the behavior:
~ took 25s
❯ kubectl create namespace kubevious
namespace/kubevious created
~
❯ helm repo add kubevious https://helm.kubevious.io
"kubevious" has been added to your repositories
~ took 2s
❯ helm upgrade --atomic -i kubevious kubevious/kubevious --version 0.8.15 -n kubevious
Release "kubevious" does not exist. Installing it now.
Error: release kubevious failed, and has been uninstalled due to atomic being set: timed out waiting for the condition
Expected behavior
A running Kubevious system up and running
Screenshots
If applicable, add screenshots to help explain your problem.
Environment Details:
MacBook Pro M1
❯ minikube start
😄 minikube v1.23.2 on Darwin 12.0.1 (arm64)
🎉 minikube 1.24.0 is available! Download it: https://github.com/kubernetes/minikube/releases/tag/v1.24.0
💡 To disable this notice, run: 'minikube config set WantUpdateNotification false'
✨ Using the docker driver based on existing profile
👍 Starting control plane node minikube in cluster minikube
🚜 Pulling base image ...
🔄 Restarting existing docker container for "minikube" ...
🐳 Preparing Kubernetes v1.22.2 on Docker 20.10.8 ...
🔎 Verifying Kubernetes components...
▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
╭──────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ Registry addon with docker driver uses port 54143 please use that instead of default port 5000 │
│ │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────╯
📘 For more information see: https://minikube.sigs.k8s.io/docs/drivers/docker
▪ Using image registry:2.7.1
▪ Using image gcr.io/google_containers/kube-registry-proxy:0.4
🔎 Verifying registry addon...
🌟 Enabled addons: storage-provisioner, default-storageclass, registry
🏄 Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
The text was updated successfully, but these errors were encountered: