search

chanwit / wks-firekube-upgrade-demo

1 stars 24 forks source link

Got error when run ./setup.sh #1

Open iporsut opened 4 years ago

iporsut commented 4 years ago

I try to follow the instruction in README.md when I run ./setup.sh I found this error.

• Installing Kubernetes cluster
ERRO[2020-03-04T17:38:07+07:00] machines[0].spec.versions.controlPlane: Invalid value: "": inconsistent controlPlane version, expected "1.14.1" 
ERRO[2020-03-04T17:38:07+07:00] machines[1].spec.versions.controlPlane: Invalid value: "": inconsistent controlPlane version, expected "1.14.1" 
ERRO[2020-03-04T17:38:07+07:00] machines[2].spec.versions.controlPlane: Invalid value: "": inconsistent controlPlane version, expected "1.14.1" 
FATA[2020-03-04T17:38:07+07:00] Error parsing manifest: /var/folders/0y/fhcctdl5551bgtcpt0gj2plm0000gn/T/wkp576384284/machines.yaml failed validation, use --skip-validation to force the operation

Software version in my machine (macOS) :

chanwit commented 4 years ago

As mentioned on the blog post, this demo uses Firekube with Ignite mode. Firekube in the Ignite mode runs on Linux only as the Firecracker VMs require KVM to start.

For the non-Ignite (Docker) mode, it needs to make changes backend: docker to config.yaml. But you may get a different result. YMMV.

djcoder100 commented 4 years ago

Oops I found same on a non MacOS but mistakenly created in wksctl repo https://github.com/weaveworks/wksctl/issues/145

chanwit commented 4 years ago

@djcoder100 got it. Thank you for reporting.

Maybe we use the different versions of wksctl. I'll fix a code generation for that field in this repo and get back to you.

cdenneen commented 4 years ago

As mentioned on the blog post, this demo uses Firekube with Ignite mode. Firekube in the Ignite mode runs on Linux only as the Firecracker VMs require KVM to start.

For the non-Ignite (Docker) mode, it needs to make changes backend: docker to config.yaml. But you may get a different result. YMMV.

the setup.sh says it changes config.yaml to docker and in fact it does read docker but still gives the same error. I see the nodes are up in docker so not sure why it's getting same error above

cdenneen commented 4 years ago

@chanwit for some reason when I pull down the quickstart it works fine. Here the setup isn't actually connecting to the footloose vm's to do the install... so it's comparing null very strange

RiskyFeryansyahP commented 4 years ago

@cdenneen did you solve this problem ?

because i have same issue