Closed robhaswell closed 8 years ago
I was unable to verify that my install had completed once I had finished the configuration stage, following the instructions at http://build.clusterhq.com/results/docs/containerized-uft-FLOC-2993/build-10115/labs/installer.html.
A transcript is below:
rob@spirit:~/Projects/uft-installer-test-2015-09-21$ uft-flocker-install cluster.yml && uft-flocker-config cluster.yml && uft-flocker-plugin-install cluster.yml Attempting to connect to 54.76.148.4:22... Connected to 54.76.148.4:22 after 0.00 seconds! Attempting to connect to 54.77.16.194:22... Connected to 54.77.16.194:22 after 0.00 seconds! Attempting to connect to 54.77.82.27:22... Connected to 54.77.82.27:22 after 0.00 seconds! Attempting to connect to ec2-52-19-194-242.eu-west-1.compute.amazonaws.com:22... Connected to ec2-52-19-194-242.eu-west-1.compute.amazonaws.com:22 after 0.00 seconds! Enabled root login for 54.77.82.27 Enabled root login for 54.76.148.4 Enabled root login for 54.77.16.194 Enabled root login for ec2-52-19-194-242.eu-west-1.compute.amazonaws.com Running install for 54.76.148.4 ... Running install for 54.77.16.194 ... Running install for 54.77.82.27 ... Running install for ec2-52-19-194-242.eu-west-1.compute.amazonaws.com ... Completed install for ec2-52-19-194-242.eu-west-1.compute.amazonaws.com Completed install for 54.77.82.27 Completed install for 54.76.148.4 Completed install for 54.77.16.194 Installed clusterhq-flocker-node on all nodes To configure and deploy the cluster: uft-flocker-config cluster.yml Initialized cluster CA. Created control cert. Generated aa05a7f9-34e4-4586-8f28-e4f6ebaecf85 for 54.76.148.4 Generated e512d508-3099-422b-962e-8425ffb6c09f for 54.77.16.194 Generated 45432fc2-b009-4030-94a7-843a9c348a25 for 54.77.82.27 Created user key for user Making /etc/flocker directory on all nodes Uploading keys to respective nodes: * Uploaded control cert & key to control node. * Uploaded node crt to 54.77.16.194 * Uploaded cluster cert to 54.77.16.194 * Uploaded node key to 54.77.16.194 * Uploaded agent.yml to 54.77.16.194 * Uploaded cluster cert to 54.76.148.4 * Uploaded node crt to 54.76.148.4 * Uploaded cluster cert to 54.77.82.27 * Uploaded node key to 54.76.148.4 * Uploaded agent.yml to 54.76.148.4 * Uploaded node crt to 54.77.82.27 * Uploaded agent.yml to 54.77.82.27 * Uploaded node key to 54.77.82.27 * Uploaded cluster cert to ec2-52-19-194-242.eu-west-1.compute.amazonaws.com * Uploaded control key to ec2-52-19-194-242.eu-west-1.compute.amazonaws.com * Uploaded control crt to ec2-52-19-194-242.eu-west-1.compute.amazonaws.com Skipping installing new docker binary because we're on ubuntu/centos, assuming we installed a sufficiently recent one already. Generating plugin certs Generated plugin certs for 54.76.148.4 Generated plugin certs for 54.77.16.194 Generated plugin certs for 54.77.82.27 Uploading plugin certs... Uploaded plugin cert for 54.77.82.27 Uploaded plugin cert for 54.77.82.27 Uploaded plugin cert for 54.77.16.194 Uploaded plugin cert for 54.76.148.4 Uploaded plugin cert for 54.76.148.4 Uploaded plugin cert for 54.77.16.194 Uploaded plugin certs Installing flocker plugin Using 54.76.148.4 => 172.31.37.222 Installing plugin for 54.76.148.4 ... Using 54.77.16.194 => 172.31.42.24 Installing plugin for 54.77.16.194 ... Using 54.77.82.27 => 172.31.47.151 Installing plugin for 54.77.82.27 ... Completed plugin install for 54.76.148.4 Completed plugin install for 54.77.82.27 Completed plugin install for 54.77.16.194 Creating the /run/docker/plugins folder Writing flocker-docker-plugin upstart job to 54.76.148.4 running command: ssh -o LogLevel=error -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -i /host/Users/rob/Projects/uft-installer-test-2015-09-21/terraform/uft-installer.pem root@54.76.148.4 bash -c 'echo; cat <<EOF > /etc/init/flocker-docker-plugin.conf # flocker-plugin - flocker-docker-plugin job file description "Flocker Plugin service" author "ClusterHQ <support@clusterhq.com>" respawn env FLOCKER_CONTROL_SERVICE_BASE_URL=https://ec2-52-19-194-242.eu-west-1.compute.amazonaws.com:4523/v1 env MY_NETWORK_IDENTITY=172.31.37.222 env PYTHONPATH=/opt/flocker/lib/python2.7/site-packages/:\$PYTHONPATH exec /opt/flocker/bin/flocker-docker-plugin EOF service flocker-docker-plugin restart ' stop: Unknown instance: Creating the /run/docker/plugins folder Writing flocker-docker-plugin upstart job to 54.77.16.194 running command: ssh -o LogLevel=error -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -i /host/Users/rob/Projects/uft-installer-test-2015-09-21/terraform/uft-installer.pem root@54.77.16.194 bash -c 'echo; cat <<EOF > /etc/init/flocker-docker-plugin.conf # flocker-plugin - flocker-docker-plugin job file description "Flocker Plugin service" author "ClusterHQ <support@clusterhq.com>" respawn env FLOCKER_CONTROL_SERVICE_BASE_URL=https://ec2-52-19-194-242.eu-west-1.compute.amazonaws.com:4523/v1 env MY_NETWORK_IDENTITY=172.31.42.24 env PYTHONPATH=/opt/flocker/lib/python2.7/site-packages/:\$PYTHONPATH exec /opt/flocker/bin/flocker-docker-plugin EOF service flocker-docker-plugin restart ' stop: Unknown instance: Creating the /run/docker/plugins folder Writing flocker-docker-plugin upstart job to 54.77.82.27 running command: ssh -o LogLevel=error -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -i /host/Users/rob/Projects/uft-installer-test-2015-09-21/terraform/uft-installer.pem root@54.77.82.27 bash -c 'echo; cat <<EOF > /etc/init/flocker-docker-plugin.conf # flocker-plugin - flocker-docker-plugin job file description "Flocker Plugin service" author "ClusterHQ <support@clusterhq.com>" respawn env FLOCKER_CONTROL_SERVICE_BASE_URL=https://ec2-52-19-194-242.eu-west-1.compute.amazonaws.com:4523/v1 env MY_NETWORK_IDENTITY=172.31.47.151 env PYTHONPATH=/opt/flocker/lib/python2.7/site-packages/:\$PYTHONPATH exec /opt/flocker/bin/flocker-docker-plugin EOF service flocker-docker-plugin restart ' stop: Unknown instance: rob@spirit:~/Projects/uft-installer-test-2015-09-21$ uft-flocker-volumes list-nodes Unhandled Error Traceback (most recent call last): Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused.
can't reproduce, and lots of bugs have been fixed since this bug report. can you try this again and reopen it if you still have the problem?
I was unable to verify that my install had completed once I had finished the configuration stage, following the instructions at http://build.clusterhq.com/results/docs/containerized-uft-FLOC-2993/build-10115/labs/installer.html.
A transcript is below: