On 01/19/2011 12:39 AM, MJ wrote:
I'm suspect it is one of the subtle and strange behavoir. I suppose
I should have just posted a link to the code in git hub. I guess I
was expecting that this would be something that was going to jump out
as something obvious. My apologies for not doing so.
On Tue, Jan 18, 2011 at 10:57 -0800, Jeff McCune wrote:
puppet cert --confdir ~/.puppet/conf_test --certdnsnames
puppet-old.domain:puppet-new.domain:puppet-old:puppet-new --generate
puppet-new.domain
Thank you, this works!
Robert Scheer
--
You received this message because you are
Sorry, I missed that part. Site is a define. Looking at the logs I'm
also getting a different message at random:
Could not run Puppet configuration client: Parameter alias failed:
Munging failed for value scisoc.uwaterloo.ca in class alias: Cannot
alias
On Tue, Jan 18, 2011 at 06:41:26PM -0800, Bostjan Skufca wrote:
Hi again!
Is there any way to override client-specified environment in puppet
master? I would like my puppetmaster node definition to set the real
environment the node is in.
Tnx for info,
b.
I dont think this will work
Without seeing your code, does the user 'scisoc.uwaterloo.ca' already exist in
your manifest? Or maybe you didn't fully revert your changes? Also puppet
doesn't revert changes made to nodes unless you tell it how.
Other tip would be to try virtualizing the resource and realize it, or striping
Den,
It was the second problem, not reverting all of my code. I still had a
drupal6::site with the alias parameter (which I renamed to not
conflict with the meta params to sitealias) set to
'scisoc.uwaterloo.ca'. After I changed alias to sitealias puppet ran
fine. It was hard to pin down from the
My pleasure.
On 20/01/2011, at 8:45, Lithium brad.kr...@gmail.com wrote:
Den,
It was the second problem, not reverting all of my code. I still had a
drupal6::site with the alias parameter (which I renamed to not
conflict with the meta params to sitealias) set to
'scisoc.uwaterloo.ca'.
On Jan 19, 12:58 am, Felix Frank felix.fr...@alumni.tu-berlin.de
wrote:
On 01/19/2011 12:39 AM, MJ wrote:
I'm suspect it is one of the subtle and strange behavoir. I suppose
I should have just posted a link to the code in git hub. I guess I
was expecting that this would be something
On 19 January 2011 17:41, Bruce Richardson itsbr...@workshy.org wrote:
On Wed, Jan 19, 2011 at 05:10:56PM +1100, John Warburton wrote:
wishes - https://projects.puppetlabs.com/issues/3910
*Looks at discussion* Ouch. If the client were still allowed to
override the environment, even when
(...or, y'know, write the patch. We are really happy to accept that
sort of thing.)
Aaah, I always forget that these sorts of things are easy with
scripted languages:)
Anyway, ticked has been opened as #5936 and feature has been
implemented in here:
The way John sums it up really makes sense. Feature request?
b.
On 20 jan., 00:04, John Warburton jwarbur...@gmail.com wrote:
On 19 January 2011 17:41, Bruce Richardson itsbr...@workshy.org wrote:
On Wed, Jan 19, 2011 at 05:10:56PM +1100, John Warburton wrote:
wishes
On 20 January 2011 13:18, Bostjan Skufca bostjan.skufca.w...@gmail.comwrote:
The way John sums it up really makes sense. Feature request?
Alan Barrett did this in note 17 -
https://projects.puppetlabs.com/issues/3910#note-17
John
--
You received this message because you are subscribed to
On 01/18/2011 03:06 PM, Avi Miller wrote:
Mike Lococo wrote:
2) Use the yum-driven options *AND* run your own satellite server so you
can ping it as often as you like.
You don't need a Satellite Server for this, just a plain Yum server will
do, which is essentially just httpd + createrepo
I 'm configuring puppet in an ubuntu server and a client. When I define the
server's IP as hostname puppet, things are working well. But When I try to
change the hostname to something different it is not working
root@client ~# puppetd --test --server server.example.local
err: Could not retrieve
On Wed, Jan 19, 2011 at 17:33, Bostjan Skufca
bostjan.skufca.w...@gmail.com wrote:
(...or, y'know, write the patch. We are really happy to accept that
sort of thing.)
Aaah, I always forget that these sorts of things are easy with
scripted languages:)
Anyway, ticked has been opened as #5936
On Jan 18, 2011, at 9:38 PM, Bostjan Skufca wrote:
Would anyone else fancy a wildcard path expansion in module path
specification?
Example:
modulepath = /etc/puppet/modules/*
---[ above should expand to this
equivalent ]--
[ provided that repo1 and
Hi
I have a small number of gems I install on my puppet server, and manage to
get them compiled and they pick up my non standard environment and install
OK
However, I need to send some options to the mysql gem to get it to compile.
Hence I do it by hand, which is now biting, as well as not the
On Wed, Jan 19, 2011 at 20:01, Derek J. Balling dr...@megacity.org wrote:
On Jan 18, 2011, at 9:38 PM, Bostjan Skufca wrote:
Would anyone else fancy a wildcard path expansion in module path
specification?
[...]
There are a couple potential caveats to that, the most serious being sort
On Wed, Jan 19, 2011 at 20:02, John Warburton jwarbur...@gmail.com wrote:
I have a small number of gems I install on my puppet server, and manage to
get them compiled and they pick up my non standard environment and install
OK
I can't help with the gem provider, but my general advice is:
On 20 January 2011 15:08, Daniel Pittman dan...@puppetlabs.com wrote:
On Wed, Jan 19, 2011 at 20:02, John Warburton jwarbur...@gmail.com
wrote:
2) Trying to pre-compile the gem and install it. Since I have no idea what
I
This. Always do this. It gives you predictable, uniform behaviour,
I know that's not the exact answer you want but why not filling up the
hosts file with additional puppet on the concerned server ? Or in the
DNS if you're in a biggest organization ...
On Jan 20, 12:06 am, Basil Kurian basilkur...@gmail.com wrote:
I 'm configuring puppet in an ubuntu server and
On Jan 19, 2011, at 6:06 AM, Basil Kurian wrote:
root@client ~# puppetd --test
err: Could not retrieve catalog from remote server: undefined method
`closed?' for nil:NilClass
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
This
I had a problem like this when I changed the hostname I was using to access the
puppet server (from puppet to something else).
I think in the end I regenerated the ssl keys on the server and it started
working. Not sure if that was a required fix or a coincidental fix as I didn't
do any
On Jan 17, 6:38 pm, Nigel Kersten ni...@puppetlabs.com wrote:
I'm trying to get a feel for the actual use cases for the Schedule type in
Puppet.
Anyone care to help me out with some real world examples?
Schedules go great with exported resources. My use case is getting
applied changes on
On Thu, Jan 20, 2011 at 10:04:37AM +1100, John Warburton wrote:
On 19 January 2011 17:41, Bruce Richardson itsbr...@workshy.org wrote:
On Wed, Jan 19, 2011 at 05:10:56PM +1100, John Warburton wrote:
wishes - https://projects.puppetlabs.com/issues/3910
*Looks at discussion* Ouch. If
25 matches
Mail list logo
