Skip to content
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.

validation failure list: spec.rollback.timeout in body must be of type int64: "integer" #2250

Closed
sureshamk opened this issue Jul 12, 2019 · 1 comment · Fixed by #2251
Closed

Comments

@sureshamk
Copy link

sureshamk commented Jul 12, 2019

Describe the bug
My helm release as follows

apiVersion: flux.weave.works/v1beta1
kind: HelmRelease
metadata:
  name: demolocal
  namespace: local
  annotations:
    flux.weave.works/automated: "true"
    flux.weave.works/tag.chart-image: glob:loc-*
spec:
  releaseName: demo-local
  chart:
    git: git@bitbucket.org:sureshamk/my_helm.git
    path: charts/demo
    ref: local
  values:
    demoadmin:
      name: demoadmin
      image: cr.demolocal.com/demoadmin:loc-1
      imagePullPolicy: IfNotPresent
      ingress:
        enabled: true
        annotations:
          traefik.ingress.kubernetes.io/rule-type: PathPrefixStrip
          nginx.ingress.kubernetes.io/rewrite-target: /
        path: /newadmin/api
        hosts:
        - apps.demolocal.com
  rollback:
    # If set, will perform rollbacks for this release.
    enable: true
    # If set, will force resource update through delete/recreate if
    # needed.
    force: true
    # Prevent hooks from running during rollback.
    disableHooks: false
    # Time in seconds to wait for any individual Kubernetes operation.
    timeout: 5000
    # If set, will wait until all Pods, PVCs, Services, and minimum
    # number of Pods of a Deployment are in a ready state before
    # marking the release as successful. It will wait for as long
    # as the set timeout.
    wait: false

When i apply this file (kubectl apply -f local.yaml)
i m getting this error
: validation failure list:
spec.rollback.timeout in body must be of type int64: "integer"

@sureshamk sureshamk added blocked-needs-validation Issue is waiting to be validated before we can proceed bug labels Jul 12, 2019
@hiddeco hiddeco added helm and removed blocked-needs-validation Issue is waiting to be validated before we can proceed labels Jul 12, 2019
@hiddeco
Copy link
Member

hiddeco commented Jul 12, 2019

Small mistake in the validation scheme, probably due to me copy/pasting without thinking. I created a PR to fix the CRD.

Running kubectl apply -f https://github.com/fluxcd/flux/raw/2363a65a8bc3bd58e6b3ed831856df319a1f8754/deploy-helm/flux-helm-release-crd.yaml should fix it for you.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants