Mysql cookbook fails : Chef::Exceptions::Exec: apt-get -q -y install mysql-client=5.5.24-0ubuntu0.12.04.1 returned 100, expected 0


#1

I created a folder for vagrantVM, edited Vagrantfile to add solo recipes, created a cookbooks folder and cloned mysql, build-essential, openssl from https://github.com/opscode-cookbooks and then vagrant up but chef failed.

https://gist.github.com/4039324 Is this a known issue?


#2

Ohai, Nilesh

When I have this kind of problem, first thing to test its simple:

  • vagrant up without provision vm . ( comment out all chef references on
    Vagrantfile)
  • run offending command WITHOUT run apt-get update first.
  • If it fails, run apt-get update and fire up again.

This situation is common when package has been removed from repos, but your
local cache have references to it.

2012/11/8 Nilesh lvnilesh@yahoo.com

I created a folder for vagrantVM, edited Vagrantfile to add solo recipes,
created a cookbooks folder and cloned mysql, build-essential, openssl from
https://github.com/opscode-cookbooks and then vagrant up but chef failed.

https://gist.github.com/4039324 Is this a known issue?


#3

Thanks. is there a recipe for apt-get update that I am missing?

On Nov 8, 2012, at 7:43 AM, Jorge Bianquetti jbianquetti@gmail.com wrote:

Ohai, Nilesh

When I have this kind of problem, first thing to test its simple:

  • vagrant up without provision vm . ( comment out all chef references on Vagrantfile)
  • run offending command WITHOUT run apt-get update first.
  • If it fails, run apt-get update and fire up again.

This situation is common when package has been removed from repos, but your local cache have references to it.

2012/11/8 Nilesh lvnilesh@yahoo.com
I created a folder for vagrantVM, edited Vagrantfile to add solo recipes, created a cookbooks folder and cloned mysql, build-essential, openssl from https://github.com/opscode-cookbooks and then vagrant up but chef failed.

https://gist.github.com/4039324 Is this a known issue?


#4

You can include the ‘apt’ cookbook’s default recipe in the run list to take
care of that.

-J

On Thu, Nov 8, 2012 at 10:06 AM, Nilesh lvnilesh@yahoo.com wrote:

Thanks. is there a recipe for apt-get update that I am missing?

On Nov 8, 2012, at 7:43 AM, Jorge Bianquetti jbianquetti@gmail.com
wrote:

Ohai, Nilesh

When I have this kind of problem, first thing to test its simple:

  • vagrant up without provision vm . ( comment out all chef references on
    Vagrantfile)
  • run offending command WITHOUT run apt-get update first.
  • If it fails, run apt-get update and fire up again.

This situation is common when package has been removed from repos, but
your local cache have references to it.

2012/11/8 Nilesh lvnilesh@yahoo.com

I created a folder for vagrantVM, edited Vagrantfile to add solo recipes,
created a cookbooks folder and cloned mysql, build-essential, openssl from
https://github.com/opscode-cookbooks and then vagrant up but chef failed.

https://gist.github.com/4039324 Is this a known issue?


Joshua Buysse, System Engineer
College of Liberal Arts, Office of Information Technology
University of Minnesota

“On two occasions I have been asked, ‘Pray, Mr. Babbage, if you
put into the machine wrong figures, will the right answers come
out?’ I am not able rightly to apprehend the kind of confusion of
ideas that could provoke such a question.”

  • Charles Babbage

#5

Thanks. It worked.

This is what I have been playing with https://github.com/fungibleclouds/khanakhazana

On Nov 8, 2012, at 8:16 AM, Joshua Buysse buysse@umn.edu wrote:

You can include the ‘apt’ cookbook’s default recipe in the run list to take care of that.

-J

On Thu, Nov 8, 2012 at 10:06 AM, Nilesh lvnilesh@yahoo.com wrote:
Thanks. is there a recipe for apt-get update that I am missing?

On Nov 8, 2012, at 7:43 AM, Jorge Bianquetti jbianquetti@gmail.com wrote:

Ohai, Nilesh

When I have this kind of problem, first thing to test its simple:

  • vagrant up without provision vm . ( comment out all chef references on Vagrantfile)
  • run offending command WITHOUT run apt-get update first.
  • If it fails, run apt-get update and fire up again.

This situation is common when package has been removed from repos, but your local cache have references to it.

2012/11/8 Nilesh lvnilesh@yahoo.com
I created a folder for vagrantVM, edited Vagrantfile to add solo recipes, created a cookbooks folder and cloned mysql, build-essential, openssl from https://github.com/opscode-cookbooks and then vagrant up but chef failed.

https://gist.github.com/4039324 Is this a known issue?


Joshua Buysse, System Engineer
College of Liberal Arts, Office of Information Technology
University of Minnesota

“On two occasions I have been asked, ‘Pray, Mr. Babbage, if you
put into the machine wrong figures, will the right answers come
out?’ I am not able rightly to apprehend the kind of confusion of
ideas that could provoke such a question.”

  • Charles Babbage

#6

Am 08.11.2012 16:43 schrieb “Jorge Bianquetti” jbianquetti@gmail.com:

Ohai, Nilesh

When I have this kind of problem, first thing to test its simple:

  • vagrant up without provision vm . ( comment out all chef references
    on Vagrantfile)

Or simply use ‘vagrant up --no-provision’

  • run offending command WITHOUT run apt-get update first.
  • If it fails, run apt-get update and fire up again.

This situation is common when package has been removed from repos, but
your local cache have references to it.

2012/11/8 Nilesh lvnilesh@yahoo.com

I created a folder for vagrantVM, edited Vagrantfile to add solo
recipes, created a cookbooks folder and cloned mysql, build-essential,
openssl from https://github.com/opscode-cookbooks and then vagrant up but
chef failed.

https://gist.github.com/4039324 Is this a known issue?