no good

gistfile1.txt

➜  chef-client  ls
Vagrantfile        chef-validator.pem
➜  chef-client  vu node2
Bringing machine 'node2' up with 'virtualbox' provider...
==> node2: Importing base box 'phusion/ubuntu-14.04-amd64'...
==> node2: Matching MAC address for NAT networking...
==> node2: Checking if box 'phusion/ubuntu-14.04-amd64' is up to date...
==> node2: Setting the name of the VM: chef-client_node2_1426853090304_55807
==> node2: Clearing any previously set forwarded ports...
==> node2: Clearing any previously set network interfaces...
==> node2: Preparing network interfaces based on configuration...
    node2: Adapter 1: nat
    node2: Adapter 2: hostonly
==> node2: Forwarding ports...
    node2: 22 => 2222 (adapter 1)
==> node2: Running 'pre-boot' VM customizations...
==> node2: Booting VM...
==> node2: Waiting for machine to boot. This may take a few minutes...
    node2: SSH address: 127.0.0.1:2222
    node2: SSH username: vagrant
    node2: SSH auth method: private key
    node2: Warning: Connection timeout. Retrying...
    node2: Warning: Remote connection disconnect. Retrying...
    node2:
    node2: Vagrant insecure key detected. Vagrant will automatically replace
    node2: this with a newly generated keypair for better security.
    node2:
    node2: Inserting generated public key within guest...
    node2: Removing insecure key from the guest if its present...
    node2: Key inserted! Disconnecting and reconnecting using new SSH key...
==> node2: Machine booted and ready!
==> node2: Checking for guest additions in VM...
==> node2: Setting hostname...
==> node2: Configuring and enabling network interfaces...
==> node2: Mounting shared folders...
    node2: /var/www => /Users/mwang/src/vagrants/chef-client/www
    node2: /vagrant => /Users/mwang/src/vagrants/chef-client
    node2: /tmp/vagrant-cache => /Users/mwang/.vagrant.d/cache/phusion/ubuntu-14.04-amd64
==> node2: Configuring cache buckets...
==> node2: Running provisioner: chef_client...
==> node2: Detected Chef (latest) is already installed
==> node2: Creating folder to hold client key...
==> node2: Uploading chef client validation key...
Generating chef JSON and uploading...
==> node2: Warning: Chef run list is empty. This may not be what you want.
==> node2: Running chef-client...
==> node2: stdin: is not a tty
==> node2: [2015-03-20T12:05:27+00:00] INFO: Forking chef instance to converge...
==> node2: [2015-03-20T12:05:27+00:00] WARN:
==> node2: * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
==> node2: SSL validation of HTTPS requests is disabled. HTTPS connections are still
==> node2: encrypted, but chef is not able to detect forged replies or man in the middle
==> node2: attacks.
==> node2:
==> node2: To fix this issue add an entry like this to your configuration file:
==> node2:
==> node2: ```
==> node2:   # Verify all HTTPS connections (recommended)
==> node2:   ssl_verify_mode :verify_peer
==> node2:
==> node2:   # OR, Verify only connections to chef-server
==> node2:   verify_api_cert true
==> node2: ```
==> node2:
==> node2: To check your SSL configuration, or troubleshoot errors, you can use the
==> node2: `knife ssl check` command like so:
==> node2:
==> node2: ```
==> node2:   knife ssl check -c /tmp/vagrant-chef/client.rb
==> node2: ```
==> node2:
==> node2: * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
==> node2: [2015-03-20T12:05:27+00:00] INFO: *** Chef 11.12.2 ***
==> node2: [2015-03-20T12:05:27+00:00] INFO: Chef-client pid: 1961
==> node2: [2015-03-20T12:05:30+00:00] INFO: Client key /etc/chef/client.pem is not present - registering

src/vagrants/chef-client