Vagrant environment never completely started about quickstart

[ckt114]

I figured out that the problem is with the line below. I had to change it to netstat -an | grep :::443 && break to get past it for now.

quickstart/vagrant/scripts/configure_rancher_server.sh

Line 30 in 3b4d1c6

wget -T 5 -c https://localhost/ping && break

[ckt114]

Then I ran into another problem below. Has this been tested with vagrant? Thanks.

    server-01: ++ docker run --net=host --rm appropriate/curl -s 'https://127.0.0.1/v3-public/localProviders/local?action=login' -H 'content-type: application/json' --data-binary '{"username":"admin","password":"admin"}' --insecure
    server-01: Unable to find image 'appropriate/curl:latest' locally
    server-01: latest: Pulling from appropriate/curl
    server-01: ff3a5c916c92: Pulling fs layer
    server-01: 3151abf94102: Pulling fs layer
    server-01: 58ae3cb4aac4: Pulling fs layer
    server-01: 58ae3cb4aac4: Verifying Checksum
    server-01: 58ae3cb4aac4: Download complete
    server-01: 3151abf94102: Verifying Checksum
    server-01: 3151abf94102: Download complete
    server-01: ff3a5c916c92: Verifying Checksum
    server-01: ff3a5c916c92: Download complete
    server-01: ff3a5c916c92: Pull complete
    server-01: 3151abf94102: Pull complete
    server-01: 58ae3cb4aac4: Pull complete
    server-01: Digest: sha256:c8bf5bbec6397465a247c2bb3e589bb77e4f62ff88a027175ecb2d9e4f12c9d7
    server-01: Status: Downloaded newer image for appropriate/curl:latest
    server-01: + LOGINRESPONSE=
    server-01: ++ jq -r .token
    server-01: ++ echo
    server-01: + LOGINTOKEN=
    server-01: + docker run --net=host --rm appropriate/curl -s 'https://127.0.0.1/v3/users?action=changepassword' -H 'content-type: application/json' -H 'Authorization: Bearer ' --data-binary '{"currentPassword":"admin","newPassword":"admin"}' --insecure
    server-01: ++ docker run --net host --rm appropriate/curl -s https://127.0.0.1/v3/token -H 'content-type: application/json' -H 'Authorization: Bearer ' --data-binary '{"type":"token","description":"automation","name":""}' --insecure
    server-01: + APIRESPONSE=
    server-01: ++ jq -r .token
    server-01: ++ echo
    server-01: + APITOKEN=
    server-01: ++ docker run --net host --rm appropriate/curl -s https://127.0.0.1/v3/settings/server-url -H 'content-type: application/json' -H 'Authorization: Bearer ' -X PUT --data-binary '{"name":"server-url","value":"https://172.22.101.101"}' --insecure
    server-01: + SERVERURLRESPONSE=
    server-01: ++ docker run --net host --rm appropriate/curl -s https://127.0.0.1/v3/cluster -H 'content-type: application/json' -H 'Authorization: Bearer ' --data-binary '{"type":"cluster","rancherKubernetesEngineConfig":{"ignoreDockerVersion":false,"sshAgentAuth":false,"type":"rancherKubernetesEngineConfig","kubernetesVersion":"v1.11.2-rancher1-1","authentication":{"type":"authnConfig","strategy":"x509"},"network":{"type":"networkConfig","plugin":"flannel","flannelNetworkProvider":{"iface":"eth1"},"calicoNetworkProvider":null},"ingress":{"type":"ingressConfig","provider":"nginx"},"services":{"type":"rkeConfigServices","kubeApi":{"podSecurityPolicy":false,"type":"kubeAPIService"},"etcd":{"type":"etcdService","extraArgs":{"heartbeat-interval":500,"election-timeout":5000}}}},"name":"quickstart"}' --insecure
    server-01: + CLUSTERRESPONSE=
    server-01: ++ jq -r .id
    server-01: ++ echo
    server-01: + CLUSTERID=
    server-01: ++ docker run --net=host --rm appropriate/curl -s https://127.0.0.1/v3/clusterregistrationtoken -H 'content-type: application/json' -H 'Authorization: Bearer ' --data-binary '{"type":"clusterRegistrationToken","clusterId":""}' --insecure
    server-01: + CLUSTERREGTOKEN=
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what

[tbigby-kristin]

I've had the same two issues today. Thanks for the tip about using netstat rather than wget.

I've tried re-provisioning server-01 several times to get the provisioning script to work.

It seems as though lines 35-38 of configure_rancher_server.sh only intermittently work. Sometimes it will correctly return the data to LOGINRESPONSE, and then the remainder of the script works. Other times, it returns blank and of course nothing else in the script works.

I suspect more of a bug in the Vagrant base VM somehow? I can't see any logical reason why it works sometimes and not others with no changes.

But to re-run the script run: 'vagrant provision server-01'. Then after you get lucky and that is successful, you can 'vagrant provision node-01' too which seemed to work first try for me.

[ckt114]

@tbigby-kristin I was wondering when Rancher is going to look into this issue so I went ahead and make some modification to make it work. Below is the PR if you're interested.

#29

[mahendrashelke]

I am in the same boat , I don't think this script was tested before releasing it to the masses.

while true; do wget -T 5 -c https://localhost/ping && break sleep 5 done

[tbigby-kristin]

@chngtrn Thanks very much for the PR - worked well for me rebuilding my cluster just now.

[ckt114]

@chngtrn Thanks very much for the PR - worked well for me rebuilding my cluster just now.

No problem. Glad I could help.