jtalks-org / jtalks-vm

Virtual Machines configured by Vagrant (VirtualBox + Chef) in order to start environment for JTalks projects much faster and in a more repeatable manner.
1 stars 3 forks source link

error at running chief solo #7

Open jonua opened 9 years ago

jonua commented 9 years ago

when I exec vagrant up, I receive an error:

...
ERROR: Cookbook loaded at path(s) [/tmp/vagrant-chef/ef3e5ee91657285c71348b704c51177c/cookbooks/openssl] has invalid metadata: The `name' attribute is required in cookbook metadata
==> default: [2015-02-28T19:38:59+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
...

full trace:

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'precise32' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Adding box 'precise32' (v0) for provider: virtualbox
    default: Downloading: http://files.vagrantup.com/precise32.box
==> default: Successfully added box 'precise32' (v0) for 'virtualbox'!
==> default: Importing base box 'precise32'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: jtalks-vm_default_1425152208485_24024
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 80 => 4000 (adapter 1)
    default: 22 => 2222 (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection timeout. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: 
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default: 
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if its present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: The guest additions on this VM do not match the installed version of
    default: VirtualBox! In most cases this is fine, but in rare cases it can
    default: prevent things such as shared folders from working properly. If you see
    default: shared folder errors, please make sure the guest additions within the
    default: virtual machine match the version of VirtualBox you have installed on
    default: your host and reload your VM.
    default: 
    default: Guest Additions Version: 4.2.0
    default: VirtualBox Version: 4.3
==> default: Mounting shared folders...
    default: /vagrant => /home/user/git/jtalks-vm
    default: /tmp/vagrant-chef/ef3e5ee91657285c71348b704c51177c/cookbooks => /home/user/git/jtalks-vm/cookbooks
    default: /tmp/vagrant-chef/c2508cc815cf0ec16878d77a0f8af6f3/cookbooks => /home/user/git/jtalks-vm/cookbooks-dependencies
==> default: Running provisioner: chef_solo...
    default: Installing Chef (latest)...
Generating chef JSON and uploading...
==> default: Running chef-solo...
==> default: stdin: is not a tty
==> default: [2015-02-28T19:38:56+00:00] INFO: Forking chef instance to converge...
==> default: [2015-02-28T19:38:56+00:00] INFO: *** Chef 12.0.3 ***
==> default: [2015-02-28T19:38:56+00:00] INFO: Chef-client pid: 1603
==> default: [2015-02-28T19:38:59+00:00] INFO: Setting the run_list to ["recipe[resolver]", "recipe[apt-get]", "recipe[nginx]", "recipe[java]", "recipe[openssl::default]", "recipe[mysql::server]", "recipe[tomcat7]", "recipe[python::pip]", "recipe[apt]", "recipe[git]", "recipe[jtalks::cicd]"] from CLI options
==> default: [2015-02-28T19:38:59+00:00] INFO: Run List is [recipe[resolver], recipe[apt-get], recipe[nginx], recipe[java], recipe[openssl::default], recipe[mysql::server], recipe[tomcat7], recipe[python::pip], recipe[apt], recipe[git], recipe[jtalks::cicd]]
==> default: [2015-02-28T19:38:59+00:00] INFO: Run List expands to [resolver, apt-get, nginx, java, openssl::default, mysql::server, tomcat7, python::pip, apt, git, jtalks::cicd]
==> default: [2015-02-28T19:38:59+00:00] INFO: Starting Chef Run for precise32
==> default: [2015-02-28T19:38:59+00:00] INFO: Running start handlers
==> default: [2015-02-28T19:38:59+00:00] INFO: Start handlers complete.
==> default: [2015-02-28T19:38:59+00:00] ERROR: Running exception handlers
==> default: [2015-02-28T19:38:59+00:00] ERROR: Exception handlers complete
==> default: [2015-02-28T19:38:59+00:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
==> default: [2015-02-28T19:38:59+00:00] ERROR: Cookbook loaded at path(s) [/tmp/vagrant-chef/ef3e5ee91657285c71348b704c51177c/cookbooks/openssl] has invalid metadata: The `name' attribute is required in cookbook metadata
==> default: [2015-02-28T19:38:59+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
Chef never successfully completed! Any errors should be visible in the
output above. Please fix your recipes so that they properly complete.
ctapobep commented 9 years ago

The chef scripts proved to be very unreliable. E.g. these scripts were fully functional couple of months ago. So we'll probably move to Docker for the purpose of deployment automation. Our first steps in this direction are described here in README, would be useful if you could try and provide your feedback (haven't tried this on end users yet). I will fix Docker scripts if they don't work for you.