I'm trying to execute a custom mcollective RPC call via Atlassian Bamboo
and have run into a frustrating issue. I've posted this question to the
Bamboo community help page but figured I could try asking the same thing
here in case anyone's run into this problem as well, even though I suspect
possible if mco is waiting for stdin to close.
Do you have any suggestions for band-aid fixes to get around this issue
(from the mcollective side)?
Thanks,
Guy
On Monday, August 11, 2014 12:01:06 PM UTC-7, R.I. Pienaar wrote:
- Original Message -
From: Guy Knights guy.k...@gmail.com
Ok, I'll take a look at that. Thanks!
On Monday, August 11, 2014 1:03:50 PM UTC-7, R.I. Pienaar wrote:
- Original Message -
From: Guy Knights guy.k...@gmail.com javascript:
To: puppet...@googlegroups.com javascript:
Sent: Monday, August 11, 2014 9:00:53 PM
Subject: Re
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
the systems are running the same
version.
On 16.05.2014 12:09, Guy Knights wrote:
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
I'm looking at ways to better automate our build pipeline and I'm trying to
envision ways to get our latest code package onto servers, while also being
able to update this package at specific, later times.
The code will be served from a local yum repository, so I figure we can
install the
. I was under the impression that the actual file, not the symlink,
had to have these permissions, but apparently the symlink does as well.
Anyway, it's working now but I've updated this thread in case anyone else
runs into the same problem.
On Thursday, 10 April 2014 16:02:18 UTC-7, Guy Knights
I just upgraded puppet on my master machine (Ubuntu 12.04, running under
Passenger/Apache) and it doesn't work properly any more. The upgrade was
from 3.3.2 to 3.4.3.
First of all, after the upgrade I found that the location of config.ru had
changed, from
I have a service set up with a custom status check, but when I run puppet
it ignores my custom status command and runs the standard upstart status
check.
My service definition is as follows:
service { gamedeploy-${title}:
ensure = running,
provider = upstart,
start =
I'd like to use the same init script (via upstart) for multiple service
definitions, and I thought that if I gave them different titles but the
same name paramter (eg. script name) it should allow that. However, I get a
duplicated definition error.
eg.
* service { gamedeploy-backend:*
*name
I have a bunch of dev servers which have begun experiencing the same issue
when I run puppet apply. The full command I'm using is: sudo puppet apply
--modulepath=/opt/puppet-conf/development/modules
--environment=development.
I've never had a problem running this command before, but very
, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f87e13ba000
read(0,
It just hangs there at the read(0, line.
On Fri, Jan 17, 2014 at 11:04 AM, Guy Knights
g...@eastsidegamestudio.comwrote:
I have a bunch of dev servers which have begun experiencing the same issue
when I run puppet apply. The full
Oops...never mind. I just realised that I forgot to point the puppet apply
command at a manifest file. I did that and the command works now. Still, it
would be nice if it gave an error message if you don't supply a manifest.
On Fri, Jan 17, 2014 at 11:11 AM, Guy Knights
g
Well, wouldn't you know it but I just discovered the hiera() lookup
function which does exactly what I want.
On Friday, 13 December 2013 11:39:27 UTC-8, Guy Knights wrote:
Is it possible to reuse hiera variables within hiera itself? We have some
cases where we have a value that needs
deep in the puppetdb documentation. In any case, I'll work with this
option and see how I go.
On Monday, 9 December 2013 14:26:32 UTC-8, Guy Knights wrote:
I'm doing some testing with the puppetlabs/haproxy module on a vagrant box
with puppet 3 set up. The module we use requires exported
the ssh keys out of the hiera-data to keep the files
human readable
This is my response to the Unpleasant puppetlabs experience” Thread. I
am happy to share what I have tinkered together.
On Dec 6, 2013, at 5:23 PM, Guy Knights
g...@eastsidegamestudio.comjavascript:
wrote:
We're
I'm doing some testing with the puppetlabs/haproxy module on a vagrant box
with puppet 3 set up. The module we use requires exported resources to be
enabled in order to specify haproxy backends, but I don't have it
configured in puppet. I have our puppet repo checked out to the VM and am
using
We're working on implementing hiera with our puppet 3 setup, and I'm
curious if the following is achievable. Currently, we manage each user
account within a class that realises a defined resource that creates the
user, groups, etc (for the record, we use the torrancew/account module). We
then
sure the error is b/c the class names need to be capitalized.
On Tue, Sep 17, 2013 at 10:05 AM, Guy Knights
g...@eastsidegamestudio.comjavascript:
wrote:
Can someone tell me the correct way to specify the following require
statement in an rspec-puppet test?
*require =
[Class['ssl
Does anyone have any feedback on this? I found at least one example
(eg.
https://genuxation.com/wiki/index.php/RSpec_tests_for_puppet_modules#Specifying_parameters_used_within_the_class)
but it didn't work for me.
Thanks,
Guy
On Tuesday, 17 September 2013 10:05:26 UTC-7, Guy Knights wrote
Can someone tell me the correct way to specify the following require
statement in an rspec-puppet test?
*require =
[Class['ssl'],Class['pcre3'],Staging::Extract[nginx-${version}.tar.gz]]*
I tried this: *'require' =
[Class['ssl'],Class['pcre3'],Staging::Extract['nginx-1.4.1.tar.gz']]* but
got
...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
--
Guy Knights
Lead Systems Administrator
http://eastsidegamestudio.com
...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
--
Guy Knights
Lead Systems Administrator
http://eastsidegamestudio.com
puppet agent to tell me what environment it's using
when it requests the catalogue from the master?
Thanks,
Guy
On Thu, Sep 12, 2013 at 10:48 AM, Guy Knights
g...@eastsidegamestudio.comwrote:
Thanks for the reply John. Here's my hiera.yaml file:
---
:backends:
- yaml
:yaml:
:datadir
I'm not sure at all what's going on here, but I've spent a lot of time
reading over the puppet hiera docs and setting everything up, but when I
run puppet agent it just seems to ignore the hiera setup completely.
Both the puppet master and agent nodes have exactly the same versions of
puppet
I just worked this out shortly after my original post. The syntax I found
that works is
*'require' = 'Class[Couchbase::Server::Install]'*
On Monday, 2 September 2013 11:46:34 UTC-7, Guy Knights wrote:
I'm writing a test for a module which declares a service resource that has
a require
Ok, I found the solution - it was a simple case of adding the path to the
rspec bin directory to my PATH. Rake is using the -S switch, which uses
PATH to find the rspec binary.
Thanks,
Guy
On Fri, Aug 30, 2013 at 4:23 PM, Guy Knights g...@eastsidegamestudio.comwrote:
Do I need to replace
Hi,
What is the best way to ensure that when a node inherits another node, that
the inherited node's manifest runs first? Is there was a to ensure this
happens?
Thanks,
Guy
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this
Oh ok, thanks Dominic. I'll give that a go.
Regards,
Guy
On Wed, Jun 20, 2012 at 1:37 AM, Dominic Cleal dcl...@redhat.com wrote:
On 19/06/12 22:02, Guy Knights wrote:
I can now confirm that Dominic was correct. I'm upgraded to puppet
2.7.16 now and the augeas resources are working. One
That looks like the issue then. We're using augeas 0.10 (default with
ubuntu 10.04) and puppet 2.7.3. I'll look at upgrading puppet and see how
that goes.
Thanks all,
Guy
On Saturday, June 16, 2012 12:45:54 AM UTC-7, Dominic Cleal wrote:
On 15/06/12 22:42, Guy Knights wrote:
Ok, thanks
Sorry, never mind this. I discovered that the source version of puppet was
install in /usr/local/libs/site_ruby while the repository version appears
to have been installed in /usr/lib/ruby1.8.
On Tue, Jun 19, 2012 at 12:41 PM, Guy Knights
g...@eastsidegamestudio.comwrote:
Hi again,
I
Knights wrote:
That looks like the issue then. We're using augeas 0.10 (default with
ubuntu 10.04) and puppet 2.7.3. I'll look at upgrading puppet and see how
that goes.
Thanks all,
Guy
On Saturday, June 16, 2012 12:45:54 AM UTC-7, Dominic Cleal wrote:
On 15/06/12 22:42, Guy Knights
Cleal wrote:
On 15/06/12 22:42, Guy Knights wrote:
Ok, thanks for your help Alan. BTW, I forgot include our puppet version
- it's 2.7.0.
Which version of Augeas are you using? There's a bug if you're using
Augeas 0.10.0 with any version of Puppet before 2.7.10 where it won't
save
I've recently configured a couple of augeas resources, one for a php.ini
file and one for sudoers, however neither set of changes is being saved. I
have no idea why. The sudoers resource is here:
augeas { 'set_sudoers':
context= '/files/etc/sudoers/spec[user=%sudo]',
changes
/projects/1/wiki/Puppet_Augeas
http://augeas.net/docs/references/lenses/files/inifile-aug.html
Regards,
-Alan
On Fri, Jun 15, 2012 at 2:47 PM, Guy Knights g...@eastsidegamestudio.com
wrote:
I've recently configured a couple of augeas resources, one for a php.ini
file and one for sudoers
,
],
}
-Alan
On Fri, Jun 15, 2012 at 5:00 PM, Guy Knights g...@eastsidegamestudio.com
wrote:
Yeah, I tried --debug in my puppet command and it didn't give me any
errors.
In my original message i did say I tried doing the set from augtool and
it
worked, but I just tried it again with augtool
give it a bit
more thought.
Regards,
-ALan
On Fri, Jun 15, 2012 at 5:27 PM, Guy Knights g...@eastsidegamestudio.com
wrote:
Ok, thanks for the info. Are you implying that the puppet augeas resource
type acts in '--noload' mode, then?
I tried doing the fully qualified set statement
match, if you need to. Use the built-in $clientcert variable,
which contains the node's certname.
(This assumes you're doing the default behavior of using the certname
as the node name. Hint: you almost certainly are.)
On Apr 26, 4:38 pm, Guy Knights g...@eastsidegamestudio.com wrote:
I
I appears that backreferences when using regexes in node names doesn't
work. Can anyone confirm this? If I'm incorrect, how do I go about using a
backreference to the name regex within the node definition container?
Thanks,
Guy
--
You received this message because you are subscribed to the
39 matches
Mail list logo
