Chef-client package fetch error


#1

I started seeing this yesterday and Chef support indicates that this may be caused on their end. All of us in my company who are trying to bootstrap some node, using different Chef server setup, are seeing it. Is the rest of the community seeing it?

Chris

$ knife bootstrap leeds-fnkm -N leeds-fnkm -x user -P password -VV
INFO: Using configuration from /home/builder/.chef/knife.rb
Doing old-style registration with the validation key at /home/builder/.chef/alton-brown-arq-dev-validator.pem…
Delete your validation key in order to use your user credentials instead

Connecting to leeds-fnkm
DEBUG: Looking for bootstrap template in /opt/chef/embedded/apps/chef/lib/chef/knife/bootstrap/templates
DEBUG: Found bootstrap template in /opt/chef/embedded/apps/chef/lib/chef/knife/bootstrap/templates
DEBUG: Adding leeds-fnkm
DEBUG: establishing connection to leeds-fnkm:22
DEBUG: connection established
INFO: negotiating protocol version
DEBUG: remote is SSH-2.0-OpenSSH_4.3' DEBUG: local isSSH-2.0-Ruby/Net::SSH_2.9.2 x86_64-linux’
DEBUG: read 704 bytes
DEBUG: received packet nr 0 type 20 len 700
INFO: got KEXINIT from server
INFO: sending KEXINIT
DEBUG: queueing packet nr 0 type 20 len 1684
DEBUG: sent 1688 bytes
INFO: negotiating algorithms
DEBUG: negotiated:

  • kex: diffie-hellman-group-exchange-sha1
  • host_key: ssh-rsa
  • encryption_server: aes128-cbc
  • encryption_client: aes128-cbc
  • hmac_client: hmac-sha1
  • hmac_server: hmac-sha1
  • compression_client: none
  • compression_server: none
  • language_client:
  • language_server:
    DEBUG: exchanging keys
    DEBUG: queueing packet nr 1 type 34 len 20
    DEBUG: sent 24 bytes
    DEBUG: read 152 bytes
    DEBUG: received packet nr 1 type 31 len 148
    DEBUG: queueing packet nr 2 type 32 len 140
    DEBUG: sent 144 bytes
    DEBUG: read 720 bytes
    DEBUG: received packet nr 2 type 33 len 700
    DEBUG: queueing packet nr 3 type 21 len 20
    DEBUG: sent 24 bytes
    DEBUG: received packet nr 3 type 21 len 12
    DEBUG: beginning authentication of root' DEBUG: queueing packet nr 4 type 5 len 28 DEBUG: sent 52 bytes DEBUG: read 52 bytes DEBUG: received packet nr 4 type 6 len 28 DEBUG: trying none DEBUG: queueing packet nr 5 type 50 len 44 DEBUG: sent 68 bytes DEBUG: read 84 bytes DEBUG: received packet nr 5 type 51 len 60 DEBUG: allowed methods: publickey,gssapi-with-mic,password DEBUG: none failed DEBUG: trying publickey DEBUG: connecting to ssh-agent ERROR: could not connect to ssh-agent DEBUG: trying publickey (cb:de:74:1c:fb:5e:63:68:78:23:18:74:bc:93:a3:3c) DEBUG: queueing packet nr 6 type 50 len 348 DEBUG: sent 372 bytes DEBUG: read 84 bytes DEBUG: received packet nr 6 type 51 len 60 DEBUG: allowed methods: publickey,gssapi-with-mic,password DEBUG: trying password DEBUG: queueing packet nr 7 type 50 len 60 DEBUG: sent 84 bytes DEBUG: read 36 bytes DEBUG: received packet nr 7 type 52 len 12 DEBUG: password succeeded DEBUG: queueing packet nr 8 type 90 len 44 DEBUG: sent 68 bytes DEBUG: read 52 bytes DEBUG: received packet nr 8 type 91 len 28 INFO: channel_open_confirmation: 0 0 0 32768 INFO: sending channel request "env" DEBUG: queueing packet nr 9 type 98 len 44 INFO: sending channel request "pty-req" DEBUG: queueing packet nr 10 type 98 len 60 INFO: sending channel request "exec" DEBUG: queueing packet nr 11 type 98 len 5164 DEBUG: sent 5340 bytes DEBUG: read 88 bytes DEBUG: received packet nr 9 type 93 len 28 INFO: channel_window_adjust: 0 +2097152 DEBUG: received packet nr 10 type 99 len 12 INFO: channel_success: 0 DEBUG: read 68 bytes DEBUG: received packet nr 11 type 94 len 44 INFO: channel_data: 0 27b leeds-fnkm Installing Chef Client... DEBUG: read 100 bytes DEBUG: received packet nr 12 type 94 len 76 INFO: channel_data: 0 62b leeds-fnkm --2015-03-20 10:02:32-- https://www.chef.io/chef/install.sh DEBUG: read 68 bytes DEBUG: received packet nr 13 type 94 len 44 INFO: channel_data: 0 25b DEBUG: read 204 bytes DEBUG: received packet nr 14 type 94 len 28 INFO: channel_data: 0 12b DEBUG: received packet nr 15 type 94 len 28 INFO: channel_data: 0 2b leeds-fnkm Resolving www.chef.io... 199.27.76.65 DEBUG: received packet nr 16 type 94 len 76 INFO: channel_data: 0 47b DEBUG: read 52 bytes DEBUG: received packet nr 17 type 94 len 28 INFO: channel_data: 0 12b leeds-fnkm Connecting to www.chef.io|199.27.76.65|:443... connected. DEBUG: read 264 bytes DEBUG: received packet nr 18 type 94 len 124 INFO: channel_data: 0 100b leeds-fnkm ERROR: certificate common nameg.ssl.fastly.net’ doesn’t match requested host name www.chef.io'. DEBUG: read 84 bytes DEBUG: received packet nr 19 type 94 len 92 INFO: channel_data: 0 69b leeds-fnkm To connect to www.chef.io insecurely, use–no-check-certificate’.
    DEBUG: received packet nr 20 type 94 len 60
    INFO: channel_data: 0 37b
    leeds-fnkm Unable to establish SSL connection.
    DEBUG: read 84 bytes
    DEBUG: read 100 bytes
    DEBUG: received packet nr 21 type 94 len 60
    INFO: channel_data: 0 35b
    leeds-fnkm Starting first Chef Client run…
    DEBUG: read 140 bytes
    DEBUG: received packet nr 22 type 94 len 76
    INFO: channel_data: 0 48b
    leeds-fnkm bash: line 117: chef-client: command not found
    DEBUG: received packet nr 23 type 98 len 44
    INFO: channel_request: 0 exit-status false
    DEBUG: received packet nr 24 type 96 len 12
    INFO: channel_eof: 0
    DEBUG: received packet nr 25 type 97 len 12
    INFO: channel_close: 0
    DEBUG: queueing packet nr 12 type 97 len 28
    INFO: closing remaining channels (0 open)

