Hey, You need to install vagrant berkshelf as I mentioned. Vagrant berkshelf has a dependency on chefdk so you'll need that too.
Documentation really needs to be updated. On 11 Jan 2015 12:59, "Supun Muthutantrige" <sup...@wso2.com> wrote: > Hi, > > Cloned from the latest repository. made the network adjustments and ran the > "bash scripts/vagrant_prep.sh vbox" command, but due to the above mentioned > errors, still haven't been able to configure cloudstack properly. Would > highly appreciate your support and suggestions about what might be going > wrong. > > Thank you, > Regards. > > > *Supun Rasitha Muthutantrige* > Software Engineer | Intern > WSO2 Inc: http://wso2.com > lean.enterprise.middleware > Mobile: 0758374608 > > On Sat, Jan 10, 2015 at 2:04 PM, Supun Muthutantrige <sup...@wso2.com> > wrote: > > > As instructed, before running the Vagrant up command, I have run "bash > > scripts/vagrant_prep.sh vbox" command and the output as follows > > > > > /opt/vagrant/bin/../embedded/gems/gems/vagrant-1.6.5/lib/vagrant/pre-rubygems.rb:31: > > warning: Insecure world writable dir /...../opt/apache-maven-3.2.3/bin in > > PATH, mode 040777 > > > /opt/vagrant/bin/../embedded/gems/gems/vagrant-1.6.5/lib/vagrant/pre-rubygems.rb:31: > > warning: Insecure world writable dir /...../opt/apache-maven-3.2.3/bin in > > PATH, mode 040777 > > /opt/vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/runtime.rb:222: > > warning: Insecure world writable dir /...../opt/apache-maven-3.2.3/bin in > > PATH, mode 040777 > > > /opt/vagrant/bin/../embedded/gems/gems/vagrant-1.6.5/lib/vagrant/pre-rubygems.rb:31: > > warning: Insecure world writable dir /...../opt/apache-maven-3.2.3/bin in > > PATH, mode 040777 > > /opt/vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/runtime.rb:222: > > warning: Insecure world writable dir /...../opt/apache-maven-3.2.3/bin in > > PATH, mode 040777 > > All plugins are installed! > > > > > > > > > > *Supun Rasitha Muthutantrige* > > Software Engineer | Intern > > WSO2 Inc: http://wso2.com > > lean.enterprise.middleware > > Mobile: 0758374608 > > > > On Sat, Jan 10, 2015 at 12:31 PM, Ian Duffy <i...@ianduffy.ie> wrote: > > > >> You need vagrant-berkshelf as the error says. > >> > >> vagrant plugin install vagrant-berkshelf > >> > >> On 10 January 2015 at 03:50, Supun Muthutantrige <sup...@wso2.com> > wrote: > >> > Hi, > >> > > >> > I have cloned the latest version. Now when running the vagrant up > >> command > >> > getting the following error > >> > > >> > *There was an error loading a Vagrantfile. The file being loaded* > >> > *and the error message are shown below. This is usually caused by* > >> > *a syntax error.* > >> > > >> > *Path: ..../binary-installation-advanced/Vagrantfile* > >> > *Message: vagrant-berkshelf is not installed!* > >> > > >> > > >> > Thank you, > >> > Regards > >> > > >> > > >> > > >> > *Supun Rasitha Muthutantrige* > >> > Software Engineer | Intern > >> > WSO2 Inc: http://wso2.com > >> > lean.enterprise.middleware > >> > Mobile: 0758374608 > >> > > >> > On Fri, Jan 9, 2015 at 5:38 PM, Supun Muthutantrige <sup...@wso2.com> > >> wrote: > >> > > >> >> Great Iwill try this out and update the thread > >> >> > >> >> > >> >> Thank you, > >> >> Regards > >> >> > >> >> > >> >> *Supun Rasitha Muthutantrige* > >> >> Software Engineer | Intern > >> >> WSO2 Inc: http://wso2.com > >> >> lean.enterprise.middleware > >> >> Mobile: 0758374608 > >> >> > >> >> On Fri, Jan 9, 2015 at 2:52 AM, Ian Duffy <i...@ianduffy.ie> wrote: > >> >> > >> >>> That issue should be fixed. Can you confirm your on the latest > clone? > >> Just > >> >>> do a git pull. > >> >>> > >> >>> If it still fails remove ~/.berkshelf and try again. > >> >>> On 8 Jan 2015 14:04, "Supun Muthutantrige" <sup...@wso2.com> wrote: > >> >>> > >> >>> > Hi Ian, > >> >>> > > >> >>> > Thank you for the information. When I run the "vagrant up" command > >> >>> > in binary-installation-advanced folder the following error > >> occurred. I > >> >>> > tried this after stopping and starting the mysql server, changed > the > >> >>> > default mysql 3306 port, but the error seems to be there, Would > >> like to > >> >>> > know the reason > >> >>> > > >> >>> > Terminal output as follows, > >> >>> > > >> >>> > > >> >>> > >> > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > >> >>> > > >> >>> > ==> management: [2015-01-08T13:54:31+00:00] INFO: Forking chef > >> instance > >> >>> to > >> >>> > converge... > >> >>> > ==> management: [2015-01-08T13:54:31+00:00] WARN: > >> >>> > ==> management: * * * * * * * * * * * * * * * * * * * * * * * * * > * > >> * * > >> >>> * * > >> >>> > * * * * * * * * * * > >> >>> > ==> management: SSL validation of HTTPS requests is disabled. > HTTPS > >> >>> > connections are still > >> >>> > ==> management: encrypted, but chef is not able to detect forged > >> >>> replies or > >> >>> > man in the middle > >> >>> > ==> management: attacks. > >> >>> > ==> management: > >> >>> > ==> management: To fix this issue add an entry like this to your > >> >>> > configuration file: > >> >>> > ==> management: > >> >>> > ==> management: ``` > >> >>> > ==> management: # Verify all HTTPS connections (recommended) > >> >>> > ==> management: ssl_verify_mode :verify_peer > >> >>> > ==> management: > >> >>> > ==> management: # OR, Verify only connections to chef-server > >> >>> > ==> management: verify_api_cert true > >> >>> > ==> management: ``` > >> >>> > ==> management: > >> >>> > ==> management: To check your SSL configuration, or troubleshoot > >> errors, > >> >>> > you can use the > >> >>> > ==> management: `knife ssl check` command like so: > >> >>> > ==> management: > >> >>> > ==> management: ``` > >> >>> > ==> management: knife ssl check -c /tmp/vagrant-chef-2/solo.rb > >> >>> > ==> management: ``` > >> >>> > ==> management: > >> >>> > ==> management: * * * * * * * * * * * * * * * * * * * * * * * * * > * > >> * * > >> >>> * * > >> >>> > * * * * * * * * * * > >> >>> > ==> management: > >> >>> > ==> management: [2015-01-08T13:54:31+00:00] INFO: *** Chef 11.16.0 > >> *** > >> >>> > ==> management: [2015-01-08T13:54:31+00:00] INFO: Chef-client pid: > >> 2932 > >> >>> > ==> management: [2015-01-08T13:54:36+00:00] INFO: Setting the > >> run_list > >> >>> to > >> >>> > ["recipe[nat-router]", "recipe[cloudstack::management-server]"] > >> from CLI > >> >>> > options > >> >>> > ==> management: [2015-01-08T13:54:36+00:00] INFO: Run List is > >> >>> > [recipe[nat-router], recipe[cloudstack::management-server]] > >> >>> > ==> management: [2015-01-08T13:54:36+00:00] INFO: Run List expands > >> to > >> >>> > [nat-router, cloudstack::management-server] > >> >>> > ==> management: [2015-01-08T13:54:36+00:00] INFO: Starting Chef > Run > >> for > >> >>> > localhost > >> >>> > ==> management: [2015-01-08T13:54:36+00:00] INFO: Running start > >> handlers > >> >>> > ==> management: [2015-01-08T13:54:36+00:00] INFO: Start handlers > >> >>> complete. > >> >>> > ==> management: > >> >>> > ==> management: > >> >>> > > >> >>> > > >> >>> > >> > ================================================================================ > >> >>> > ==> management: Recipe Compile Error > >> >>> > ==> management: > >> >>> > > >> >>> > > >> >>> > >> > ================================================================================ > >> >>> > ==> management: > >> >>> > ==> management: > >> >>> > ==> management: Chef::Exceptions::RecipeNotFound > >> >>> > ==> management: -------------------------------- > >> >>> > ==> management: could not find recipe client for cookbook mysql > >> >>> > ==> management: > >> >>> > ==> management: > >> >>> > ==> management: [2015-01-08T13:54:36+00:00] ERROR: Running > exception > >> >>> > handlers > >> >>> > ==> management: [2015-01-08T13:54:36+00:00] ERROR: Exception > >> handlers > >> >>> > complete > >> >>> > ==> management: [2015-01-08T13:54:36+00:00] FATAL: Stacktrace > >> dumped to > >> >>> > /var/chef/cache/chef-stacktrace.out > >> >>> > ==> management: [2015-01-08T13:54:36+00:00] ERROR: could not find > >> recipe > >> >>> > client for cookbook mysql > >> >>> > ==> management: [2015-01-08T13:54:37+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. > >> >>> > > >> >>> > > >> >>> > > >> >>> > >> > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > >> >>> > > >> >>> > > >> >>> > Thank you, > >> >>> > Regards > >> >>> > > >> >>> > > >> >>> > *Supun Rasitha Muthutantrige* > >> >>> > Software Engineer | Intern > >> >>> > WSO2 Inc: http://wso2.com > >> >>> > lean.enterprise.middleware > >> >>> > Mobile: 0758374608 > >> >>> > > >> >>> > >> >> > >> >> > >> > > > > >
