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.

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

CloudFormation error. #43

Open
depohmel opened this issue Feb 12, 2018 · 3 comments
Open

CloudFormation error. #43

depohmel opened this issue Feb 12, 2018 · 3 comments

Comments

@depohmel
Copy link

I'm getting the following error from cloud formation.

This account is currently blocked and not recognized as a valid account. Please contact [email protected] if you have questions.
 ```

I was following: http://scaleio-framework.readthedocs.io/en/latest/user-guide/demo/ 
@kacole2
Copy link
Contributor

kacole2 commented Feb 12, 2018

@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.

@depohmel
Copy link
Author

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 [email protected] 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 [email protected] 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 [email protected] 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 [email protected] 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 [email protected] if you have questions.

@kacole2
Copy link
Contributor

kacole2 commented Feb 13, 2018

@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.
Imgur

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants