amazon-ec2 - 橡胶 ec2 部署重复的默认安全组

Question

运行以下命令时出现此错误: cap Rubber:create_staging
response_call': Duplicate => the specified rule \"peer: sg-86b557e9, TCP, from port: 1, to port: 65535, ALLOW\" already exists (Fog::Compute::AWS::Error) from /home/user/.rvm/gems/ruby-2.1.0/gems/excon-0.37.0/lib/excon/middlewares/response_parser.rb:26:in response_call'
来自/home/user/.rvm/gems/ruby-2.1.0/gems/excon-0.37.0/lib/excon/connection.rb:402:in response' from /home/user/.rvm/gems/ruby-2.1.0/gems/excon-0.37.0/lib/excon/connection.rb:272:in要求'
来自/home/user/.rvm/gems/ruby-2.1.0/gems/excon-0.37.0/lib/excon/middlewares/idempotent.rb:12:in error_call' from /home/user/.rvm/gems/ruby-2.1.0/gems/excon-0.37.0/lib/excon/middlewares/base.rb:10:in error_call'
来自/home/user/.rvm/gems/ruby-2.1.0/gems/excon-0.37.0/lib/excon/middlewares/base.rb:10:in error_call' from /home/user/.rvm/gems/ruby-2.1.0/gems/excon-0.37.0/lib/excon/connection.rb:292:in请求救援'
来自/home/user/.rvm/gems/ruby-2.1.0/gems/excon-0.37.0/lib/excon/connection.rb:229:in request' from /home/user/.rvm/gems/ruby-2.1.0/gems/excon-0.37.0/lib/excon/middlewares/idempotent.rb:12:in error_call'
来自/home/user/.rvm/gems/ruby-2.1.0/gems/excon-0.37.0/lib/excon/middlewares/base.rb:10:in error_call' from /home/user/.rvm/gems/ruby-2.1.0/gems/excon-0.37.0/lib/excon/middlewares/base.rb:10:in error_call'
来自/home/user/.rvm/gems/ruby-2.1.0/gems/excon-0.37.0/lib/excon/connection.rb:292:in rescue in request' from /home/user/.rvm/gems/ruby-2.1.0/gems/excon-0.37.0/lib/excon/connection.rb:229:in要求'
来自/home/user/.rvm/gems/ruby-2.1.0/gems/excon-0.37.0/lib/excon/middlewares/idempotent.rb:12:in error_call' from /home/user/.rvm/gems/ruby-2.1.0/gems/excon-0.37.0/lib/excon/middlewares/base.rb:10:in error_call'
来自/home/user/.rvm/gems/ruby-2.1.0/gems/excon-0.37.0/lib/excon/middlewares/base.rb:10:in error_call' from /home/user/.rvm/gems/ruby-2.1.0/gems/excon-0.37.0/lib/excon/connection.rb:292:in请求救援'
来自/home/user/.rvm/gems/ruby-2.1.0/gems/excon-0.37.0/lib/excon/connection.rb:229:in request' from /home/user/.rvm/gems/ruby-2.1.0/gems/fog-1.22.1/lib/fog/xml/sax_parser_connection.rb:35:in要求'
来自/home/user/.rvm/gems/ruby-2.1.0/gems/fog-1.22.1/lib/fog/xml.rb:21:in request' from /home/user/.rvm/gems/ruby-2.1.0/gems/fog-1.22.1/lib/fog/aws/compute.rb:462:in _要求'
来自/home/user/.rvm/gems/ruby-2.1.0/gems/fog-1.22.1/lib/fog/aws/compute.rb:457:in request' from /home/user/.rvm/gems/ruby-2.1.0/gems/fog-1.22.1/lib/fog/aws/requests/compute/authorize_security_group_ingress.rb:49:in authorize_security_group_ingress'
来自/home/user/.rvm/gems/ruby-2.1.0/gems/fog-1.22.1/lib/fog/aws/models/compute/security_group.rb:102:in authorize_port_range' from /home/user/.rvm/gems/ruby-2.1.0/gems/rubber-2.10.0/lib/rubber/cloud/aws.rb:380:in add_security_group_rule'
来自/home/user/.rvm/gems/ruby-2.1.0/gems/rubber-2.10.0/lib/rubber/cloud/aws.rb:481:in block (2 levels) in sync_security_groups' from /home/user/.rvm/gems/ruby-2.1.0/gems/rubber-2.10.0/lib/rubber/cloud/aws.rb:476:in每个'
来自/home/user/.rvm/gems/ruby-2.1.0/gems/rubber-2.10.0/lib/rubber/cloud/aws.rb:476:in block in sync_security_groups' from /home/user/.rvm/gems/ruby-2.1.0/gems/rubber-2.10.0/lib/rubber/cloud/aws.rb:405:in每个'
来自/home/user/.rvm/gems/ruby-2.1.0/gems/rubber-2.10.0/lib/rubber/cloud/aws.rb:405:in sync_security_groups' from /home/user/.rvm/gems/ruby-2.1.0/gems/rubber-2.10.0/lib/rubber/cloud/aws.rb:260:in setup_security_groups'
来自/home/user/.rvm/gems/ruby-2.1.0/gems/rubber-2.10.0/lib/rubber/cloud/aws.rb:75:in before_create_instance' from /home/user/.rvm/gems/ruby-2.1.0/gems/rubber-2.10.0/lib/rubber/thread_safe_proxy.rb:13:in method_missing'
来自/home/user/.rvm/gems/ruby-2.1.0/gems/rubber-2.10.0/lib/rubber/recipes/rubber/instances.rb:267:in block in create_instance' from /home/user/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/monitor.rb:211:in mon_synchronize'
来自/home/user/.rvm/gems/ruby-2.1.0/gems/rubber-2.10.0/lib/rubber/recipes/rubber/instances.rb:266:in create_instance' from /home/user/.rvm/gems/ruby-2.1.0/gems/rubber-2.10.0/lib/rubber/recipes/rubber/instances.rb:230:in create_instances' 中的 block (2 级)

Answer 1

我刚刚找到了一个解决方法，虽然我不确定它有多安全。

我进入我的实例并编辑了默认组。除了最基本的规则外，我删除了所有入站规则。然后我向任何人开放了这个:



这似乎解决了问题。

更新:这是在 recent commit 中修复的到橡胶。我目前指向 github repo，但您也可以等待 2.10.1 出来。