Open IvRRimum opened 8 years ago
I think i am on a lead:
in aws/cloudformation/common.py
I found this:
14 MAPPINGS = {
15
16 # TODO: we should build our own AMIs in all cases
17 # amzn-ami-minimal-hvm-2015.03.rc-1.x86_64-s3
18 "MinimalAmazonLinuxAMI": {
19 "us-east-1": {"instance": "ami-f02e0f98", "ebs": "ami-822e0fea"}
20 }
21 }
Its staticly added, when i try to find the ami's in the EC2, no records are found. So i need to create the AMI'S myself ? By witch template ?
Found the problem with those 3.
the AMI's where outdated, here are the valid ones:
16 # TODO: we should build our own AMIs in all cases
17 # amzn-ami-minimal-hvm-2015.03.rc-1.x86_64-s3
18 "MinimalAmazonLinuxAMI": {
19 "us-east-1": {"instance": "ami-c74dfcac", "ebs": "ami-314cfd5a"}
20 }
21 }
The comment helped me trace the problem - # amzn-ami-minimal-hvm-2015.03.rc-1.x86_64-s3
, a beer from me whoever put it there!
Master needs updating, admin should i do it, confirm ?
Ran into antoher problem.
This time its not the Configs, but the Scalings.
See below:
The following resource(s) failed to create: [ElasticsearchLbAutoScalingGroup, ElasticsearchMasterAutoScalingGroup, ElasticsearchDataAutoScalingGroup]. . Rollback requested by user.
Ideas are welcome!
The documentation is seriously lacking!
Finally, i got progress!
You must signal the AutoScaling resources from local konsole, fot them to proceed. Heres how you do it:
aws cloudformation signal-resource --stack-name search-elasticsearch --logical-resource-id ElasticsearchDataAutoScalingGroup --status SUCCESS --unique-id ElasticsearchDataAutoScalingGroup
I have alredy next error, but its validation error. Will try to figure it out
Finally got Elastiqsearch Clusters Working... AWS Documentation helped me( altho was a bit hard to understand ).
This repo's README still needs updates!!!
Thanks for finding these issues! The documentation for cosr-ops
is indeed lacking, we've done some work on the frontend and backend, the ops side is the next one to tackle!
The previous AMI IDs indeed seem to have been deleted, good find! I've updated the new IDs, thanks!
The AutoScaling hack looks like an issue or regression with the new AMIs, we clearly didn't need that before. Did you find more on that?
Let us know what updates you think the README needs, or feel free to send a pull request!
Cheers,
I ran into another problem.
Some things fail to CREATE, when calling
make aws_elasticsearch_create
Error listed below, any ideas?The following resource(s) failed to create: [ElasticsearchLbLaunchConfiguration, ElasticsearchMasterLaunchConfiguration, ElasticsearchDataLaunchConfiguration]. . Rollback requested by user.
Any ideas ?