[chef] Re: Error running knife winrm

[Sölvi Páll Ásgeirsson < >]

Hi

I'm hitting the exact same issue - I'd also appreciate hints.

$ rpm -qa chef chef-server

chef-server-11.0.8-1.el6.x86_64

chef-11.4.4-1.el6.x86_64

$ knife winrm -VV "role:some_role" 'chef-client c:/chef/client.rb'

DEBUG: Signing the request as xxxx

DEBUG: Sending HTTP Request via GET to chef-server:443//search/node

DEBUG: ---- HTTP Status and Header Data: ----

DEBUG: HTTP 1.1 200 OK

DEBUG: server: nginx/1.2.3

DEBUG: date: Sun, 05 May 2013 20:52:45 GMT

DEBUG: content-type: application/json

DEBUG: transfer-encoding: chunked

DEBUG: connection: close

DEBUG: x-ops-api-info: flavor=osc;version=11.0.2;erchef=1.2.6

DEBUG: content-encoding: gzip

DEBUG: ---- End HTTP Status/Header Data ----

DEBUG: decompressing gzip response

FATAL: 1 node found, but does not have the required attribute (fqdn) to establish the connection. Try setting another attribute to open the connection using --attribute.

$ knife search 'role:some_role' -a fqdn

1 items found

some-host.fqdn:

  fqdn: some-host.fqdn

regards,

Sölvi Páll Á.

On Thu, May 2, 2013 at 2:06 PM, Jeppe Nejsum Madsen < " target="_blank"> > wrote:

Hi,

When running

$ knife winrm -VV "name:vmtest2.09b08bebde2d44ab9f6d19c28c86f56d.econ-azu-vm1.3744114705.europewest.internal.cloudapp.net" -p 5990

I get the following error:

DEBUG: Signing the request as xxxx
DEBUG: Sending HTTP Request via GET to api.opscode.com:443/organizations/xxxx/search/node
DEBUG: ---- HTTP Status and Header Data: ----
DEBUG: HTTP 1.1 200 OK
DEBUG: server: ngx_openresty
DEBUG: date: Thu, 02 May 2013 14:02:37 GMT
DEBUG: content-type: application/json
DEBUG: transfer-encoding: chunked
DEBUG: connection: close
DEBUG: x-ops-api-info: flavor=ohc;version=10.0.0;oc_erchef=0.19.11
DEBUG: content-encoding: gzip
DEBUG: ---- End HTTP Status/Header Data ----
DEBUG: decompressing gzip response
FATAL: 1 node found, but does not have the required attribute (fqdn) to establish the connection. Try setting another attribute to open the connection using --attribute.

Yet the fqdn attribute is there:

$ knife node show vmtest2.09b08bebde2d44ab9f6d19c28c86f56d.econ-azu-vm1.3744114705.europewest.internal.cloudapp.net -a fqdn
vmtest2.09b08bebde2d44ab9f6d19c28c86f56d.econ-azu-vm1.3744114705.europewest.internal.cloudapp.net:
  fqdn: vmtest2.09b08bebde2d44ab9f6d19c28c86f56d.econ-azu-vm1.3744114705.europewest.internal.cloudapp.net

Any hints?

/Jeppe