search

jx3-gitops-repositories / jx3-kubernetes-vault

Jenkins X 3.x GitOps repository for a vanilla Kubernetes cluster with vault
Apache License 2.0
0 stars 2 forks source link

helmfile sync fails on first run #1

Open ddavis-intel opened 3 years ago

ddavis-intel commented 3 years ago

When running helmfile sync for the first time, I received the following output:

Adding repo banzaicloud-stable https://kubernetes-charts.banzaicloud.com
"banzaicloud-stable" has been added to your repositories

Adding repo jx3 https://storage.googleapis.com/jenkinsxio/charts
"jx3" has been added to your repositories

Affected releases are:
  vault-instance (jx3/vault-instance) UPDATED
  vault-operator (banzaicloud-stable/vault-operator) UPDATED

Upgrading release=vault-operator, chart=banzaicloud-stable/vault-operator
Upgrading release=vault-instance, chart=jx3/vault-instance
Release "vault-instance" does not exist. Installing it now.

Release "vault-operator" does not exist. Installing it now.
NAME: vault-operator
LAST DEPLOYED: Thu May  6 22:37:15 2021
NAMESPACE: jx-vault
STATUS: deployed
REVISION: 1
TEST SUITE: None

Listing releases matching ^vault-operator$
vault-operator  jx-vault        1               2021-05-06 22:37:15.242932052 +0000 UTC deployed        vault-operator-1.10.0                                                                                      1.10.0

UPDATED RELEASES:
NAME             CHART                               VERSION
vault-operator   banzaicloud-stable/vault-operator    1.10.0

FAILED RELEASES:
NAME
vault-instance
in ./helmfile.yaml: failed processing release vault-instance: command "/usr/local/bin/helm" exited with non-zero status:

PATH:
  /usr/local/bin/helm

ARGS:
  0: helm (4 bytes)
  1: upgrade (7 bytes)
  2: --install (9 bytes)
  3: --reset-values (14 bytes)
  4: vault-instance (14 bytes)
  5: jx3/vault-instance (18 bytes)
  6: --version (9 bytes)
  7: 1.0.15 (6 bytes)
  8: --create-namespace (18 bytes)
  9: --namespace (11 bytes)
  10: jx-vault (8 bytes)
  11: --history-max (13 bytes)
  12: 10 (2 bytes)

ERROR:
  exit status 1

EXIT STATUS
  1

STDERR:
  Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "Vault" in version "vault.banzaicloud.com/v1alpha1"

COMBINED OUTPUT:
  Release "vault-instance" does not exist. Installing it now.
  Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "Vault" in version "vault.banzaicloud.com/v1alpha1"

However, running helmfile sync again immediately after resulted in a successful deployment.

Helm version: v3.5.3 Helmfile version: v0.139.0 Kubernetes version: v1.19.9

mohideen commented 10 months ago

I had the same issue, and I was able to fix it with the changes in #7