Open depohmel opened 6 years ago
@depohmel can you give me a bit more info to help me and @dvonthenen debug this issue for you? I also want to verify you are using the US West N. California
region.
I just ran it following the directions as laid out and all resources came up and were deployed as expected.
Hi @kacole2, yes i'm using US West N. California
So I was following the guide (thru ui part) I uploaded http://scaleio-framework.readthedocs.io/en/latest/user-guide/Framework_Testing_Cluster_RHEL7.json and clicked Create.
Everything was fine until instances creation. Looks it failing to use AMIs form your account.
11:38:03 UTC-0800 | DELETE_COMPLETE | AWS::EC2::Instance | MesosAgent1 |
-- | -- | -- | -- | --
| 11:37:43 UTC-0800 | ROLLBACK_IN_PROGRESS | AWS::CloudFormation::Stack | ScaleIO-Test | The following resource(s) failed to create: [ScaleIONode1, ScaleIONode2, MesosAgent2, MesosMaster, MesosAgent1]. . Rollback requested by user.
| 11:37:42 UTC-0800 | CREATE_FAILED | AWS::EC2::Instance | ScaleIONode1 | This account is currently blocked and not recognized as a valid account. Please contact aws-verification@amazon.com if you have questions.
| 11:37:42 UTC-0800 | CREATE_FAILED | AWS::EC2::Instance | MesosAgent2 | This account is currently blocked and not recognized as a valid account. Please contact aws-verification@amazon.com if you have questions.
| 11:37:42 UTC-0800 | CREATE_FAILED | AWS::EC2::Instance | ScaleIONode2 | This account is currently blocked and not recognized as a valid account. Please contact aws-verification@amazon.com if you have questions.
| 11:37:41 UTC-0800 | CREATE_FAILED | AWS::EC2::Instance | MesosMaster | This account is currently blocked and not recognized as a valid account. Please contact aws-verification@amazon.com if you have questions.
| 11:37:41 UTC-0800 | CREATE_FAILED | AWS::EC2::Instance | MesosAgent1 | This account is currently blocked and not recognized as a valid account. Please contact aws-verification@amazon.com if you have questions.
@depohmel Assuming it's trying to place it in us-west-1
because that seems to work for me. I just deployed it again without any issue
Here are the AMIs in use. ami-64174404 ami-d51447b5 ami-65174405 ami-c21a4ba2 ami-441a4b24 ami-15184975
You can go to your EC2 console, click on AMIs, then hit the drop down for public images and you should see them available to you.
I'm getting the following error from cloud formation.