Flux: New install - errors with fluxctl and automatic deployments

Created on 2 Mar 2020  路  3Comments  路  Source: fluxcd/flux

Describe the bug

fluxctl --k8s-fwd-ns flux list-workloads
== Error ==

Unable to parse files as manifests

Flux was unable to parse the files in the git repo as manifests,
giving this error:

    parsing YAML doc from "etc/ansible/generate-from-template-deploy-system-id-conf.yml": yaml: unmarshal errors:
  line 1: cannot unmarshal !!seq into resource.baseObject

To Reproduce

fluxctl --k8s-fwd-ns flux list-workloads

Steps to reproduce the behaviour:
Flux was installed with

helm upgrade -i flux fluxcd/flux --set [email protected]:my-project/project --set git.label=stage --set git.branch=stage -n flux

Expected behavior

flux should list any pending workloads

The
Additional context

  • Flux version: 1.18.0
  • Kubernetes version: 1.15.4
  • Git provider: github
  • Container registry provider: ECR

I'm running into this on 3 different clusters - it seems to be causing some problems with automatic deployments from ECR

blocked-needs-validation bug

All 3 comments

I should also note in the flux log i see these errors as well -

caller=loop.go:107 component=sync-loop err="loading resources from repo: parsing YAML doc from \"etc/ansible/generate-from-template-deploy-system-id-conf.yml\": yaml: unmarshal errors:
  line 1: cannot unmarshal !!seq into resource.baseObject"

and

caller=images.go:23 component=sync-loop error="getting unlocked automated resources: parsing YAML doc from \"etc/ansible/generate-from-template-deploy-system-id-conf.yml\": yaml: unmarshal errors:
  line 1: cannot unmarshal !!seq into resource.baseObject"

figured this out :-)

figured this out :-)

how? I have the same problem

Was this page helpful?
0 / 5 - 0 ratings