I tried it again and spun up a new ec2 instance to test:
ec2-184-72-15-173.us-west-1.compute.amazonaws.com [Fri, 03 Aug 2012
22:05:03 +0000] INFO: Processing execute[apt-get-update] action run
(apt::default line 22)
ec2-184-72-15-173.us-west-1.compute.amazonaws.com [Fri, 03 Aug 2012
22:05:03 +0000] INFO: Processing execute[apt-get update] action nothing
(apt::default line 29)
ec2-184-72-15-173.us-west-1.compute.amazonaws.com [Fri, 03 Aug 2012
22:05:03 +0000] INFO: Processing package[update-notifier-common] action
install (apt::default line 36)
ec2-184-72-15-173.us-west-1.compute.amazonaws.com [Fri, 03 Aug 2012
22:05:03 +0000] INFO: Processing execute[apt-get-update-periodic] action
run (apt::default line 40)
ec2-184-72-15-173.us-west-1.compute.amazonaws.com [Fri, 03 Aug 2012
22:05:03 +0000] INFO: Processing directory[/var/cache/local] action create
(apt::default line 50)
ec2-184-72-15-173.us-west-1.compute.amazonaws.com [Fri, 03 Aug 2012
22:05:03 +0000] INFO: directory[/var/cache/local] created directory
/var/cache/local
ec2-184-72-15-173.us-west-1.compute.amazonaws.com [Fri, 03 Aug 2012
22:05:03 +0000] INFO: directory[/var/cache/local] mode changed to 644
ec2-184-72-15-173.us-west-1.compute.amazonaws.com [Fri, 03 Aug 2012
22:05:03 +0000] INFO: Processing directory[/var/cache/local/preseeding]
action create (apt::default line 50)
ec2-184-72-15-173.us-west-1.compute.amazonaws.com [Fri, 03 Aug 2012
22:05:03 +0000] INFO: directory[/var/cache/local/preseeding] created
directory /var/cache/local/preseeding
ec2-184-72-15-173.us-west-1.compute.amazonaws.com [Fri, 03 Aug 2012
22:05:03 +0000] INFO: directory[/var/cache/local/preseeding] mode changed
to 644
ec2-184-72-15-173.us-west-1.compute.amazonaws.com [Fri, 03 Aug 2012
22:05:03 +0000] INFO: Processing package[sudo] action upgrade
(sudo::default line 20)
ec2-184-72-15-173.us-west-1.compute.amazonaws.com [Fri, 03 Aug 2012
22:05:03 +0000] INFO: Processing directory[/etc/sudoers.d] action create
(sudo::default line 25)
ec2-184-72-15-173.us-west-1.compute.amazonaws.com [Fri, 03 Aug 2012
22:05:03 +0000] INFO: Processing template[/etc/sudoers.d/001_sudoers]
action create (sudo::default line 34)
ec2-184-72-15-173.us-west-1.compute.amazonaws.com [Fri, 03 Aug 2012
22:05:04 +0000] INFO: template[/etc/sudoers.d/001_sudoers] backed up to
/var/chef/backup/etc/sudoers.d/001_sudoers.chef-20120803220504
ec2-184-72-15-173.us-west-1.compute.amazonaws.com [Fri, 03 Aug 2012
22:05:04 +0000] INFO: template[/etc/sudoers.d/001_sudoers] mode changed to
440
ec2-184-72-15-173.us-west-1.compute.amazonaws.com [Fri, 03 Aug 2012
22:05:04 +0000] INFO: template[/etc/sudoers.d/001_sudoers] updated content
ec2-184-72-15-173.us-west-1.compute.amazonaws.com [Fri, 03 Aug 2012
22:05:04 +0000] INFO: Processing package[nginx] action install
(nginx::proxy-cloudant line 1)
ec2-184-72-15-173.us-west-1.compute.amazonaws.com [Fri, 03 Aug 2012
22:05:04 +0000] INFO: package[nginx] is a virtual package, actually acting
on package[nginx-full]
ec2-184-72-15-173.us-west-1.compute.amazonaws.com [Fri, 03 Aug 2012
22:05:04 +0000] ERROR: package[nginx] (nginx::proxy-cloudant line 1) has
had an error
ec2-184-72-15-173.us-west-1.compute.amazonaws.com [Fri, 03 Aug 2012
22:05:04 +0000] ERROR: package[nginx]
(/var/chef/cache/cookbooks/nginx/recipes/proxy-cloudant.rb:1:in
`from_file') had an error:
ec2-184-72-15-173.us-west-1.compute.amazonaws.com package[nginx]
(nginx::proxy-cloudant line 1) had an error: Chef::Exceptions:
nginx has no candidate in the apt-cache
nginx is a virtual package which installs nginx-full, which goes back to
the fact that the apt recipe doesn't actually seem to be updating the cache
like it should and says it is.
--
~~ StormeRider ~~
"Every world needs its heroes [...] They inspire us to be better than we
are. And they protect from the darkness that's just around the corner."
(from Smallville Season 6x1: "Zod")
On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSS
On Fri, Aug 3, 2012 at 3:02 PM, Morgan Blackthorne stormerider@gmail.comwrote:
That's what the default nginx recipe went to install, but if you look at
the gist I do an apt-cache search nginx and nothing is found. If I do a
manual update (which should have already been done according to the chef
run) and re-search it works fine.
--
~~ StormeRider ~~
"Every world needs its heroes [...] They inspire us to be better than we
are. And they protect from the darkness that's just around the corner."
(from Smallville Season 6x1: "Zod")
On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSS
On Fri, Aug 3, 2012 at 2:57 PM, Mike miketheman@gmail.com wrote:
It's probably from this line: nginx::proxy-cloudant line 1
The package name is probably "nginx" not "nginx-full".
On Fri, Aug 3, 2012 at 5:48 PM, Morgan Blackthorne
stormerider@gmail.com wrote:
I'm trying to install nginx via Chef. I've got an Ubuntu 12.04 AMI, but
when
I go to install nginx it can't find it. I even customized a recipe that
goes
to install nginx-full, but it's not in the apt cache.
I added the apt cookbook and placed that first in the role, to trigger
apt-get update, but it's still not updating the cache even though I see
it
firing before the package install:
https://gist.github.com/3251781
Anyone run into this before or know what I'm doing wrong?
--
~~ StormeRider ~~
"Every world needs its heroes [...] They inspire us to be better than we
are. And they protect from the darkness that's just around the corner."
(from Smallville Season 6x1: "Zod")
On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSS