Skip to content

Conversation

fr3nd
Copy link

@fr3nd fr3nd commented Aug 2, 2017

aws-sdk-core conflicts with codedeploy-commands-1.0.0:

/usr/lib/ruby/2.1.0/rubygems/specification.rb:2064:in `raise_if_conflicts': Unable to activate codedeploy-commands-1.0.0, because aws-sdk-core-2.9.44 conflicts with aws-sdk-core (~> 2.6.11) (Gem::LoadError)
        from /usr/lib/ruby/2.1.0/rubygems/specification.rb:1262:in `activate'
        from /usr/lib/ruby/2.1.0/rubygems.rb:196:in `rescue in try_activate'
        from /usr/lib/ruby/2.1.0/rubygems.rb:193:in `try_activate'
        from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:132:in `rescue in require'
        from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:144:in `require'
        from /opt/codedeploy-local/gems/aws_codedeploy_agent-0.1/lib/instance_agent/plugins/codedeploy/codedeploy_control.rb:1:in `<top (required)>'
        from /opt/codedeploy-local/gems... (1701 more, please see e.stderr)

aws-sdk-core conflicts with codedeploy-commands-1.0.0:
```
/usr/lib/ruby/2.1.0/rubygems/specification.rb:2064:in `raise_if_conflicts': Unable to activate codedeploy-commands-1.0.0, because aws-sdk-core-2.9.44 conflicts with aws-sdk-core (~> 2.6.11) (Gem::LoadError)
        from /usr/lib/ruby/2.1.0/rubygems/specification.rb:1262:in `activate'
        from /usr/lib/ruby/2.1.0/rubygems.rb:196:in `rescue in try_activate'
        from /usr/lib/ruby/2.1.0/rubygems.rb:193:in `try_activate'
        from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:132:in `rescue in require'
        from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:144:in `require'
        from /opt/codedeploy-local/gems/aws_codedeploy_agent-0.1/lib/instance_agent/plugins/codedeploy/codedeploy_control.rb:1:in `<top (required)>'
        from /opt/codedeploy-local/gems... (1701 more, please see e.stderr)
```
@coveralls
Copy link

Coverage Status

Coverage remained the same at 94.584% when pulling 7a18181 on wuakitv:aws-sdk-core_version_fix into a72260d on aws:master.

@feverLu
Copy link
Contributor

feverLu commented Aug 2, 2017

This seems caused the aws sdk version conflict, the agent only use 2.9.2 for the most recent release, while the aws sdk exists on your host is 2.9.44. There are two ways you can migrate this temporarily:

  1. update the agent code as what you've done here

  2. Upgrade to the most recent host agent(currently support 2.9.2), and then install 2.9.2 aws sdk

@rohkat-aws rohkat-aws closed this Nov 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants