[Puppet Users] puppet repos on ubuntu 14.04
Hello, I was trying out ubuntu trusty over the weekend and am having some trouble installing puppet 3.5.1 from the puppetlabs repo. I've tried adding the repo and searching for the package, but no luck: cd /tmp wget -N https://apt.puppetlabs.com/puppetlabs-release-trusty.deb sudo dpkg -i puppetlabs-release-trusty.deb sudo apt-get update sudo apt-cache madison puppet puppet |3.4.3-1 | http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages puppet |3.4.3-1 | http://us.archive.ubuntu.com/ubuntu/ trusty/main Sources cat /etc/apt/sources.list.d/puppetlabs.list # Puppetlabs products deb http://apt.puppetlabs.com trusty main deb-src http://apt.puppetlabs.com trusty main # Puppetlabs dependencies deb http://apt.puppetlabs.com trusty dependencies deb-src http://apt.puppetlabs.com trusty dependencies # Puppetlabs devel (uncomment to activate) # deb http://apt.puppetlabs.com trusty devel # deb-src http://apt.puppetlabs.com trusty devel I noticed when I added the precise repos (12.04), puppet 3.5.1 was there, but couldn't install because of all kinds of repo mismatching. I'm assuming this is because I'm using the wrong repo. Has anyone else had luck installing? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/4dfd2268-d1b1-4931-8d20-8494ffe0e8a8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Announcing our new quest based Learning VM
I'm trying this out today. Seems quite useful, however even when I perform the required tasks, it doesn't always mark them as complete. Eg. Conditions and Ordering quests. On Friday, 18 April 2014 09:45:17 UTC+10, Ben Ford wrote: Hi, We just rolled out the new and improved Learning VM — now with fun quests to learn Puppet at your own pace. If you've been meaning to explore the technology in depth, now you can do so with a series of detailed, multi-step quests. The Learning VM covers topics such as: accessing the Puppet Enterprise console, writing and using Puppet modules, and delving into Puppet resources, manifests, facts and more. Check out the new Learning VM: http://puppetlabs.com/download-learning-vm Happy learning. - Ben -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/425f273f-3399-4d4b-8e14-9b56d9739f65%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] mco for linux is ok，but for windows display ‘unsubscribe’
mco-client（RHEL6.4）： [root@webui ~]# mco rpc puppet runonce operate=true environment=sgmprd tags=puppet_env -F hostname=node4 \ [ === ] 7 / 9debug 2014/04/21 15:10:05: rabbitmq.rb:149:in `receive' Waiting for a message from RabbitMQ debug 2014/04/21 15:10:05: pluginmanager.rb:83:in `[]' Returning cached plugin security_plugin with class MCollective::Security::Ssl debug 2014/04/21 15:10:05: ssl.rb:222:in `deserialize' De-Serializing using marshal debug 2014/04/21 15:10:05: ssl.rb:175:in `validrequest?' Validating request from debug 2014/04/21 15:10:05: runnerstats.rb:38:in `validated' Incrementing validated stat debug 2014/04/21 15:10:05: ssl.rb:222:in `deserialize' De-Serializing using marshal | [ =] 8 / 9debug 2014/04/21 15:10:05: rabbitmq.rb:149:in `receive' Waiting for a message from RabbitMQ debug 2014/04/21 15:10:05: pluginmanager.rb:83:in `[]' Returning cached plugin security_plugin with class MCollective::Security::Ssl debug 2014/04/21 15:10:05: ssl.rb:222:in `deserialize' De-Serializing using marshal debug 2014/04/21 15:10:05: ssl.rb:175:in `validrequest?' Validating request from debug 2014/04/21 15:10:05: runnerstats.rb:38:in `validated' Incrementing validated stat debug 2014/04/21 15:10:05: ssl.rb:222:in `deserialize' De-Serializing using marshal * [ ] 9 / 9debug 2014/04/21 15:10:05: client.rb:73:in `unsubscribe' Unsubscribing reply target for puppet debug 2014/04/21 15:10:05: pluginmanager.rb:83:in `[]' Returning cached plugin connector_plugin with class MCollective::Connector::Rabbitmq debug 2014/04/21 15:10:05: cache.rb:105:in `read' Cache hit on 'ddl' key 'agent/puppet' node4Request Aborted Puppet command 'puppet agent --onetime --color=false --tags puppet_env --splay --splaylimit 30 --no-noop --environment sgmprd' had exit code 1, expected 0 Summary: Puppet command 'puppet agent --onetime --color=false --tags puppet_env --splay --splaylimit 30 --no-noop --environment sgmprd' had exit code 1, expected 0 Finished processing 9 / 9 hosts in 2406.03 ms debug 2014/04/21 15:10:05: pluginmanager.rb:83:in `[]' Returning cached plugin connector_plugin with class MCollective::Connector::Rabbitmq debug 2014/04/21 15:10:05: rabbitmq.rb:265:in `disconnect' Disconnecting from RabbitMQ info 2014/04/21 15:10:05: rabbitmq.rb:20:in `on_disconnect' Disconnected from stomp://n...@mq.rsyslog.org:6163 mco-server（windows）： D, [2014-04-21T15:10:05.044854 #1140] DEBUG -- : runnerstats.rb Incrementing total stat D, [2014-04-21T15:10:05.044854 #1140] DEBUG -- : pluginmanager.rb Returning cached plugin security_plugin with class MCollective::Security::Ssl D, [2014-04-21T15:10:05.044854 #1140] DEBUG -- : ssl.rb De-Serializing using marshal D, [2014-04-21T15:10:05.044854 #1140] DEBUG -- : ssl.rb Validating request from cert=noc-public D, [2014-04-21T15:10:05.044854 #1140] DEBUG -- : runnerstats.rb Incrementing validated stat D, [2014-04-21T15:10:05.044854 #1140] DEBUG -- : ssl.rb De-Serializing using marshal D, [2014-04-21T15:10:05.044854 #1140] DEBUG -- : pluginmanager.rb Returning cached plugin security_plugin with class MCollective::Security::Ssl D, [2014-04-21T15:10:05.044854 #1140] DEBUG -- : pluginmanager.rb Returning cached plugin security_plugin with class MCollective::Security::Ssl D, [2014-04-21T15:10:05.044854 #1140] DEBUG -- : base.rb Passing based on agent puppet D, [2014-04-21T15:10:05.044854 #1140] DEBUG -- : base.rb Passing based on agent puppet D, [2014-04-21T15:10:05.044854 #1140] DEBUG -- : base.rb Message passed the filter checks D, [2014-04-21T15:10:05.044854 #1140] DEBUG -- : runnerstats.rb Incrementing passed stat D, [2014-04-21T15:10:05.044854 #1140] DEBUG -- : runner.rb Handling message for agent 'discovery' on collective 'mcollective' D, [2014-04-21T15:10:05.044854 #1140] DEBUG -- : agents.rb Dispatching a message to agent discovery D, [2014-04-21T15:10:05.044854 #1140] DEBUG -- : rabbitmq.rb Waiting for a message from RabbitMQ D, [2014-04-21T15:10:05.044854 #1140] DEBUG -- : pluginmanager.rb Returning cached plugin discovery_agent with class MCollective::Agent::Discovery D, [2014-04-21T15:10:05.044854 #1140] DEBUG -- : pluginmanager.rb Returning cached plugin security_plugin with class MCollective::Security::Ssl D, [2014-04-21T15:10:05.044854 #1140] DEBUG -- : pluginmanager.rb Returning cached plugin security_plugin with class MCollective::Security::Ssl D, [2014-04-21T15:10:05.044854 #1140] DEBUG -- : ssl.rb Serializing using marshal D, [2014-04-21T15:10:05.044854 #1140] DEBUG -- : ssl.rb Creating message hash using c:\mcollective\ssl\server-private.pem D, [2014-04-21T15:10:05.044854 #1140] DEBUG -- : base.rb Encoded a message for request 7dcf954d83d850b19535d2d0af04a0bb D, [2014-04-21T15:10:05.044854 #1140] DEBUG --
[Puppet Users] Re: Received certificate does not match private key.
In the agent puppet.conf: server=FQDN does the FQDN in the agents puppet.conf match the private key FQDN in the puppet master in /var/lib/puppet/ssl/private_keys/? On Saturday, April 19, 2014 9:50:43 AM UTC-7, Chris Johnson wrote: I know this has been asked about before, I've searched it. There seem to be two main responses. Synchronize clocks or start over with generating certificates. I've done both. And puppet used to work. I have an mini virtual cluster set up using VBox running orginally CentOS 6.4. I provision it with cobbler and added puppet. Puppet was running great. I then had to upgrade to 6.5. I set up a new cobbler server from the old, upgraded the clients and reinstalled puppet. I then tried setting puppet back up from scratch and now I'm getting this error from the clients. I'm using puppet and puppet-server RPMS 2.7.25.-2.el6.noarch. Facter is installed. I've tried deleting all files in /var/lib/puppet on client and server and regeneration certificates in various orders. The clocks are synchronized two with one second of each other and they all run ntpd. Still I get this error. I give up. I have found nothing else to do. What am I missing please? Help. Thank you. Chris Johnson. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/ce906700-520a-4b02-90d4-827fbe233a72%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] puppet apply stops with message Killed
Hi, I'm having a problem with my puppet script hanging for a while then dying with the message Killed printed to the console. There is no further explanation of what happened but I'm suspecting some event propagation might get stuck and puppet may have some mechanism to kill the process if it hangs for too long. That's just a guess though, so please let me know if anyone has some insight on this problem. Thanks! I'm running on Debian 7, Puppet 3.5.1. Tail of the output of puppet apply --verbose --debug --modulepath=/root/puppet/modules /root/puppet/ks-prod.pp is: ... Notice: /Stage[main]/Ks::Database/Exec[create-blog-db]/returns: executed successfully Debug: /Stage[main]/Ks::Database/Exec[create-blog-db]: The container Class[Ks::Database] will propagate my refresh event Debug: Class[Ks::Database]: The container Stage[main] will propagate my refresh event Debug: Class[Ks::Database]: The container Class[Ks::Server] will propagate my refresh event Debug: /Stage[main]/Apache::Mod::Autoindex/Apache::Mod[autoindex]/File[autoindex.load symlink]/mode: Not managing symlink mode Debug: /Stage[main]/Apache::Mod::Autoindex/Apache::Mod[autoindex]/File[autoindex.conf symlink]/mode: Not managing symlink mode Debug: Exec[concat_/etc/apache2/ports.conf](provider=posix): Executing check '/var/lib/puppet/concat/bin/concatfragments.sh -o /var/lib/puppet/concat/_etc_apache2_ports.conf/fragments.concat.out -d /var/lib/puppet/concat/_etc_apache2_ports.conf -t' Debug: Executing '/var/lib/puppet/concat/bin/concatfragments.sh -o /var/lib/puppet/concat/_etc_apache2_ports.conf/fragments.concat.out -d /var/lib/puppet/concat/_etc_apache2_ports.conf -t' Debug: /Stage[main]/Apache::Mod::Prefork/Apache::Mpm[prefork]/File[/etc/apache2/mods-enabled/prefork.conf]/mode: Not managing symlink mode Debug: /Stage[main]/Apache::Mod::Php/Apache::Mod[php5]/File[php5.conf symlink]/mode: Not managing symlink mode Debug: Exec[own apache log directory](provider=posix): Executing 'chown -R -f www-data:www-data /var/log/apache2' Debug: Executing 'chown -R -f www-data:www-data /var/log/apache2' Notice: /Stage[main]/Ks::Web/Exec[own apache log directory]/returns: executed successfully Debug: /Stage[main]/Ks::Web/Exec[own apache log directory]: The container Class[Ks::Web] will propagate my refresh event Debug: Class[Ks::Web]: The container Stage[main] will propagate my refresh event Debug: Class[Ks::Web]: The container Class[Ks::Server] will propagate my refresh event Debug: Class[Ks::Server]: The container Stage[main] will propagate my refresh event Killed -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/43d2d9fd-30bc-42f9-b289-e0c697df9ba0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] puppetlabs/ntp failing to find operatingsystem fact...
Is this not just a mixup between $::operatingsystem and $::osfamily?
On Fri, Apr 18, 2014 at 3:41 PM, R. Tyler Croy ty...@monkeypox.org wrote:
On 04/18/2014 10:24, Dennis Kirkpatrick wrote:
I have run into a problem in using the puppetlabs/ntp module that I was
not expecting. In calling on puppetlabs-ntp::init in my rspec tests, I am
getting a failure of ntp::params to find the correct fact for
operationingsystem, which happens to be RedHat. I've even issued a test to
see if I could manually set the operatingsystem fact, but alas.
Here is my client_ntp_spec.rb--
require 'spec_helper'
describe ntp do
let(:facts) { { :operatingsystem = RedHat } }
it { should contain_notify(operatingsystem).with_message(RedHat) }
end
describe 'client_ntp', :type = :class do
describe 'client_ntp' do
it { should create_class('client_ntp') }
it { should contain_class('client_ntp::params') }
end
end
Does the RSpec tag :type = :class do anything special to override
facts? The `ntp` module depends on `stdlib` and the fact that it is not
loaded might be what is causing you trouble, I use this:
https://github.com/jenkinsci/puppet-jenkins/blob/master/spec/spec_helper.rb#L26https://github.com/jenkinsci/puppet-jenkins/blob/master/spec/spec_helper.rb#L26to
ensure that the per-spec compiled catalog has the `stdlib` class
compiled in.
This also requires that stdlib is in spec/fixtures.
Here are my test results--
$ rake spec
HEAD is now at 564ec4f Merge branch '3.0.x'
HEAD is now at 6a5dee2 Merge pull request #239 from
kylog/maint/remove-facter-versions-test
/usr/bin/ruby -S rspec spec/classes/client_ntp_spec.rb --color
FFF
Failures:
1) ntp
Failure/Error: it { should
contain_notify(operatingsystem).with_message(RedHat) }
Puppet::Error:
The ntp module is not supported on an based system. at
/home/user/code/client-appaccelerator/modules/client_ntp/spec/fixtures/modules/ntp/manifests/params.pp:183
on node denqca3utdev01.client.org
# ./spec/classes/client_spec.rb:6
2) client_ntp client_ntp
Failure/Error: it { should create_class('client_ntp') }
Puppet::Error:
The ntp module is not supported on an based system. at
/home/user/code/client-appaccelerator/modules/client_ntp/spec/fixtures/modules/ntp/manifests/params.pp:183
on node denqca3utdev01.client.org
# ./spec/classes/client_ntp_spec.rb:12
3) client_ntp client_ntp
Failure/Error: it { should contain_class('client_ntp::params') }
Puppet::Error:
The ntp module is not supported on an based system. at
/home/user/code/client-appaccelerator/modules/client_ntp/spec/fixtures/modules/ntp/manifests/params.pp:183
on node denqca3utdev01.client.org
# ./spec/classes/client_ntp_spec.rb:13
Finished in 0.46827 seconds
3 examples, 3 failures
Failed examples:
rspec ./spec/classes/client_ntp_spec.rb:6 # ntp
/usr/bin/ruby -S rspec spec/classes/client_ntp_spec.rb --color failed
Based on the error message, I traced the output straight to the
puppetlabs/ntp::params class, line 183 here--
default: {
fail(The ${module_name} module is not supported on an ${::osfamily}
based system.)
}
It seems that the puppetlabs/ntp module is getting a null value for the
operatingsystem fact.
I can manually test for the fact at the command line--
$ facter operatingsystem
RedHat
This is RedHat 6.4--
$ lsb_release -a
LSB Version:
:base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
Distributor ID: RedHatEnterpriseServer
Description:Red Hat Enterprise Linux Server release 6.4 (Santiago)
Release:6.4
Codename: Santiago
I'm feeling stumped. Any clues?
Thanks.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/79b69beb-b06e-40be-8ea9-3c05886acc8c%40googlegroups.comhttps://groups.google.com/d/msgid/puppet-users/79b69beb-b06e-40be-8ea9-3c05886acc8c%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/5351AA09.2070906%40monkeypox.orghttps://groups.google.com/d/msgid/puppet-users/5351AA09.2070906%40monkeypox.org?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
[Puppet Users] How to check a text file for a certain line?
Hi everyone, I'm pretty new to puppet, and I was wondering if you guys to help me with something pretty basic. I'm attempting to write a module that will check a text file for a certain line of text, and if it doesn't find it, to add a that content in a new line. I'm pretty sure I can add the new line using exec to run echo content file.txt, but checking the file for said content has me completely stumped. What can I do here? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/ff5d0baa-7adc-4162-983a-67bb010a3fb1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Hiera Performance Testing
Thank you for your input Daniele! We're currently working to move to Puppet 3 but we've got such a large code base, so many people committing to the repo, and so much refactoring to do that it's a very complex and long term project. But I like a challenge! ;-) On Wednesday, April 16, 2014 1:29:41 AM UTC-6, Daniele Sluijters wrote: Ah, Then I'm afraid you're on your own. The instrumentation framework got added and expanded upon somewhere in the 3.x series, I believe 3.2 was the first to be able to give some useful information and as of 3.5 the API is actually public so that others can build on it. As far as Hiera goes, lookup times depend on a bunch of things. Part of it is the complexity of the hierarchy, the more places it might need to look the longer it will take. If you do a 'normal' hiera call it'll exit on the first match so depending on how quickly it can find a match it'll take a bit longer or not. Then there's the hiera_array and hiera_hash calls which search the whole hierarchy and build up an array or hash of all the returned values which will take longer than a hiera call. If you really want to get an indication I'd say just switch a few modules to hiera and compare compile times. You could also start adding Hiera.debug() calls with time information in Hiera's backend.rb. In all honesty though, I'd suggest you get to upgrading to 3.4+ first. That'll give you a bit of a performance boost and 3.4+ doesn't require Hiera, it just ships with it. It'll also enable a bunch of things that will make your life more pleasant as a module author or maintainer. If you're using opensource modules it's likely they'll shortly start dropping 2.7 support if they haven't already with the coming of Puppet 3.6 and 4.x. -- Daniele Sluijters On Monday, 14 April 2014 19:35:37 UTC+2, David Danzilio wrote: Unfortunately, and I probably should've mentioned this in the OP, we're currently stuck on the 2.7 series. On Monday, April 14, 2014 1:11:36 PM UTC-4, Daniele Sluijters wrote: Hi, I think a good start would be to turn on profiling, aka profiling=true in puppet.conf or puppet agent --profile. The output will show up in the master's logs. -- Daniele Sluijters On Friday, 11 April 2014 22:55:45 UTC+2, David Danzilio wrote: Hi Everybody. I'm trying to come up with a way to understand how Hiera is going to affect compile times on our Puppet masters. We've got just over 100K lines of Puppet code, and thousands of hosts across a few environments. I know there are a lot of variables to this problem, but I'm drawing a blank on a good way to test this. Has anybody run into this? Is there a simple way to do this that I'm just not seeing? Thanks! David -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/4ba63067-0897-4893-8b02-adf73bd4a697%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Hiera Performance Testing
Thank you Nan! On Wednesday, April 16, 2014 10:31:13 AM UTC-6, Nan Liu wrote: On Mon, Apr 14, 2014 at 12:35 PM, David Danzilio david.d...@gmail.comjavascript: wrote: Unfortunately, and I probably should've mentioned this in the OP, we're currently stuck on the 2.7 series. You should be able to run puppet master --compile certname and time it to get a coarse measurement of before and after. Just make sure you take a good random sample from a variety of systems with different classes. HTH, Nan -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/28ada285-3247-408f-9c0f-01daf40649dd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Configure puppetdb to allow cross domain requests?
Hi, I'm trying to do some interesting javascript integration between grafana and puppetdb. I'd like a grafana scripted dashboard to to make a puppetdb API call, to then create a list of hosts for a dashboard. However, this is a cross-domain request, so browsers don't allow it. With Apache, I would add this to the configuration: Header set Access-Control-Allow-Origin * Header set Access-Control-Allow-Methods GET, OPTIONS Header set Access-Control-Allow-Headers origin, authorization, accept However, puppetdb is runny via jetty, and I can't figure out a way to do this. Anyone know how to allow this? Thanks! -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/d8ae1fae-32c1-4f5b-a281-f26a5ed50df8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Debian jessie, puppetlabs dist-upgrade problem
This is probably because the default ruby used to provide libxmlrpc-ruby and libopenssl-ruby*/ruby-openssl, but the rubies available in jessie do not. Because puppet depends on both of those packages, the upgrade does not succeed because apt can't find the needed dependencies. This has been fixed in master in commit https://github.com/puppetlabs/puppet/commit/b6514b8dfe92a1e66c086fe1f45e5e7261bd45fb, but it has not yet been released. It should be released in Puppet 3.6.0. HTH On Mon, Apr 21, 2014 at 5:16 AM, Juan Sierra Pons j...@elsotanillo.net wrote: El 20/04/2014 18:29, Mike R. mroa...@gmail.com escribió: Using wheezy or unstable puppetlabs release, dist-upgrade wants to remove puppet and puppet-common to upgrade libruby. Anyone seen this? root@enigma:~# apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: facter hiera libaugeas-ruby1.8 libjson-ruby libruby libshadow-ruby1.8 ruby-rgen virt-what Use 'apt-get autoremove' to remove them. The following packages will be REMOVED: puppet puppet-common The following packages will be upgraded: libruby 1 upgraded, 0 newly installed, 2 to remove and 0 not upgraded. Need to get 7,296 B of archives. After this operation, 5,186 kB disk space will be freed. Do you want to continue? [Y/n] n Abort. root@enigma:~# -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/ce5a9804-9488-4aa0-9a04-f92bb273d962%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. Hi, I had the same problem. I installed older package version using the alternatives proposed by aptitude. Hope it helps Best regards -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CABS%3Dy9tHHKySmJVpNye5QBhnVuvrN_eiB3unHuDREru_jjFi%2BQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- Matthaus Owens Puppet Labs Join us at PuppetConf 2014, September 22-24 in San Francisco Register by May 30th to take advantage of the Early Adopter discount —save $349! -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CACD%3DwAf%2B0EkTH%3Dgi5hFna0FKxMbp08Z4VxofSMxLb_%2B1e6wP0g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] puppet repos on ubuntu 14.04
Puppet hasn't been released for Ubuntu 14.04 yet. There were some dependency updates for the puppet package that are needed for Trusty that haven't been released yet. The commit with the fix (https://github.com/puppetlabs/puppet/commit/b6514b8dfe92a1e66c086fe1f45e5e7261bd45fb) should be released in Puppet 3.6.0. Until then I would recommend using Ubuntu's 3.4.3 packages. HTH On Sun, Apr 20, 2014 at 9:29 PM, Matt McMahand mmcmah...@gmail.com wrote: Hello, I was trying out ubuntu trusty over the weekend and am having some trouble installing puppet 3.5.1 from the puppetlabs repo. I've tried adding the repo and searching for the package, but no luck: cd /tmp wget -N https://apt.puppetlabs.com/puppetlabs-release-trusty.deb sudo dpkg -i puppetlabs-release-trusty.deb sudo apt-get update sudo apt-cache madison puppet puppet |3.4.3-1 | http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages puppet |3.4.3-1 | http://us.archive.ubuntu.com/ubuntu/ trusty/main Sources cat /etc/apt/sources.list.d/puppetlabs.list # Puppetlabs products deb http://apt.puppetlabs.com trusty main deb-src http://apt.puppetlabs.com trusty main # Puppetlabs dependencies deb http://apt.puppetlabs.com trusty dependencies deb-src http://apt.puppetlabs.com trusty dependencies # Puppetlabs devel (uncomment to activate) # deb http://apt.puppetlabs.com trusty devel # deb-src http://apt.puppetlabs.com trusty devel I noticed when I added the precise repos (12.04), puppet 3.5.1 was there, but couldn't install because of all kinds of repo mismatching. I'm assuming this is because I'm using the wrong repo. Has anyone else had luck installing? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/4dfd2268-d1b1-4931-8d20-8494ffe0e8a8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Matthaus Owens Puppet Labs Join us at PuppetConf 2014, September 22-24 in San Francisco Register by May 30th to take advantage of the Early Adopter discount —save $349! -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CACD%3DwAerTA8V2dA01rRSM4qZfs2OnJJYzize6YBpN_N7i7fdbg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Duplicate declaration problem
So, I am trying to do something with a list (array) of users from hieara.
Here is the yaml:
profile::sysconfig::sftp_users: [ joe, bill, nancy ]
In my profile I have a defined class debugUsers that I am calling with
the array I got from hiera:
class profile::sysconfig::sftpserver {
define debugUsers {
notify { username: \${user}\: }
}
class doWork {
$users = hiera('profile::sysconfig::sftp_users')
validate_array($users)
debugUsers { $users: }
}
include doWork
}
From everything I know and have read that should give me a notify line for
user in my array. But it doesn't. Instead I get this error from the agent:
Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Duplicate declaration: Notify[username: ] is already declared in file
/etc/puppetlabs/puppet/environments/r10k/dev_users/modules/profile/manifests/sysconfig/sftpserver.pp:5;
cannot redeclare at
/etc/puppetlabs/puppet/environments/r10k/dev_users/modules/profile/manifests/sysconfig/sftpserver.pp:5
Why am I getting duplicate null declarations? If I call out specific
elements of the array I get back exactly what I would expect:
class profile::sysconfig::sftpserver {
class doWork {
$users = hiera('profile::sysconfig::sftp_users')
validate_array($users)
notify { user1: \${users[0]}\: }
notify { user2: \${users[1]}\: }
notify { user3: \${users[2]}\: }
}
include doWork
}
returns this:
Notice: user1: joe
Notice: /Stage[main]/Profile::Sysconfig::Sftpserver::Dowork/Notify[user1:
joe]/message: defined 'message' as 'user1: joe'
Notice: user3: nancy
Notice: /Stage[main]/Profile::Sysconfig::Sftpserver::Dowork/Notify[user3:
nancy]/message: defined 'message' as 'user3: nancy'
Notice: user2: bill
Notice: /Stage[main]/Profile::Sysconfig::Sftpserver::Dowork/Notify[user2:
bill]/message: defined 'message' as 'user2: bill'
I am sure this is something really stupid, but can someone point out what
I'm doing wrong here?
Thanks,
--Sean
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/4477ce95-b58e-4ead-80bc-5ae9ef0b5bda%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] How to check a text file for a certain line?
On Mon, Apr 21, 2014 at 8:18 AM, Dan Pasacrita whitewind...@gmail.comwrote:
Hi everyone, I'm pretty new to puppet, and I was wondering if you guys to
help me with something pretty basic. I'm attempting to write a module that
will check a text file for a certain line of text, and if it doesn't find
it, to add a that content in a new line.
You want to use unless in your exec
http://docs.puppetlabs.com/references/latest/type.html#exec
Here are some example of what you're trying to accomplish:
http://projects.puppetlabs.com/projects/puppet/wiki/Simple_Text_Patterns/5
exec { /bin/echo '${line}' '${file}':
unless = /bin/grep -qFx '${line}' '${file}'
}
--
Steven Kuryło
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAMd2BmOaFSpafcxXZkJcTrrsfZreu55GKadFEz0VyA5KYu%2BUMw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] puppet module permissions - librarian-puppet
I have noticed lately that on my development system (OS X) and my production Puppet master (CentOS 6.5) that when installing puppet modules using librarian-puppet the permissions of some modules and files is very restrictive to the point where the puppetmaster can't read the files. Some modules end up with all files being 0400, while some end up 0644 and some 0664. The files read-only to user are unable to be accessed by the Passenger based Puppet master and the files that sometimes go from 0664 to 0644 are creating a lot of noise in agent reports. Is there a defacto standard for the appropriate permissions, especially for custom puppet providers/types/functions? I've noticed that whatever the permissions end up being on the master is what they get set to on the clients. I'm unsure if the permissions are being set by librarian-puppet, the puppet module command, or some other mechanism. The permissions are always like this after a bundle exec librarian-puppet install. I've since had to put a script in my librarian-puppet repo that executes a find and modifies permissions, which does not seem right. Curious if anyone else has seen this or has suggestions for how to debug. Thanks - Trey -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/bc4f86d5-0c65-4ec6-bc98-43f437a611e6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] puppet module permissions - librarian-puppet
What umask are you using? R. On 21 Apr 2014 19:18, treydock treyd...@gmail.com wrote: I have noticed lately that on my development system (OS X) and my production Puppet master (CentOS 6.5) that when installing puppet modules using librarian-puppet the permissions of some modules and files is very restrictive to the point where the puppetmaster can't read the files. Some modules end up with all files being 0400, while some end up 0644 and some 0664. The files read-only to user are unable to be accessed by the Passenger based Puppet master and the files that sometimes go from 0664 to 0644 are creating a lot of noise in agent reports. Is there a defacto standard for the appropriate permissions, especially for custom puppet providers/types/functions? I've noticed that whatever the permissions end up being on the master is what they get set to on the clients. I'm unsure if the permissions are being set by librarian-puppet, the puppet module command, or some other mechanism. The permissions are always like this after a bundle exec librarian-puppet install. I've since had to put a script in my librarian-puppet repo that executes a find and modifies permissions, which does not seem right. Curious if anyone else has seen this or has suggestions for how to debug. Thanks - Trey -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/bc4f86d5-0c65-4ec6-bc98-43f437a611e6%40googlegroups.comhttps://groups.google.com/d/msgid/puppet-users/bc4f86d5-0c65-4ec6-bc98-43f437a611e6%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAJGKfwBxQ_OYmgq1UWbrwSHCTdxUd96epNC8AYiZm7D0VrkN3Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Duplicate declaration problem
Found the problem. When passing an array to a define the default variable
name for the elements of the array is $name. This works:
define debugUsers {
validate_string($name)
notify { username: \${name}\: }
}
On Monday, April 21, 2014 11:31:52 AM UTC-6, Sean Korten wrote:
So, I am trying to do something with a list (array) of users from hieara.
Here is the yaml:
profile::sysconfig::sftp_users: [ joe, bill, nancy ]
In my profile I have a defined class debugUsers that I am calling with
the array I got from hiera:
class profile::sysconfig::sftpserver {
define debugUsers {
notify { username: \${user}\: }
}
class doWork {
$users = hiera('profile::sysconfig::sftp_users')
validate_array($users)
debugUsers { $users: }
}
include doWork
}
From everything I know and have read that should give me a notify line for
user in my array. But it doesn't. Instead I get this error from the agent:
Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Duplicate declaration: Notify[username: ] is already declared in file
/etc/puppetlabs/puppet/environments/r10k/dev_users/modules/profile/manifests/sysconfig/sftpserver.pp:5;
cannot redeclare at
/etc/puppetlabs/puppet/environments/r10k/dev_users/modules/profile/manifests/sysconfig/sftpserver.pp:5
Why am I getting duplicate null declarations? If I call out specific
elements of the array I get back exactly what I would expect:
class profile::sysconfig::sftpserver {
class doWork {
$users = hiera('profile::sysconfig::sftp_users')
validate_array($users)
notify { user1: \${users[0]}\: }
notify { user2: \${users[1]}\: }
notify { user3: \${users[2]}\: }
}
include doWork
}
returns this:
Notice: user1: joe
Notice: /Stage[main]/Profile::Sysconfig::Sftpserver::Dowork/Notify[user1:
joe]/message: defined 'message' as 'user1: joe'
Notice: user3: nancy
Notice: /Stage[main]/Profile::Sysconfig::Sftpserver::Dowork/Notify[user3:
nancy]/message: defined 'message' as 'user3: nancy'
Notice: user2: bill
Notice: /Stage[main]/Profile::Sysconfig::Sftpserver::Dowork/Notify[user2:
bill]/message: defined 'message' as 'user2: bill'
I am sure this is something really stupid, but can someone point out what
I'm doing wrong here?
Thanks,
--Sean
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/cee17fb4-89ae-4a4c-a4af-c7a34c47b0f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Announcing our new quest based Learning VM
Is there by chance a torrent available of these files? For whatever reason, downloads.puppetlabs.com is being especially slow with the ovf file for me. Jeff On 04/17/2014 07:45 PM, Ben Ford wrote: Hi, We just rolled out the new and improved Learning VM — now with fun quests to learn Puppet at your own pace. If you've been meaning to explore the technology in depth, now you can do so with a series of detailed, multi-step quests. The Learning VM covers topics such as: accessing the Puppet Enterprise console, writing and using Puppet modules, and delving into Puppet resources, manifests, facts and more. Check out the new Learning VM: http://puppetlabs.com/download-learning-vm Happy learning. - Ben -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5355818E.1010007%40bericotechnologies.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Installing multiple packages (via apt) on one command line...
Hey we have a problem that I think we need to solve with a custom Puppet
provider, but I could use a bit of help getting started. Overall the issue
of being able to install multiple packages at-once has been discussed a ton
of times (issue #2128 for example). We ultimately need to be able to pass
in an arbitrary list of packages (and their versions) to a package-like
provider in Puppet and have it install them all at once. For example:
package { 'myapp':
packages = [ 'backend=1.0', 'frontend=1.1' ],
provider= some_custom_provider;
}
Ultimately the provider would need to validate that each and every
package supplied (backend, and frontend in this example) are either
installed or not. If not, they are all installed on one commandline:
aptitude install backend=1.0 frontend=1.1 -y -q -f
Should we just build a resource from scratch? or do you think we should
build a provider for the Package resource in Puppet and go from there?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/5b98ce35-a9ff-4e76-89e7-a4d4475cedd3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] puppet repos on ubuntu 14.04
Great, thanks for letting us know On Monday, April 21, 2014 1:09:31 PM UTC-4, Matthaus Litteken wrote: Puppet hasn't been released for Ubuntu 14.04 yet. There were some dependency updates for the puppet package that are needed for Trusty that haven't been released yet. The commit with the fix ( https://github.com/puppetlabs/puppet/commit/b6514b8dfe92a1e66c086fe1f45e5e7261bd45fb) should be released in Puppet 3.6.0. Until then I would recommend using Ubuntu's 3.4.3 packages. HTH On Sun, Apr 20, 2014 at 9:29 PM, Matt McMahand mmcm...@gmail.comjavascript: wrote: Hello, I was trying out ubuntu trusty over the weekend and am having some trouble installing puppet 3.5.1 from the puppetlabs repo. I've tried adding the repo and searching for the package, but no luck: cd /tmp wget -N https://apt.puppetlabs.com/puppetlabs-release-trusty.deb sudo dpkg -i puppetlabs-release-trusty.deb sudo apt-get update sudo apt-cache madison puppet puppet |3.4.3-1 | http://us.archive.ubuntu.com/ubuntu/trusty/main amd64 Packages puppet |3.4.3-1 | http://us.archive.ubuntu.com/ubuntu/trusty/main Sources cat /etc/apt/sources.list.d/puppetlabs.list # Puppetlabs products deb http://apt.puppetlabs.com trusty main deb-src http://apt.puppetlabs.com trusty main # Puppetlabs dependencies deb http://apt.puppetlabs.com trusty dependencies deb-src http://apt.puppetlabs.com trusty dependencies # Puppetlabs devel (uncomment to activate) # deb http://apt.puppetlabs.com trusty devel # deb-src http://apt.puppetlabs.com trusty devel I noticed when I added the precise repos (12.04), puppet 3.5.1 was there, but couldn't install because of all kinds of repo mismatching. I'm assuming this is because I'm using the wrong repo. Has anyone else had luck installing? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/4dfd2268-d1b1-4931-8d20-8494ffe0e8a8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Matthaus Owens Puppet Labs Join us at PuppetConf 2014, September 22-24 in San Francisco Register by May 30th to take advantage of the Early Adopter discount —save $349! -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/a8c127fb-5f64-4d36-a735-e0dce5990392%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] How to check a text file for a certain line?
On 04/21/14 19:42, Kenton Brede wrote: Look into using file_line, it's part of stdlib. https://forge.puppetlabs.com/puppetlabs/stdlib Hmm, I don't detect any documentation of file_line at that URL. Could you post another link with documentation? Thanks, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod, Roedermark, Germany Email: jsch...@acm.org -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/lj450h%24glh%241%40ger.gmane.org. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Augeas lens to change an arbitrary line in a file?
Hi,
I'm new to Puppet, and also new to Augeas.
I want to change a line in a file. In particular, the file is
/usr/share/ghostscript/${gs_version}/Resource/Init/gs_init.ps
and the line is
% /DEFAULTPAPERSIZE (a4) def
that I want to change into
/DEFAULTPAPERSIZE (a4) def
Is Augeas the right tool for such a task? I looked through its
available lenses, but there ain't no Postscript lens.
Of course, the other approach would be to use an exec resource to
change that line.
What is best practice?
Joachim
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Joachim Schrod, Roedermark, Germany
Email: jsch...@acm.org
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/lj45s9%24t7q%241%40ger.gmane.org.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Announcing our new quest based Learning VM
Turns out the Quest system only marks progress as completed if you use the full path to the files you are applying. I was already in the right directory so wasn't using the full path. On Monday, 21 April 2014 19:48:48 UTC+10, Jason Oakley wrote: I'm trying this out today. Seems quite useful, however even when I perform the required tasks, it doesn't always mark them as complete. Eg. Conditions and Ordering quests. On Friday, 18 April 2014 09:45:17 UTC+10, Ben Ford wrote: Hi, We just rolled out the new and improved Learning VM — now with fun quests to learn Puppet at your own pace. If you've been meaning to explore the technology in depth, now you can do so with a series of detailed, multi-step quests. The Learning VM covers topics such as: accessing the Puppet Enterprise console, writing and using Puppet modules, and delving into Puppet resources, manifests, facts and more. Check out the new Learning VM: http://puppetlabs.com/download-learning-vm Happy learning. - Ben -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/6b6dcaa6-5dad-4015-9152-4aba8a0c5af2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] How to check a text file for a certain line?
On 2014-04-22 00:10, Joachim Schrod wrote: On 04/21/14 19:42, Kenton Brede wrote: Look into using file_line, it's part of stdlib. https://forge.puppetlabs.com/puppetlabs/stdlib Hmm, I don't detect any documentation of file_line at that URL. Could you post another link with documentation? Funny that it doesn't seem to be mentioned in the README anymore, but here is the code and the documentation: https://github.com/puppetlabs/puppetlabs-stdlib/blob/master/lib/puppet/type/file_line.rb Andreas signature.asc Description: OpenPGP digital signature
[Puppet Users] A couple of problems with the Learning Puppet VM
Hey! I've been learning Puppet from the VM I downloaded yesterday. Two things I've noticed: 1. If you do not use the full path to a file you are applying, the quest doesn't mark it as complete. Eg. puppet apply modules1-ntp2.pp Doesn't get marked as completed. puppet apply /root/examples/modules1-ntp2.pp Does get marked as completed. 2. Using the module search command doesn't always work: [root@learn ~]# puppet module search puppetlabs | grep mysql puppetlabs-mysql Mysql module @puppetlabsmysql database percona mariadb centos rhel ubuntu debian This shows the module is definitely on the Forge, but if you search for it using the command example in the Quest Guide, you get no result: [root@learn ~]# puppet module search puppetlabs-mysql Notice: Searching https://forgeapi.puppetlabs.com ... No results found for 'puppetlabs-mysql'. [root@learn ~]# -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/7a69245c-8fce-4bd7-a033-f8fc967320b3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] bucketing all changed files
Hi All, I want to be able to bucket any file that is being changed including the /etc/passwd and shadow for user changes, I see this is not the default behavior .It would be awesome to use something like git or svn to keep track of changed files. thanks for any help Robert -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/d94aa4d2-1827-480c-a271-a3635b619aa5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Facts in ERB Template not working
Having an odd issue with the facts inside an ERB template. I'm using the facts to build a somewhat dynamic MOTD. I made some changes to init.pp for the module and deployed to my Dev environment and it started breaking things. It started off with not being able to find a value for lsbdistdescription Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to parse template motd/motd.erb: Filepath: /usr/lib/ruby/site_ruby/1.8/puppet/parser/templatewrapper.rb Line: 81 Detail: Could not find value for 'lsbdistdescription' at /etc/puppet/environments/development/modules/motd/templates/motd.erb:10 at /etc/puppet/environments/development/modules/motd/manifests/init.pp:44 on node cbe01d.example.com Looking into the issue the only thing I found was that facts should now have an @ sign in front of them. Changing that didn't help. I have reverted back to the old code and its still broken. Oddly enough, it works as expected when I go to the server and run $ sudo puppet agent -t. It applies the lsbdistdescription to MOTD, then the puppet daemon fires off after 30minutes and does not acknowledge lsbdistdescription. Here is the current template: +: System Data :+++ + Hostname = %= hostname % + Domain = %= domain % + Address = %= ipaddress_eth0 % + OS: %= @lsbdistdescription % %= architecture % + Kernel = %= kernelrelease % + Uptime = %= uptime % + CPU = %= processorcount %x %= processor0 % + Total Memory = %= memorysize % + Managed by Puppet version %= puppetversion % % if @extra -% + Extra Info = %= @extra % % end -% +++ Any ideas why only manual runs work as expected? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/745beae5-fc41-45e2-b151-7930fe40bd28%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] bucketing all changed files
Hey all, Is there a existing way to bucket all changes ? This works great for the file type, but would be great when modifying the passwd or shadow file with the user type. I have searched on this topic but not found anything, maybe my search terms are wrong... It would be even better if i could check the files into a revisioning system. Thanks ! Robert -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/be77d09b-e06e-4d89-9978-48776bad7457%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] How to check a text file for a certain line?
Click on the types tab on that page and you'll see the documentation for file_line. Kent On Mon, Apr 21, 2014 at 5:53 PM, Andreas Ntaflos d...@pseudoterminal.orgwrote: On 2014-04-22 00:10, Joachim Schrod wrote: On 04/21/14 19:42, Kenton Brede wrote: Look into using file_line, it's part of stdlib. https://forge.puppetlabs.com/puppetlabs/stdlib Hmm, I don't detect any documentation of file_line at that URL. Could you post another link with documentation? Funny that it doesn't seem to be mentioned in the README anymore, but here is the code and the documentation: https://github.com/puppetlabs/puppetlabs-stdlib/blob/master/lib/puppet/type/file_line.rb Andreas -- Kent Brede -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CA%2BnSE38vtL0_JVfBX3dnPhLv%3DiFF98_L-nAZu7nxjyibZWjf8Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] using custom array based fact with defined type
Hello ,
I have a custom facts which returns the block devices based on some
condition in an array.
facter | grep arraydev
arraydev = [sdb, sdc]
Now i want to use this array in defined type so that a exec resource can
run as no. of times elements in the array.
vi modules/test/manifest/exeecho.pp
define test::exeecho() {
exec {echo_${name}:
command = echo hello /tmp/foo23,
path = ['/bin'],
}
}
vi modules/test/manifest/init.pp
class test {
test::exeecho{$::arraydev:}
}
But puppet agent -t run gives a error.
Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid
resource type exec at
/etc/puppetlabs/puppet/modules/test/manifests/exeecho.pp:5 on node
pzxdcc0002.cdbt.pldc.kp.org
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
Please tell me if i am doing something wrong.
Regards,
Ritesh Nanda
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/e1496d63-5bbd-45bc-ac0b-9141287ba2c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] puppet module permissions - librarian-puppet
I'm using 0022 on no both desktop and puppet master. - Trey On Apr 21, 2014 2:02 PM, Robin Bowes robin.bo...@yo61.com wrote: What umask are you using? R. On 21 Apr 2014 19:18, treydock treyd...@gmail.com wrote: I have noticed lately that on my development system (OS X) and my production Puppet master (CentOS 6.5) that when installing puppet modules using librarian-puppet the permissions of some modules and files is very restrictive to the point where the puppetmaster can't read the files. Some modules end up with all files being 0400, while some end up 0644 and some 0664. The files read-only to user are unable to be accessed by the Passenger based Puppet master and the files that sometimes go from 0664 to 0644 are creating a lot of noise in agent reports. Is there a defacto standard for the appropriate permissions, especially for custom puppet providers/types/functions? I've noticed that whatever the permissions end up being on the master is what they get set to on the clients. I'm unsure if the permissions are being set by librarian-puppet, the puppet module command, or some other mechanism. The permissions are always like this after a bundle exec librarian-puppet install. I've since had to put a script in my librarian-puppet repo that executes a find and modifies permissions, which does not seem right. Curious if anyone else has seen this or has suggestions for how to debug. Thanks - Trey -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/bc4f86d5-0c65-4ec6-bc98-43f437a611e6%40googlegroups.comhttps://groups.google.com/d/msgid/puppet-users/bc4f86d5-0c65-4ec6-bc98-43f437a611e6%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to a topic in the Google Groups Puppet Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/puppet-users/eFMjkVhBhZA/unsubscribe. To unsubscribe from this group and all its topics, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAJGKfwBxQ_OYmgq1UWbrwSHCTdxUd96epNC8AYiZm7D0VrkN3Q%40mail.gmail.comhttps://groups.google.com/d/msgid/puppet-users/CAJGKfwBxQ_OYmgq1UWbrwSHCTdxUd96epNC8AYiZm7D0VrkN3Q%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAN0oX1YEn7ked8gPTQFLGnWa__%2BaZnV7smbNYORESoKQr%3Dpw%3DA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
