We found a root of that - SC does not like EC2 limitation " Create new instances only in one selected subnet " - despite we are creating instances only in one subnet !!!
Andrey Evtikhov
Lead Software Maintenance Engineer
Email: andrey_evtikhov_at_epam.com<mailto:andrey_evtikhov_at_epam.com>
Saint-Petersburg, Russia (GMT+3) epam.com<
http://www.epam.com>
CONFIDENTIALITY CAUTION AND DISCLAIMER
This message is intended only for the use of the individual(s) or entity(ies) to which it is addressed and contains information that is legally privileged and confidential. If you are not the intended recipient, or the person responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. All unintended recipients are obliged to delete this message and destroy any printed copies.
From: Andrey Evtikhov
Sent: Thursday, May 14, 2015 5:51 PM
To: 'starcluster_at_mit.edu'
Subject: launching c3.xlarge crashed every time
Hi there - we`re seeing a weird behavior - when I tried to start c3.xlarge we got following error:
>>> Cluster template settings are valid
>>> Starting cluster...
>>> Launching a 4-node VPC cluster...
>>> Creating security group _at_sc-test-big-cluster-ae...
>>> Creating placement group _at_sc-test-big-cluster-ae...
!!! ERROR - UnauthorizedOperation: You are not authorized to perform this operation. Encoded authorization failure message: ppMtGmkpwecYK0HVdCOo4hfojboeMHX_5o5qhpKVHhcllS3nduh13jiBVylikVNAI1UG0qbQmghBBxo3xizYmDF_ Cp2yjrXi3Az4-nsfK03-mKBIIsxDDTuscEQQUzwvhgb_Ln7550yfOqensIsYLq7OEm752IOcv4SugNcfDGWTUsEiJRy5p-FWS-yQhjWIjHZwjYFp6URUHyLBQHE7TlhIBg90q0A3XhchbhzihhRSlC2B9-UxR3oeJi_Tw0DD0bSQghS3WfkrbVkB_pTXVC9CKMbRop3Piql8sfUlzbA7 Ua9mtxAOxJwp_Ujv1L_VuaJaD_l1agwWiSTcbeRHLaQRLxam704PJlFmC-RV3_tWYUzhb7-jtT6ktawyStwPKJ2B7s0hMeWGBFzI1tkzlbZARQ5ywzLtlRiD5DoaUbfPX_Jm9a1Ur9pRxX5mPIoGO7ysZLljQ3x8Nlebu5ZHfm8vayd6ZKR0wz0dXjLS9LyjSGFpskfIMMwT47OtZ1F1
There is a table with different images we tried and it seems c3.xlarge failed everywhere : What could be a problem ? We can launch c3 manually from AWS console without any problem. But starcluster crashed every time .
AMI
description
c3.xlarge
m3.xlarge
t1.micro
t2.micro
i2.xlarge
r3.xlarge
c1.xlarge
ami-8a6d78e2
bioc-3.1-starcluster-ubuntu-14.04-100GB-201505061055
Fail
Success
Fail
Error*
ami-6b211202
starcluster-base-ubuntu-13.04-x86_64-hvm
Fail
Success
Fail
Error*
ami-3393a45a
starcluster-base-ubuntu-13.04-x86_64
Fail
Success
Success
Error*
Success
ami-52a0c53b
starcluster-base-ubuntu-12.04-x86_64-hvm
Fail
Success
Error
Success
Fail
Fail
Error*
ami-765b3e1f
starcluster-base-ubuntu-12.04-x86_64
Fail
Success
Error*
Success
If somebody met the same problem please let me know.
Cheers
Andrey
Received on Tue May 26 2015 - 08:53:06 EDT