Ok, opened a ticket with more info. Same bug happened on my learning VM.
http://projects.puppetlabs.com/issues/20643
On Wednesday, May 8, 2013 10:57:09 AM UTC-7, Aaron Stone wrote:
Interesting! Let me see if this still happens in the rails3 branch. Please
file a ticket so the issue doesn't
Hi Eric,
By default, hiera-cli uses /etc/hiera.yaml, hiera-puppet uses
/etc/puppet/hiera.yaml as config file. That was my mistake starting
using hiera cli for testing.
Btw, facter --puppet region wil also work, so no need for grep anymore.
On 05/09/2013 04:34 AM, Eric wrote:
When I run
Hi,
I know it's been a while since this original posting but if you are still
looking for a solution to 'track changes' please check out the tool we
built, www.metaforsoftware.com. We just opened it up to free beta. I
think it can help you.
On Tuesday, January 24, 2012 8:02:03 AM UTC-8,
bump
--
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 post to this group, send email to
Are those packages defined in different files? If they are in the same
file you can just do the following
package {['pgk1', 'pkg2']:
ensure = 'installed',
} -
file { 'file1':
...
}
If they are in different files you maybe will be able to hack something
with the spaceship operator but it
On my server /etc/puppet/hiera.yaml is a symbolic link that points to
/etc/hiera.yaml, so I don't think that's the issue.
On Wednesday, May 8, 2013 11:52:04 PM UTC-7, Johan De Wit wrote:
Hi Eric,
By default, hiera-cli uses /etc/hiera.yaml, hiera-puppet uses
/etc/puppet/hiera.yaml as
nobody really ever had to deal with this ?
Dne pondělí, 6. května 2013 10:03:15 UTC+2 Tomáš Brandýský napsal(a):
Hello,
We've been running puppet for 5 years until the last week when the
certificate on the puppet server is expired.
We were looking for a procedure describing how to create a
Hi Campee,
On Thursday, May 9, 2013 3:34:20 AM UTC+1, Campee wrote:
I run puppet and get this error:
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Could not find data item ak_auth_primary in any Hiera data file and no
default supplied at
Thanks for the reply. You've answered my question.
I'll post back if I need anymore help.
On Tuesday, May 7, 2013 3:49:38 PM UTC+1, Ashley Penney wrote:
Foreman does replace nodes.pp. It acts as an 'ENC', the external node
classifier. We'd need more details on what you're doing with
Greetings Robin!
What about this solution? It's a quick-fix, but it might work well as you
want it to? Do a script which contains (see it as pseudocode):
for each hostname in hosts
do
echo node '$hostname' {include run_script}
/etc/puppet/manifests/site.pp
done
What do you other guys
Excuse again
This is the output of my node
puppet agent --server=puppet.x.x.x. --no-daemonize --verbose --onetime
info: Caching catalog for rlltas05a.x.x.x.x.
info: Applying configuration version '1368021386'
notice: Finished catalog run in 0.01 seconds
this is my site.pp
node 'rlltas05a' {
Hi Jeffrey,
It is a 'bug', and a known one at that:
http://projects.puppetlabs.com/issues/17523
Feel free to watch/vote for it.
ken.
On Wed, May 8, 2013 at 7:04 PM, Jeffrey Watts jeffrey.w.wa...@gmail.com wrote:
I'm setting up PuppetDB for the first time (and on OpenSuSE, yay). After
some
I believe you are missing a basic concept: Hiera is for the puppet MASTER, not
the agent/client.
From http://docs.puppetlabs.com/hiera/1/installing.html#installing-hiera
Installing Hiera
If you are using Hiera with Puppet, you should install it on your puppet master
server(s); it is optional
Thanks Ken!
J.
On Thu, May 9, 2013 at 7:26 AM, Ken Barber k...@puppetlabs.com wrote:
Hi Jeffrey,
It is a 'bug', and a known one at that:
http://projects.puppetlabs.com/issues/17523
Feel free to watch/vote for it.
ken.
On Wed, May 8, 2013 at 7:04 PM, Jeffrey Watts
I seem to get this off and on, but not consistently. Is yours every run?
puppet-master[7020]: Failed to submit 'replace facts' command for
ue1a-devdb01.ineu.us to PuppetDB at puppet.example.com:8081: SSL_connect
SYSCALL returned=5 errno=0 state=SSLv3 read finished A
I am also on puppetdb
On Monday, May 6, 2013 10:03:15 AM UTC+2, Tomáš Brandýský wrote:
Hello,
We've been running puppet for 5 years until the last week when the
certificate on the puppet server is expired.
We were looking for a procedure describing how to create a new server
certificate without a need to
On Wednesday, May 8, 2013 8:38:52 AM UTC-5, Robin Jonsson wrote:
Thank you for your reply.
First of, we are kinda aware of that we are not using Puppet as it should
be used with the state management service. But Puppet seemed to be the a
great piece of software with great capabilities.
On Wednesday, May 8, 2013 8:06:27 PM UTC-5, James Kyle wrote:
I started getting the following errors from my puppet master:
Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: Invalid parameter provider at /some/module/manifests/foo.pp
The module would vary,
Dear All,
I am using puppet agent v3.0.1 (On FreeBSD), trying to connect to a puppet
master v3.0.2 (On Ubuntu) and the puppet agent hangs with the following
debug output:
*puppet agent --debug --no-daemonize*
...
Debug: /File[/var/puppet/ssl/private_keys]: Autorequiring
File[/var/puppet/ssl]
On Tuesday, May 1, 2012 12:00:19 PM UTC-4, Eric Lake wrote:
I am wondering what would cause a puppet client to get into a state like
this. I had a test vm do the same thing to me today.
Since nobody else responded first let me say thanks for posting the correct
syntax - I googled the
On Thu, May 9, 2013 at 12:06 AM, John Warburton jwarbur...@gmail.com wrote:
I suppose all HA solutions are difficult
Nah. A service correctly designed to be resilient can be HA with
trivial investment.
DNS is a good example. It may have blemishes but nobody stresses about
its availability.
On Thu, May 9, 2013 at 10:42 AM, Martin Langhoff
martin.langh...@gmail.com wrote:
I am writing some tooling for git+puppet (search for ppg in recent
posts to this list), and it's trivial to add N-tiers of redundant
servers...
Heh, so trivial in fact that you can use round-robin DNS and it'll
2013/5/9 Nicolai Mollerup nicolai.molle...@gmail.com
Anyway I think the easy way is to setup some autosigning of clients after
creating a new CA.
Think you will have to clean the ssl-dir on clients for this to work,
though.
Since we are going to make a brand new puppetmaster here sometime
Hmm..it seems like a pretty basic use case is an accompanying gpg file for
each level of a hierarchy, just to store things like passwords, or
sensitive data. Minimizing the use of things like hiera's 3.x data bindings
to gain speed in hiera-gpg lookups feels like throwing the baby out with
the
Hm, I started seeing this when I moved to a dynamic environment
configuration and began incorporating the openstack modules.
Are there workarounds or rules of thumb to avoid it while still being able
to use environments?
-james
On Thursday, May 9, 2013 6:33:38 AM UTC-7, jcbollinger wrote:
I was able to solve this. The facts were being communicated correctly,
however the custom facts had a additional newline at the end. So I just
needed to clean up the whitespace.
fact.last.strip
Once the fact was cleaned, hiera lookups started to work again.
On Monday, May 6, 2013
I don't get how any of your points are relevant to my issue.
I never said that I'm trying to run Hiera on my client. I have a puppet
module with templates, and the variables in my template are looked up in
Hiera on my Puppet Master server. My client is unable to apply the module
because it
Thanks for telling me about the debug option.
ericc@ops1-2-qa-sjc:puppet$ hiera -c /etc/puppet/hiera.yaml ak_auth_primary
region=northamerica datacenter=sjc environment=qa machinetype=qa
hostname=tag5-4-qa-sjc --debug
DEBUG: Thu May 09 11:04:27 -0700 2013: Hiera YAML backend starting
DEBUG:
On 5/9/2013 7:42 AM, Martin Langhoff wrote:
On Thu, May 9, 2013 at 12:06 AM, John Warburton jwarbur...@gmail.com wrote:
I suppose all HA solutions are difficult
Nah. A service correctly designed to be resilient can be HA with
trivial investment.
DNS is a good example. It may have blemishes
Did you restart your puppetmaster process ?
If you made any change to your config file (/etc/puppet/hiera.yaml) you need to
restart the puppetmaster process for the updates to be in effect.
I spun my wheels a bit before that sunk in for me :)
“Sometimes I think the surest sign that
I am running httpd + passenger. The puppetmaster service is turned off and
not running. Do I need to restart httpd instead or does this not apply if
you're running httpd?
On Thursday, May 9, 2013 11:36:34 AM UTC-7, Ygor wrote:
Did you restart your puppetmaster process ?
If you made any
I use Passenger also.
You need to restart the httpd for the change to kick in.
Is that what happened ?
“Sometimes I think the surest sign that intelligent life exists elsewhere in
the universe is that none of it has tried to contact us.”
Bill Waterson (Calvin Hobbes)
- Original Message
I definitely did not restart httpd, but I can try that the next time I
encounter this issue.
On Thursday, May 9, 2013 11:48:40 AM UTC-7, Ygor wrote:
I use Passenger also.
You need to restart the httpd for the change to kick in.
Is that what happened ?
“Sometimes I think the surest sign
Good luck to you.
My apologies at misunderstanding you earlier. Just trying to help
“Sometimes I think the surest sign that intelligent life exists elsewhere in
the universe is that none of it has tried to contact us.”
Bill Waterson (Calvin Hobbes)
- Original Message -
From: Campee
rhel 6.4
puppet 3.1.1
I've written a puppet module for configuring qpidd brokers. I have
installed the module in /usr/share/puppet/modules.
I can successfully configure broker artifacts (exchanges, queues, bindings,
etc), using manifests and puppet apply from the commandline.
Now I'm trying to
I've run into several incidences where a module attempts to install a
package before the apt::source is added or an update is run. Result is a
bunch apt errors and explosions.
Basically what should be done is all the apt::sources are added and and an
update run _before_ any packages are
On Wed, 8 May 2013 06:49:32 -0700 (PDT)
jcbollinger john.bollin...@stjude.org wrote:
Examining the code doesn't reveal any obvious error. Facter uses
this:
def
self.read_sysfs_dmi_entries(path=/sys/firmware/dmi/entries/1-0/raw)
if File.exists?(path) File.read(path)
end
end
On Thu, May 9, 2013 at 2:31 PM, Ramin K ramin-l...@badapple.net wrote:
Hubris, today thy name is Martin. :-)
Fair enough. I am happy about the tool I am writing (almost finished!)
but, as the followup post makes clear, it isn't about the designe of
ppg. It is about the design of git.
I'd argue
On Thu, 9 May 2013 17:10:51 +0200
Lorenzo Salvadorini lorenzo.salvador...@softecspa.it wrote:
2013/5/9 Nicolai Mollerup nicolai.molle...@gmail.com
Anyway I think the easy way is to setup some autosigning of clients
after creating a new CA.
Think you will have to clean the ssl-dir on
Here's the output for the commands you requested. Thanks again for looking
into it.
+* ruby --version*
ruby 1.9.3p392 (2013-02-22 revision 39386) [x86_64-linux]
+* ls -l /sys/firmware/dmi/entries/1-0/raw*
-r 1 root root 0 May 6 10:39 /sys/firmware/dmi/entries/1-0/raw
+* stat
I've done the following, it ended up being a bit simpler for me when I'm
not sure what random services a new CentOS install has installed and/or
enabled...
define no_service ( ) {
service { ${name} :
ensure = stopped ,
enable = false ,
status = stat -t
On Thu, 9 May 2013 13:58:45 -0700 (PDT)
John Simpson j...@voalte.com wrote:
I've done the following, it ended up being a bit simpler for me when
I'm not sure what random services a new CentOS install has installed
and/or enabled...
define no_service ( ) {
service { ${name} :
Please apply the diff from
https://github.com/puppetlabs/puppet-dashboard/pull/226 to resolve the
issue.
On Tue, May 7, 2013 at 6:12 AM, Klavs Klavsen kl...@enableit.dk wrote:
Found out anything about why this is ? Any fix ?
deleting a node hangs puppet-dashboard here :( - I have to restart
If I have something like this in my node file:
daemontools_service::setup {
'carbon-cache':
service_name = 'carbon-cache',
extra_envs = {
GRAPHITE_STORAGE_DIR = /mnt/statsd-data/graphite-storage
SOMETHING_ELSE
Upgrade to 0.3.1 is advised since it fixes a serious issue in an specific
circumstance.
El lunes, 6 de mayo de 2013 00:23:38 UTC-5, Gerardo Santana Gómez Garrido
escribió:
This release adds a new option for ensuring that resource titles are
quoted.
puppet-cleaner is a set of tools that
OK. I have looked thru the module and I have some comments and feedback.
I am delightfully impressed with what you have here.
I am a bit disappointed with the sterile naming convention by CIS Benchmark
document paragraph numbers. I think it makes it tougher to maintain, but that
is just my
On Thu, May 9, 2013 at 11:52 AM, James Kyle li...@jameskyle.org wrote:
I've run into several incidences where a module attempts to install a
package before the apt::source is added or an update is run. Result is a
bunch apt errors and explosions.
Basically what should be done is all the
On Thu, May 9, 2013 at 3:57 PM, Stefan Schulte
stefan.schu...@taunusstein.net wrote:
On Thu, 9 May 2013 17:10:51 +0200
Lorenzo Salvadorini lorenzo.salvador...@softecspa.it wrote:
2013/5/9 Nicolai Mollerup nicolai.molle...@gmail.com
Anyway I think the easy way is to setup some
48 matches
Mail list logo