[Puppet Users] Re: Cache for the local system while offline
I am too getting the same message error as, err: Could not retrieve catalog from remote server: getaddrinfo: Name or service not known err: Could not retrieve catalog; skipping run err: Could not send report: getaddrinfo: Name or service not known Can anyone assist how cache cache can be achieve on the nodes. Thanks mukulm On Feb 16, 8:05 am, Khoury Brazil khoury.bra...@gmail.com wrote: On Wed, Feb 15, 2012 at 5:51 PM, Daniel Pittman dan...@puppetlabs.com wrote: On Wed, Feb 15, 2012 at 17:26, Khoury Brazil khoury.bra...@gmail.com wrote: On Thu, Feb 9, 2012 at 1:09 PM, Daniel Pittman dan...@puppetlabs.com wrote: On Thu, Feb 9, 2012 at 06:12, mukulm smilemukul2...@gmail.com wrote: I want to cache the updates for the users system received from the server so that the users can get the updates from the local system cache while offline. Any idea how can server updates be stored on the users system while offline ? You likely want `--usecacheonfailure`, or the equivalent setting in `puppet.conf`: http://docs.puppetlabs.com/references/stable/configuration.html#useca... Whether to use the cached configuration when the remote configuration will not compile. This option is useful for testing new configurations, where you want to fix the broken configuration rather than reverting to a known-good one. That should also apply when you can't communicate with the master. Unfortunately, at least in my case, when I run puppet on a client that is off of the network (in this particular case its a Macbook Pro) it seems that something is failing locally, causing a warning: not using cache on failed catalog. […] This is the output from an offline debug run: macbookproagent:/ admin$ sudo puppet agent -t --debug One of the features of the `-t` or `--test` flag is that it disables use of the cached catalog when you can't fetch it down. Does it work better if you don't specify `--test`? If not, please file a bug report. :) -- Daniel Pittman ⎋ Puppet Labs Developer –http://puppetlabs.com ♲ Made with 100 percent post-consumer electrons -- I guess I *was* missing something (something very obvious...). Thanks for the help, that was indeed the issue. :) -- 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.
Re: [Puppet Users] Re: vmware provisioning
You might want to take a look at veewee03. It now can create baseboxes on Vmware Fusion. Which allows you to export them to OVA format that you can import in Vsphere/Esx https://github.com/jedi4ever/veewee On 16/02/12 00:34, Eric Shamow wrote: Indeed, at $(job - 1) we implemented something to do this pretty quickly, although not with the flexibility of cloud provisioner. In theory it should be easy to write something through the cloud provisioning framework that takes even less time and is more flexible than our tools, but it's a fairly straightforward task. -Eric -- Eric Shamow Professional Services http://puppetlabs.com/ (c)631.871.6441 On Wednesday, February 15, 2012 at 5:36 PM, Brian Gupta wrote: Foreman has support for this. (Tied into Foreman provisioning workflow). I am unaware of any other support for VMware provisioning in the open source Puppet world, but in theory it shouldn't be too hard to write. -Brian On Wed, Feb 15, 2012 at 3:55 PM, Luke lutay...@gmail.com mailto:lutay...@gmail.com wrote: Just to clarify, We currently have centos templates in ESX that we manually clone to VM and configure (add HD network etc) then kick off puppet. We would like to automate these initial steps. On Feb 15, 4:30 pm, Luke lutay...@gmail.com mailto:lutay...@gmail.com wrote: Does anyone know of a module that will spin up and configure a centos vmware template? I see options with PE any with the open source version? -- 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 mailto:puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com mailto:puppet-users%2bunsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- http://aws.amazon.com/solutions/solution-providers/brandorr/ -- 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 mailto:puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com mailto: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-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. -- 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.
Re: [Puppet Users] Re: vmware provisioning
On 16. feb. 2012 00:34, Eric Shamow wrote: In theory it should be easy to write something through the cloud provisioning framework that takes even less time and is more flexible than our tools, but it's a fairly straightforward task. I've been thinking about doing exactly that but I'm a bit worried about what Puppetlabs response would be. I've asked earlier and from what I could understand it wouldn't be a problem, but still .. All the pieces for an open source implementation are right there, if someone wants to connect the dots. -- http://www.uib.no/personer/Jan.Ivar.Beddari -- 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: About puppet report
PS: my tagmail.conf file contains: warning: m...@email.tld On Feb 16, 9:44 am, Dmitry trtrmi...@gmail.com wrote: Hello! I am using puppet-2.7.6 under FreeBSD. Here is my config file: [agent] server = some.server.tld splay = true [master] reportfrom = s...@email.tld reports = store, tagmail ssl_client_header = SSL_CLIENT_S_DN ssl_client_verify_header = SSL_CLIENT_VERIFY If client is unable to sync files with master, I want to receive e- mail with problem description. Recently I made a mistake in my server config (wrong path to a file). I got error in client's log: puppet-agent[82214]: (/Stage[main]/Suggest-test/File[/etc/rc.conf.d/ lighttpd]) Could not evaluate: Could not retrieve information from environment production source(s) puppet:///modules/bsd/etc/rc.conf.d/lighttpd at /usr/local/etc/puppet/modules/bsd/manifests/init.pp:16 but no e-mail so this problem was unnoticed until I found it in log. What should I do in order to receive e-mail from puppet next time I make similar mistake? Thanks! -- 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] puppet agent test showing error.
Hi , I have installed puppet master and puppet client on the same machine using synaptic package manager. Puppet client and Puppet master are on the same machine having Ubuntu (10.10 LTS )as base operating system. root@laptop:/etc/puppet# puppetd agent --test info: Retrieving plugin err: /File[/var/lib/puppet/lib]: Failed to generate additional resources using 'eval_generate': Connection refused - connect(2) err: /File[/var/lib/puppet/lib]: Failed to retrieve current state of resource: Connection refused - connect(2) Could not retrieve file metadata for puppet://puppet/plugins: Connection refused - connect(2) err: Could not retrieve catalog from remote server: Connection refused - connect(2) warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run Installed Puppet Version is 0.25.4 Can you guys help me resolving this error . -- Best Regards, Suresh Kumar Prajapati Operation Engineer(Inmobi India) E-mail: er.sureshprajap...@gmail.com Mob No: +91-8800920533 Theory is when you know all and nothing works. Practice is when all works and nobody knows why. In this case we have put together theory and practice: nothing works... and nobody knows why! -- 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.
Re: [Puppet Users] puppet agent test showing error.
Installed Puppet Version is 0.25.4 Can you guys help me resolving this error . Could you get the latest from repos - http://apt.puppetlabs.com/dists/maverick/main/binary-amd64/Packages And did your puppetmaster start? -- Krish OlinData.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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet agent test showing error.
On Thu, Feb 16, 2012 at 5:42 PM, krish das.srikris...@gmail.com wrote: Installed Puppet Version is 0.25.4 Can you guys help me resolving this error . Could you get the latest from repos - http://apt.puppetlabs.com/dists/maverick/main/binary-amd64/Packages And did your puppetmaster start? thanx for replying... done the same installed everything from scratch using source ... Now puppet version is : root@inmobi-laptop:~# puppet --version 2.7.10 root@inmobi-laptop:~# facter --version 1.6.5 And again new error came : root@laptop:/etc/puppet# puppetd agent --test /usr/local/lib/site_ruby/1.8/puppet/util/plugins.rb:49:in `expand_path': No such file or directory - getcwd (Errno::ENOENT) from /usr/local/lib/site_ruby/1.8/puppet/util/plugins.rb:49:in `look_in' from /usr/local/lib/site_ruby/1.8/puppet/util/plugins.rb:49:in `collect' from /usr/local/lib/site_ruby/1.8/puppet/util/plugins.rb:49:in `look_in' from /usr/local/lib/site_ruby/1.8/puppet/util/plugins.rb:54 from /usr/local/lib/site_ruby/1.8/puppet/application.rb:2:in `require' from /usr/local/lib/site_ruby/1.8/puppet/application.rb:2 from /usr/local/lib/site_ruby/1.8/puppet/application/agent.rb:1:in `require' from /usr/local/lib/site_ruby/1.8/puppet/application/agent.rb:1 from /usr/sbin/puppetd:3:in `require' from /usr/sbin/puppetd:3 -- Krish OlinData.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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Best Regards, Suresh Kumar Prajapati Linux System Admin E-mail: er.sureshprajap...@gmail.com Mob No: +91-8800920533 Theory is when you know all and nothing works. Practice is when all works and nobody knows why. In this case we have put together theory and practice: nothing works... and nobody knows why! -- 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.
Re: [Puppet Users] Re: puppet on solaris 11
Whoa! It was just a syntax error! That did it! Thanks man! However
don't you agree if puppet would say something more informative such as
... oh I don't know.. 'command not found' or 'syntax error'... I
don't necessarily expect anyone to do something about this... just
sayin'!
but anyway, thanks again!
tim
On Thu, Feb 16, 2012 at 12:22 AM, deet somew...@gmail.com wrote:
Tim.
From your example I don't think puppet file /etc/hosts is a valid
puppet command. I'm guessing you wanted to query the /etc/hosts file
resource with the resource command like the following. See if that
works for you.
$puppet resource file /etc/hosts
file { '/etc/hosts':
ensure = 'file',
content = '{md5}37f394d9e3ddf52285821ff88367c099',
ctime = 'Tue Jan 03 15:43:33 -0800 2012',
group = '0',
mode = '644',
mtime = 'Tue Jan 03 15:43:33 -0800 2012',
owner = '0',
type = 'file',
}
On Feb 15, 8:11 pm, heriyanto shell.heriya...@gmail.com wrote:
Maybe you can check this log installation for solaris
11http://log.unixhat.com/2012/02/setup-instalasi-solaris-sebagai-puppet...
On 02/16/2012 10:53 AM, Tim Dunphy wrote:
Hello Darin,
Thanks for your input. Well I've tried the repo that you suggested
however the result appears to be the same:
root@sol5:~# puppet file /etc/hosts
/opt/csw/lib/ruby/site_ruby/1.8/puppet/application.rb:219:in `find':
undefined method `join' for Puppet::Application::File:Class
(NoMethodError)
from
/opt/csw/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:60:in
`execute'
from /opt/csw/bin/puppet:4
Same exact error as when I install puppet via gem or source. Any
further thoughts?
thanks!
tim
On Wed, Feb 15, 2012 at 5:02 PM, Darin Perusichda...@darins.net wrote:
Puppet package for solaris are available from OpenCSW.org and are kept
up to date by the maintainer. You may find this easier and cleaner
then mucking around with source and gem installs.
--
Later,
Darin
On Wed, Feb 15, 2012 at 4:40 PM, Tim Dunphybluethu...@gmail.com wrote:
hello,
I've been asked to install puppet client onto a solaris 11 machine. I
found some instructions that referenced a website called
'codenursary.com' however that website does not appear to be online
anymore.
http://projects.puppetlabs.com/projects/1/wiki/Puppet_Solaris
codenursery.com
However I attempted both a gem install of puppet as well as a source
install with ./install.rb and I get the same results whenever I try to
run a puppet foo command:
root@sol3:/opt/puppet-2.7.10# puppet file /etc/hosts
/usr/ruby/1.8/lib/ruby/site_ruby/1.8/puppet/application.rb:219:in
`find': undefined method `join' for Puppet::Application::File:Class
(NoMethodError)
from
/usr/ruby/1.8/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:60:in
`execute'
from /usr/ruby/1.8/bin/puppet:4
So kind puppeteers I would like to know what on earth I am doing wrong
and how can I get a working puppet installation under Solaris 11 x86?
Thanks you
tim
tim
--
GPG me!!
gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
--
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
athttp://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-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group
athttp://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-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.
--
GPG me!!
gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
--
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: Removing the ability to serve symlinks as symlinks from the master...
On Feb 15, 3:29 pm, Daniel Pittman dan...@puppetlabs.com wrote: On Tue, Feb 14, 2012 at 06:54, jcbollinger john.bollin...@stjude.org wrote: [...] As I understand it, the issue is not with putting a symlink in a module but rather with recursively managing a directory tree that contains symlinks. Modules appear to have nothing to do with it -- it's all about the behavior of the File resource type. That is more or less true; modules are relatively unrelated to this, although part of the motivation is understanding how to make things more predictable so we have less headache getting reusable modules built up. Fair enough. As to the main issue, then, I recognize that the File resource's recursive directory management is a perpetual source of headaches, but I'm not seeing why its documented (but failing) behavior with respect to symlinks is inherently worse than the rest of the recursive management stuff. Nor do I see why recursive management of symlinks as symlinks presents a particular issue for reusable modules. Furthermore, if it makes sense (and it does) for the File resource to be able to manage individual symlinks via ensure = link, possibly augmented by force = true, then why would it not make sense to provide the same capabilities in a recursive situation? Indeed, it would present an internal consistency problem if Puppet were willing to manage symlinks only for individual File resources, and not recursively. It shouldn't require recursive file copying for this to take effect, I think, but the uncertainty is part of the motivation here. If the File resource behaved as documented then there would be no uncertainty. With recurse = true, links = manage, force = true the File resource would always manage a node's corresponding directory tree into an exact match to the master's. Where is the uncertainty in that? The uncertainty arises because of a *bug*. Removing the buggy feature would clear up the uncertainty, but so would fixing the bug. Ergo, uncertainty is not a valid argument for removing the feature. John -- 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.
Re: [Puppet Users] Re: Removing the ability to serve symlinks as symlinks from the master...
On 02/16/2012 03:30 PM, jcbollinger wrote: If the File resource behaved as documented then there would be no uncertainty. With recurse = true, links = manage, force = true the File resource would always manage a node's corresponding directory tree into an exact match to the master's. Where is the uncertainty in that? Agree, and I would expect Puppet to behave this way. If I wanted a symlink, I'd force create a symlink on the master and expect it to be created exactly the same on the agent. If I wanted that symlink to point to a file with some content, I'd manage the real path. To me, a symlink is just a pointer with no content. Simple as that. I didn't know about the 'links = follow' setting and I'd argue that feature is a bit misguided. I wouldn't expect or maybe even want Puppet to have this ability. -- http://www.uib.no/personer/Jan.Ivar.Beddari -- 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.
Re: [Puppet Users] Puppet on Windows
Hi Jay,
On Thu, Feb 16, 2012 at 6:14 AM, Jay Ze iltisannihila...@googlemail.comwrote:
Hi,
I want to run Puppet on a Windows 2003 Server. I already have a
working Puppetmaster (Scientific Linux).
I installed Puppet on Windows like shown here:
http://projects.puppetlabs.com/projects/1/wiki/Puppet_Windows
This worked very well.
Great to hear.
notice: Ignoring --listen on onetime run
info: Retrieving plugin
err: /File[C:/Dokumente und Einstellungen/All Users/Anwendungsdaten/
PuppetLabs/p
uppet/var/lib]: Failed to generate additional resources using
'eval_generate: Co
uld not intern_multiple from pson: Paths must be fully qualified
err: /File[C:/Dokumente und Einstellungen/All Users/Anwendungsdaten/
PuppetLabs/p
uppet/var/lib]: Could not evaluate: Could not intern from pson: Paths
must be fu
lly qualified Could not retrieve file metadata for puppet://
foreman.id.dvag.com/
plugins: Could not intern from pson: Paths must be fully qualified
This is https://projects.puppetlabs.com/issues/11408#note-32
It will be fixed shortly.
err: Could not retrieve catalog from remote server: Error 400 on
SERVER: PGError
: ERROR: invalid byte sequence for encoding UTF8: 0xe46973
: INSERT INTO fact_values (value, host_id, created_at,
fact_name_id,
updated_at) VALUES ('Mitteleuropõische Zeit ', 88, '2012-02-16
15:13:29.29309
9', 28, '2012-02-16 15:13:29.293099') RETURNING id
Somewhere between facter gathering the hostname and the hostname being
inserted into the database, there is a problem with how we are handling
UTF8 encoding. The text 'Mitteleuropõische Zeit' should be UTF8 encoded as
'4D 69 74 74 65 6C 65 75 72 6F 70 C3 B5 69 73 63 68 65 20 5A 65 69 74 20'
(in hex). The sequence 'e4 69 73' is most definitely an illegal UTF8
sequence.
Can you file a ticket against puppet?
Thanks,
Josh
--
Josh Cooper
Developer, Puppet Labs
--
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.
Re: [Puppet Users] Re: puppet on solaris 11
On Thu, Feb 16, 2012 at 5:39 AM, Tim Dunphy bluethu...@gmail.com wrote:
Whoa! It was just a syntax error! That did it! Thanks man! However
don't you agree if puppet would say something more informative such as
... oh I don't know.. 'command not found' or 'syntax error'... I
don't necessarily expect anyone to do something about this... just
sayin'!
Tim, feel free to file that as a fix. That error message is a bit unhelpful.
http://projects.puppetlabs.com/projects/puppet/issues
Thanks
Mike
but anyway, thanks again!
tim
On Thu, Feb 16, 2012 at 12:22 AM, deet somew...@gmail.com wrote:
Tim.
From your example I don't think puppet file /etc/hosts is a valid
puppet command. I'm guessing you wanted to query the /etc/hosts file
resource with the resource command like the following. See if that
works for you.
$puppet resource file /etc/hosts
file { '/etc/hosts':
ensure = 'file',
content = '{md5}37f394d9e3ddf52285821ff88367c099',
ctime = 'Tue Jan 03 15:43:33 -0800 2012',
group = '0',
mode = '644',
mtime = 'Tue Jan 03 15:43:33 -0800 2012',
owner = '0',
type = 'file',
}
On Feb 15, 8:11 pm, heriyanto shell.heriya...@gmail.com wrote:
Maybe you can check this log installation for solaris
11http://log.unixhat.com/2012/02/setup-instalasi-solaris-sebagai-puppet...
On 02/16/2012 10:53 AM, Tim Dunphy wrote:
Hello Darin,
Thanks for your input. Well I've tried the repo that you suggested
however the result appears to be the same:
root@sol5:~# puppet file /etc/hosts
/opt/csw/lib/ruby/site_ruby/1.8/puppet/application.rb:219:in `find':
undefined method `join' for Puppet::Application::File:Class
(NoMethodError)
from
/opt/csw/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:60:in
`execute'
from /opt/csw/bin/puppet:4
Same exact error as when I install puppet via gem or source. Any
further thoughts?
thanks!
tim
On Wed, Feb 15, 2012 at 5:02 PM, Darin Perusichda...@darins.net wrote:
Puppet package for solaris are available from OpenCSW.org and are kept
up to date by the maintainer. You may find this easier and cleaner
then mucking around with source and gem installs.
--
Later,
Darin
On Wed, Feb 15, 2012 at 4:40 PM, Tim Dunphybluethu...@gmail.com wrote:
hello,
I've been asked to install puppet client onto a solaris 11 machine. I
found some instructions that referenced a website called
'codenursary.com' however that website does not appear to be online
anymore.
http://projects.puppetlabs.com/projects/1/wiki/Puppet_Solaris
codenursery.com
However I attempted both a gem install of puppet as well as a source
install with ./install.rb and I get the same results whenever I try to
run a puppet foo command:
root@sol3:/opt/puppet-2.7.10# puppet file /etc/hosts
/usr/ruby/1.8/lib/ruby/site_ruby/1.8/puppet/application.rb:219:in
`find': undefined method `join' for Puppet::Application::File:Class
(NoMethodError)
from
/usr/ruby/1.8/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:60:in
`execute'
from /usr/ruby/1.8/bin/puppet:4
So kind puppeteers I would like to know what on earth I am doing wrong
and how can I get a working puppet installation under Solaris 11 x86?
Thanks you
tim
tim
--
GPG me!!
gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
--
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
athttp://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-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group
athttp://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-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.
--
GPG me!!
gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
--
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.
--
You received this message because you are subscribed to the Google Groups
[Puppet Users] Could not set present on ensure: Read-only file system
Hi, I try install python-psycopg2 with other packages, when run apt-get -y update returns the errors: err: /Stage[main]/Etc/Package[build-essential]/ensure: change from purged to present failed: Could not set 'present on ensure: Read-only file system - /tmp/puppet20120216-1063-18q7lsz-0 at /tmp/vagrant-puppet/manifests/vagrant.pp:15 err: /Stage[main]/Etc/Package[python-psycopg2]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install python-psycopg2' returned 100: W: Not using locking for read only lock file /var/lib/dpkg/lock E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. err: /Stage[main]/Python::Gunicorn/File[/var/log/gunicorn]/ensure: change from absent to directory failed: Could not set 'directory on ensure: Read-only file system - /var/log/gunicorn at /tmp/vagrant-puppet/modules-0/python/manifests/gunicorn.pp:11 notice: /Stage[main]/Python::Gunicorn/File[/var/run/gunicorn]/ensure: created err: /Stage[main]/Python::Venv/Package[python-virtualenv]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install python-virtualenv' returned 100: W: Not using locking for read only lock file /var/lib/dpkg/lock E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. err: /Group[puppet]/ensure: change from absent to present failed: Could not create group puppet: Execution of '/usr/sbin/groupadd puppet' returned 1: err: /Stage[main]/Etc/Package[libcurl3-dev]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install libcurl3-dev' returned 100: W: Not using locking for read only lock file /var/lib/dpkg/lock E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. err: /Stage[main]/Etc/Package[curl]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install curl' returned 100: W: Not using locking for read only lock file /var/lib/dpkg/lock E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. err: /Stage[main]/Monit/Package[monit]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install monit' returned 100: W: Not using locking for read only lock file /var/lib/dpkg/lock E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. notice: /Stage[main]/Monit/File[/etc/default/monit]: Dependency Package[monit] has failures: true warning: /Stage[main]/Monit/File[/etc/default/monit]: Skipping because of failed dependencies notice: /Stage[main]/Monit/File[/etc/monit/monitrc]: Dependency Package[monit] has failures: true warning: /Stage[main]/Monit/File[/etc/monit/monitrc]: Skipping because of failed dependencies notice: /Stage[main]/Monit/File[/etc/logrotate.d/monit]: Dependency Package[monit] has failures: true warning: /Stage[main]/Monit/File[/etc/logrotate.d/monit]: Skipping because of failed dependencies notice: /Stage[main]/Monit/Service[monit]: Dependency Package[monit] has failures: true warning: /Stage[main]/Monit/Service[monit]: Skipping because of failed dependencies err: /Stage[main]/Etc/Package[git-doc]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install git-doc' returned 100: W: Not using locking for read only lock file /var/lib/dpkg/lock E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. err: /Stage[main]/Etc/Package[libcurl4-gnutls-dev]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install libcurl4-gnutls-dev' returned 100: W: Not using locking for read only lock file /var/lib/dpkg/lock E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. err: /Stage[main]/Dev/Exec[apt-get -y update]/returns: change from notrun to 0 failed: /usr/bin/apt-get -y update returned 100 instead of one of [0] at /tmp/vagrant-puppet/manifests/vagrant.pp:62 err: /Stage[main]/Dev/Exec[apt-get -y make]/returns: change from notrun to 0 failed: /usr/bin/apt-get -r make upgrade returned 100 instead of one of [0] at /tmp/vagrant-puppet/manifests/vagrant.pp:70 err: /Stage[main]/Dev/Exec[apt-get -y upgrade]/returns: change from notrun to 0 failed: /usr/bin/apt-get -y upgrade returned 100 instead of one of [0] at /tmp/vagrant-puppet/manifests/vagrant.pp:66 err: /Stage[main]/Nginx/Package[nginx]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install nginx' returned 100: W: Not using locking for read only lock file /var/lib/dpkg/lock E: dpkg was interrupted, you must
Re: [Puppet Users] Could not set present on ensure: Read-only file system
Hi, Is it a read only file system? change from purged to present failed: Could not set 'present on ensure: Read-only file system - /tmp/puppet20120216-1063-18q7lsz-0 at /tmp/vagrant-puppet/manifests/vagrant.pp:15 Try doing a remount on / with rw. Also check if you can do a manual install of the package once you confirm you can right to the file system. On 17/02/2012, at 6:03, Jair Gaxiola jyr.gaxi...@gmail.com wrote: Hi, I try install python-psycopg2 with other packages, when run apt-get -y update returns the errors: err: /Stage[main]/Etc/Package[build-essential]/ensure: change from purged to present failed: Could not set 'present on ensure: Read-only file system - /tmp/puppet20120216-1063-18q7lsz-0 at /tmp/vagrant-puppet/manifests/vagrant.pp:15 err: /Stage[main]/Etc/Package[python-psycopg2]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install python-psycopg2' returned 100: W: Not using locking for read only lock file /var/lib/dpkg/lock E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. err: /Stage[main]/Python::Gunicorn/File[/var/log/gunicorn]/ensure: change from absent to directory failed: Could not set 'directory on ensure: Read-only file system - /var/log/gunicorn at /tmp/vagrant-puppet/modules-0/python/manifests/gunicorn.pp:11 notice: /Stage[main]/Python::Gunicorn/File[/var/run/gunicorn]/ensure: created err: /Stage[main]/Python::Venv/Package[python-virtualenv]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install python-virtualenv' returned 100: W: Not using locking for read only lock file /var/lib/dpkg/lock E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. err: /Group[puppet]/ensure: change from absent to present failed: Could not create group puppet: Execution of '/usr/sbin/groupadd puppet' returned 1: err: /Stage[main]/Etc/Package[libcurl3-dev]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install libcurl3-dev' returned 100: W: Not using locking for read only lock file /var/lib/dpkg/lock E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. err: /Stage[main]/Etc/Package[curl]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install curl' returned 100: W: Not using locking for read only lock file /var/lib/dpkg/lock E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. err: /Stage[main]/Monit/Package[monit]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install monit' returned 100: W: Not using locking for read only lock file /var/lib/dpkg/lock E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. notice: /Stage[main]/Monit/File[/etc/default/monit]: Dependency Package[monit] has failures: true warning: /Stage[main]/Monit/File[/etc/default/monit]: Skipping because of failed dependencies notice: /Stage[main]/Monit/File[/etc/monit/monitrc]: Dependency Package[monit] has failures: true warning: /Stage[main]/Monit/File[/etc/monit/monitrc]: Skipping because of failed dependencies notice: /Stage[main]/Monit/File[/etc/logrotate.d/monit]: Dependency Package[monit] has failures: true warning: /Stage[main]/Monit/File[/etc/logrotate.d/monit]: Skipping because of failed dependencies notice: /Stage[main]/Monit/Service[monit]: Dependency Package[monit] has failures: true warning: /Stage[main]/Monit/Service[monit]: Skipping because of failed dependencies err: /Stage[main]/Etc/Package[git-doc]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install git-doc' returned 100: W: Not using locking for read only lock file /var/lib/dpkg/lock E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. err: /Stage[main]/Etc/Package[libcurl4-gnutls-dev]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install libcurl4-gnutls-dev' returned 100: W: Not using locking for read only lock file /var/lib/dpkg/lock E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. err: /Stage[main]/Dev/Exec[apt-get -y update]/returns: change from notrun to 0 failed: /usr/bin/apt-get -y update returned 100 instead of one of [0] at /tmp/vagrant-puppet/manifests/vagrant.pp:62 err: /Stage[main]/Dev/Exec[apt-get -y make]/returns: change from notrun to 0 failed: /usr/bin/apt-get -r make upgrade returned 100 instead
Re: [Puppet Users] Could not set present on ensure: Read-only file system
On Thu, Feb 16, 2012 at 1:28 PM, Denmat tu2bg...@gmail.com wrote: Hi, Is it a read only file system? change from purged to present failed: Could not set 'present on ensure: Read-only file system - /tmp/puppet20120216-1063-18q7lsz-0 at /tmp/vagrant-puppet/manifests/vagrant.pp:15 I have of file system read only, drwxrwxrwt 3 rootroot4096 Feb 16 11:43 . drwxr-xr-x 22 rootroot4096 Jul 21 2011 .. -rw--- 1 rootroot2799 Feb 16 11:49 puppet20120216-1053-1p4uxc-0 -rw--- 1 vagrant vagrant 191 Feb 16 11:43 vagrant-network-entry -rw-r--r-- 1 rootroot 283 Feb 16 11:43 vagrant-network-interfaces drwxr-xr-x 4 rootroot4096 Feb 16 11:43 vagrant-puppet vagrant@lucid32:~$ drwxr-xr-x 4 rootroot4096 Feb 16 11:43 . drwxrwxrwt 3 rootroot4096 Feb 16 11:43 .. drwxr-xr-x 1 vagrant vagrant 102 Feb 16 11:49 manifests drwxr-xr-x 1 vagrant vagrant 238 Feb 15 15:23 modules-0 vagrant@lucid32:~$ ls -al /tmp/vagrant-puppet/manifests total 8 drwxr-xr-x 1 vagrant vagrant 102 Feb 16 11:49 . drwxr-xr-x 4 rootroot4096 Feb 16 11:43 .. -rw-r--r-- 1 vagrant vagrant 1444 Feb 16 10:32 vagrant.pp I run sudo dpkg --configure -a from console returns: dpkg: unable to access dpkg status area: Read-only file system -- 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.
Re: [Puppet Users] Re: vmware provisioning
I wrote some code to create the virtual hardware on esx/esx(i) hypervisors using jython and the vsphere api. You can find my poorly written codes here on github. https://github.com/jsabo/vmware_misc/blob/master/vmware_cli.py I was building the esx(i) boxes with Cobbler and then as part of a firstboot commit hook creating the virtual hardware on the newly installed esx(i) hypervisors and then turning them on which then booted off Cobbler and installed. The other cobbler bits are in that same repo on github. On Thu, Feb 16, 2012 at 4:35 AM, Jan Ivar Beddari jan.ivar.bedd...@uib.no wrote: On 16. feb. 2012 00:34, Eric Shamow wrote: In theory it should be easy to write something through the cloud provisioning framework that takes even less time and is more flexible than our tools, but it's a fairly straightforward task. I've been thinking about doing exactly that but I'm a bit worried about what Puppetlabs response would be. I've asked earlier and from what I could understand it wouldn't be a problem, but still .. All the pieces for an open source implementation are right there, if someone wants to connect the dots. -- http://www.uib.no/personer/Jan.Ivar.Beddari -- 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. -- 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] Basic string manipulation in puppet
Hi all,
Been searching the net for a few hours now.
I have a basic operation I wish to perform but, cannot find examples
close enough to what I'm after to implement it myself.
This is what I want to do:
$version = '10.2.0'
I want to manipulate the string to make a new var ($cutversion), equal
just 102.
For example in perl (since I know it):
$version = '10.2.0';
if ($version =~ /^(\d+)\.(\d+).*$/) {
$cutversion = $1 . $2;
}
Any help?
Thanks,
Aaron.
--
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] Puppet, Facter and Mcollective
I'm not sure if this is the right group or not, but i'll start here. I have Puppet enterprise 2.0, playing around with custom facts. I have noticed that adding a custom fact to any module will distribute that fact to all machines, regardless if they are assigned to that module or not. Is there a way around this, or is this just by design? I have the pluginsync and mcollective setup to use /etc/puppetlabs/ mcollective/facts.yaml. server.cfg # Facts factsource = yaml plugin.yaml = /etc/puppetlabs/mcollective/facts.yaml Without doing anything, after a few minutes, my facts.yaml gets populated with the new custom fact, even without following this guide: http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/FactsFacterYAML and mco find -F myfact will work as well, not at first, but after a minute or 2. why is that? -- 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: Puppet, Facter and Mcollective
Awesome Gary, Thanks for the reply. Will this also populate parameters assigned via an ENC (my case would be the puppet dashboard)? Thanks again. On Feb 16, 3:33 pm, Gary Larizza g...@puppetlabs.com wrote: Hey there, Check your cron with crontab -l and you'll see a line that calls /opt/puppet/sbin/refresh-mcollective-metadata every 15 minutes. That's the process that updates the facts.yaml file with your current custom facts. You can trigger it whenever you'd like :) On Thu, Feb 16, 2012 at 3:19 PM, Tony C tonyjch...@gmail.com wrote: I'm not sure if this is the right group or not, but i'll start here. I have Puppet enterprise 2.0, playing around with custom facts. I have noticed that adding a custom fact to any module will distribute that fact to all machines, regardless if they are assigned to that module or not. Is there a way around this, or is this just by design? I have the pluginsync and mcollective setup to use /etc/puppetlabs/ mcollective/facts.yaml. server.cfg # Facts factsource = yaml plugin.yaml = /etc/puppetlabs/mcollective/facts.yaml Without doing anything, after a few minutes, my facts.yaml gets populated with the new custom fact, even without following this guide: http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/Fact... and mco find -F myfact will work as well, not at first, but after a minute or 2. why is that? -- 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. -- Gary Larizza Professional Services Engineer Puppet Labs -- 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.
Re: [Puppet Users] Re: Puppet, Facter and Mcollective
Tony, No. Those don't become custom fact values, so client's aren't aware of them. On Thu, Feb 16, 2012 at 3:34 PM, Tony C tonyjch...@gmail.com wrote: Awesome Gary, Thanks for the reply. Will this also populate parameters assigned via an ENC (my case would be the puppet dashboard)? Thanks again. On Feb 16, 3:33 pm, Gary Larizza g...@puppetlabs.com wrote: Hey there, Check your cron with crontab -l and you'll see a line that calls /opt/puppet/sbin/refresh-mcollective-metadata every 15 minutes. That's the process that updates the facts.yaml file with your current custom facts. You can trigger it whenever you'd like :) On Thu, Feb 16, 2012 at 3:19 PM, Tony C tonyjch...@gmail.com wrote: I'm not sure if this is the right group or not, but i'll start here. I have Puppet enterprise 2.0, playing around with custom facts. I have noticed that adding a custom fact to any module will distribute that fact to all machines, regardless if they are assigned to that module or not. Is there a way around this, or is this just by design? I have the pluginsync and mcollective setup to use /etc/puppetlabs/ mcollective/facts.yaml. server.cfg # Facts factsource = yaml plugin.yaml = /etc/puppetlabs/mcollective/facts.yaml Without doing anything, after a few minutes, my facts.yaml gets populated with the new custom fact, even without following this guide: http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/Fact. .. and mco find -F myfact will work as well, not at first, but after a minute or 2. why is that? -- 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. -- Gary Larizza Professional Services Engineer Puppet Labs -- 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. -- Gary Larizza Professional Services Engineer Puppet Labs -- 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: Puppet, Facter and Mcollective
I see, but following this page does allow for that http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/FactsFacterYAML I just tested it. So in my enterprise, i would much rather control the facts.yaml using a module of the above listed link and a puppet run, than allowing a cron job to do this. Also, the parameters defined in the ENC really help me carve out my infrastructure nicely for my puppet manifests, as well as the ability to run queries in mcollective using these parameters. A good examle would be a group in the Dashboard called PRODUCTION, with a parameter for site=LA How do people typically manage that puppet generated crontab? On Feb 16, 3:38 pm, Gary Larizza g...@puppetlabs.com wrote: Tony, No. Those don't become custom fact values, so client's aren't aware of them. On Thu, Feb 16, 2012 at 3:34 PM, Tony C tonyjch...@gmail.com wrote: Awesome Gary, Thanks for the reply. Will this also populate parameters assigned via an ENC (my case would be the puppet dashboard)? Thanks again. On Feb 16, 3:33 pm, Gary Larizza g...@puppetlabs.com wrote: Hey there, Check your cron with crontab -l and you'll see a line that calls /opt/puppet/sbin/refresh-mcollective-metadata every 15 minutes. That's the process that updates the facts.yaml file with your current custom facts. You can trigger it whenever you'd like :) On Thu, Feb 16, 2012 at 3:19 PM, Tony C tonyjch...@gmail.com wrote: I'm not sure if this is the right group or not, but i'll start here. I have Puppet enterprise 2.0, playing around with custom facts. I have noticed that adding a custom fact to any module will distribute that fact to all machines, regardless if they are assigned to that module or not. Is there a way around this, or is this just by design? I have the pluginsync and mcollective setup to use /etc/puppetlabs/ mcollective/facts.yaml. server.cfg # Facts factsource = yaml plugin.yaml = /etc/puppetlabs/mcollective/facts.yaml Without doing anything, after a few minutes, my facts.yaml gets populated with the new custom fact, even without following this guide: http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/Fact. .. and mco find -F myfact will work as well, not at first, but after a minute or 2. why is that? -- 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. -- Gary Larizza Professional Services Engineer Puppet Labs -- 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. -- Gary Larizza Professional Services Engineer Puppet Labs -- 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.
Re: [Puppet Users] Re: Puppet, Facter and Mcollective
Our cron entry is declared in the pe_mcollective module that we ship in our modulepath -- /opt/puppet/share/puppet/modules/pe_mcollective/manifests/metadata.pp I'll answer this more in-depth when I get a free second to expound on it, but I'm a bit tied-up at the moment :) On Thu, Feb 16, 2012 at 3:52 PM, Tony C tonyjch...@gmail.com wrote: I see, but following this page does allow for that http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/FactsFacterYAML I just tested it. So in my enterprise, i would much rather control the facts.yaml using a module of the above listed link and a puppet run, than allowing a cron job to do this. Also, the parameters defined in the ENC really help me carve out my infrastructure nicely for my puppet manifests, as well as the ability to run queries in mcollective using these parameters. A good examle would be a group in the Dashboard called PRODUCTION, with a parameter for site=LA How do people typically manage that puppet generated crontab? On Feb 16, 3:38 pm, Gary Larizza g...@puppetlabs.com wrote: Tony, No. Those don't become custom fact values, so client's aren't aware of them. On Thu, Feb 16, 2012 at 3:34 PM, Tony C tonyjch...@gmail.com wrote: Awesome Gary, Thanks for the reply. Will this also populate parameters assigned via an ENC (my case would be the puppet dashboard)? Thanks again. On Feb 16, 3:33 pm, Gary Larizza g...@puppetlabs.com wrote: Hey there, Check your cron with crontab -l and you'll see a line that calls /opt/puppet/sbin/refresh-mcollective-metadata every 15 minutes. That's the process that updates the facts.yaml file with your current custom facts. You can trigger it whenever you'd like :) On Thu, Feb 16, 2012 at 3:19 PM, Tony C tonyjch...@gmail.com wrote: I'm not sure if this is the right group or not, but i'll start here. I have Puppet enterprise 2.0, playing around with custom facts. I have noticed that adding a custom fact to any module will distribute that fact to all machines, regardless if they are assigned to that module or not. Is there a way around this, or is this just by design? I have the pluginsync and mcollective setup to use /etc/puppetlabs/ mcollective/facts.yaml. server.cfg # Facts factsource = yaml plugin.yaml = /etc/puppetlabs/mcollective/facts.yaml Without doing anything, after a few minutes, my facts.yaml gets populated with the new custom fact, even without following this guide: http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/Fact. .. and mco find -F myfact will work as well, not at first, but after a minute or 2. why is that? -- 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. -- Gary Larizza Professional Services Engineer Puppet Labs -- 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. -- Gary Larizza Professional Services Engineer Puppet Labs -- 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. -- Gary Larizza Professional Services Engineer Puppet Labs -- 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: Puppet, Facter and Mcollective
No worries Gary. Thanks for your help already. I'm definitely on your time so just chime in if / when you have a second. On Feb 16, 4:00 pm, Gary Larizza g...@puppetlabs.com wrote: Our cron entry is declared in the pe_mcollective module that we ship in our modulepath -- /opt/puppet/share/puppet/modules/pe_mcollective/manifests/metadata.pp I'll answer this more in-depth when I get a free second to expound on it, but I'm a bit tied-up at the moment :) On Thu, Feb 16, 2012 at 3:52 PM, Tony C tonyjch...@gmail.com wrote: I see, but following this page does allow for that http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/Fact... I just tested it. So in my enterprise, i would much rather control the facts.yaml using a module of the above listed link and a puppet run, than allowing a cron job to do this. Also, the parameters defined in the ENC really help me carve out my infrastructure nicely for my puppet manifests, as well as the ability to run queries in mcollective using these parameters. A good examle would be a group in the Dashboard called PRODUCTION, with a parameter for site=LA How do people typically manage that puppet generated crontab? On Feb 16, 3:38 pm, Gary Larizza g...@puppetlabs.com wrote: Tony, No. Those don't become custom fact values, so client's aren't aware of them. On Thu, Feb 16, 2012 at 3:34 PM, Tony C tonyjch...@gmail.com wrote: Awesome Gary, Thanks for the reply. Will this also populate parameters assigned via an ENC (my case would be the puppet dashboard)? Thanks again. On Feb 16, 3:33 pm, Gary Larizza g...@puppetlabs.com wrote: Hey there, Check your cron with crontab -l and you'll see a line that calls /opt/puppet/sbin/refresh-mcollective-metadata every 15 minutes. That's the process that updates the facts.yaml file with your current custom facts. You can trigger it whenever you'd like :) On Thu, Feb 16, 2012 at 3:19 PM, Tony C tonyjch...@gmail.com wrote: I'm not sure if this is the right group or not, but i'll start here. I have Puppet enterprise 2.0, playing around with custom facts. I have noticed that adding a custom fact to any module will distribute that fact to all machines, regardless if they are assigned to that module or not. Is there a way around this, or is this just by design? I have the pluginsync and mcollective setup to use /etc/puppetlabs/ mcollective/facts.yaml. server.cfg # Facts factsource = yaml plugin.yaml = /etc/puppetlabs/mcollective/facts.yaml Without doing anything, after a few minutes, my facts.yaml gets populated with the new custom fact, even without following this guide: http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/Fact. .. and mco find -F myfact will work as well, not at first, but after a minute or 2. why is that? -- 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. -- Gary Larizza Professional Services Engineer Puppet Labs -- 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. -- Gary Larizza Professional Services Engineer Puppet Labs -- 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. -- Gary Larizza Professional Services Engineer Puppet Labs -- 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.
Re: [Puppet Users] Puppet, Facter and Mcollective
On Thu, Feb 16, 2012 at 3:19 PM, Tony C tonyjch...@gmail.com wrote:
I'm not sure if this is the right group or not, but i'll start here.
I have Puppet enterprise 2.0, playing around with custom facts.
I have noticed that adding a custom fact to any module will distribute
that fact to all machines, regardless if they are assigned to that
module or not. Is there a way around this, or is this just by design?
Gary already pointed out the cron job. I'm not aware of an easy way to
perform limited pluginsync, it's either all or nothing. The reason
this is not possible, puppet need facts to compile catalog to know
what modules belong to a node, and puppet can't compile without facts,
so chicken and egg. For example, puppet can't know if it should
pluginsync my_fact if it's in my_module with the following code:
if $my_fact {include my_module}
HTH,
Nan
--
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.
Re: [Puppet Users] Re: Puppet, Facter and Mcollective
On Thu, Feb 16, 2012 at 3:52 PM, Tony C tonyjch...@gmail.com wrote: I see, but following this page does allow for that http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/FactsFacterYAML I just tested it. So in my enterprise, i would much rather control the facts.yaml using a module of the above listed link and a puppet run, than allowing a cron job to do this. Also, the parameters defined in the ENC really help me carve out my infrastructure nicely for my puppet manifests, as well as the ability to run queries in mcollective using these parameters. A good examle would be a group in the Dashboard called PRODUCTION, with a parameter for site=LA I can see scenarios where I wouldn't want to dump the entire ENC content since there's confidential settings though relevant for that system, I don't want to make discoverable through mco inventory. Since you are using PE, another options you can take advantage of facts.d directory, and write out custom facts in key=value format in txt file under /etc/puppetlabs/facter/facts.d/ See the puppet_enterprise_installer.txt for example, and this will be a fairly straightforward file resource using a template. Thanks, Nan -- 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: Basic string manipulation in puppet
Stefan,
Your the man, thanks for the help, exactly the kind of thing I am
after!
Cheers dude,
On Feb 17, 10:24 am, Stefan Schulte stefan.schu...@taunusstein.net
wrote:
On Thu, Feb 16, 2012 at 02:50:27PM -0800, Aaron Nicoli wrote:
Hi all,
Been searching the net for a few hours now.
I have a basic operation I wish to perform but, cannot find examples
close enough to what I'm after to implement it myself.
This is what I want to do:
$version = '10.2.0'
I want to manipulate the string to make a new var ($cutversion), equal
just 102.
For example in perl (since I know it):
$version = '10.2.0';
if ($version =~ /^(\d+)\.(\d+).*$/) {
$cutversion = $1 . $2;
}
Any help?
There are not that many string manipulating functions in puppet itself
but you can always build your own [1] or have a look at the puppet-std
[2]
However your problem can be solved with the build-in function regsubst
which can be found in the function reference [3]
This should work (while untested)
$cutversion = regsubst($version, '^(\d+)\.(\d+).*$', '\1\2')
Does this help?
-Stefan
[1]http://docs.puppetlabs.com/guides/custom_functions.html
[2]https://github.com/puppetlabs/puppetlabs-stdlib
[3]http://docs.puppetlabs.com/references/2.7.9/function.html#regsubst
-Stefan
--
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: Puppet, Facter and Mcollective
Thanks Nan. I supposed every one's environment is different. For the facts.d, how does that work exactly? On Feb 16, 4:31 pm, Nan Liu n...@puppetlabs.com wrote: On Thu, Feb 16, 2012 at 3:52 PM, Tony C tonyjch...@gmail.com wrote: I see, but following this page does allow for that http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/Fact... I just tested it. So in my enterprise, i would much rather control the facts.yaml using a module of the above listed link and a puppet run, than allowing a cron job to do this. Also, the parameters defined in the ENC really help me carve out my infrastructure nicely for my puppet manifests, as well as the ability to run queries in mcollective using these parameters. A good examle would be a group in the Dashboard called PRODUCTION, with a parameter for site=LA I can see scenarios where I wouldn't want to dump the entire ENC content since there's confidential settings though relevant for that system, I don't want to make discoverable through mco inventory. Since you are using PE, another options you can take advantage of facts.d directory, and write out custom facts in key=value format in txt file under /etc/puppetlabs/facter/facts.d/ See the puppet_enterprise_installer.txt for example, and this will be a fairly straightforward file resource using a template. Thanks, Nan -- 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.
Re: [Puppet Users] Re: Puppet, Facter and Mcollective
Let me see if I can help on a couple of things: 1.) Facts.dot.d is from this repo -- https://github.com/ripienaar/facter-facts/tree/master/facts-dot-d Check it out. You can specify YAML, JSON, Shell, or even a single plain text file where you write 'factname = factval' and they turn into Facter facts. The facts-dot-d fact just reads a file, parses it, and returns what it parses as Facter facts. It's cool if you have a central source like a CMDB to scrape for facts, but if you're getting started you might want to start and play with custom facts. 2.) Facts.yaml So, MCollective, using the YAML agent, will read a YAML file for its facts/inventory information. Because running facter every time MCollective is called incurs some cost, reading a flat-file is much faster for a tool like MCollective. That's why we use it. We also want to make sure the facts are reasonably up-to-date for when you do Live Management or MCollective queries, so we run that cron job every 15 minutes. You can disable the job if you want and MAKE it so the facts are only updated according to Puppet runs - that's up to how you want to manage your environment. Yes, that inline_template will also return variables IN SCOPE to the facts.yaml file, but that's something of an 'added bonus' rather than a dependable feature. If you WANT that sort of flexibility, you should look to creating custom facts or doing some sort of external data lookup (by querying the Console's REST API, for example). You could also scrape the MySQL DB backend for that information. It's entirely up to you. There are many options available to you, but I'm not sure what you're ultimately wanting to achieve? Hope that helped a bit :) On Thu, Feb 16, 2012 at 5:40 PM, Tony C tonyjch...@gmail.com wrote: Thanks Nan. I supposed every one's environment is different. For the facts.d, how does that work exactly? On Feb 16, 4:31 pm, Nan Liu n...@puppetlabs.com wrote: On Thu, Feb 16, 2012 at 3:52 PM, Tony C tonyjch...@gmail.com wrote: I see, but following this page does allow for that http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/Fact. .. I just tested it. So in my enterprise, i would much rather control the facts.yaml using a module of the above listed link and a puppet run, than allowing a cron job to do this. Also, the parameters defined in the ENC really help me carve out my infrastructure nicely for my puppet manifests, as well as the ability to run queries in mcollective using these parameters. A good examle would be a group in the Dashboard called PRODUCTION, with a parameter for site=LA I can see scenarios where I wouldn't want to dump the entire ENC content since there's confidential settings though relevant for that system, I don't want to make discoverable through mco inventory. Since you are using PE, another options you can take advantage of facts.d directory, and write out custom facts in key=value format in txt file under /etc/puppetlabs/facter/facts.d/ See the puppet_enterprise_installer.txt for example, and this will be a fairly straightforward file resource using a template. Thanks, Nan -- 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. -- Gary Larizza Professional Services Engineer Puppet Labs -- 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: Puppet, Facter and Mcollective
As far as I know thats true... One option to limit facts is to use
confine to limit where its gets run.
For example, here is a fact that is clearly only applicable for
Solaris hosts:
Facter.add(obpversion) do
confine :kernel = :sunos
setcode do
%x{/usr/sbin/prtconf -V}.chomp.split( )[1]
end
end
Whilst this won't stop it from being downloaded, it will mean that the
code will only be run on hosts that meet the requirements.
Hope that helps...
On Feb 17, 11:23 am, Nan Liu n...@puppetlabs.com wrote:
On Thu, Feb 16, 2012 at 3:19 PM, Tony C tonyjch...@gmail.com wrote:
I'm not sure if this is the right group or not, but i'll start here.
I have Puppet enterprise 2.0, playing around with custom facts.
I have noticed that adding a custom fact to any module will distribute
that fact to all machines, regardless if they are assigned to that
module or not. Is there a way around this, or is this just by design?
Gary already pointed out the cron job. I'm not aware of an easy way to
perform limited pluginsync, it's either all or nothing. The reason
this is not possible, puppet need facts to compile catalog to know
what modules belong to a node, and puppet can't compile without facts,
so chicken and egg. For example, puppet can't know if it should
pluginsync my_fact if it's in my_module with the following code:
if $my_fact {include my_module}
HTH,
Nan
--
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] Managing /etc/yum.conf
Hi,
It's easy enough to modify, say, the exclude variable in /etc/yum.conf
with something like:
augeas { yum_exclude_kernel:
context = '/files/etc/yum.conf/main',
changes = 'set exclude kernel*'
}
However, I'd like a more flexible system where I can build the list of
excludes from various classes. Has anyone come up with a good solution to
this type of problem?
Thanks in advance.
Gonzalo
--
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.
Re: [Puppet Users] puppet agent test showing error.
Is there anyone who can help me ? On Thu, Feb 16, 2012 at 6:17 PM, sam er.sureshprajap...@gmail.com wrote: On Thu, Feb 16, 2012 at 5:42 PM, krish das.srikris...@gmail.com wrote: Installed Puppet Version is 0.25.4 Can you guys help me resolving this error . Could you get the latest from repos - http://apt.puppetlabs.com/dists/maverick/main/binary-amd64/Packages And did your puppetmaster start? thanx for replying... done the same installed everything from scratch using source ... Now puppet version is : root@inmobi-laptop:~# puppet --version 2.7.10 root@inmobi-laptop:~# facter --version 1.6.5 And again new error came : root@laptop:/etc/puppet# puppetd agent --test /usr/local/lib/site_ruby/1.8/puppet/util/plugins.rb:49:in `expand_path': No such file or directory - getcwd (Errno::ENOENT) from /usr/local/lib/site_ruby/1.8/puppet/util/plugins.rb:49:in `look_in' from /usr/local/lib/site_ruby/1.8/puppet/util/plugins.rb:49:in `collect' from /usr/local/lib/site_ruby/1.8/puppet/util/plugins.rb:49:in `look_in' from /usr/local/lib/site_ruby/1.8/puppet/util/plugins.rb:54 from /usr/local/lib/site_ruby/1.8/puppet/application.rb:2:in `require' from /usr/local/lib/site_ruby/1.8/puppet/application.rb:2 from /usr/local/lib/site_ruby/1.8/puppet/application/agent.rb:1:in `require' from /usr/local/lib/site_ruby/1.8/puppet/application/agent.rb:1 from /usr/sbin/puppetd:3:in `require' from /usr/sbin/puppetd:3 -- Krish OlinData.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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Best Regards, Suresh Kumar Prajapati Linux System Admin E-mail: er.sureshprajap...@gmail.com Mob No: +91-8800920533 Theory is when you know all and nothing works. Practice is when all works and nobody knows why. In this case we have put together theory and practice: nothing works... and nobody knows why! -- Best Regards, Suresh Kumar Prajapati Linux System Admin E-mail: er.sureshprajap...@gmail.com Mob No: +91-8800920533 Theory is when you know all and nothing works. Practice is when all works and nobody knows why. In this case we have put together theory and practice: nothing works... and nobody knows why! -- 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.
Re: [Puppet Users] Managing /etc/yum.conf
Hey Gonzalo,
Have you tried Hiera at all? (http://github.com/puppetlabs/hiera and
http://github.com/puppetlabs/hiera-puppet ) With Hiera (and, specifically
the hiera_array() function), you can scour through a hierarchy to populate
a variable inside your Puppet manifest. If you had a variable to set
excludes in many levels of your hierarchy, then hiera_array('yum_excludes')
would search every level of the hierarchy (pertinent to your node according
to its Facter facts) for a variable called 'yum_excludes', and return an
array with all values that it finds. You could then utilize a template to
populate the exclude= line in yum.conf.
On Thu, Feb 16, 2012 at 10:09 PM, Gonzalo Servat gser...@gmail.com wrote:
Hi,
It's easy enough to modify, say, the exclude variable in /etc/yum.conf
with something like:
augeas { yum_exclude_kernel:
context = '/files/etc/yum.conf/main',
changes = 'set exclude kernel*'
}
However, I'd like a more flexible system where I can build the list of
excludes from various classes. Has anyone come up with a good solution to
this type of problem?
Thanks in advance.
Gonzalo
--
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.
--
Gary Larizza
Professional Services Engineer
Puppet Labs
--
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.
Re: [Puppet Users] Managing /etc/yum.conf
On Fri, Feb 17, 2012 at 5:26 PM, Gary Larizza g...@puppetlabs.com wrote:
Hey Gonzalo,
Have you tried Hiera at all? (http://github.com/puppetlabs/hiera and
http://github.com/puppetlabs/hiera-puppet ) With Hiera (and,
specifically the hiera_array() function), you can scour through a hierarchy
to populate a variable inside your Puppet manifest. If you had a variable
to set excludes in many levels of your hierarchy, then
hiera_array('yum_excludes') would search every level of the hierarchy
(pertinent to your node according to its Facter facts) for a variable
called 'yum_excludes', and return an array with all values that it finds.
You could then utilize a template to populate the exclude= line in
yum.conf.
Ah, yes. I've heard of Hiera but didn't really have a use case for it. I'll
definitely check it out.
Thanks Gary!
- Gonzalo
--
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: Puppet on Windows
On 16 Feb., 18:11, Josh Cooper j...@puppetlabs.com wrote:
Hi Jay,
On Thu, Feb 16, 2012 at 6:14 AM, Jay Ze
iltisannihila...@googlemail.comwrote:
Hi,
I want to run Puppet on a Windows 2003 Server. I already have a
working Puppetmaster (Scientific Linux).
I installed Puppet on Windows like shown here:
http://projects.puppetlabs.com/projects/1/wiki/Puppet_Windows
This worked very well.
Great to hear.
notice: Ignoring --listen on onetime run
info: Retrieving plugin
err: /File[C:/Dokumente und Einstellungen/All Users/Anwendungsdaten/
PuppetLabs/p
uppet/var/lib]: Failed to generate additional resources using
'eval_generate: Co
uld not intern_multiple from pson: Paths must be fully qualified
err: /File[C:/Dokumente und Einstellungen/All Users/Anwendungsdaten/
PuppetLabs/p
uppet/var/lib]: Could not evaluate: Could not intern from pson: Paths
must be fu
lly qualified Could not retrieve file metadata for puppet://
foreman.id.dvag.com/
plugins: Could not intern from pson: Paths must be fully qualified
This ishttps://projects.puppetlabs.com/issues/11408#note-32
It will be fixed shortly.
err: Could not retrieve catalog from remote server: Error 400 on
SERVER: PGError
: ERROR: invalid byte sequence for encoding UTF8: 0xe46973
: INSERT INTO fact_values (value, host_id, created_at,
fact_name_id,
updated_at) VALUES ('Mitteleuropõische Zeit ', 88, '2012-02-16
15:13:29.29309
9', 28, '2012-02-16 15:13:29.293099') RETURNING id
Somewhere between facter gathering the hostname and the hostname being
inserted into the database, there is a problem with how we are handling
UTF8 encoding. The text 'Mitteleuropõische Zeit' should be UTF8 encoded as
'4D 69 74 74 65 6C 65 75 72 6F 70 C3 B5 69 73 63 68 65 20 5A 65 69 74 20'
(in hex). The sequence 'e4 69 73' is most definitely an illegal UTF8
sequence.
Can you file a ticket against puppet?
Thanks,
Josh
--
Josh Cooper
Developer, Puppet Labs
Hi,
Thanks for your quick answer. What does soon mean? 1-2 weeks or
within the next months?
I'll file a ticket against puppet for the UTF8 Problem.
Thx.
--
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.
Re: [Puppet Users] puppet agent test showing error.
Can you pastebin us a full puppetd -tdv output. -- Krish OlinData.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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet agent test showing error.
On Fri, Feb 17, 2012 at 12:39 PM, krish das.srikris...@gmail.com wrote: Can you pastebin us a full puppetd -tdv output. Ok here you go http://pastie.org/3399696 -- Krish OlinData.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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Best Regards, Suresh Kumar Prajapati Linux System Admin E-mail: er.sureshprajap...@gmail.com Mob No: +91-8800920533 Theory is when you know all and nothing works. Practice is when all works and nobody knows why. In this case we have put together theory and practice: nothing works... and nobody knows why! -- 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.
