security groups

29 views
Skip to first unread message

Brandon Casci

unread,
Nov 3, 2009, 12:52:35 PM11/3/09
to ec2-on-rails-discuss
I keep getting hung up here during an instance create, always at the step after creating the app_name_default security group.

It's creating the group, I've verified that, but fails when adding a rule to the group. Any ideas?

  * Creating new security group: loudcaster_production_default
  * Creating new rule: {"source_group_account"=>"a...@loudcaster.com", "source_group_name"=>"loudcaster_production_default"}
/usr/lib/ruby/gems/1.8/gems/amazon-ec2-0.5.5/lib/AWS.rb:282:in `aws_error?': The security group 'loudcaster_production_default' does not exist (AWS::InvalidGroupNotFound)
    from /usr/lib/ruby/gems/1.8/gems/amazon-ec2-0.5.5/lib/AWS.rb:220:in `make_request'
    from /usr/lib/ruby/1.8/net/http.rb:543:in `start'
    from /usr/lib/ruby/gems/1.8/gems/amazon-ec2-0.5.5/lib/AWS.rb:194:in `make_request'
    from /usr/lib/ruby/gems/1.8/gems/amazon-ec2-0.5.5/lib/AWS.rb:245:in `response_generator'
    from /usr/lib/ruby/gems/1.8/gems/amazon-ec2-0.5.5/lib/AWS/EC2/security_groups.rb:122:in `authorize_security_group_ingress'
    from /usr/lib/ruby/gems/1.8/gems/rubber-1.1.4/lib/rubber/cloud/aws.rb:117:in `add_security_group_rule'
    from /usr/lib/ruby/gems/1.8/gems/rubber-1.1.4/lib/rubber/recipes/rubber/security_groups.rb:179:in `sync_security_groups'
    from /usr/lib/ruby/gems/1.8/gems/rubber-1.1.4/lib/rubber/recipes/rubber/security_groups.rb:175:in `each'
    from /usr/lib/ruby/gems/1.8/gems/rubber-1.1.4/lib/rubber/recipes/rubber/security_groups.rb:175:in `sync_security_groups'
    from /usr/lib/ruby/gems/1.8/gems/rubber-1.1.4/lib/rubber/recipes/rubber/security_groups.rb:169:in `each'
    from /usr/lib/ruby/gems/1.8/gems/rubber-1.1.4/lib/rubber/recipes/rubber/security_groups.rb:169:in `sync_security_groups'
    from /usr/lib/ruby/gems/1.8/gems/rubber-1.1.4/lib/rubber/recipes/rubber/security_groups.rb:51:in `setup_security_groups'
    from /usr/lib/ruby/gems/1.8/gems/rubber-1.1.4/lib/rubber/recipes/rubber/instances.rb:158:in `create_instance'
    from /usr/lib/ruby/gems/1.8/gems/rubber-1.1.4/lib/rubber/recipes/rubber/instances.rb:36:in `load'
    from /usr/lib/ruby/gems/1.8/gems/capistrano-2.5.5/lib/capistrano/configuration/execution.rb:128:in `instance_eval'
    from /usr/lib/ruby/gems/1.8/gems/capistrano-2.5.5/lib/capistrano/configuration/execution.rb:128:in `invoke_task_directly_without_callbacks'
    from /usr/lib/ruby/gems/1.8/gems/capistrano-2.5.5/lib/capistrano/configuration/callbacks.rb:27:in `invoke_task_directly'
    from /usr/lib/ruby/gems/1.8/gems/capistrano-2.5.5/lib/capistrano/configuration/execution.rb:81:in `execute_task'
    from /usr/lib/ruby/gems/1.8/gems/capistrano-2.5.5/lib/capistrano/configuration/execution.rb:93:in `find_and_execute_task'
    from /usr/lib/ruby/gems/1.8/gems/capistrano-2.5.5/lib/capistrano/cli/execute.rb:45:in `execute_requested_actions_without_help'
    from /usr/lib/ruby/gems/1.8/gems/capistrano-2.5.5/lib/capistrano/cli/execute.rb:44:in `each'
    from /usr/lib/ruby/gems/1.8/gems/capistrano-2.5.5/lib/capistrano/cli/execute.rb:44:in `execute_requested_actions_without_help'
    from /usr/lib/ruby/gems/1.8/gems/capistrano-2.5.5/lib/capistrano/cli/help.rb:19:in `execute_requested_actions'
    from /usr/lib/ruby/gems/1.8/gems/capistrano-2.5.5/lib/capistrano/cli/execute.rb:33:in `execute!'
    from /usr/lib/ruby/gems/1.8/gems/capistrano-2.5.5/lib/capistrano/cli/execute.rb:14:in `execute'
    from /usr/lib/ruby/gems/1.8/gems/capistrano-2.5.5/bin/cap:4
    from /usr/bin/cap:19:in `load'
    from /usr/bin/cap:19




--
=========================================
I'm having a bout of spondylosis, so I can't hammer away at the keyboard too long. Please don't mistake short e-mails for rude e-mails..
=========================================

Brandon Casci

unread,
Nov 3, 2009, 3:35:56 PM11/3/09
to ec2-on-rails-discuss
I'm adding this to the issue on github, but for anyone else's benefit, I was able to get around the security group problems by setting

isolate_security_groups: false
Reply all
Reply to author
Forward
0 new messages