[Puppet Users] Re: Export resource issue - more than one of content, source, target
I would do more experimentation on your resource temporarily to find
the problem. For example:
* Set 'ensure' explicitly to 'file'. Not a var (or remove it entirely
if you are unsure). If it is interpreting that as a path it will try
to install a symbolic link which may be giving you the error you have
received for example.
* Does this occur without being exported? ie. on the original local
box? Or on the box you are trying to export to?
* Try different 'content' items ... try blank for example to make sure
its not having trouble parsing.
It feels to me like its your 'ensure' line but try a few things first.
Strip your resource back to its simplest parts until it works - then
keep applying your specific configuration piece by piece until it
breaks again.
ken.
On Apr 6, 5:10 am, Alan Sparks aspa...@doublesparks.net wrote:
I'm trying to create an exported file resource and receiving a vague
error message:
Apr 5 18:01:04 ny4-dev-util01 puppetd[12860]: Could not run Puppet
configuration client: You cannot specify more than one of content,
source, target at line 102
A puppet client (it's 0.24.8) is creating the following resource:
@@file { mlwormbackup_$fqdn:
mode = 644,
owner = root,
group = root,
ensure = $worm_backup_enabled,
path = /root/ml_backup_hosts/$fqdn,
content =
HOST=$fqdn\nCLEAR=$my_clear_shortname\nCLIENT=$my_bd_shortname\n,
tag = mlwormbackup,
}
Another server (this is a 0.25.4 puppet) has the following in its node
definition:
File | tag == mlwormbackup |
All are running against a 0.25.4 puppetmaster. We're in process of
testing migration of all to 0.25.
The message makes no sense to me. The resource only has a content
parameter, no source or target. Why is the 0.25 puppet (or the
puppetmaster?) complaining about more than one of anything? I've
looked for duplicate instances of this resource, emptied the
storeconfigs database completely, and still cannot locate the source of
this message.
Is there some incompatibility in stored configs between 0.24 and 0.25
clients?
Thanks in advance for any advice.
-Alan
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@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.
[Puppet Users] Re: Problem syncing custom fact
Yes in theory. Depending on the section you put it in of course. I have pluginsync=true in the [main] section of my puppet.conf, on both my client and server and sync works fine. Can you post your full configuration? Both client and server? Can you confirm your other settings are working when you adjust them in puppet.conf? On Apr 5, 10:43 pm, byron appelt byron.app...@gmail.com wrote: I am trying to get a custom fact to sync. The fact is in a module. It will sync if I run puppet with --pluginsync but not otherwise. I have pluginsync=true in my puppet.conf. Shouldn't the command line option and puppet.conf option have the same results? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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.
[Puppet Users] Puppet Dashboard packages now available!
Hi all I've created RPM and DEB packages for the Puppet Dashboard 1.0.0rc1. These are available via APT and Yum repositories hosted by Puppet Labs. These are first release packages and I am by no means a packaging expert with either DEBs or RPMs so any feedback or comments are welcomed. I'll continue to update the packages as updates to the Dashboard are released. Overall instructions for installing and running the Dashboard can be found at: http://github.com/reductivelabs/puppet-dashboard 1. Get DEB Packages via APT a. Add the following to your /etc/apt/sources.list file: deb http://apt.puppetlabs.com/ubuntu lucid main deb-src http://apt.puppetlabs.com/ubuntu lucid main b. Add the Puppet Labs repository key to APT (the package is signed with this key also). $ gpg --recv-key 8347A27F $ gpg -a --export 8347A27F | sudo apt-key add - c. Run apt-get update $ sudo apt-get update d. Install Puppet Dashboard $ sudo apt-get install puppet-dashboard The Dashboard will be installed in /usr/share/puppet-dashboard and you run the server from here or create a Passenger configuration. 2. Get RPM packages via Yum a. Create a Yum repo entry for Puppet Labs $ vi /etc/yum.repos.d/puppetlabs.repo [puppetlabs] name=Puppet Labs Packages baseurl=http://yum.puppetlabs.com/base/ enabled=1 gpgcheck=1 gpgkey=http://yum.puppetlabs.com/RPM-GPG-KEY-reductive b. Install via yum $ sudo yum install puppet-dashboard You will be prompted to install the Puppet Labs release key as part of the installation process and the RPM packages are signed with that key. The Dashboard will be installed in /usr/share/puppet-dashboard and you run the server from here or create a Passenger configuration. Regards James Turnbull -- Author of: * Pro Linux System Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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.
Re: [Puppet Users] Mongrel : Can't download files
2010/4/2 smain kahlouch smain...@gmail.com 2010/4/1 smain kahlouch smain...@gmail.com 2010/4/1 Smain Kahlouch smain...@gmail.com Message initial De: Michael DeHaan mich...@puppetlabs.com Reply-to: puppet-users@googlegroups.com À: puppet-users@googlegroups.com Cc: James Turnbull ja...@lovedthanlost.net Sujet: Re: [Puppet Users] Mongrel : Can't download files Date: Wed, 31 Mar 2010 10:17:24 -0400 On Wed, Mar 31, 2010 at 6:05 AM, smain kahlouch smain...@gmail.com wrote: Hi, i'm following the steps of the documentation but the links are not working. I can't download the files : http://projects.reductivelabs.com/projects/puppet/wiki/Using_Mongrel_On_Debian Thanks for your help, Grifith This looks like this might have happened as part of the redmine conversion, as the attachment still references a URL in Trac. It could also be a problem with the rewrite rules having changed since the site migration. (James, do you know anything about attachment migration?) I've seen some other docs that had attachments migrated, though I'm not sure why this one is an outlier. --Michael -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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. Hi Michael, Is there another way to get these files? Thanks, Grifith It seems that many files disapeared. I was looking the puppet dashboard features and i noticed the same problem for the pictures. http://www.puppetlabs.com/2009/12/14/a-tour-of-puppet-dashboard-0-1-0/ Regards, Grifith Is somebody has the files in order to install mongrel please ? Regards, Grifith Hi, How can i migrate to mongrel now ? I would prefer to migrate to Passenger but it seems that it is necessary to install development tools so is somebody could provide me the files that were downloadable from the following url http://projects.reductivelabs.com/projects/puppet/wiki/Using_Mongrel_On_Debian Thanks; Grifith -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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.
Re: [Puppet Users] Puppetrun with cname
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The only way that I know to do this is to make your reverse lookup match your CNAME (which doesn't really make it act like a CNAME at that point). The reverse lookup is what matters to the certs, not the forward. Trevor On 04/05/2010 05:12 PM, Brian wrote: I have a puppet server running on foo.example.com with a cname of puppet.example.com. In puppet.conf I have server set to puppet.example.com and certname set to puppet.example.com. This works fine for regular puppet runs. My issue is with puppetrun. In the puppetrunner section of namespaceauth.conf, I've allowed puppet.example.com. However, the puppet clients refuse to run with this configuration with the complaint Denying authenticated client foo.example.com(192.0.2.2) access to puppetrunner.run. Only after I add foo.example.com to namespaceauth.conf does it work. Is there a way to get puppetrun to work with the cname? I think this might be the same unresolved issue discussed at http://groups.google.com/group/puppet-users/browse_thread/thread/537c1aa347d27bad All the best, Brian Pitts - -- Trevor Vaughan Vice President, Onyx Point, Inc. email: tvaug...@onyxpoint.com phone: 410-541-ONYX (6699) pgp: 0x6C701E94 - -- This account not approved for unencrypted sensitive information -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAku7Ci4ACgkQyWMIJmxwHpQ4ywCfZFJt4EQ+aKhTVVnv7dOhJuDl o9EAnAgMAV8yeMIsi+GbhfCbJzSB+u7G =cDYa -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-us...@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. attachment: tvaughan.vcf
RE: [Puppet Users] Puppet Dashboard packages now available!
I tried installing via yum, received this error concerning the package signature.. error: rpmts_HdrFromFdno: Header V4 RSA/SHA1 signature: BAD, key ID 8347a27f -Original Message- From: puppet-users@googlegroups.com [mailto:puppet-us...@googlegroups.com] On Behalf Of James Turnbull Sent: Tuesday, April 06, 2010 2:49 AM To: puppet-dev; puppet-users; puppet-announce Subject: [Puppet Users] Puppet Dashboard packages now available! Hi all I've created RPM and DEB packages for the Puppet Dashboard 1.0.0rc1. These are available via APT and Yum repositories hosted by Puppet Labs. These are first release packages and I am by no means a packaging expert with either DEBs or RPMs so any feedback or comments are welcomed. I'll continue to update the packages as updates to the Dashboard are released. Overall instructions for installing and running the Dashboard can be found at: http://github.com/reductivelabs/puppet-dashboard 1. Get DEB Packages via APT a. Add the following to your /etc/apt/sources.list file: deb http://apt.puppetlabs.com/ubuntu lucid main deb-src http://apt.puppetlabs.com/ubuntu lucid main b. Add the Puppet Labs repository key to APT (the package is signed with this key also). $ gpg --recv-key 8347A27F $ gpg -a --export 8347A27F | sudo apt-key add - c. Run apt-get update $ sudo apt-get update d. Install Puppet Dashboard $ sudo apt-get install puppet-dashboard The Dashboard will be installed in /usr/share/puppet-dashboard and you run the server from here or create a Passenger configuration. 2. Get RPM packages via Yum a. Create a Yum repo entry for Puppet Labs $ vi /etc/yum.repos.d/puppetlabs.repo [puppetlabs] name=Puppet Labs Packages baseurl=http://yum.puppetlabs.com/base/ enabled=1 gpgcheck=1 gpgkey=http://yum.puppetlabs.com/RPM-GPG-KEY-reductive b. Install via yum $ sudo yum install puppet-dashboard You will be prompted to install the Puppet Labs release key as part of the installation process and the RPM packages are signed with that key. The Dashboard will be installed in /usr/share/puppet-dashboard and you run the server from here or create a Passenger configuration. Regards James Turnbull -- Author of: * Pro Linux System Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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.
Re: [Puppet Users] Puppet Dashboard packages now available!
Do you have something like a release tarball? I'd like to create a Gentoo ebuild for it. On Tue, Apr 6, 2010 at 3:07 PM, Baker, Luke Jefferson bake...@missouri.edu wrote: I tried installing via yum, received this error concerning the package signature.. error: rpmts_HdrFromFdno: Header V4 RSA/SHA1 signature: BAD, key ID 8347a27f -Original Message- From: puppet-users@googlegroups.com [mailto:puppet-us...@googlegroups.com] On Behalf Of James Turnbull Sent: Tuesday, April 06, 2010 2:49 AM To: puppet-dev; puppet-users; puppet-announce Subject: [Puppet Users] Puppet Dashboard packages now available! Hi all I've created RPM and DEB packages for the Puppet Dashboard 1.0.0rc1. These are available via APT and Yum repositories hosted by Puppet Labs. These are first release packages and I am by no means a packaging expert with either DEBs or RPMs so any feedback or comments are welcomed. I'll continue to update the packages as updates to the Dashboard are released. Overall instructions for installing and running the Dashboard can be found at: http://github.com/reductivelabs/puppet-dashboard 1. Get DEB Packages via APT a. Add the following to your /etc/apt/sources.list file: deb http://apt.puppetlabs.com/ubuntu lucid main deb-src http://apt.puppetlabs.com/ubuntu lucid main b. Add the Puppet Labs repository key to APT (the package is signed with this key also). $ gpg --recv-key 8347A27F $ gpg -a --export 8347A27F | sudo apt-key add - c. Run apt-get update $ sudo apt-get update d. Install Puppet Dashboard $ sudo apt-get install puppet-dashboard The Dashboard will be installed in /usr/share/puppet-dashboard and you run the server from here or create a Passenger configuration. 2. Get RPM packages via Yum a. Create a Yum repo entry for Puppet Labs $ vi /etc/yum.repos.d/puppetlabs.repo [puppetlabs] name=Puppet Labs Packages baseurl=http://yum.puppetlabs.com/base/ enabled=1 gpgcheck=1 gpgkey=http://yum.puppetlabs.com/RPM-GPG-KEY-reductive b. Install via yum $ sudo yum install puppet-dashboard You will be prompted to install the Puppet Labs release key as part of the installation process and the RPM packages are signed with that key. The Dashboard will be installed in /usr/share/puppet-dashboard and you run the server from here or create a Passenger configuration. Regards James Turnbull -- Author of: * Pro Linux System Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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. -- Cheers, Daniel -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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.
[Puppet Users] Exported resource [...] cannot override local resource - Common error, how to get around
Hi, I've runned into a fairly common problem: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Exported resource File[list-updates] cannot override local resource on node X http://projects.puppetlabs.com/projects/puppet/wiki/Frequently_Asked_Questions I cannot see how I can fix this. On all of my nodes i add the class list-updates, and on the puppetmaster i add list-updates AND list- updates::all. The manifests: http://pastebin.com/vXqP2q6q Of course this can be prevented by not including list-updates on the puppetmaster. But, this problems occours since the puppetmaster creates and uses an stored configuration. But why doesn't this pose a problem when using sshkeys? http://projects.reductivelabs.com/projects/puppet/wiki/Exported_Resources -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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.
Re: [Puppet Users] Puppet Dashboard packages now available!
On Tue, 6 Apr 2010 17:48:42 +1000, James Turnbull ja...@lovedthanlost.net wrote: Hi all I've created RPM and DEB packages for the Puppet Dashboard 1.0.0rc1. These are available via APT and Yum repositories hosted by Puppet Labs. These are first release packages and I am by no means a packaging expert with either DEBs or RPMs so any feedback or comments are welcomed. I'll continue to update the packages as updates to the Dashboard are released. Any idea if/when these will be available in EPEL? -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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.
[Puppet Users] Why we wont use zpool ever again
Hi everyone, Just wanted to tell you a little story. We've been enthusiastic puppet users since about a year ago here at the Geographic Institute of the University of Zürich. But we won't use the zpool type ever again. Its just not worth it. Here's what happened: . one of our servers lost knowledge about one of its zfs pools . puppet didn't find the pool and .. went on to zpool create it . we did indeed have a backup, but would have lost all data if not Creating zpools is a manual thing in every case, since one has to know the devices participating. The names of which tend to be a little bit different from one server to the next. Add that to the possibility of major data loss (like we just experienced) and get a negative yield for the 'zpool' type. Hoping to inspire a few.. kaspar -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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.
Re: [Puppet Users] Why we wont use zpool ever again
Hi But we won't use the zpool type ever again. Its just not worth it. Here's what happened: . one of our servers lost knowledge about one of its zfs pools . puppet didn't find the pool and .. went on to zpool create it . we did indeed have a backup, but would have lost all data if not Creating zpools is a manual thing in every case, since one has to know the devices participating. The names of which tend to be a little bit different from one server to the next. Add that to the possibility of major data loss (like we just experienced) and get a negative yield for the 'zpool' type. there was recently a similar discussion about that with the new available fs and lvm type on the puppet-dev list. these are indeed very dangerous operations, where it should somehow be possible to lock them. the problem is clearly that if puppet fails to determine the correct state it tries to transfer into the right state, which might have (obviously) - ehhh - nasty side-effects on such operations. maybe you can catch that discussion up and give your thoughts about it how puppet should behave and how it would be possible to lock such operations. cheers pete -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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.
[Puppet Users] Re: Problem syncing custom fact
Thanks, testing other settings was an excellent suggestion. It seems no settings in my puppet.conf are working. Any suggestions on how to debug this? This was all working before I upgrading from 0.24.5 to 0.25.4 For reference, here are my configs, although it seems that the client config is not even being read. Here is my client puppet.conf:[main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/etc/puppet/ssl rundir=/var/run/puppet factpath=/var/lib/facter pluginsync=true server=puppetmaster.numerex.com environments=production,testing environment=production [puppetd] report = true And here is the puppetmaster: main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var/run/puppet pluginsync=true server = puppetmaster.numerex.com environments = development,testing,production node_terminus = exec external_nodes = /etc/puppet/query_deploymanager.rb [puppetmasterd] certname=puppetmaster.numerex.com [puppetd] report = true [testing] modulepath = /etc/puppet-dev/manifests/classes templatedir=/etc/puppet-dev/templates manifest = /etc/puppet-dev/manifests/site.pp pluginsync = true [production] modulepath = /etc/puppet/manifests/classes templatedir=/etc/puppet/templates manifest = /etc/puppet/manifests/site.pp pluginsync = true On Apr 6, 2:17 am, Ken k...@bob.sh wrote: Yes in theory. Depending on the section you put it in of course. I have pluginsync=true in the [main] section of my puppet.conf, on both my client and server and sync works fine. Can you post your full configuration? Both client and server? Can you confirm your other settings are working when you adjust them in puppet.conf? On Apr 5, 10:43 pm, byron appelt byron.app...@gmail.com wrote: I am trying to get a custom fact to sync. The fact is in a module. It will sync if I run puppet with --pluginsync but not otherwise. I have pluginsync=true in my puppet.conf. Shouldn't the command line option and puppet.conf option have the same results? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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.
Re: [Puppet-dev] Re: [Puppet Users] Puppet Dashboard packages now available!
James Cammarata wrote: Any idea if/when these will be available in EPEL? Bundled rails and various gems will make that difficult, unfortunately. I don't know all that much about rails and gems, but if anyone knows if it's possible to cleanly install multiple versions of rails and gems, I'd be curious. If we were able to ship at least several major versions of rails in parallel, it might make it possible to package more recent tools like dashboard in Fedora and EPEL. But as long the rails stack encourages vendoring so extensively, no packages which do this will be acceptable for Fedora and EPEL. The rationale for not allowing bundled libraries (except in rare circumstances) is here: https://fedoraproject.org/wiki/Packaging:No_Bundled_Libraries Debian has a similar policy, I believe. -- ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ I do not want people to be agreeable, as it saves me the trouble of liking them. -- Jane Austen pgpP9zFSJ5GF6.pgp Description: PGP signature
Re: [Puppet Users] Why we wont use zpool ever again
Peter Meier wrote: Hi But we won't use the zpool type ever again. Its just not worth it. Here's what happened: . one of our servers lost knowledge about one of its zfs pools . puppet didn't find the pool and .. went on to zpool create it . we did indeed have a backup, but would have lost all data if not Creating zpools is a manual thing in every case, since one has to know the devices participating. The names of which tend to be a little bit different from one server to the next. Add that to the possibility of major data loss (like we just experienced) and get a negative yield for the 'zpool' type. there was recently a similar discussion about that with the new available fs and lvm type on the puppet-dev list. these are indeed very dangerous operations, where it should somehow be possible to lock them. the problem is clearly that if puppet fails to determine the correct state it tries to transfer into the right state, which might have (obviously) - ehhh - nasty side-effects on such operations. maybe you can catch that discussion up and give your thoughts about it how puppet should behave and how it would be possible to lock such operations. cheers pete I see this as being distinctly part of the provisioning portion of a server life-cycle. I haven't looked at the discussion on -dev, but i'm not sure these types really belong in core puppet. They're not unix-agnostic resources for one (has that fundamental bit of philosophy changed?), and they're unlikely to change in a way that you want puppet to 'correct'. That being said, some people have 'bootstrap' envs, which would be a better place to have these destructive resources than in your production environment. -- Joe McDonagh AIM: YoosingYoonickz IRC: joe-mac on freenode L'ennui est contre-révolutionnaire -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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.
Re: [Puppet Users] Why we wont use zpool ever again
Kaspar Schiess wrote: Hi everyone, Just wanted to tell you a little story. We've been enthusiastic puppet users since about a year ago here at the Geographic Institute of the University of Zürich. But we won't use the zpool type ever again. Its just not worth it. Here's what happened: . one of our servers lost knowledge about one of its zfs pools . puppet didn't find the pool and .. went on to zpool create it . we did indeed have a backup, but would have lost all data if not Creating zpools is a manual thing in every case, since one has to know the devices participating. The names of which tend to be a little bit different from one server to the next. Add that to the possibility of major data loss (like we just experienced) and get a negative yield for the 'zpool' type. Hoping to inspire a few.. kaspar Thunderbird and/or GMail just flaked so apologies if this is sent twice: I see this as being distinctly part of the provisioning portion of a server life-cycle. I haven't looked at the discussion on -dev, but i'm not sure these types really belong in core puppet. They're not unix-agnostic resources for one (has that fundamental bit of philosophy changed?), and they're unlikely to change in a way that you want puppet to 'correct'. That being said, some people have 'bootstrap' envs, which would be a better place to have these destructive resources than in your production environment. -- Joe McDonagh AIM: YoosingYoonickz IRC: joe-mac on freenode L'ennui est contre-révolutionnaire -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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.
Re: [Puppet Users] Why we wont use zpool ever again
On Tue, Apr 6, 2010 at 10:52 AM, Kaspar Schiess e...@space.ch wrote: Creating zpools is a manual thing in every case, since one has to know the devices participating. The names of which tend to be a little bit different from one server to the next. Wow, so I've got a fairly large Solaris 10 server deployment and I've never used the zpool type out of F.U.D. I've often thought I should, but at the same time thought I'd have to dig into the source to see what it'd actually do. So I'm surprised by the result, could you describe the situation a bit more? Every time I've used the zpool create command on a block device that was/is a member of a zpool the command complains loudly that this is a potentially dangerous and destructive operation. If I'm sure I then force the operation with zpool create -f Does the zpool type just blindly force creation and ignore these warning? In addition, I totally agree about the complexities surrounding zpool creation. I run with MPxIO and the device path names change when the system first boots after MPxIO is activated. With the complexity of dealing with two device paths before puppet configures MPxIO and one totally new name after MPxIO, I've just always dealt with it semi-manually with some helper scripts that look at format/dev/null before and after outputs, comparing them to determine the actual path I'm interested in. So I don't think this is an intractable problem, I think the type just needs to be smarter and follow the expectations people have about zpool create versus zpool create -f Is anyone interested in diving into it a bit more with me? -Jeff -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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.
[Puppet Users] sysutils/puppet: disabling freebsd ports package provider
Is there any objection to the ports provider being disabled on FreeBSD systems since it mostly just causes puppet to hang anyway? I've had no luck in fixing it. The problem is that portupgrade and script don't interact well when running non-interactively. I've been running it this way in a local port, and I'm thinking of disabling it in the official port as well. I'd post a patch for upstream as well. If there are no objections, I'll submit a PR for the change by the end of the week. Thanks, -- Russell A. Jackson r...@csub.edu Network Analyst California State University, Bakersfield -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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.
[Puppet Users] Re: Problem syncing custom fact
I found the problem. My puppet.conf somehow got checked into SVN with CR/LF line endings. Apparently this causes puppet to fail to read it, quite silently even with --debug unfortunately. On Apr 6, 11:59 am, byron appelt byron.app...@gmail.com wrote: Thanks, testing other settings was an excellent suggestion. It seems no settings in my puppet.conf are working. Any suggestions on how to debug this? This was all working before I upgrading from 0.24.5 to 0.25.4 For reference, here are my configs, although it seems that the client config is not even being read. Here is my client puppet.conf:[main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/etc/puppet/ssl rundir=/var/run/puppet factpath=/var/lib/facter pluginsync=true server=puppetmaster.numerex.com environments=production,testing environment=production [puppetd] report = true And here is the puppetmaster: main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var/run/puppet pluginsync=true server = puppetmaster.numerex.com environments = development,testing,production node_terminus = exec external_nodes = /etc/puppet/query_deploymanager.rb [puppetmasterd] certname=puppetmaster.numerex.com [puppetd] report = true [testing] modulepath = /etc/puppet-dev/manifests/classes templatedir=/etc/puppet-dev/templates manifest = /etc/puppet-dev/manifests/site.pp pluginsync = true [production] modulepath = /etc/puppet/manifests/classes templatedir=/etc/puppet/templates manifest = /etc/puppet/manifests/site.pp pluginsync = true On Apr 6, 2:17 am, Ken k...@bob.sh wrote: Yes in theory. Depending on the section you put it in of course. I have pluginsync=true in the [main] section of my puppet.conf, on both my client and server and sync works fine. Can you post your full configuration? Both client and server? Can you confirm your other settings are working when you adjust them in puppet.conf? On Apr 5, 10:43 pm, byron appelt byron.app...@gmail.com wrote: I am trying to get a custom fact to sync. The fact is in a module. It will sync if I run puppet with --pluginsync but not otherwise. I have pluginsync=true in my puppet.conf. Shouldn't the command line option and puppet.conf option have the same results? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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.
[Puppet Users] Re: Problem syncing custom fact
Looks like you are right. Line 892 from puppet/util/settings.rb:
text.split(/\n/).each { |line|
Its splitting on line feed. I'd raise a ticket if I was you - seems
like a trivial change to that regular expression.
Also - I think the puppet configuration doesn't throw errors when its
wrong. It does when you get it wrong on the command line however, so
the logic is there somewhere. This is already an open ticket here:
http://projects.puppetlabs.com/issues/3119
ken.
On Apr 6, 9:52 pm, byron appelt byron.app...@gmail.com wrote:
I found the problem. My puppet.conf somehow got checked into SVN with
CR/LF line endings. Apparently this causes puppet to fail to read it,
quite silently even with --debug unfortunately.
On Apr 6, 11:59 am, byron appelt byron.app...@gmail.com wrote:
Thanks, testing other settings was an excellent suggestion. It seems
no settings in my puppet.conf are working. Any suggestions on how to
debug this? This was all working before I upgrading from 0.24.5 to
0.25.4 For reference, here are my configs, although it seems that the
client config is not even being read.
Here is my client puppet.conf:[main]
logdir=/var/log/puppet
vardir=/var/lib/puppet
ssldir=/etc/puppet/ssl
rundir=/var/run/puppet
factpath=/var/lib/facter
pluginsync=true
server=puppetmaster.numerex.com
environments=production,testing
environment=production
[puppetd]
report = true
And here is the puppetmaster:
main]
logdir=/var/log/puppet
vardir=/var/lib/puppet
ssldir=/var/lib/puppet/ssl
rundir=/var/run/puppet
pluginsync=true
server = puppetmaster.numerex.com
environments = development,testing,production
node_terminus = exec
external_nodes = /etc/puppet/query_deploymanager.rb
[puppetmasterd]
certname=puppetmaster.numerex.com
[puppetd]
report = true
[testing]
modulepath = /etc/puppet-dev/manifests/classes
templatedir=/etc/puppet-dev/templates
manifest = /etc/puppet-dev/manifests/site.pp
pluginsync = true
[production]
modulepath = /etc/puppet/manifests/classes
templatedir=/etc/puppet/templates
manifest = /etc/puppet/manifests/site.pp
pluginsync = true
On Apr 6, 2:17 am, Ken k...@bob.sh wrote:
Yes in theory. Depending on the section you put it in of course. I
have pluginsync=true in the [main] section of my puppet.conf, on both
my client and server and sync works fine.
Can you post your full configuration? Both client and server? Can you
confirm your other settings are working when you adjust them in
puppet.conf?
On Apr 5, 10:43 pm, byron appelt byron.app...@gmail.com wrote:
I am trying to get a custom fact to sync. The fact is in a module. It
will sync if I run puppet with --pluginsync but not otherwise. I
have pluginsync=true in my puppet.conf. Shouldn't the command line
option and puppet.conf option have the same results?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@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.
[Puppet Users] Re: Exported resource [...] cannot override local resource - Common error, how to get around
You've got to think about it from the servers perspective ... its
going to see many File[list-update] resources ... one for each
machine in fact. Which is why you're getting that error. Each machines
definition is trying to overwrite the other:
@@file { list-updates:
ensure = present,
path= /opt/puppet/list-updates/${fqdn},
source = file:///tmp/puppet-list-updates,
backup = false,
}
File | title == list-updates |
The name of the resource needs to be unique when being imported, so
I'd change your configuration to use the path as the name because in
your case it _is_ going to be unique because of the fqdn var. Then
search for tags for instead for the import.
For example:
@@file { /opt/puppet/list-updates/${fqdn}:
ensure = present,
source = file:///tmp/puppet-list-updates,
backup = false,
tag = foo
}
And then on the server use:
File | tag == foo |
ken.
On Apr 6, 3:00 pm, Tore tore.lo...@gmail.com wrote:
Hi,
I've runned into a fairly common problem:
err: Could not retrieve catalog from remote server: Error 400 on
SERVER: Exported resource File[list-updates] cannot override local
resource on node
Xhttp://projects.puppetlabs.com/projects/puppet/wiki/Frequently_Asked_...
I cannot see how I can fix this. On all of my nodes i add the class
list-updates, and on the puppetmaster i add list-updates AND list-
updates::all.
The manifests:http://pastebin.com/vXqP2q6q
Of course this can be prevented by not including list-updates on the
puppetmaster. But, this problems occours since the puppetmaster
creates and uses an stored configuration. But why doesn't this pose a
problem when using
sshkeys?http://projects.reductivelabs.com/projects/puppet/wiki/Exported_Resou...
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@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.
Re: [Puppet Users] Why we wont use zpool ever again
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi On Tue, Apr 6, 2010 at 10:52 AM, Kaspar Schiess e...@space.ch wrote: Creating zpools is a manual thing in every case, since one has to know the devices participating. The names of which tend to be a little bit different from one server to the next. Wow, so I've got a fairly large Solaris 10 server deployment and I've never used the zpool type out of F.U.D. I've often thought I should, but at the same time thought I'd have to dig into the source to see what it'd actually do. So I'm surprised by the result, could you describe the situation a bit more? Every time I've used the zpool create command on a block device that was/is a member of a zpool the command complains loudly that this is a potentially dangerous and destructive operation. If I'm sure I then force the operation with zpool create -f Does the zpool type just blindly force creation and ignore these warning? as far as I understood was that the zpool information was lost, hence puppet thought that there was no zpool anymore. I assume that this means that zpool-tools didn't know about that anymore either, but it might have been recoverable with manual interaction. and looking at the code [1] it doesn't look like it uses -f. In addition, I totally agree about the complexities surrounding zpool creation. I run with MPxIO and the device path names change when the system first boots after MPxIO is activated. With the complexity of dealing with two device paths before puppet configures MPxIO and one totally new name after MPxIO, I've just always dealt with it semi-manually with some helper scripts that look at format/dev/null before and after outputs, comparing them to determine the actual path I'm interested in. in general I see disk allocation as part of provisioning, which shouldn't go into puppet. but that's how I seperate things and others might have reasons to do differently. So I don't think this is an intractable problem, I think the type just needs to be smarter and follow the expectations people have about zpool create versus zpool create -f It's a bit like the discussion in [2], how can puppet determine that there have been once something on that and that it shouldn't take the dangerous actions if the tools don't reveal it. cheers pete [1] http://github.com/reductivelabs/puppet/blob/master/lib/puppet/provider/zpool/solaris.rb [2] http://groups.google.com/group/puppet-dev/browse_thread/thread/195faece1199ef88#d34b2b17b7bdac17 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAku7x9UACgkQbwltcAfKi3/O+ACffnIb9iFMBQkYg0bE3/3eNfc9 K38AnAxfXUvmo3EtZwIYhRCSN+MPlhQf =o8pM -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-us...@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.
Re: [Puppet Users] Puppet Dashboard packages now available!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/04/10 11:07 PM, Baker, Luke Jefferson wrote: I tried installing via yum, received this error concerning the package signature.. error: rpmts_HdrFromFdno: Header V4 RSA/SHA1 signature: BAD, key ID 8347a27f What platform is this? Did it prompt you to install the GPG key? Regards James Turnbull - -- Author of: * Pro Linux System Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBS7vTQyFa/lDkFHAyAQJNzwgAkfUgzTMFKdXHGFytr5m+//Ji/8Q6Jvy8 L8+tYnGReBTMqUfjDZncTYOHI/ANYHGyB9hkaAFGd8kc9U2CQbzTnr38SReg5zOk nAMweyWy4ZTdmfS18Sq0MwJCWlKs07GDuSM3AFoz9foQnMx/+cnnS+7Bb8RWX5d2 WuY2cILUCzPXJFYcJjfLOmuLFM1kROFdAPACg2YJnj9PEyG8IZzUOuZ1U0GEjFLu RDGwc4y3Twf9oyfr0JA/+sePqpPeaPuh11TeDMG2pjoLvHc9W1DPrlDn8UPAIjxv AqmNNUY/mXE36x0roM3yahJLk38RpikInK85HlyWl+kE8AmYeBcYhw== =DOvo -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-us...@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.
Re: [Puppet Users] Puppet Dashboard packages now available!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/04/10 11:09 PM, Daniel Kerwin wrote: Do you have something like a release tarball? I'd like to create a Gentoo ebuild for it. http://yum.puppetlabs.com/sources/ Regards James Turnbull - -- Author of: * Pro Linux System Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBS7vT3SFa/lDkFHAyAQLH8AgAzpixMaDE89rBTj9Y4Ynm7V+y8uxVWaAR i6nBXKE5VdOmAzlCrlyrcdwJDOWI9ZHxjzYDs6t7JPF/1Gz84w/KTUoO3O0Y1DTE pXdoHrIoPpZgtY6Jnr1qBz2/2V/prl8/oQWVqamBD6MDzg2ptG4X4TOyfNoOrQmn Ogyqe/Kra7O3A4gXRdxqmMAViljmK1uE+ZyAiyadCfef8fF1FjIlBDZsakaIG1qi 1eqWXPYJzuKTAAwZWVy3l/arQrhHnfRrhLXKMEB7cA6ZjAoUI1WTTrtN3kylUOvM fomTiuM5N43ND3d2E7Jb9pzF9oHflIG/dYLqkOJT7oEAqPJM6g4KiA== =9BG1 -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-us...@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.
[Puppet Users] Re: Puppet Dashboard packages now available!
On Tue, Apr 6, 2010 at 3:48 AM, James Turnbull ja...@lovedthanlost.net wrote: Hi all I've created RPM and DEB packages for the Puppet Dashboard 1.0.0rc1. These are available via APT and Yum repositories hosted by Puppet Labs. Cool. A puppetlabs-release RPM might be nice for this. --Michael -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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.
Re: [Puppet Users] Re: Puppet Dashboard packages now available!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/04/10 10:38 AM, Michael DeHaan wrote: On Tue, Apr 6, 2010 at 3:48 AM, James Turnbull ja...@lovedthanlost.net wrote: Hi all I've created RPM and DEB packages for the Puppet Dashboard 1.0.0rc1. These are available via APT and Yum repositories hosted by Puppet Labs. Cool. A puppetlabs-release RPM might be nice for this. On the list. Regards James Turnbull - -- Author of: * Pro Linux System Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBS7vUniFa/lDkFHAyAQK45QgA5R4nCKx71vhKIye/2U6OigRUje0+pFAD Ea/uuxfBCX4ZuuAv7lzGD4C7SdYZj1eHyK7+CYtJ4gkyV8WKrzpGJMYCl3S0IIot DPxa5rJCzaJL5AcrgOn4Tyl3wrlY+BldiRk1lRTPwf6ZPOPZl5/Zosw6tisVMPq/ YtNK1vDZu/cTB96q2GeniQlZ1LZ8fYvNNuuxqAxqzqpaDKi5HJkR+AoCMZXzKTNx VJ1bjkrYYdW9wdBWLBh7YEdHUCrobavEoSJLC1I13QLcaN/iSzIJB0x2mhb/PJO2 y+Gh9/4tbKzWeEtzsBvuEYyNls4BucEYr89MFUr2mhYeI+nix5qMgQ== =zQIi -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-us...@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.
Re: [Puppet Users] Puppet Dashboard packages now available!
RHEL5.5 (beta) x86_64. It did not prompt to sign the GPG key. On Apr 6, 2010, at 19:35, James Turnbull ja...@lovedthanlost.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/04/10 11:07 PM, Baker, Luke Jefferson wrote: I tried installing via yum, received this error concerning the package signature.. error: rpmts_HdrFromFdno: Header V4 RSA/SHA1 signature: BAD, key ID 8347a27f What platform is this? Did it prompt you to install the GPG key? Regards James Turnbull - -- Author of: * Pro Linux System Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBS7vTQyFa/lDkFHAyAQJNzwgAkfUgzTMFKdXHGFytr5m+//Ji/8Q6Jvy8 L8+tYnGReBTMqUfjDZncTYOHI/ANYHGyB9hkaAFGd8kc9U2CQbzTnr38SReg5zOk nAMweyWy4ZTdmfS18Sq0MwJCWlKs07GDuSM3AFoz9foQnMx/+cnnS+7Bb8RWX5d2 WuY2cILUCzPXJFYcJjfLOmuLFM1kROFdAPACg2YJnj9PEyG8IZzUOuZ1U0GEjFLu RDGwc4y3Twf9oyfr0JA/+sePqpPeaPuh11TeDMG2pjoLvHc9W1DPrlDn8UPAIjxv AqmNNUY/mXE36x0roM3yahJLk38RpikInK85HlyWl+kE8AmYeBcYhw== =DOvo -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-us...@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 . -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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.
Re: [Puppet Users] Re: Puppet Dashboard packages now available!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/04/10 10:38 AM, Michael DeHaan wrote: On Tue, Apr 6, 2010 at 3:48 AM, James Turnbull ja...@lovedthanlost.net wrote: Hi all I've created RPM and DEB packages for the Puppet Dashboard 1.0.0rc1. These are available via APT and Yum repositories hosted by Puppet Labs. Cool. A puppetlabs-release RPM might be nice for this. I've created and update a puppetlabs-repo RPM at: http://yum.puppetlabs.com/base/puppetlabs-repo-1.0-1.noarch.rpm That adds the Puppet Labs GPG key and a puppetlabs.repo file. Regards James Turnbull - -- Author of: * Pro Linux System Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBS7vYdiFa/lDkFHAyAQIBNQf+PrpQWXeVM3Zx5VbsmT3YKkDS3Zqrl3zk /VioFeJoBoR6/RERvFOh6h0Y5Iu/Rgnjcr2eODiCAcGI0k9g6Vy4MytxtlLo8RPW lo4+YVB+KxbZpT1g6JSVRm5ZYxq+NCURCVYFdc01uiIs4RYgCtqw8PMwc0G94ewW PzrWBFqnUVKbfRUdgJlcwBSxrhfetkR/RJsBYFYgWGlbJTnyzZdO1j7rPkSytKbH 7ntiBIOkCyAhsxHqW4vw46npkm/i7iaMOBw1WKjhdVog7IaTod2rZIzdQxuO8vIG YdqLhUGi4WLyaL8xovREseQFaQ9bQ0RIIPC35xZkoSTL8vL2oZTZgQ== =QC8W -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-us...@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.
Re: [Puppet Users] Specifying Yum Options
On Sat, Apr 3, 2010 at 3:46 AM, Eric Shamow eric.sha...@gmail.com wrote: A not-so-elegant solution is to write your own yum provider that allows you to do this. In my case I found one online -- if you google yum_plus.rb you should be able to find it. If not let me know and I'll post the work here. On Thu, Apr 1, 2010 at 10:19 PM, Isaac Christoffersen isaac.christoffer...@gmail.com wrote: We're using RHN Satellite server to manage our packages and we have a custom package channel for third-party packages. Unfortunately, some of the packages in the channel are unsigned. Is there a way to get the Package Provider for yum to use the nogpgcheck option? Right now, I'm using an exec declaration instead of a package, but it seems kludgy to do this. Of course, from a larger perspective, I'd like to be able to pass any valid yum option via the package syntax in Puppet. (i.e. Download Only, Enable Repo, Group Install, etc.) thanks, Isaac -- I just created a separate repository for those packages, and turned off gpgcheck. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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.
Re: [Puppet Users] Export resource issue - more than one of content, source, target
Alan Sparks wrote:
I'm trying to create an exported file resource and receiving a vague
error message:
Apr 5 18:01:04 ny4-dev-util01 puppetd[12860]: Could not run Puppet
configuration client: You cannot specify more than one of content,
source, target at line 102
A puppet client (it's 0.24.8) is creating the following resource:
@@file { mlwormbackup_$fqdn:
mode= 644,
owner = root,
group = root,
ensure = $worm_backup_enabled,
path= /root/ml_backup_hosts/$fqdn,
content =
HOST=$fqdn\nCLEAR=$my_clear_shortname\nCLIENT=$my_bd_shortname\n,
tag = mlwormbackup,
}
Another server (this is a 0.25.4 puppet) has the following in its node
definition:
File | tag == mlwormbackup |
All are running against a 0.25.4 puppetmaster. We're in process of
testing migration of all to 0.25.
The message makes no sense to me. The resource only has a content
parameter, no source or target. Why is the 0.25 puppet (or the
puppetmaster?) complaining about more than one of anything? I've
looked for duplicate instances of this resource, emptied the
storeconfigs database completely, and still cannot locate the source of
this message.
Is there some incompatibility in stored configs between 0.24 and 0.25
clients?
Thanks in advance for any advice.
-Alan
Actually the problem was the value of ensure. That was getting set to
true or false (set by a boolean test). Puppet saw true, and threw
that error message (not very helpful, oh well). Fixing it to a
conditional file or absent helped.
Thanks Ken for making me think in that direction.
-Alan
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@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.
[Puppet Users] puppet clients dieing
Hi list, has anyone else experienced puppet clients that die when the network goes down for an extended period of time ? OS rhel 5 puppet clients / master 0.25.1 clients are left in a state where ~# service puppet status puppetd dead but pid file exists ~# service puppet restart Stopping puppet: [FAILED] Starting puppet: [ OK ] Obviously the stopping part fails because the puppet process has dies previously. Regards, Nathan -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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.
