Yes that was the case, incompatible files. I upgraded my chef-client to v12.0.3 and it works now. Thanks!
Chris
From: Fouts, Chris [mailto:Chris.Fouts@Sensus.com]
Sent: Wednesday, January 14, 2015 5:24 PM
To: chef@lists.opscode.com; Steven Murawski
Subject: [chef] RE: RE: Pleae help with windows bootstrap
Ok my bad, I had to use single quotes for the username and password. But now I get this. Do I have an incompatible windows gem?
bootstrap windows winrm mynode.domain.com -x ‘Administrator’ -P ‘password’ -p 5985 -VV
Waiting for remote response before bootstrap.mynode.domain.com .
Mynode.domain.com Response received.
Remote node responded after 0.01 minutes.
Bootstrapping Chef on mynode.domain.com
DEBUG: Looking for bootstrap template in /opt/chef/embedded/lib/ruby/gems/2.1.0/gems/knife-windows-0.8.2/lib/chef/knife/bootstrap
DEBUG: Found bootstrap template in /opt/chef/embedded/lib/ruby/gems/2.1.0/gems/knife-windows-0.8.2/lib/chef/knife/bootstrap
ERROR: ArgumentError: wrong number of arguments (3 for 4)
Chris
From: Fouts, Chris [mailto:Chris.Fouts@Sensus.com]
Sent: Wednesday, January 14, 2015 4:41 PM
To: Steven Murawski; chef@lists.opscode.commailto:chef@lists.opscode.com
Subject: [chef] RE: Pleae help with windows bootstrap
I’m bootstrapping a Windows Server 2012 R2 node from a RHEL 5.11 chef-client.
Chris
From: Steven Murawski [mailto:steven.murawski@gmail.com]
Sent: Wednesday, January 14, 2015 4:33 PM
To: Fouts, Chris; chef@lists.opscode.commailto:chef@lists.opscode.com
Subject: Re: [chef] Pleae help with windows bootstrap
Are you bootstrapping from a Windows node or a Linux node? What OS is the windows node?
If you are attempting from a linux or Mac node, could you try (replacing the url with the fqdn or ip of your target node)
curl --header “Content-Type: application/soap+xml;charset=UTF-8” --header “WSMANIDENTIFY: unauthenticated” http://192.168.1.82:5985/wsman --data ‘<s:Envelope xmlns:s=“http://www.w3.org/2003/05/soap-envelope” xmlns:wsmid=“http://schemas.dmtf.org/wbem/wsman/identity/1/wsmanidentity.xsd”><s:Header/><s:Body>wsmid:Identify/</s:Body></s:Envelope>’
or if on Windows
test-wsman 192.168.1.82
–
Steven Murawski
Community Software Development Engineer @ Chef
Microsoft MVP - PowerShell
http://stevenmurawski.comhttp://stevenmurawski.com/
On January 14, 2015 at 3:26:50 PM, Fouts, Chris (chris.fouts@sensus.commailto:chris.fouts@sensus.com) wrote:
With the help of this group I was able to get this working when I had chef-client v11.x, and chef-server v11.x. I moved to chef-client v12.0 and Chef 12 Enterprise. Again, as before, I followed these instructions: https://docs.chef.io/plugin_knife_windows.html to set up winrm on the Windows box, which checks out.
I do…
knife bootstrap windows winrm ‘mynode.domain.com’ -x domain\Administrator -P password -p 5985 -VV
INFO: Using configuration from /opt/jenkins/workspace/Chef-Deploy-RNIs/chef-deploy-leeds/.chef/knife.rb
Waiting for remote response before bootstrap
…DEBUG:
Adding leed-dc.davis.sensus.lab
DEBUG: :session => :init
DEBUG: :relay_to_servers => echo . & echo Response received.
DEBUG: :relayed => mynode.domain.com
DEBUG: leed-dc.davis.sensus.lab => :run_command
(above lines repeated 12 times)
ERROR: No response received from remote node after 1.84 minutes, giving up.
ERROR: Network Error: getaddrinfo: Name or service not known (http://mynode.domain.com:5985)
Check your knife configuration and network settings
Here’s my knife.rb (secret values changed)
current_dir = File.dirname(FILE)
log_level :info
log_location STDOUT
node_name "jenkins"
client_key "#{current_dir}/jenkins.pem"
validation_client_name "chef-validator"
validation_key “#{current_dir}/chef-validator.pem"
chef_server_url “https://mychefserver.domain.com/organizations/myorg"
cache_type 'BasicFile’
cache_options( :path => “#{ENV[‘HOME’]}/.chef/checksums” )
cookbook_path [”#{current_dir}/…/chef-repo/cookbooks”]
knife[:editor]=“vim”