etcdctl and fleetctl fail to download because of curl SSL verification error in 0.4.6
Closed this issue · 1 comments
deftdawg commented
Here's the output from iTerm, at the end it gets stuck in an infinite loop getting it's connections to port 8080 refused.
Installing k8s files to master and nodes:
Warning: Permanently added '[127.0.0.1]:2222' (ED25519) to the list of known hosts.
master.tgz 100% 23MB 23.1MB/s 00:01
Warning: Permanently added '[127.0.0.1]:2200' (ED25519) to the list of known hosts.
nodes.tgz 100% 16MB 16.1MB/s 00:00
Warning: Permanently added '[127.0.0.1]:2201' (ED25519) to the list of known hosts.
nodes.tgz 100% 16MB 16.1MB/s 00:00
Done installing ...
Connection to 127.0.0.1 closed.
Downloading etcdctl 2.0.12 for OS X
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 407 0 407 0 0 1593 0 --:--:-- --:--:-- --:--:-- 2055
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: http://curl.haxx.se/docs/sslcerts.html
curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
Connection to 127.0.0.1 closed.
Downloading fleetctl v0.10.2 for OS X
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 410 0 410 0 0 2164 0 --:--:-- --:--:-- --:--:-- 2216
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: http://curl.haxx.se/docs/sslcerts.html
curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
etcd cluster:
/Applications/CoreOS k8s Cluster.app/Contents/Resources/first-init.command: line 166: /Users/ged/coreos-k8s-cluster/bin/etcdctl: No such file or directory
fleetctl list-machines:
/Applications/CoreOS k8s Cluster.app/Contents/Resources/first-init.command: line 174: /Users/ged/coreos-k8s-cluster/bin/fleetctl: No such file or directory
Installing fleet units from '~/coreos-k8s-cluster/fleet' folder:
/Applications/CoreOS k8s Cluster.app/Contents/Resources/first-init.command: line 179: /Users/ged/coreos-k8s-cluster/bin/fleetctl: No such file or directory
/Applications/CoreOS k8s Cluster.app/Contents/Resources/first-init.command: line 180: /Users/ged/coreos-k8s-cluster/bin/fleetctl: No such file or directory
Finished installing fleet units
/Applications/CoreOS k8s Cluster.app/Contents/Resources/first-init.command: line 182: /Users/ged/coreos-k8s-cluster/bin/fleetctl: No such file or directory
Waiting for Kubernetes cluster to be ready. This can take a few minutes...
error: couldn't read version from server: Get http://172.17.15.101:8080/api: dial tcp 172.17.15.101:8080: connection refused
/Applications/CoreOS k8s Cluster.app/Contents/Resources/first-init.command: line 190: spin: i++%0: division by 0 (error token is "0")
error: couldn't read version from server: Get http://172.17.15.101:8080/api: dial tcp 172.17.15.101:8080: connection refused
\error: couldn't read version from server: Get http://172.17.15.101:8080/api: dial tcp 172.17.15.101:8080: connection refused
|error: couldn't read version from server: Get http://172.17.15.101:8080/api: dial tcp 172.17.15.101:8080: connection refused
....
rimusz commented
fix released with v0.4.7