I opened a ticket for the environmentpath issue.
https://tickets.puppetlabs.com/browse/PUP-2607
--
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+uns
We released puppetlabs-rabbitmq 4.0.0 today with several new features and
bug fixes.
Let us know if you have any issues!
On Fri, May 16, 2014 at 12:23 PM, Morgan Haskel wrote:
> Steve,
>
> We can cut a new release. Is there anything outstanding you need to have
> merged in before we do that?
>
Hi,
It will confirm that the package is present. If it is not present it
will attempt to install it. If it is, then no action is taken.
Br,
-g
On 5/16/14, 9:09 AM, Guy Knights wrote:
> Thanks Garrett - so can you confirm then that ensure => present will
> never try to upgrade a package after th
My guess. Incompatible underlying ruby version.
On Friday, May 16, 2014 7:20:49 AM UTC-7, Paul Seymour wrote:
>
> Hello,
>
> Just updated to 3.6.0 and a strange thing is happening (might not be
> related to 3.6 specifically just testing before making the jump from 2.7
> for real).
>
> I have a
Hello: This might be a dumb question, but can you build a system manually
with the various CMSes? Are there a cross-set of technologies (Apache,
PHP, MySQL) that will work on all CMSes in your organization? I would
think in terms in how you would build these systems manually w/o puppet in
som
Hello Jesse & Matt.
This might be a dumb question, but can you build a system manually with the
various CMSes? Are there a cross-set of technologies (Apache, PHP, MySQL)
that will work on all CMSes in your organization? I would think in terms
in how you would build these systems manually w/o
On 5/15/2014 12:14 PM, Christopher Wood wrote:
(inline)
On Thu, May 15, 2014 at 11:45:21AM -0700, Ramin K wrote:
I'd also like to disagree slightly with Christopher who also
posted in this thread. Your profile:: classes are the perfect place
for all sorts of site specific nonsense including re
Thanks Jeremy, I was pretty sure that was the behaviour but I just wanted
to confirm as I hadn't found anywhere that explicitly spelled it out.
On Friday, May 16, 2014 9:24:22 AM UTC-7, Jeremy wrote:
>
> Guy,
>
> With ensure set to present all puppet will do is ensure that the
> software packag
On 05/16/2014 01:53 AM, Matthias Saou wrote:
> On Fri, 16 May 2014 07:28:23 +0200
> David Schmitt wrote:
>
>> easy solution: create a local site module (e.g. "matthew") an put
>> every thing there. Manage it like all other modules. I did that at >
>> https://github.com/DavidS/dasz-configuration/
Guy,
With ensure set to present all puppet will do is ensure that the
software package is installed. Regardless of what version it will simply
validate that it is installed and if it isn't it will trigger and
install of the current version. You can then make use of 'mco package
update ' to tr
Steve,
We can cut a new release. Is there anything outstanding you need to have
merged in before we do that?
Thanks,
Morgan
On Wednesday, May 14, 2014 11:54:34 AM UTC-4, Stephen Boissiere wrote:
>
> Hi all, I'm hoping somebody can tell me if a new release of the Rabbit MQ
> plugin is imminent
Thanks Garrett - so can you confirm then that ensure => present will never
try to upgrade a package after the initial install?
On Thursday, May 15, 2014 11:39:02 AM UTC-7, Garrett Honeycutt wrote:
>
> On 5/15/14, 11:19 AM, Guy Knights wrote:
> > I'm looking at ways to better automate our build p
I work with Matt and am filling in for him since I posed this question to
him originally.
Our confusion really lies around how you layout profiles for a
multi-function box. For example, suppose you have a role, "CMS App Server"
that will host various CMS like Wordpress, Drupal, and others. They
Hi,
The strange is that problem appears only use hiera (hiera_include), when i
comment this line in my site.pp and create any simple manifest this is
applicate without problem in my node.
2014-05-16 9:29 GMT-04:00 jcbollinger :
>
>
> On Thursday, May 15, 2014 12:14:41 PM UTC-5, mike wrote:
>>
>>
Hello,
Just updated to 3.6.0 and a strange thing is happening (might not be
related to 3.6 specifically just testing before making the jump from 2.7
for real).
I have a puppet master running under Apache/Passenger and when testing a
client this happens:-
$ puppet agent -t --no-daemonize --noo
On 05/16/2014 09:29 AM, Johan Sunnerstig wrote:
> Hello,
>
> I'm just wondering how people with a decent collection of modules are
> organizing their modules and repositories?
> We currently have one big repository with everything in it, and three
> branches, basically stuff moves alpha -> beta ->
Hello
I have a local puppet client installed in my machine.
I downolad https://github.com/swanke/puppet-users.git to manage linux users
I try to do a probe with the test folder:
puppet apply /root/git/puppet-users/tests/init.pp
Error: Puppet::Parser::AST::Resource failed with error ArgumentError:
That's good info! I wasn't entirely sure how Augeas handled each statement
in the changes block, so I did initially try chaining multiple statements
with Puppet ordering to make sure. I'll give this a shot and see what
happens.
On Thursday, May 15, 2014 1:02:02 PM UTC-4, David Lutterkort wrot
On Thursday, May 15, 2014 12:14:41 PM UTC-5, mike wrote:
>
> Hi everyone,
> I'm setting in my Puppet the MySQL module with Hiera but when i run the
> node agent i give the error.
>
> --
> [root@node1 ~]# puppet agent --test
> Info: Retrieving plugin
> Error: Could not retrieve catal
Hello,
I'm just wondering how people with a decent collection of modules are
organizing their modules and repositories?
We currently have one big repository with everything in it, and three
branches, basically stuff moves alpha -> beta -> production. This is nice
and simple in a way, but has so
On Thursday, May 15, 2014 3:44:02 PM UTC-5, Marc DiPasquale wrote:
>
> Is it possible to use the resource metatype (or some other way) to purge
> my custom resource?
> I'm using Puppet v3.4.3 (Puppet Enterprise 3.2.0)
>
> I have a custom resource that is exported by a puppet module when an
> a
Am 16.05.2014 12:26, schrieb Andy Adman:
> /Warning: Puppet kick is deprecated./
Maybe mcollective is what you want.
Bye...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
Am 16.05.2014 12:26, schrieb Andy Adman:
> Shit now it fails. I checked my sudoers rules and ok there is written:
Your $HOME is different than foreman's. Puppet looks into $HOME/.puppet
for it's certs.
HTH...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recomm
Hi All,
I'm having issues with what seems to be incorrect parsing by all the custom
functions we have.
If I run "ruby -rpuppet" I get something like:
[root@puppet modules]# ruby -rpuppet
/var/lib/puppet/lib/puppet/parser/functions/foreman.rb
/usr/lib/ruby/site_ruby/1.8/puppet/parser/functions.rb
So I'm testing out puppet 3.6 with our existing environment and in general
i'm pleased.
There's one oddity that I'm tripping on and I'm not sure how to address it.
We have a number of places where we leverage the 'file' resource with an
array of sources - using fileservers to pick the first ma
Hey all,
i am a little confused, so i need some ideas. I have a
Foreman(PuppetMaster) server installed on Amazon EC2 and i am able to
provision instances to the same ec2 subnet.
After the provisioning i can run puppet from the agent and everything is
going well.
Ok, but i want to kick the pupp
On Friday, May 16, 2014 8:12:55 AM UTC-4, Dirk Heinrichs wrote:
>
> Am 15.05.2014 21:25, schrieb Ugo Bellavance:
>
> I wrote my first puppet module and it is for lsyncd.
>
>
> Just looked into lsyncd and what it can achieve. While I like rsync and
> use it quite often, there's a better way to
Am 15.05.2014 21:25, schrieb Ugo Bellavance:
> I wrote my first puppet module and it is for lsyncd.
Just looked into lsyncd and what it can achieve. While I like rsync and
use it quite often, there's a better way to mirror directories to
multiple destinations: BitTorrent Sync (btsync). btsync use
I can confirm all three of these issues in my environment also.
The environmentpath works in [main] only. Even though configprint shows it
is still there when moved to [master] and the modulepath looks correct
also, but the puppet master does not find any of the modules.
# puppet master --conf
Hi Felix,
>>puppet master --configprint all
Does show that environmentpath is set when placed in [master] section,
except client cannot find is modules anymore.
Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Could not find class vmware for on node
>>some configu
On 05/16/2014 11:20 AM, Stefan Heijmans wrote:
> - directory environments
> Documentation says; "Set environmentpath = $confdir/environments in the
> puppet master’s puppet.conf (in the [master] or [main] section)."
> Except environmentpath does not work in the [master] section, [main]
> section w
On Friday, May 16, 2014 1:35:22 AM UTC-4, David Schmitt wrote:
>
> Hi,
>
> On 16.05.2014 04:37, Ugo Bellavance wrote:
> > I worked on this tonight, but now I get an error when I try to apply it:
> >
> > Could not retrieve catalog from remote server: Error 400 on SERVER:
> > Invalid parameter
Hello,
Just upgraded Puppet from 3.4.3 to 3.6.0 in our sandbox, noticed the
following.
- directory environments
Documentation says; "Set environmentpath = $confdir/environments in the
puppet master’s puppet.conf (in the [master] or [main] section)."
Except environmentpath does not work in th
It works. Thanks a lot my Google'ing turned up nothing
--
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 thi
Hi,
I think someone said a workaround in this group that consisted in
setting the arch. You can try with:
package { 'openssh-server.x86_64':
ensure => 'absent',
}
Hth,
El 16/05/2014 09:54, "Paul Seymour" escribió:
> Hello,
>
> Working through some issues with upgrading our environment
On Thu, 15 May 2014 11:42:01 -0700
Eric Sorenson wrote:
> Hot on the heels of Puppet 3.5 comes Puppet 3.6.0. We said things
> were going to accelerate in Puppet's open-source release cadence, and
> here it is.
>
> Puppet 3.6.0 is a backward-compatible features and fixes release in
> the Puppet 3
Hello,
Working through some issues with upgrading our environment from 2.x to 3.5
(now I should probably target 3.6 !) anyway we have a module which
does basically.
package { 'openssh-server':
ensure => 'absent',
}
package { '3rd-party-ssh':
ensure => 'installed'
}
This 3rd party SSH pack
On Fri, 16 May 2014 07:28:23 +0200
David Schmitt wrote:
> easy solution: create a local site module (e.g. "matthew") an put
> every thing there. Manage it like all other modules. I did that at >
> https://github.com/DavidS/dasz-configuration/tree/master/modules/dasz
> and never looked back.
I s
38 matches
Mail list logo
