Open rkuzsma opened 7 years ago
Found a workaround:
If I open a new iterm window and run this line of code to install the VMs, I don't get the openpgp error:
$ ~/bin/corectl load settings/k8smaster-01.toml
> booting k8smaster-01 (1/1)
[WARN] /Users/myusername/.coreos/images/stable/1122.2.0/coreos_production_pxe.vmlinuz missing - stable/1122.2.0 ignored
---> downloading and verifying stable/1122.2.0
32.63 MB / 32.63 MB [==================================================================================================================================] 100.00 %
---> SHA512 hash for coreos_production_pxe.vmlinuz OK
220.78 MB / 220.78 MB [================================================================================================================================] 100.00 %
---> SHA512 hash for coreos_production_pxe_image.cpio.gz OK
---> stable/1122.2.0 ready
---> 'k8smaster-01' started successfuly with address 192.168.64.2 and PID 87297
---> 'k8smaster-01' boot logs can be found at '/Users/myusername/.coreos/running/7E79BC00-7E3C-4B19-9CDF-83F99FD73A23/log'
---> 'k8smaster-01' console can be found at '/Users/myusername/.coreos/running/7E79BC00-7E3C-4B19-9CDF-83F99FD73A23/tty'
I can then manually execute all the code inside the first-init.command
shell script successfully to get everything up and running.
that's is a very weird issue, it could be that first time the download got interrupted.
@AntonioMeireles would be possible to make corectl
tool to try to re-download the missing fail automatically?
It might have been an interrupted download, but I am not so sure... After the issue occurred, I removed my ~/kube-cluster
directory, re-ran the installation, and got the same error. The error happened immediately, before the download progress meter appears. If other folks arent seeing this, though, then maybe consider it a connectivity problem on my end.
I freshly installed the latest corectl and kube-cluster-osx today on OS X El Capitan 10.11.2 (15C50). When I click Setup->Initial setup of Kube-Cluster VMs, I get this error:
Full console log: