Hi Folks,
I'm new to puppet and rspec and like to write a unit test that checks if an
fail message is raised in case my module is run on non-supported operating
system, so I wrote something like the code below, but I end-up if an error
of 'No matching value for selector Darwin'.
# my_module/m
Hi,
the docs seem to indicate that there are a few caveats to consider.
http://docs.puppetlabs.com/guides/rest_api.html#the-agent-rest-api
Do you have both namespaceauth.conf and proper rest_authconfig settings?
HTH,
Felix
On 04/17/2013 11:01 AM, Javier Dehesa wrote:
> Is there any possibility
On Friday, April 19, 2013 11:58:27 AM UTC-7, Matt Hargrave wrote:
>
> I am trying to use the attributes field for AIX user attributes. I
> currently have:
>
> user { "test1":
> ensure => present,
> uid => '123456',
> gid => 'system',
> shell => '/bin/ksh',
>
This doesn't seem to work for me in THIS specific case:
-editing the file directly under /var/named
Adding a new file works fine, but editing an existing one doesn't trigger
the exec. I think the directory mtime doesn't change, and Puppet doesn't
know that a change has happened. Thoughts?
On
I am trying to use the attributes field for AIX user attributes. I
currently have:
user { "test1":
ensure => present,
uid => '123456',
gid => 'system',
shell => '/bin/ksh',
home => '/home/test1',
attributes => ["login=true", "rlogin = true"],
Based on a thread seen earlier, it appears not-entirely-offensive for
puppet community members like myself to post job openings for their places
of employment. Hence I post:
http://www.reddit.com/r/sysadminjobs/comments/1cmo2l/hiring_system_administrator_for_the_genome/
--
You received this
yum list puppet puppet-server --enablerepo=puppetlabs-devel
Installed Packages
puppet.noarch 3.1.1-1.el5 installed
puppet-server.noarch 3.1.1-1.el5 installed
Available Packages
puppet.noarch 3.2.0-0.1rc1.el5 puppetlabs-devel
puppet-server.noarch 3.2.0-0.1rc1.el5 puppetlabs-devel
OK. Now it
On Friday, April 19, 2013 5:46:37 AM UTC-4, David Schmitt wrote:
>
> Is there any reason to use a puppet as source? You can put that on an
> NFS share too and reference it by path. Or clone a git repo.
>
Simplicity. Keeping everything in the puppet milieu, which is already
set up. Don't want
Have you run yum clean all yet? If you haven't, you're cache might be
outdated, and you wouldn't see the update.
On Friday, April 19, 2013 7:50:12 AM UTC-7, Ygor wrote:
>
> RHEL 5, x86_64
>
> The rpm is there --
> https://yum.puppetlabs.com/el/5/devel/x86_64/puppet-3.2.0-0.1rc1.el5.noarch.rpm
>
Is the "puppetlabs-devel" repo enabled?
[puppetlabs-devel]
...
enabled=1
On Friday, April 19, 2013 10:50:12 AM UTC-4, Ygor wrote:
>
> RHEL 5, x86_64
>
> The rpm is there --
> https://yum.puppetlabs.com/el/5/devel/x86_64/puppet-3.2.0-0.1rc1.el5.noarch.rpm
>
>
> But yum cannot see it to pull
> As far as I am aware, resource defaults still affect the dynamic scope in
> which they are declared, just as they always have done. The guide to which
> you referred seems to say that, too. That means that the defaults you
> declare in class 'mongo' apply to all resources declared in that cl
RHEL 5, x86_64
The rpm is there --
https://yum.puppetlabs.com/el/5/devel/x86_64/puppet-3.2.0-0.1rc1.el5.noarch.rpm
But yum cannot see it to pull it down. I can see
puppet-server-3.2.0-0.1rc1.el5, and when I tried to install, it failed on
missing dependency.
“Sometimes I think the surest si
On Thursday, April 18, 2013 12:32:28 PM UTC-5, Gerard B wrote:
>
> Hi,
>
> I'm running into some trouble when trying to access some variables which
> actually are a class parameter.
>
> The following works OK:
>
> node "common" {
> $var='foo'
> }
>
> node "gratia-base" inherits common {
>
> c
On Thursday, April 18, 2013 4:25:14 AM UTC-5, Matthias Saou wrote:
>
>
> --
> Matthias Saou ██ ██
> ██ ██
> Web: http://matthias.saou.eu/ ██
> Mail/XMPP: matt...@saou.eu
On Thursday, April 18, 2013 4:25:14 AM UTC-5, Matthias Saou wrote:
>
> Hi,
>
> I've been bitten by this quite a few times now, so it got me
> wondering...
>
> When I have both the following classes available :
>
> nagios::client
> mycompany::nagios::client
>
> And I decide to "include nagio
Hi,
I have a problem with running puppet with hiera based data. I am trying to
cleanup
user accounts on a range of servers (to have the same uid/gid). When I
create existing account
but with different uid/gid it doesn't change files group ownership so I
need to
run a script which cleanups after
puppetlabs-stdlib (v2.5.1)
This is what was listed in the output. What are the thoughts around this?
Thanks again!
On Thursday, April 18, 2013 11:19:45 PM UTC-4, Matthaus Litteken wrote:
>
> That's also true. stdlib 4.x has facts.d removed, while stdlib 2.x and
> 3.x still have facts.d, so fi
On Apr 19, 2013, at 9:34 AM, jcbollinger wrote:
> Moreover, I wanted to point out that, contrary to Brian's implication,
> automated class parameter binding is independent of whether parameters have
> explicit default values. If you do not bind a parameter's value via a
> class's declaration
Thanks for the response and help on this. I've pasted the output from the
facter -p command. The hostname looks legit as does the fqdn.
architecture => x86_64
augeasversion => 0.10.0
bios_release_date => 10/05/2012
bios_vendor => Cisco Systems, Inc.
bios_version => B200M3.2.1.1.0.100520121419
b
You can deactivate nodes with the instructions here on your Puppet master:
http://docs.puppetlabs.com/puppetdb/1.2/maintain_and_tune.html#deactivate-decommissioned-nodes
This will deactivate them, which means they should no longer be used
during exported resource collection. You can do this from
On Thursday, April 18, 2013 3:42:32 PM UTC-5, blalor wrote:
>
> When you use the hiera() function, you ate by definition not doing
> automatic param lookup. :-) whatever you put in for the first argument is
> the key that will be looked up via hiera verbatim. If you leave the class
> parameter
On Thursday, April 18, 2013 3:44:34 PM UTC-5, Matthew Barr wrote:
>
> I'm seeing an interesting dependency issue, based on scoping of default
> types.
> Using 3.1.1 & aware of
> http://docs.puppetlabs.com/guides/scope_and_puppet.html#declare-resource-defaults-per-file
>
> Our mongo::repos cl
To remove the certificate you can use the REST api
http://docs.puppetlabs.com/guides/rest_api.html
DELETE /{environment}/certificate_status/{hostname}
As for removing the node, I dont have an answer, I have posted the question
here prior and have yet to obtain a response. For now I an using ss
On Thursday, April 18, 2013 8:52:59 PM UTC-5, pho...@gmail.com wrote:
>
>
> I'm trying to use puppet to automate IBM Domino installation. The first
> demo that I want to make is including two servers.
>
>- One will be the primary Domino Server.
>- The other will be the additional serve
On Fri, Apr 12, 2013 at 12:23:45PM -0700, Larry Fast wrote:
> Windows NuBQ:
> I'm running windows with a clean install of puppet and an empty node
> definition. puppet agent -t pauses with no prompt. When I hit enter, I
> get this warning:
>
> Using Facter::Util::Resolution.exec with a shell
On 18.04.2013 21:00, Ken Coar wrote:
Background:
The puppetmasters are under the authority and control of a specific group
(not mine ;-) ). Client sysadmins have control over the node manifests
and, to a certain extent, can modify the puppet modules.
One of the modules (and potentially others)
26 matches
Mail list logo
