On 28 January 2011 16:52, Peter Berghold <salty.cowd...@gmail.com> wrote:
> This one has me scratching my head. Simply enough I have the following in
> one of my manifests:
>
> package { postgresq1: ensure => latest }
>
> I checked with the Debian site to ensure that I had the correct package
> name, puppetd did its thing and lo and behold I get the following error
> message:
>
> err: /Stage[main]/Groupware-server/Package[postgresq1]/ensure: change from
> purged to latest failed: Could not update: Execution of '/usr/bin/apt-get -q
> -y -o DPkg::Options::=--force-confold install postgresq1' returned 100:
> Reading package lists...
> Building dependency tree...
> Reading state information...
> E: Couldn't find package postgresq1
> at /etc/puppet/manifests/templates.pp:58
> notice: Finished catalog run in 3.05 seconds
>
>
> So.. just for grins I did the apt-get manually
>
> # apt-get install postgresql
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> postgresql is already the newest version.
> 0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.
>
> Since I had already installed postgresql on this server, that message made
> perfect sense to me.
>
> So.... why during a puppet run can't it find postgresql but apt-get done
> manually can?
>
>
You have "postgresq1" in your puppet manifest - yet "postgresql" in your
command... notice the addition of "1".
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
