-
Notifications
You must be signed in to change notification settings - Fork 102
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
Cant launch cluster in VPC - WARNING: undefined method `group_id' for nil:NilClass #295
Comments
I believe the offending statement may be the Closing this as a duplicate. |
@temujin9 sorry, i should have said. I tried it without auto_elastic_ip, and also declaring an elastic_ip and got the same error and resulting stack trace. i just retried that too and have the same issue. I thought that maybe it wasnt fetching the group id of the security group it had created? |
Hrm; okay, that's certainly possible. Two things to try:
Let me know if either of those fixes your problem. If it's the former, I'll reopen this, since that's a novel bug. |
I removed the dash, and im already running ironfan (4.10.3), but the problem still persists. thanks for your help |
Latest is 4.10.4, which shouldn't change this at all. Okay, reopening, this is novel. Can you drop the security group statement entirely? I want to see if it's the one you're stating, or one of the built-in groups, that's causing this. |
I just deleted the statement, and it still presents the same error. What exactly do you mean by built in groups? |
The facet and the cluster both should be creating security groups named Cheers, Nathaniel Eliot On Wed, Jun 5, 2013 at 11:59 AM, willejs notifications@github.com wrote:
|
So, it seems that its actually creating the cluster and facet security groups in ec2 not in the vpc atall. Strange? Im going to have a read of the code later to see if i can see whats going on. any ideas? |
Couldent see anything obvious when i browsed through the source. Any chance you could have a quick look? |
Hello. My conf:
Stack trace:
|
Note: I got the same stack trace if I move the code outside the face block |
@willejs - I'm 90% certain there's something b0rked about the implementation of security groups against VPC, such that it's creating those automatic groups as regular groups instead of VPC groups. I don't remember it doing so in past, so it's likely a regression, but its been a while since I last used the VPC setup. I can't promise a high-speed fix on this one: with the transition to private consulting, I'm juggling a lot of balls. I can say that bug-fixes take priority over new features, and so this will probably get addressed fairly soon. If you're feeling gutsy, the steps to start tracking down the problem yourself are very basically: a) clone the Ironfan repo, b) point your homebase at the clone, c) start dropping in diagnostic code snippets, and trying commands you know will exercise those snippets. Lemme know if you go this route and want additional pointers. @lyrixx - this looks like a different problem; could you please open a new issue? |
When trying to launch a cluster, i receive the following error:
http://pastebin.com/r29jSrWd
Really cant understand exactly why or where this is coming from, scanned the code and tripple checked the cluster definition against docs and examples, with no luck.
It is creating the security group and rules, but then fails.
The text was updated successfully, but these errors were encountered: