yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #91882
[Bug 961142] Re: chef 0.10: package installation: returned 100, expected 0
Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/2248
** Bug watch added: github.com/canonical/cloud-init/issues #2248
https://github.com/canonical/cloud-init/issues/2248
** Changed in: cloud-init
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/961142
Title:
chef 0.10: package installation: returned 100, expected 0
Status in cloud-init:
Expired
Status in cloud-init package in Ubuntu:
Expired
Bug description:
I'm trying to prepare nodes with cloud-init and chef 0.10 on Ubuntu
11.10 (Oneiric Ocelot) (amazon) instances.
On simple package installation via chef recipe, e.g:
package "munin-node"
I'm running into a apt-get error:
apt-get -q -y install munin-node=1.4.5-3ubuntu4 returned 100, expected 0 error.
Which can be traced back to 'Bad file descriptor' error, from man-db.
Same installation works fine without problems, when running chef without cloud-init.
I could trace this error back to some env variables, which are still set while chef starts to run it's scripts.
Unsetting these variables in the chef recipe solves the problem:
ENV['DEBCONF_REDIR'] = ""
ENV['DEBIAN_HAS_FRONTEND'] = ""
package "munin-node"
Does these variables still needs to be set, while executing the chef
client?
My cloud-config:
apt_update: True
apt_upgrade: True
byobu_by_default: disable
manage_etc_hosts: True
hostname: hostname
disable_root: true
timezone: UTC
packages:
- ntp
apt_sources:
- source: deb http://apt.opscode.com/ oneiric-0.10 main
filename: opscode.list
key: |
the key
chef:
install_type: "packages"
server_url: "https://api.opscode.com/organizations/myorganization"
node_name: "node name"
environment: "dev"
validation_name: "cloudcontrol-validator"
validation_cert: |
the cert
run_list:
- "role[arole]"
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/961142/+subscriptions