[Puppet Users] Re: trouble with custom type on 0.24.8
Hi, >> I'm having trouble getting a simple custom type to work. >> >> Clients are giving me the following error: >> "Could not retrieve catalog: Could not find resource type zypper_repo >> at /etc/puppet/manifests/nodes/mgt.pp:33 on node " I'm experiencing the same problem with a custom type in 0.24.8. The type compiles when called with 'ruby -rpuppet '. With irb, I can retrieve the type just fine. Any chance that it is related to this bug? http://projects.reductivelabs.com/issues/2574 best regards Bernhard --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Puppet Users] weird puppet behavior
Hi,
I have an exec command that executed successfully, but when checking the
processes it did not run the command.
--manifest--
179 exec { "sh /mnt/oracle-installation/database/runInstaller -silent
-ignoreDiskWarning -responsefile
/mnt/oracle-installation/database/oracle-11g_SE.rsp":
180 alias => oracle_installed,
181 require => [User["oracle_user"],
182 Exec["oracle_dl"],
183 Exec["oracle_extracted"],
184 File["responsefile"],
185 File["oracle_installation_dir"],
186 File["oracle_orainventory_dir"],
187 File["oracle_dir"]],
188 path => ["/usr/bin", "/usr/sbin", "/bin", "/sbin"],
190 user => oracle,
191 creates => "/var/puppet/state/oracleinstalled",
--log says--
Fri Oct 16 11:04:42 + 2009 //Node[basenode]/oraclecube/Exec[sh
/mnt/oracle-installation/database/runInstaller -silent
-ignoreDiskWarning -responsefile
/mnt/oracle-installation/database/oracle-11g_SE.rsp] (debug): Changing
returns
Fri Oct 16 11:04:42 + 2009 //Node[basenode]/oraclecube/Exec[sh
/mnt/oracle-installation/database/runInstaller -silent
-ignoreDiskWarning -responsefile
/mnt/oracle-installation/database/oracle-11g_SE.rsp] (debug): 1 change(s)
Fri Oct 16 11:04:42 + 2009 //Node[basenode]/oraclecube/Exec[sh
/mnt/oracle-installation/database/runInstaller -silent
-ignoreDiskWarning -responsefile
/mnt/oracle-installation/database/oracle-11g_SE.rsp] (debug): Executing
'sh /mnt/oracle-installation/database/runInstaller -silent
-ignoreDiskWarning -responsefile
/mnt/oracle-installation/database/oracle-11g_SE.rsp'
Fri Oct 16 11:04:42 + 2009 Puppet (debug): Executing 'sh
/mnt/oracle-installation/database/runInstaller -silent
-ignoreDiskWarning -responsefile
/mnt/oracle-installation/database/oracle-11g_SE.rsp'
Fri Oct 16 11:04:47 + 2009 //Node[basenode]/oraclecube/Exec[sh
/mnt/oracle-installation/database/runInstaller -silent
-ignoreDiskWarning -responsefile
/mnt/oracle-installation/database/oracle-11g_SE.rsp]/returns (notice):
executed successfully
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
[Puppet Users] Re: weird puppet behavior
> I have an exec command that executed successfully, but when checking the > processes it did not run the command. version etc? If puppet tells you that the exec ran successfully the cmd exited with exit code 0. 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-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 -~--~~~~--~~--~--~---
[Puppet Users] Local disks and puppet ?
Hello there, I would like to automatize my snmpd.conf with all local disks discovered by puppet. For example, in my template : snmpd.erb I have : --//-- syslocation "<%= syslocation %>" syscontact "ITadmin " rocommunity cfmpublic sysservices 78 # Monitoring des partition disk / 2000 disk /opt 2000 --//-- I'd like to add disk 2000 on every local disks. Before I doing anything about that, I wanted to know if someone has already done that before ? /Xavier -- Xavier Beaudouin - http://kazar.net/ http://magicduck.labrute.fr/ --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Puppet Users] Re: Local disks and puppet ?
Hello If you really want all disks 2000 then net-snmp's "includeAllDisks 2000" might do for you. Neil Xavier Beaudouin wrote: > Hello there, > > I would like to automatize my snmpd.conf with all local disks discovered > by puppet. > > For example, in my template : snmpd.erb I have : > > --//-- > syslocation "<%= syslocation %>" > syscontact "ITadmin mailto:itad...@cfm.fr>>" > rocommunity cfmpublic > > sysservices 78 > > # Monitoring des partition > disk / 2000 > disk /opt 2000 > --//-- > > I'd like to add disk 2000 on every local disks. Before I > doing anything about that, I wanted to know if someone has already done > that before ? > > /Xavier > > -- > Xavier Beaudouin - http://kazar.net/ > http://magicduck.labrute.fr/ > > > --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Puppet Users] Re: weird puppet behavior
Yes, it did return exit 0, that's why it's weird Peter Meier wrote: >> I have an exec command that executed successfully, but when checking the >> processes it did not run the command. > > version etc? > > If puppet tells you that the exec ran successfully the cmd exited with > exit code 0. > > 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-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 -~--~~~~--~~--~--~---
[Puppet Users] ANNOUNCE: Puppet 0.25.1rc2 available
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Puppet 0.25.1 Release Candidate 2 is now available for testing.
This is the second release candidate for 0.25.1. The 0.25.1 release
is a maintenance release in the 0.25.x branch.
The release candidate is available at:
http://reductivelabs.com/downloads/puppet/puppet-0.25.1rc2.tar.gz
http://reductivelabs.com/downloads/gems/puppet-0.25.1rc2.gem
Please test the release and report feedback via the Reductive Labs
Redmine site:
http://projects.reductivelabs.com
Please select an affected version of 0.25.1rc2.
RELEASE NOTES
* We've clarified that the new 'require' function only works for
0.25.x clients. If the function is specified with 0.24.x or earlier
clients the class will be included but the inherent dependency will
not be created. A warning message will be generated informing you
of this.
* Node regular expression matching rules have been clarified - see
http://reductivelabs.com/trac/puppet/wiki/LanguageTutorial#matching-nodes-with-regular-expressions.
* The Nagios serviceescalation type now supports the use of the
servicegroup_name attribute.
* The Puppet gem now installs all binaries to the 'bin' directory
because Gems lack support for both a 'bin' and 'sbin' directory.
Facter (version later than 1.5.1) is now also a dependency for the gem.
CHANGELOG
* Bug #1538: Yumrepo sets permissions wrongly on files in
/etc/yum.repos.d
* Bug #1719: Puppetd runtime increase dramatically after upgrading
to 24.6
* Bug #2508: misleading error about ActiveRecord versions
* Bug #2600: Master under mongrel wrong number of arguments (3 for 2)
* Bug #2601: fqdn_rand raises exception when passed a seed
* Bug #2605: Ruby 1.8.1 compatibility - #1963 fix uses method not in
1.8.1
* Bug #2606: Gems can't handle binaries in the sbin directory
* Bug #2607: 0.25 gem does not have facter as a dependency
* Bug #2608: install.rb will not run on ruby 1.9.1 due to ftools
being deprecated
* Bug #2612: vim syntax highlighting of new regex language features
* Bug #2613: Autorequire fails when a directory's path has a trailing /
* Bug #2615: YAML sometimes modifies the contents of string data
* Bug #2616: Locking error in tagmail
* Bug #2618: Spurious test failures when testing redhat service
providers on debian variants
* Bug #2619: Fresh 0.25.0 client cannot 'authenticate' to 0.25.0
puppetmaster.
* Bug #2620: Regex problem in puppetmaster auth.conf
* Bug #2621: possible JSon serialization issue (on debian/lenny/amd64)
* Bug #2622: puppetdoc returns undefined method '[]'
* Bug #2626: Unhelpful error message
* Bug #2627: Node regular expressions only work in some cases
* Bug #2632: require doesnt seem to work
* Bug #2634: nagios type serviceescalation should support
servicegroup_name
* Bug #2637: SSL socket race condition under webrick
* Bug #2638: inconsistent behaviour when more than one "node /foo/ {
}" stanza matches.
* Bug #2639: Fail to store reports in simple default config
* Bug #2640: runit service provider does not create symlinks
* Bug #2642: runit service provider doesn't have a restart command
* Bug #2648: macauthorization provider spuriously changes values
when not needed.
* Bug #2651: Directory permissions on man pages can be incorrect
* Bug #2652: syntax error in lib/puppet/util/selinux.rb according to
Fedora 11 ruby 1.8.6
* Bug #2654: Confusing error message when a provider lacks a feature
* Bug #2656: Puppet --parseonly tests hang forever
* Bug #2664: regexp parse error
* Bug #2672: Cannot have underscores in node name
* Bug #2674: createpackage.sh: problem finding install.rb
* Bug #2675: ending slash in directory name gets stripped off
* Bug #2676: lib/puppet/agent.rb apparent typo
* Bug #2679: Possible regression
* Bug #2681: "Duplicate generated resource;skipping" for each
managed resource
* Bug #2686: ActiveSupport >= 2.3.3 forces use of defective JSON library
* Bug #2688: macauthorization provider now doesn't deal with
booleans correctly.
* Bug #2697: provider/portage.rb: update-eix is deprecated
* Bug #2698: provider/portage.rb: format string has changed (again)
* Bug #2699: Configurable port in the included Red Hat init script
is broken
* Bug #2702: puppetdoc rdoc mode fails if outputdir not specified
* Bug #2707: 'config_version' should behave better on failure
* Bug #2711: Storeconfigs don't work with puppet command
* Feature #2393: We should maintain a dynamically-built 'next' branch
Regards
James Turnbull
- --
Author of:
* Pro Linux Systems 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/
iQEVAwUBStkpsSFa/lDkFHAyAQIT8wgAwpqI4UzUMBjaerndeRLkA8JWWpc81tBG
qwytX5gd0qRqnVofMj7reZH9RVEKQBSF305FzhEui/I5XEfrOJbJywN5P+MmYJ6C
5h4KeSs8Puedc7q8gTnf+zIPlify9Fwqt532SrU+6OL2Niwv1uGydX
[Puppet Users] Re: Is there a limit to the number of entires you can have for modulepath in puppet.conf?
Are you experiencing an error? Have you tested? Regards James Turnbull -- Author of: * Pro Linux Systems 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-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 -~--~~~~--~~--~--~---
