Github user ahgittin commented on the pull request:
https://github.com/apache/incubator-brooklyn/pull/705#issuecomment-114345523
Okay, I've added a more helpful error if this situation is encountered, and
that seems to be working:
| 2015-06-22 20:30:33,643 ERROR Detected that your EC2 account is a legacy
'classic' account, but the recommended instance type requires VPC. You can
specify the 'eu-central-1' region to avoid this problem, or you can specify a
classic-compatible instance type, or you can specify a subnet to use (taking
care that the subnet auto-assigns public IP's, or Brooklyn can see the subnet
or is configured to use a jump host for this location). For more information
see http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-vpc.html.
However the "fixes" aren't working:
* `networkName: subnet-ID` gives the same `VPCResourceNotSpecified` error;
maybe the syntax is off?
* `eu-central-1` (VPC) gives
`com.google.common.util.concurrent.UncheckedExecutionException:
java.lang.RuntimeException: security group
eu-central-1/jclouds#brooklyn-bxza-alex-eu-central-shoul-u2jy-nginx-ielm is not
available after creating` -- I saw one of those pages suggested max security
groups was 5, so maybe that's it
I'm investigating.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