#2

On Fri, Mar 20, 2015 at 10:08 AM, Fouts, Chris Chris.Fouts@sensus.com wrote:

I started seeing this yesterday and Chef support indicates that this may be
caused on their end. All of us in my company who are trying to bootstrap
some node, using different Chef server setup, are seeing it. Is the rest of
the community seeing it?

Well, we definitely cut the site over to be fronted by the Fastly CDN
yesterday, so this could be the cause, though I’m pretty sure the SSL
certificates have SNI.

Can you share what is the operating system and version of the machine
you’re trying to bootstrap?

  • Julian


[ Julian C. Dunn jdunn@aquezada.com * Sorry, I’m ]
[ WWW: http://www.aquezada.com/staff/julian * only Web 1.0 ]
[ gopher://sdf.org/1/users/keymaker/ * compliant! ]
[ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9 ]


#3

A quick follow up to Julian, if you need to get going right now, try adding:

–bootstrap-url “https://www.opscode.com/chef/install.sh

to your bootstrap command. The opscode.com domain doesn’t require SNI.

On Fri, Mar 20, 2015 at 2:41 PM, Julian C. Dunn jdunn@aquezada.com wrote:

On Fri, Mar 20, 2015 at 10:08 AM, Fouts, Chris Chris.Fouts@sensus.com wrote:

I started seeing this yesterday and Chef support indicates that this may be
caused on their end. All of us in my company who are trying to bootstrap
some node, using different Chef server setup, are seeing it. Is the rest of
the community seeing it?

Well, we definitely cut the site over to be fronted by the Fastly CDN
yesterday, so this could be the cause, though I’m pretty sure the SSL
certificates have SNI.

Can you share what is the operating system and version of the machine
you’re trying to bootstrap?

  • Julian


[ Julian C. Dunn jdunn@aquezada.com * Sorry, I’m ]
[ WWW: http://www.aquezada.com/staff/julian * only Web 1.0 ]
[ gopher://sdf.org/1/users/keymaker/ * compliant! ]
[ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9 ]