db to delete
specific virtual resources! So far as I can tell it doesn't work with -X
DELETE at all.
On Wednesday, August 5, 2015 at 11:28:49 AM UTC-7, Matthew Burgess wrote:
>
> On 5 Aug 2015 19:10, "Steve Wray" > wrote:
> >
> > I have a problem where a v
I have a problem where a virtual resource has, in an early run, got the
wrong value. I've fixed the manifest so that the virtual resource gets the
correct values and I've rerun Puppet on the node that populates the virtual
resource. However when it is instantiated it still gets the old value.
I
;ll do some more tests with the newer
version of foreman.
On 16 October 2013 20:02, Greg Sutcliffe wrote:
> On 16 October 2013 11:48, Steve Wray wrote:
>
>> Sure, I'm using this repository
>>
>> deb http://deb.theforeman.org/ precise stable
>>
>> it loo
ped out foreman. I didn't
have time to research the issue further or try to fix foreman.
On Wednesday, 16 October 2013 17:24:46 UTC+8, ohad wrote:
>
>
>
>
> On Wed, Oct 16, 2013 at 11:07 AM, Steve Wray
> > wrote:
>
>> It turned out that there was an update
17:26:33 UTC+8, Andreas Ntaflos wrote:
>
> On 2013-10-16 10:07, Steve Wray wrote:
> > It turned out that there was an update to the foreman package which
> > completely broke Puppets ability to enroll new nodes.
> >
> > Call me old fashioned, I've been a Debian
It turned out that there was an update to the foreman package which
completely broke Puppets ability to enroll new nodes.
Call me old fashioned, I've been a Debian sysadmin for over 10 years, but
on a 'stable' system an apt-get upgrade is not supposed to break things.
Thats one of the things De
I just realised that between now and then there was a foreman upgrade which
has basically broken my ability to enroll new nodes.
Great. Thanks package maintainer.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group a
I have about 75 nodes now and recently added 6 of them. They are all
running Debian squeeze and all have exactly the same Puppet packages. One
is giving an error when I try to enroll it:
Failed to import facts: PG::UndefinedColumn: ERROR: column "environment"
of relation "hosts" does not exist
On Wednesday, 11 September 2013 22:50:59 UTC+8, jcbollinger wrote:
>
>
> On Wednesday, September 11, 2013 2:49:50 AM UTC-5, Steve Wray wrote:
>>
>> I need to get an array of hostnames of clients of the puppet server.
>>
>> There doesn't seem to be a sim
I need to get an array of hostnames of clients of the puppet server.
There doesn't seem to be a simple way to do this so I've tried a few
methods.
I've tried a curl expression in a fact like this:
curl -s -k -H "Accept: yaml"
https://localhost:8140/production/facts_search/search?facts.nodetype
with
Puppet. I don't think the error message is about the MySQL configuration, I
think theres an undocumented Puppet configuration.
On Sunday, 14 July 2013 01:26:48 UTC+8, Ramin K wrote:
>
> On 7/13/2013 8:18 AM, Steve Wray wrote:
> > Getting this error;
> > The max p
Getting this error;
The max pool size is currently 5; consider increasing it
using MySQL.
Surprisingly, I haven't been able to find exactly where I make the
configuration change that Puppet suggests.
Any clues?
Thanks.
--
You received this message because you are subscribed to the Google Gro
ctory.
The advantage of doing it this way is that you can pull in *any*
puppet git branch as "upstream". If you're more familiar with
git-buildpackage, you can point it at any git branch as upstream, but
this seemed a simpler path to follow.
Silviu
Steve Wray wrote:
James T
James Turnbull wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/01/10 6:57 AM, Steve Wray wrote:
Hi there
I'd like to build packages of 0.25.2 for Debian but I'm finding that the
git repositories are still on 0.25.1
I am not sure how that's happening because they a
Hi there
I'd like to build packages of 0.25.2 for Debian but I'm finding that the
git repositories are still on 0.25.1
I'm not sure of how I should get 0.25.2 from git.
At the moment I'm using the commandline:
git clone git://github.com/reductivelabs/puppet
Please advise
Thanks!
--
Pleas
Quoting Nigel Kersten :
On Wed, Jan 6, 2010 at 6:16 PM, Steve Wray wrote:
Hi there
I am about to embark on a project to implement puppet for server management
and I'm noticing that the version currently in Debian testing is 0.25.1-3
while the latest stable version is 0.25.2
I'm
Hi there
I am about to embark on a project to implement puppet for server management
and I'm noticing that the version currently in Debian testing is 0.25.1-3
while the latest stable version is 0.25.2
I'm not seeing any indication on the Debian project page about 0.25.2 so I
thought I'd chec
Luke Kanies wrote:
> Hi all,
>
> I've been hesitant to send Reductive Labs updates to the community
> lists, but I've been told that not knowing who works for us makes some
> communication difficult.
>
[snip]
> Rein started out in the design world but quickly discovered an
> affinity for de
Hi there
I was reading the type reference, which seems to be autogenerated. It seems
current (last generated on Mon Mar 30 02:57:00 + 2009)
It mentions some types for supporting nagios.
If I recall correctly, from last time I tried to use this feature, it
wasn't producing nagios configura
jcbollinger wrote:
>
>
> On Aug 6, 9:03 pm, Steve Wray wrote:
>> Steve Wray wrote:
>
> [...]
>
>>> something seems wrong...
>>> This is all running under Debian Lenny.
>>> r...@tec-lb1:/etc# puppetd --version
>>> dnsdomainname: Unkn
Steve Wray wrote:
> Hi there,
>
> I have a small isolated group of servers. I don't want to set up DNS
> infrastructure for this.
>
> I have an /etc/hosts file that looks like:
>
>
> 127.0.0.1 localhost.localdomain localhost
> 192.168.50.70 tec-pup
Hi there,
I have a small isolated group of servers. I don't want to set up DNS
infrastructure for this.
I have an /etc/hosts file that looks like:
127.0.0.1 localhost.localdomain localhost
192.168.50.70 tec-puppet.tec.cwa.co.nztec-puppet
I can ping tec-puppet fine:
r...@tec
Hi there,
I'd like to reduce log traffic by stopping entries such as:
Starting configuration run
Finished configuration run in 1.23 seconds
What is the appropriate config option to disable this?
Thanks!
--
Please remember that an email is just like a postcard; it is not
confidential nor
Nigel Kersten wrote:
> On Tue, Mar 17, 2009 at 12:48 PM, Steve Wray wrote:
>> Nigel Kersten wrote:
>>> On Mon, Mar 16, 2009 at 12:44 PM, Steve Wray wrote:
>>>> I'm seeing these errors on many servers:
>>>>
>>>> Could not
Nigel Kersten wrote:
> On Mon, Mar 16, 2009 at 12:44 PM, Steve Wray wrote:
>> I'm seeing these errors on many servers:
>>
>> Could not run Puppet::Client::MasterClient: undefined method `-' for
>> #
>>
>>
>> This does not seem to happen when
I'm seeing these errors on many servers:
Could not run Puppet::Client::MasterClient: undefined method `-' for
#
This does not seem to happen when puppetd -vt is run manually. It shows
every half an hour or so.
Any ideas?
Thanks!
--
Please remember that an email is just like a postcard; i
Peter Meier wrote:
> Hi
>
>> Any comment or advice? Is this going to do something unexpected?
>
> looks fine to me. But didn't test it. You can put into a file and test
> it with:
>
> puppet --parseonly foo.pp
> for any syntax problems.
I am more concerned about logic problems :)
Syntax probl
Peter Meier wrote:
> Hi
>
>> Ok well, of neccessity, I am running in a mixed environment.
>
> I can understand that, on the otherside I would recommend to run a
> unique puppet environment and the custom packaging time you have to do
> for that is really worth the time.
Thats the objective.
In
Peter Meier wrote:
> Hi
>
>> Thats odd, last week I had thought this was working, now monday morning is
>> here and I get:
>>
>> err: Could not retrieve configuration: Could not parse for environment
>> production: Syntax error at '('; expected ')' at
>> /etc/puppet/manifests/classes/local_ser
Joshua Anderson wrote:
> Case statements don't work inside of resource definitions. There are
> three ways I can think of do what you're doing:
>
> 1. Use multiple inline selectors. (Very long and ugly.)
> 2. Write four different definitions of the NTP service and wrap them
> in a case statem
if you have multiple services that differ in a
> similar fashion, you can define all the variables you need in a few
> statements at the top of your class and have one short definition for
> each service.
A
A lot of things in puppet now make more sense, thanks heaps!
>
>
RijilV wrote:
>
> 2009/3/9 Steve Wray mailto:steve.w...@cwa.co.nz>>
>
>
> I want to stop ntpd on all domU and openvz virtual machines while
> enabling
> it on all dom0 and physical machines.
>
> I've been trying to get my
I want to stop ntpd on all domU and openvz virtual machines while enabling
it on all dom0 and physical machines.
I've been trying to get my head around this and searched through
documentation and examples but cannot find anything like this so far.
If its running Debian Sarge then the init scri
be totally ignored on sarge
machines; as it stands when puppetd runs I get an error on sarge servers:
"No packages found matching libc6-xen.'
which is right... there is no libc6-xen on sarge.
I'm a little surprised as it seems that 'absent' actually checks whether
the packag
de, it just doesn't seem to do anything
interesting with it.
>
> manufacturer => VMware, Inc.
> virtual => vmware
>
> manufacturer => Xen
> virtual => physical
>
> It appears that $virtual doesn't work on Xen :(
>
> Steve Wray wrote:
>>
ts
> distributed by Puppet.
>
> -Josh
>
> On Mar 9, 2009, at 1:50 PM, Steve Wray wrote:
>
>> Hi there,
>>
>> I'm trying to use a fact to tell whether the machine is virtualised.
>>
>> I found this and, in testing, its been ok:
>> http://reductive
Avi Miller wrote:
> Steve Wray wrote:
>> I prefer the second one but cannot fathom why the syntax is wrong.
>
> Inline syntax is a little different:
>
> package { ntp:
>ensure => $lsbdistcodename ? {
> sarge => present,
> default => a
facter -v
1.3.5
This is Debian Etch and Sarge. The -p works fine in Lenny with facter 1.5.1
> -Josh
>
> On Mar 9, 2009, at 1:50 PM, Steve Wray wrote:
>
>> Hi there,
>>
>> I'm trying to use a fact to tell whether the machine is virtualised.
>>
>>
Hi there,
I'm trying to use a fact to tell whether the machine is virtualised.
I found this and, in testing, its been ok:
http://reductivelabs.com/trac/puppet/wiki/Recipes/VirtualMachine
However, trying to roll this new fact out has been difficult.
1. Debian has got facter looking in /var/pupp
gt; as it seems to me to be more accurate in describing what I want it to
> do. It should achieve the same thing though.
>
> Steve Wray wrote:
>> Based on the documentation I had thought that this:
>>
>>file { "/var/puppet":
>> ensure => "/v
Based on the documentation I had thought that this:
file { "/var/puppet":
ensure => "/var/lib/puppet"
}
should create a symlink /var/puppet which points to the directory
/var/lib/puppet
It doesn't seem to be working :-/
Any ideas?
Thanks!
--
Please remember that an email is ju
Hi there,
I understand we have a variable $lsbdistcodename which gets its info from
the output of the lsb_release command but I've just found that this is not
very reliable.
I have several Debian Etch servers for which lsb_release reports that they
are running sarge :(
So far I've been unabl
Avi Miller wrote:
> Steve Wray wrote:
>> I prefer the second one but cannot fathom why the syntax is wrong.
>
> Inline syntax is a little different:
>
> package { ntp:
>ensure => $lsbdistcodename ? {
> sarge => present,
> default => a
Hi there,
we have a mixed deployment of sarge, etch and now lenny servers.
The first example works:
case $lsbdistcodename {
sarge: { package { ntp: ensure => present } }
default: { package { ntp: ensure => absent } }
}
This does not:
package { ntp:
case $lsbdistcodenam
pt/preferences:
>
> Package: *
> Pin: release a=experimental
> Pin-Priority: 1
>
> Package: puppet
> Pin: release a=experimental
> Pin-Priority: 1001
>
> Package: puppetmaster
> Pin: release a=experimental
> Pin-Priority: 1001
>
>
> sincerely
>
Hi there,
I was wondering if anyone might know of a repository or other source for
puppet packages for Debian Sarge? (and supporting packages for ruby etc)
Thanks!
--
Please remember that an email is just like a postcard; it is not
confidential nor private nor secure and can be read by many
46 matches
Mail list logo
