We’re working on getting knife-windows 1.0.0 out soon, which includes a lot
of improvements that are passed due.
To that end, we’ve just released knife-window 0.8.5. The only change from
0.8.4 is that the dependency on winrm-s is updated to a pessimistic
constraint on the patch version. This is to ensure it doesn’t pull in
winrm-s 0.3.0, which we will release soon, which depends on winrm 1.3.0,
which has some major changes.
Bryan
On Mon, May 18, 2015 at 1:19 PM, Bryan McLellan btm@loftninjas.org wrote:
To that end, we've just released knife-window 0.8.5. The only change from
0.8.4 is that the dependency on winrm-s is updated to a pessimistic
constraint on the patch version. This is to ensure it doesn't pull in
winrm-s 0.3.0, which we will release soon, which depends on winrm 1.3.0,
which has some major changes.
winrm-s 0.3.0 has now been released.
Bryan
On 22 May 2015, at 4:22 am, Bryan McLellan btm@loftninjas.org wrote:
On Mon, May 18, 2015 at 1:19 PM, Bryan McLellan btm@loftninjas.org wrote:
To that end, we've just released knife-window 0.8.5. The only change from 0.8.4 is that the dependency on winrm-s is updated to a pessimistic constraint on the patch version. This is to ensure it doesn't pull in winrm-s 0.3.0, which we will release soon, which depends on winrm 1.3.0, which has some major changes.winrm-s 0.3.0 has now been released.
Since this change has occurred; I’m getting some serious dependency issues with winrm-s and knife-ec2/knife windows.
No hassles with his version:
$ chef --version
Chef Development Kit Version: 0.5.1
chef-client version: 12.3.0
berks version: 3.2.3
kitchen version: 1.4.0
$ chef gem list |egrep 'knife|winrm'
em-winrm (0.6.0)
knife-ec2 (0.10.0)
knife-spork (1.5.0)
knife-windows (0.8.5, 0.8.4)
winrm (1.3.3, 1.3.2, 1.2.0)
winrm-s (0.2.4)
winrm-transport (1.0.0)
However with an Out Of the Box ChefDK 0.6.0 (Only since the update to a pessimistic constraint) I get the below errors.
Note: this worked fine with knife-ec2 and knife-windows and all the dependencies with ChefDK 0.6.0 prior to seeing this email about the constraint change.
$ chef --version
Chef Development Kit Version: 0.6.0
chef-client version: 12.3.0
berks version: 3.2.4
kitchen version: 1.4.0
$ chef gem list |egrep 'knife|winrm'
em-winrm (0.6.0)
knife-ec2 (0.10.0)
knife-spork (1.5.0)
knife-windows (0.8.5, 0.8.4)
winrm (1.3.3, 1.2.0)
winrm-s (0.2.4)
winrm-transport (1.0.0)
$ chef verify
Running verification for component 'berkshelf'
Running verification for component 'test-kitchen'
Running verification for component 'chef-client'
Running verification for component 'chef-dk'
Running verification for component 'chefspec'
Running verification for component 'rubocop'
Running verification for component 'fauxhai'
Running verification for component 'knife-spork'
Running verification for component 'kitchen-vagrant'
Running verification for component 'package installation'
.....
/opt/chefdk/embedded/lib/ruby/site_ruby/2.1.0/rubygems/specification.rb:2104:in raise_if_conflicts': Unable to activate winrm-s-0.2.4, because winrm-1.3.3 conflicts with winrm (~> 1.2.0) (Gem::ConflictError) from /opt/chefdk/embedded/lib/ruby/site_ruby/2.1.0/rubygems/specification.rb:1282:in activate'
from /opt/chefdk/embedded/lib/ruby/site_ruby/2.1.0/rubygems/specification.rb:1316:in block in activate_dependencies' from /opt/chefdk/embedded/lib/ruby/site_ruby/2.1.0/rubygems/specification.rb:1302:in each'
from /opt/chefdk/embedded/lib/ruby/site_ruby/2.1.0/rubygems/specification.rb:1302:in activate_dependencies' from /opt/chefdk/embedded/lib/ruby/site_ruby/2.1.0/rubygems/specification.rb:1284:in activate'
from /opt/chefdk/embedded/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:117:in require' from /Users/ted/.chefdk/gem/ruby/2.1.0/gems/knife-ec2-0.10.0/lib/chef/knife/ec2_server_create.rb:22:in <top (required)>'
from /opt/chefdk/embedded/apps/chef/lib/chef/knife/core/subcommand_loader.rb:44:in load' from /opt/chefdk/embedded/apps/chef/lib/chef/knife/core/subcommand_loader.rb:44:in block in load_commands'
from /opt/chefdk/embedded/apps/chef/lib/chef/knife/core/subcommand_loader.rb:44:in each' from /opt/chefdk/embedded/apps/chef/lib/chef/knife/core/subcommand_loader.rb:44:in load_commands'
from /opt/chefdk/embedded/apps/chef/lib/chef/knife.rb:127:in load_commands' from /opt/chefdk/embedded/apps/chef/lib/chef/knife.rb:208:in run'
from /opt/chefdk/embedded/apps/chef/lib/chef/application/knife.rb:142:in run' from /opt/chefdk/embedded/apps/chef/bin/knife:25:in <top (required)>'
from /opt/chefdk/bin/knife:51:in load' from /opt/chefdk/bin/knife:51:in '
.../opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/mixlib-shellout-2.0.1/lib/mixlib/shellout.rb:278:in invalid!': Expected process to exit with [0], but received '1' (Mixlib::ShellOut::ShellCommandFailed) ---- Begin output of /usr/bin/knife exec -E true ---- STDOUT: STDERR: /opt/chefdk/embedded/lib/ruby/site_ruby/2.1.0/rubygems/specification.rb:2104:in raise_if_conflicts': Unable to activate winrm-s-0.2.4, because winrm-1.3.3 conflicts with winrm (~> 1.2.0) (Gem::ConflictError)
from /opt/chefdk/embedded/lib/ruby/site_ruby/2.1.0/rubygems/specification.rb:1282:in activate' from /opt/chefdk/embedded/lib/ruby/site_ruby/2.1.0/rubygems/specification.rb:1316:in block in activate_dependencies'
from /opt/chefdk/embedded/lib/ruby/site_ruby/2.1.0/rubygems/specification.rb:1302:in each' from /opt/chefdk/embedded/lib/ruby/site_ruby/2.1.0/rubygems/specification.rb:1302:in activate_dependencies'
from /opt/chefdk/embedded/lib/ruby/site_ruby/2.1.0/rubygems/specification.rb:1284:in activate' from /opt/chefdk/embedded/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:117:in require'
from /Users/ted/.chefdk/gem/ruby/2.1.0/gems/knife-ec2-0.10.0/lib/chef/knife/ec2_server_create.rb:22:in <top (required)>' from /opt/chefdk/embedded/apps/chef/lib/chef/knife/core/subcommand_loader.rb:44:in load'
from /opt/chefdk/embedded/apps/chef/lib/chef/knife/core/subcommand_loader.rb:44:in block in load_commands' from /opt/chefdk/embedded/apps/chef/lib/chef/knife/core/subcommand_loader.rb:44:in each'
from /opt/chefdk/embedded/apps/chef/lib/chef/knife/core/subcommand_loader.rb:44:in load_commands' from /opt/chefdk/embedded/apps/chef/lib/chef/knife.rb:127:in load_commands'
from /opt/chefdk/embedded/apps/chef/lib/chef/knife.rb:208:in run' from /opt/chefdk/embedded/apps/chef/lib/chef/application/knife.rb:142:in run'
from /opt/chefdk/embedded/apps/chef/bin/knife:25:in <top (required)>' from /usr/bin/knife:51:in load'
from /usr/bin/knife:51:in <main>' ---- End output of /usr/bin/knife exec -E true ---- Ran /usr/bin/knife exec -E true returned 1 from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/mixlib-shellout-2.0.1/lib/mixlib/shellout.rb:265:in error!'
from /opt/chefdk/embedded/apps/chef-dk/lib/chef-dk/component_test.rb:99:in block in sh!' from /opt/chefdk/embedded/apps/chef-dk/lib/chef-dk/component_test.rb:99:in tap'
from /opt/chefdk/embedded/apps/chef-dk/lib/chef-dk/component_test.rb:99:in sh!' from /opt/chefdk/embedded/apps/chef-dk/lib/chef-dk/command/verify.rb:199:in block (2 levels) in class:Verify'
from /opt/chefdk/embedded/apps/chef-dk/lib/chef-dk/component_test.rb:78:in instance_eval' from /opt/chefdk/embedded/apps/chef-dk/lib/chef-dk/component_test.rb:78:in run_smoke_test'
from /opt/chefdk/embedded/apps/chef-dk/lib/chef-dk/command/verify.rb:268:in `block (2 levels) in invoke_tests'
--
Ted
GPG Key: 0x2B272DFD | E564 BCC1 F601 5D1F 01CD AC10 C37D D2B0 2B27 2DFD
On Mon, May 25, 2015 at 1:37 AM, Ted B ted@pobox.com wrote:
Since this change has occurred; I’m getting some serious dependency issues
with winrm-s and knife-ec2/knife windows.
I wasn't able to reproduce that. I've filed an issue based on your email,
could you update it with more environment information like platform?
Bryan
Ted,
Can you add any additional information to reproduce your issue on the
ticket please?
Bryan