Hello all,
So I''m off to a roaring start with puppet, and it''s lots of
fun.
I am getting this though:
Jun 12 08:37:42 devdb puppetd[15841]: Starting catalog run
Jun 12 08:37:48 devdb puppetd[15841]:
(//Node[devdb]/pgsql::server/pgsql::server-real/Package[postgresql81-contrib]/ensure)
change from absent to present failed: Execution of ''/usr/sbin/pkg_add
-r postgresql81-contrib'' returned 256: pkg_add: package
''postgresql-contrib-8.1.10_1'' or its older version already
installed
Jun 12 08:37:50 devdb puppetd[15841]: Finished catalog run in 7.88 seconds
If I do a pkg_info:
postgresql-client-8.1.10 PostgreSQL database (client)
postgresql-contrib-8.1.10_1 The contrib utilities from the PostgreSQL
distribution
postgresql-server-8.1.10_2 The most advanced open-source databas
So puppet is right.
The problem is that the installed name and the install name for some
FreeBSD packages are different (I know, that''s a pain in the butt).
Which means to install postgres-contrib, I need to call:
package { "postgresql-contrib":
name => ''postgresql81-contrib'',
ensure => present,
provider => freebsd,
require => Package["$pgsqlpackage"]
}
But once it is installed I need this to read:
package { "postgresql-contrib":
name => ''postgresql-contrib'',
ensure => present,
provider => freebsd,
require => Package["$pgsqlpackage"]
}
to stop it attempting to install again.
I read a ticket on the tracker about this, and it was set to design decision.
Maybe an installed_name => tag would be useful?
Any thoughts? How are the other BSD Puppeteers handling this?
The only thing I can think of is make an exec {} that does the pkg_add
-r manually... but this is (1) hackish and (2) means I have to do
require Exec[''postgres-contrib''] instead of require
Package[''postgres-contrib'']
Mikel
--~--~---------~--~----~------------~-------~--~----~
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-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
No FreeBSD puppeteers? I know quite a bit of Ruby and would be willing to write / submit patches on this. Would like to know if anyone else has done any work etc before I dive into it... See the below message for what I am after. Mikel On Fri, Jun 13, 2008 at 11:01 AM, Mikel Lindsaar <raasdnil@gmail.com> wrote:> Hello all, > > So I''m off to a roaring start with puppet, and it''s lots of fun. > > I am getting this though: > > Jun 12 08:37:42 devdb puppetd[15841]: Starting catalog run > Jun 12 08:37:48 devdb puppetd[15841]: > (//Node[devdb]/pgsql::server/pgsql::server-real/Package[postgresql81-contrib]/ensure) > change from absent to present failed: Execution of ''/usr/sbin/pkg_add > -r postgresql81-contrib'' returned 256: pkg_add: package > ''postgresql-contrib-8.1.10_1'' or its older version already installed > Jun 12 08:37:50 devdb puppetd[15841]: Finished catalog run in 7.88 seconds > > If I do a pkg_info: > > postgresql-client-8.1.10 PostgreSQL database (client) > postgresql-contrib-8.1.10_1 The contrib utilities from the PostgreSQL > distribution > postgresql-server-8.1.10_2 The most advanced open-source databas > > So puppet is right. > > The problem is that the installed name and the install name for some > FreeBSD packages are different (I know, that''s a pain in the butt). > Which means to install postgres-contrib, I need to call: > > package { "postgresql-contrib": > name => ''postgresql81-contrib'', > ensure => present, > provider => freebsd, > require => Package["$pgsqlpackage"] > } > > But once it is installed I need this to read: > > package { "postgresql-contrib": > name => ''postgresql-contrib'', > ensure => present, > provider => freebsd, > require => Package["$pgsqlpackage"] > } > > to stop it attempting to install again. > > I read a ticket on the tracker about this, and it was set to design decision. > > Maybe an installed_name => tag would be useful? > > Any thoughts? How are the other BSD Puppeteers handling this? > > The only thing I can think of is make an exec {} that does the pkg_add > -r manually... but this is (1) hackish and (2) means I have to do > require Exec[''postgres-contrib''] instead of require > Package[''postgres-contrib''] > > Mikel >--~--~---------~--~----~------------~-------~--~----~ 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-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mikel Lindsaar wrote:> No FreeBSD puppeteers? > > I know quite a bit of Ruby and would be willing to write / submit > patches on this. Would like to know if anyone else has done any work > etc before I dive into it... > > See the below message for what I am after. >Mikel Jump in and patch I recommend. I have seen no activity on that ticket. Feel free to ping Luke/Andrew/me for design question. Cheers James - -- Author of: * Pulling Strings with Puppet (http://www.amazon.com/gp/product/1590599780/) * Pro Nagios 2.0 (http://www.amazon.com/gp/product/1590596099/) * Hardening Linux (http://www.amazon.com/gp/product/1590594444/) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIU1wC9hTGvAxC30ARAhS9AJ4nF+RW2pXYwVyZehudOUaVSjw7OQCeK5Sx xdzJgi7NQXVSyQQdjKF6P7Y=i7o6 -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ 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-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Jun 14, 2008, at 12:42 AM, Mikel Lindsaar wrote:> No FreeBSD puppeteers? > > I know quite a bit of Ruby and would be willing to write / submit > patches on this. Would like to know if anyone else has done any work > etc before I dive into it...The closest thing we''ve had to a FreeBSD maintainer is Tomoyuki Sakurai (trombik on irc and trac), but he has mostly focused on fixing specific issues. It''d be great to have someone more focused on it, because I appear to be chemically incapable of understanding FreeBSD and definitely can''t provide the kind of behaviour they''re expecting. For the record, I believe you would be the third FreeBSD user, at least, to tackle this problem. The last two claimed it was trivial to fix but gave up in a couple of days. I''d love to have it actually fixed. -- Today at work an ethernet switch decided to take the ''N'' out of NVRAM -- Richard Letts --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Sun, Jun 15, 2008 at 2:00 AM, Luke Kanies <luke@madstop.com> wrote:> On Jun 14, 2008, at 12:42 AM, Mikel Lindsaar wrote: >> No FreeBSD puppeteers? > It''d be great to have someone more focused on it, because I appear to > be chemically incapable of understanding FreeBSD and definitely can''t > provide the kind of behaviour they''re expecting.I saw your blog post on pkg_add :)> For the record, I believe you would be the third FreeBSD user, at > least, to tackle this problem. The last two claimed it was trivial to > fix but gave up in a couple of days. I''d love to have it actually > fixed.Heh... hell.. that''s throwing the gauntlet down :) And on a public mailing list no less... :p Guess I can''t say no now :) I''ll have a look... but I need to understand puppet more to get there... Mikel --~--~---------~--~----~------------~-------~--~----~ 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-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---