Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Issue with Cloudformation Template #3005

Open
KuruvaSomaSekhar opened this issue Mar 15, 2017 · 2 comments
Open

Issue with Cloudformation Template #3005

KuruvaSomaSekhar opened this issue Mar 15, 2017 · 2 comments

Comments

@KuruvaSomaSekhar
Copy link

KuruvaSomaSekhar commented Mar 15, 2017 •
edited
Loading

Today I tried to deploy flocker and docker swarm using Cloudformation template provided here. I started in N.Virginia region , but AMI provided in the default template doesn't exists in that region. I changed to Ubuntu Server 16.04 (ami-f4cc1de2). Then I started with required input parameters. It's started but after some time it rollbacked. Then I checked in Cloudformation Template-Resources location, it was saying that -WaitCondition timed out. Received 0 conditions when expecting 1. It started only three instances (2 Agent nodes, 1 Control node) instead of four nodes.

I logged in into Control node and observed logs in "/var/log/cloud-init-output.log" ,it's mostly saying like flocker itself not downloaded. Docker also not started before starting flocker installation. I'm not sure it's issue with Image I used or provided Cloudformation Template .
Find below logs from Control node

Cloud-init v. 0.7.8 running 'init-local' at Wed, 15 Mar 2017 08:53:53 +0000. Up 7.15 seconds.
Cloud-init v. 0.7.8 running 'init' at Wed, 15 Mar 2017 08:53:55 +0000. Up 9.11 seconds.
ci-info: +++++++++++++++++++++++++++++++++++++Net device info++++++++++++++++++++++++++++++++++++++
ci-info: +--------+------+----------------------------+---------------+-------+-------------------+
ci-info: | Device | Up | Address | Mask | Scope | Hw-Address |
ci-info: +--------+------+----------------------------+---------------+-------+-------------------+
ci-info: | eth0 | True | 172.31.26.206 | 255.255.240.0 | . | 0e:a1:07:24:af:7e |
ci-info: | eth0 | True | fe80::ca1:7ff:fe24:af7e/64 | . | link | 0e:a1:07:24:af:7e |
ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . | . |
ci-info: | lo | True | ::1/128 | . | host | . |
ci-info: +--------+------+----------------------------+---------------+-------+-------------------+
ci-info: +++++++++++++++++++++++++++++Route IPv4 info+++++++++++++++++++++++++++++
ci-info: +-------+-------------+-------------+---------------+-----------+-------+
ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |
ci-info: +-------+-------------+-------------+---------------+-----------+-------+
ci-info: | 0 | 0.0.0.0 | 172.31.16.1 | 0.0.0.0 | eth0 | UG |
ci-info: | 1 | 172.31.16.0 | 0.0.0.0 | 255.255.240.0 | eth0 | U |
ci-info: +-------+-------------+-------------+---------------+-----------+-------+
Generating public/private rsa key pair.
Your identification has been saved in /etc/ssh/ssh_host_rsa_key.
Your public key has been saved in /etc/ssh/ssh_host_rsa_key.pub.
The key fingerprint is:
SHA256:38p+R1RnC09upgJKxoX9rtUjGRxImjov6RRGvjK5P6c root@ip-172-31-26-206
The key's randomart image is:
+---[RSA 2048]----+
| +.. |
| .o+ . . .+|
| ..o. o . =oo|
| o .+ . + .* |
| *o S o +.+ |
| o *. . B +. |
| + = . + +.. |
| *... o .. . |
| ..E+ .+. . |
+----[SHA256]-----+
Generating public/private dsa key pair.
Your identification has been saved in /etc/ssh/ssh_host_dsa_key.
Your public key has been saved in /etc/ssh/ssh_host_dsa_key.pub.
The key fingerprint is:
SHA256:0u4Q90o3dkwAfv6vUveFaUJS58a9anSlzhvMq+VZ2TM root@ip-172-31-26-206
The key's randomart image is:
+---[DSA 1024]----+
| . |
| . . . . |
| . o. + . |
| . o... + o|
| o S .o.. +o|
| = . +o+*o+|
| . o =.=*BE+|
| + +.o o=+|
| o .+o. |
+----[SHA256]-----+
Generating public/private ecdsa key pair.
Your identification has been saved in /etc/ssh/ssh_host_ecdsa_key.
Your public key has been saved in /etc/ssh/ssh_host_ecdsa_key.pub.
The key fingerprint is:
SHA256:ktnkrGXJjNHeVS+NUZzNyznlu65sMZdYwv9rWdtwSVk root@ip-172-31-26-206
The key's randomart image is:
+---[ECDSA 256]---+
| o++|
| . . *E|
| . o o +.O|
| & o . o X.|
| = S . * =|
| = +.o|
| . +oB|
| .. =o|
| .o+o.|
+----[SHA256]-----+
Generating public/private ed25519 key pair.
Your identification has been saved in /etc/ssh/ssh_host_ed25519_key.
Your public key has been saved in /etc/ssh/ssh_host_ed25519_key.pub.
The key fingerprint is:
SHA256:deEqVfcdCOPAGvBX9OU4eTJOVwmK4u/dNgJafj54yLE root@ip-172-31-26-206
The key's randomart image is:
+--[ED25519 256]--+
| .. ...=+.+oo|
| .. .=o++=o+|
| ooooooO +o|
| ..oo oo * |
| .S . . |
| .= |
| =. |
| ..E.=.o |
| .+o+.. |
+----[SHA256]-----+
Generating locales (this might take a while)...
en_US.UTF-8... done
Generation complete.
Cloud-init v. 0.7.8 running 'modules:config' at Wed, 15 Mar 2017 08:53:57 +0000. Up 10.85 seconds.
@KuruvaSomaSekhar
Copy link
Author

Any update on this issue ?

@wallnerryan
Copy link
Contributor

@KuruvaSomaSekhar clusterhq shutdown in december 16. So those aws resources are probably destroyed.

You can try to find more help here: https://github.com/ScatterHQ/flocker where the project moved where some of the maintainers are trying to help where they can and people interested in using it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wallnerryan @KuruvaSomaSekhar