Skip to content

Error: release kubevious failed, and has been uninstalled due to atomic being set: timed out waiting for the condition #59

@maorkuriel

Description

@maorkuriel

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions