[Puppet Users] puppet bug in File selector ?

I tried to conditionally run etckeeper at the end of a puppet run. For that I defined the following class : class os::etckeeper::commit { $cmd = "$operatingsystem" ? { 'debian' => '/usr/sbin/etckeeper', default => '/usr/bin/etckeeper', } exec {"etckeeper commit":

[Puppet Users] puppet and std

I'm running puppet on a Centos 5.8 I'm trying to launch puppet as a daemon and it fail silently. --debug provides no help So I tried to strace it, I'm getting this : 1845 close(0) = 0 1845 open("/dev/null", O_RDONLY) = 0 1845 close(1) =

Re: [Puppet Users] puppet and std

t;strace -s 2048" and see the entire message. > > On Sep 20, 2012, at 8:49 AM, Fabrice Bacchella wrote: >> I'm running puppet on a Centos 5.8 >> >> I'm trying to launch puppet as a daemon and it fail silently. --debug >> provides no help >> >> S

[Puppet Users] puppet --no-client ignore USR1

When puppet is launched as a daemon, a kill -USR trigger a catalog run : Sep 21 12:56:01 XXX puppet-agent[15324]: Caught USR1; calling reload Sep 21 12:56:24 XXX puppet-agent[15324]: Finished catalog run in 12.96 seconds But when launched with --listen --no-client, nothing happens any more : Sep

Re: [Puppet Users] puppet and std

Le 21 sept. 2012 à 17:05, jcbollinger a écrit : > > > On Friday, September 21, 2012 4:35:41 AM UTC-5, Fabrice Bacchella wrote: > I'm starting it by hand. It's the same process (pid 1845) that is nulling > stderr that is writing to it, so it's not related to the

Re: [Puppet Users] Re: puppet --no-client ignore USR1

Le 21 sept. 2012 à 15:35, jcbollinger a écrit : > > > On Friday, September 21, 2012 6:21:04 AM UTC-5, Fabrice Bacchella wrote: > When puppet is launched as a daemon, a kill -USR trigger a catalog run : > > Sep 21 12:56:01 XXX puppet-agent[15324]: Caught USR1; calling relo

Re: [Puppet Users] puppet and std

Le 24 sept. 2012 à 15:58, jcbollinger a écrit : > > > On Saturday, September 22, 2012 3:36:35 AM UTC-5, Fabrice Bacchella wrote: > > Le 21 sept. 2012 à 17:05, jcbollinger a écrit : > >> >> >> On Friday, September 21, 2012 4:35:41 AM UTC-5, Fabrice Ba

Re: [Puppet Users] Re: puppet --no-client ignore USR1

Le 24 sept. 2012 à 15:48, jcbollinger a écrit : > > > I'm not well-versed in MCollective, but I would be surprised if it could not > issue requests asynchronously. Even if it can't natively do so, whatever > node is issuing the mco commands certainly can issue several of them > asynchronou

[Puppet Users] err: Could not retrieve catalog from remote server: Error 400 on SERVER: allocator undefined for Proc

My puppet setup break just a few hours with this message. I didn't upgrade anything, didn't really changed my module and it just broke. The node what where working suddenly stop working. I'm using the official Puppet 3.0 on Scientific Linux (aka Redhat) 6.3 Can some one explain me this magic ?

Re: [Puppet Users] err: Could not retrieve catalog from remote server: Error 400 on SERVER: allocator undefined for Proc

27; [2012-10-22 17:18:50] puppet-master[25373]: /usr/bin/puppet:4 Le 18 oct. 2012 à 17:26, Jeff McCune a écrit : > Could you check the server logs and run the master with --verbose > --debug --trace? > > The information I'm looking for is a backtrace to the file and ljne > numbe

Re: [Puppet Users] Variables and autoloading

> On Mon, Oct 22, 2012 at 12:37 PM, jcbollinger > wrote: > $param1 = 'default1', > $param2 = 'default2' ) { > # declarations > } > > I recommend some variation on > > class mymodule::foo { > $param1 = hiera('foo::param1', 'default1') > $param2 = hiera('foo::param2', 'default2') > #

Re: [Puppet Users] err: Could not retrieve catalog from remote server: Error 400 on SERVER: allocator undefined for Proc

Le 24 oct. 2012 à 17:49, Jeff McCune a écrit : > Are you using stored configs? Could you also paste your puppet.conf with > passwords redacted? Yes I'm using stored config. > > It looks like the YAML library itself is raising the exception. Could you > apply this small patch to one of you

Re: [Puppet Users] err: Could not retrieve catalog from remote server: Error 400 on SERVER: allocator undefined for Proc

Le 25 oct. 2012 à 18:40, Jeff McCune a écrit : > On Thu, Oct 25, 2012 at 4:42 AM, Fabrice Bacchella > wrote: > This patch does something magic. A broken node (with allocator undefined for > Proc) is working when I apply your patch to the puppet master and restart it. > I can

[Puppet Users] tags and template

I'm trying to use tags in templates. I have a resource declared as : define apache::instance($instance_name=$title,$mpm='worker') { tag("declared-apache-$instance_name") ... } this resource is called in the class apache : class apache{ ... apache::instance{$instances: } } and then a

Re: [Puppet Users] err: Could not retrieve catalog from remote server: Error 400 on SERVER: allocator undefined for Proc

Le 27 nov. 2012 à 19:44, Jeff McCune a écrit : > Fabrice mentioned that restarting the puppet master helped with this > issue. Could you please bounce the puppet master and see if that > helps resolve this issue? Restarting the puppet master was not enough. I need to restart it with your pat

[Puppet Users] Stomp connector deprecated ?

I found almost by accident in the release nots for mcollective 2.2.3 : The STOMP adapter will not be maintained past this release series, we now issue deprecation warnigns ... 2012/02/12 Deprecate the stomp connector 19146 And the ticket is: (9 days old, so not from 2012) http://projects.p

Re: [Puppet Users] Shorten require list

Le 12 mars 2013 à 12:24, Gergo Erdosi a écrit : > Hi David, > > Nice, didn't know I can use multiple packages inside Package. Thanks! > > Gergo Erdosi > > On Tue, Mar 12, 2013 at 12:19 PM, David Schmitt wrote: >> On 12.03.2013 11:45, ge...@timble.net wrote: >>> >>> Hi, >>> >>> I have an Ex

Re: [Puppet Users] Shorten require list

Le 12 mars 2013 à 17:46, jcbollinger a écrit : > > This works too : > > package{'needed for exec': > name => $packages, > ensure => present, > } > > exec { "foo": require => Package['needed for exec'] } > > Less object, so a smaller catalog, and faster because your package tool is

[Puppet Users] About Facter via YAML and mcollective

I'm looking at http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/FactsFacterYAML If my understanding is right, just using this class can be dangerous because if puppet is run with a --tags that dooesn't match it, it will not be run. But some fact can be changer any way (fqdn, ssh

Re: [Puppet Users] request for /proc/cpuinfo examples from aix, hpux, kfreebsd, & non-x86 linux

I checked on our few aix, I didn't find the requested /proc/cpuinfo. ~$ facter operatingsystemrelease 6100-02-00- Le 22 oct. 2013 à 04:17, Joshua Hoblitt a écrit : > It's been a week and I haven't gotten a single response. Does anyone > actually use those platforms? :) > > -Josh > > --

[Puppet Users] Puppet 3.4.0 name as an array in package

Puppet 3.4 is out and broke an very usefull undocument feature. Previsiously, one can write : package {'bla': ensure => present, name => ['pkg1', 'pkg2'] } and it will install pkg1 and pkg2. It now says : Parameter name failed on Package['blab']: Name must be a String n

Re: [Puppet Users] Puppet 3.4.0 name as an array in package

Le 20 déc. 2013 à 19:55, Charlie Sharpsteen a écrit : > On Friday, December 20, 2013 10:30:14 AM UTC-8, Fabrice Bacchella wrote: > > > > Puppet 3.4 is out and broke an very usefull undocument feature. > > Previsiously, one can write : > > package {'bl

[Puppet Users] mco package fail with puppet 3.4.0

When I upgrade a node with puppet 3.4.0, puppet-package is broken : ~$ mco package puppet status -I $(facter hostname) -v | [ > ] 0 / 1 The package application failed to run, use -v for full error details: undefined class/module Puppe

Re: [Puppet Users] Hiera + parametrised classes

I defined a custom ruby function called create_type Then if in my hiera, I define : localclasses: - class1: arg1: value arg2: value - class2: arg1: value arg2: value - class3 A simple call to : $localclasses = hiera_array("localclasses", []) create_type("

Re: [Puppet Users] Hiera + parametrised classes

code is written. > > Andrey > > > On 3 January 2014 16:23, Fabrice Bacchella wrote: > I defined a custom ruby function called create_type > > Then if in my hiera, I define : > > localclasses: >- class1: > arg1: value > arg2: value >

Re: [Puppet Users] Hiera + parametrised classes

use cases, this is an interesting > approach. Nice work! > > Cheers, > Felix > > On 01/03/2014 05:23 PM, Fabrice Bacchella wrote: >> localclasses: >> - class1: >> arg1: value >> arg2: value >> - class2: >> arg1: value &g

[Puppet Users] puppet certificate confusion

I'm very confused about puppet certificate and ca management. There is many puppet command to do the work : caLocal Puppet Certificate Authority management. cert Manage certificates and requests certificate Provide access to the CA for certificate manageme

Re: [Puppet Users] puppet certificate confusion

know and use that. But are all the other commands for ? Is there any specification somewhere for the content of the ssl directory ? > > HTH, > Felix > > On 01/13/2014 01:28 PM, Fabrice Bacchella wrote: >> When I look at http://docs.puppetlabs.com/puppet/, or >&

[Puppet Users] template and scope

I wrote the following manifest : === define mysubtype($filepath = $title, $source) { file {"$filepath": content => template("$source") } } define mytype($param2) { mysubtype{"/tmp/parsed1": source => "/tmp/parsed.erb" } file{"/tmp/par

[Puppet Users] puppetdb and client certificate

I'm trying to authenticate a puppetdb on a postgresql server using a client certificate. I managed to set up SSL on server side without any problem but http://docs.puppetlabs.com/puppetdb/2.1/postgres_ssl.html says : Note: At this point the documentation below only covers server-based SSL, clie

Re: [Puppet Users] puppetdb and client certificate

something I'm not across sorry, you'll have to > experiment on your own :-). Respond if you need more help, or if you > make more progress. > > ken. > > On Wed, Jul 16, 2014 at 3:40 PM, Fabrice Bacchella > wrote: >> I'm trying to authenticate a puppetdb

Re: [Puppet Users] puppetdb and client certificate

> https://github.com/puppetlabs/puppetdb/blob/master/documentation/postgres_ssl.markdown > > ken. > > On Thu, Jul 17, 2014 at 12:03 PM, Fabrice Bacchella > wrote: >> I got it ! >> >> I dit it using the java way (with a standard jks). >> >> F

[Puppet Users] puppetdb export before migration

I ran an puppetdb export yesterday. It ran fine. It was a puppetdb 2.0 Now, after an export to puppetdb 2.1, I got some strange exception. puppet master is working fine, I didn't see anything special in the release notes. puppetmaster is running fine. Did I miss something ? $ puppetdb export

Re: [Puppet Users] puppetdb export before migration

y fixed it in source, but not > shipped a fix yet. We were holding off for someone complaining loud > enough or just shipping it with 2.2.0 (which should be out in a few > weeks or so). > > ken. > > On Fri, Jul 18, 2014 at 5:42 PM, Fabrice Bacchella > wrote: >> I r

[Puppet Users] hashes not hashes ?

I'm trying to send an hash to a template. I'm calling a type with : supervisord::program{'hadoop.namenode': ... environment => { JAVA_HOME => "$javahome", HADOOP_HOME => "/data/hadoop/distrib", HADOOP_CONF_DIR => "/data/hadoop/config",

Re: [Puppet Users] hashes not hashes ?

Le 3 sept. 2014 à 20:02, jcbollinger a écrit : > > > For bare words to be interpreted as strings, they must begin with a lowercase > letter. There are other restrictions, too. Yes, it's a bit weird -- in > fact, I wasn't mindful of the initial letter rule in this context until I > looked i

Re: [Puppet Users] puppetlabs-release not signed

And did you update the yum database after that ? I'm getting strange results. > Le 20 avr. 2016 à 16:55, Melissa Stone a écrit : > > Thanks for reporting this, everyone. I've fixed the packages on > yum.puppetlabs.com , and I'll start investigating > apt.puppetlabs.

Re: [Puppet Users] [ann] Action Required: New Puppet Inc. Public Key

In puppetlabs-release-pc1-1.1.0-1.el7.noarch there is a strange key : # rpm -qil puppetlabs-release-pc1-1.1.0-1.el7.noarch ... /etc/pki/rpm-gpg/RPM-GPG-KEY-nightly-puppetlabs And the same key is in puppetlabs-release: # rpm -qilp .../puppetlabs-release-22.0-2.noarch.rpm /etc/pki/rpm-gpg/RPM-

[Puppet Users] puppet does not like ~ in file name

I need a file called /etc/cron.hourly/~cronalive. I don't like the ~ but don't have real choice here. So I defined the following resource: file{'/etc/cron.hourly/~cronalive': } But if fails with: Error: Could not set 'file' on ensure: user cronalive20161110-32243-1wx31rr d

Re: [Puppet Users] puppet does not like ~ in file name

ls...@gmail.com <mailto:rnels...@gmail.com> > On Thu, Nov 10, 2016 at 9:16 AM, Fabrice Bacchella > mailto:fabrice.bacche...@orange.fr>> wrote: > I need a file called /etc/cron.hourly/~cronalive. I don't like the ~ but > don't have real choice here. > > So I defin

Re: [Puppet Users] puppet does not like ~ in file name

> Le 10 nov. 2016 à 18:22, Rob Nelson a écrit : > > That said, who decided a tilde to start a file name was good for anything but > a temp file??? I understand you have no choice as a user, but someone > somewhere, somewhen, chose it :( because in the sort algorithm from glob, ~ is one of the

Re: [Puppet Users] puppet does not like ~ in file name

Thanks ! > Le 10 nov. 2016 à 23:47, Christopher Wood a > écrit : > > I reproduced this with 4.8.0 and filed a ticket. > > https://tickets.puppetlabs.com/browse/PUP-6914 > > Seems like it's a ruby thing? > > https://ruby-doc.org/core-2.1.8/File.html#method-c-expand_path > > https://github.co

Re: [Puppet Users] Over-engineering rant

> Le 8 janv. 2017 à 03:00, Jakov Sosic a écrit : > > Hi guys, > > this is maybe a topic better suited for -dev list, but, well, here goes. > > I've been using puppet heavily for 3-4 years, up until version 4, now I'm > mostly maintaining my own open source modules. > > What stumped me lately

Re: [Puppet Users] Over-engineering rant

> Le 8 janv. 2017 à 14:54, Jakov Sosic a écrit : > > On 01/08/2017 11:04 AM, Fabrice Bacchella wrote: > >> And that's for something that for a given environment > > never change, have no options. So dropping a standard > > file that is hand made once in a

[Puppet Users] puppet certificate

I'm playing with the "puppet certificate" command. But when I run "puppet certificate --ca-location remote list" I see in the log: 10.83.16.17 - - [05/Apr/2017:15:52:46 +0200] "GET /puppet-ca/v1/certificate_statuss/*?environment=production&for=certificate_request HTTP/1.1" 404 9 "-" "Puppet/4.

Re: [Puppet Users] puppet certificate

int of the command. > Le 5 avr. 2017 à 15:58, Fabrice Bacchella a > écrit : > > I'm playing with the "puppet certificate" command. > > But when I run "puppet certificate --ca-location remote list" > > I see in the log: > > 1

Re: [Puppet Users] puppet certificate

> Le 10 avr. 2017 à 19:13, Martin Alfke a écrit : > > Hi Fabrice, > >> On 05 Apr 2017, at 17:02, Fabrice Bacchella >> wrote: >> >> One more problem, since puppet certificate --ca-location remote destroy does >> nothing, what is the whole point

[Puppet Users] bug with systemd's mask

I'm trying to stop rpc-svcgssd.service on some servers. But I thing I've hit a bug. This service is marked as static: systemctl status rpc-svcgssd.service rpc-svcgssd.service - RPC security service for NFS server Loaded: loaded (/usr/lib/systemd/system/rpc-svcgssd.service; static; vendor p

Re: [Puppet Users] revoke / delete node certificate from puppet ca remotely?

It might be linked to that: https://tickets.puppetlabs.com/browse/PUP-7452 > Le 23 août 2017 à 20:16, Jason McMahan a écrit : > > Thank you Martin, > Still running into problems. > > I must not be using correct certificate most likely. > > App

[Puppet Users] yumrepo still not working ?

I tried to create a yumrepo for elasticsearch, and like many years ago, puppet seems to be unable to create it in the requested files: yumrepo {'elasticsearch-5.x': name => 'elasticsearch-5.x', baseurl=> 'https://artifacts.elastic.co/packages/5.x/yum', mirro

[Puppet Users] puppet augeas fails with sudoers in RHEL 7.4

I've upgraded a test machin with Centos 7.4 CR When I run puppet on it, configuring /etc/sudoers with augeas, I'm getting: Warning: Augeas[sudoers include](provider=augeas): Loading failed for one or more files, see debug for /augeas//error output augtool ls /augeas//error says : pos = 2308 lin

Re: [Puppet Users] yumrepo still not working ?

Yes. > Le 25 août 2017 à 20:10, Rob Nelson a écrit : > > The puppet log shows the resource name only. Did you check for the presence > of the file at all? > > On Fri, Aug 25, 2017 at 9:20 AM Fabrice Bacchella > mailto:fabrice.bacche...@orange.fr>> wrote: > I

Re: [Puppet Users] yumrepo still not working ?

Open since june 2014... > Le 26 août 2017 à 16:37, Tomáš Krasničan a écrit : > > it seems to be known bug https://tickets.puppetlabs.com/browse/PUP-2782 > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group

Re: [Puppet Users] puppet augeas fails with sudoers in RHEL 7.4

e the stock lens > in /usr/share/augeas/lenses/dist/sudoers.aug with the updated lens > <https://github.com/hercules-team/augeas/blob/master/lenses/sudoers.aug>, and > things should just work. > > David > > On Friday, August 25, 2017 at 9:43:13 AM UTC-7, Fabrice Bacchell

Re: [Puppet Users] puppet augeas fails with sudoers in RHEL 7.4

de to RHEL7.4. Any hop to get it corrected soon in the puppet agent ? Or should I try to implement a workaround, because at the same time, there is CVE-2017-1000253 that requires an upgrade to 7.4. > Le 27 août 2017 à 14:17, Fabrice Bacchella a > écrit : > > Thanks ! > >&g

[Puppet Users] multiple puppetdb, single postgres

Is there any risk running multiple puppetdb reading or perhaps writing to a single postgres database ? For my understanding, all puppetdb's data are stored in pg, so there is no coherency problems, but too much caching on pdb's side might break that assumption. There is also the schema consist

[Puppet Users] puppet facts and mcollective are incompatible

I used to fill mcollective yaml facts with a simple facter -p > foo.yaml. But with facter 3, -p is gone, one should use 'puppet facts --render-as yaml' instead. So far so good, but mcollective can't use this command output : yaml_facts.rb:31:in `rescue in block in load_facts_from_source' Failed

Re: [Puppet Users] puppet facts and mcollective are incompatible

And I can use puppet to generate it, I don't run puppet with cron or as a daemon. > Le 20 juil. 2015 à 23:12, Fabrice Bacchella a > écrit : > > I used to fill mcollective yaml facts with a simple facter -p > foo.yaml. > > But with facter 3, -p is gone, one should

Re: [Puppet Users] puppet facts and mcollective are incompatible

> > For this (and a few other reasons), the breaking change of removing the -p > switch in Facter 3.0.0 is being reverted in 3.0.2, which will be released > very soon. > When do you expect it to be released ? I've found many bugs with facter 3 (and I've been using it only for a few days),

[Puppet Users] puppet and mcollective plugins, broken on CentOS 6

I want to both install puppet 4 and some mcollective plugins on a CentOS 6 As the the mcollective plugins are not in the PC1 repository, I need the products repository. But then : yum install https://yum.puppetlabs.com/el/6/products/x86_64/puppetlabs-release-6-11.noarch.rpm https://yum.puppe

[Puppet Users] facter productname failing in CentOS 5

> There have been a number of regression fixes including fixes to command > execution, inclusion of the -p option, porting the xendomains fact, OS fact > fixes, and the fqdn fact reporting incorrectly on some systems. > > If there's an issue you're running into that you don't see being addresse

[Puppet Users] facter 3 and linux disagree about interfaces

On a linux, if I enumerate interfaces using standards tools I get : ~# ip link list 1: lo: mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: mtu 1500 qdisc mq master bond0 state UP qlen 1000 link/ether 00:1c:c4:74:83:80 brd ff:ff:ff:ff:

Re: [Puppet Users] facter 3 and linux disagree about interfaces

> I agree that Facter could do a better job merging the secondary "interface" > into the primary one here. It shares the networking fact code with a few > other platforms (mainly OSX and the BSDs) and it currently doesn't do any > specific logic for Linux to merge bonded interfaces together. >

Re: [Puppet Users] facter 3 and linux disagree about interfaces

> Le 21 juil. 2015 à 20:33, Peter Huene a écrit : > > Thus there would be no "eth0:1" in the interfaces list; it would just show up > as the first element in the secondary array. e.g. eth0:1 becomes > eth0.secondary.0, eth0:2 becomes eth0.secondary.1, etc. > > Thoughts on this approach? It

Re: [Puppet Users] facter 3 and linux disagree about interfaces

> > > If you have access to Facter 2.x on this same system, I'd be curious to see > if it would output the secondary interface / address information. If not, I > think we could consider Facter's 3.x behavior to be a bug and fix it by > moving the secondary interfaces to where they belong. On

Re: [Puppet Users] Advice on Puppet update to 4

> Le 24 juil. 2015 à 14:10, Dirk Heinrichs a > écrit : > > Am 24.07.2015 um 12:59 schrieb Felix Frank: > >> If you need a good ENC, look at Foreman. If you need reporting, look at >> puppetboard or Puppet Explorer. > > Is any of those ready for Puppet 4? At least Foreman 1.9 (current developm

Re: [Puppet Users] Advice on Puppet update to 4

> Le 24 juil. 2015 à 14:23, Fabrice Bacchella a > écrit : > > >> Le 24 juil. 2015 à 14:10, Dirk Heinrichs a >> écrit : >> >> Am 24.07.2015 um 12:59 schrieb Felix Frank: >> >>> If you need a good ENC, look at Foreman. If you need re

[Puppet Users] facts failing (again) on RHEL5

I open another bug for failed facts on rhel5 and brothers : https://tickets.puppetlabs.com/browse/FACT-1152 Is that OS version still supported by puppet labs ? It seems there is no facts QA on it. -- You received this message because you are s

[Puppet Users] bug in RHEL's latest libblkid and facter

A bug (?) in the latest libblkid for RHEL 7 broke facter partitions For example, on two servers, with different version of this package: Before (libblkid-2.23.2-22.el7_1.x86_64.): ~# facter partitions { /dev/sda2 => { filesystem => "xfs", label => "/", mount => "/", partuuid =>

Re: [Puppet Users] how were your puppet 3->4 upgrades?

> Le 24 août 2015 à 21:59, Christopher Wood a > écrit : > > I am not seeing a large amount of blog entries complaining about this > upgrade, how has that gone for you? Is there anything you found particularly > painful? Would you have done anything different in retrospect? > > I'm staring do

Re: [Puppet Users] how were your puppet 3->4 upgrades?

> Le 26 août 2015 à 11:30, Stefan Heijmans a écrit : > > > On Wednesday, August 26, 2015 at 10:16:59 AM UTC+2, Fabrice Bacchella wrote: > > > Le 24 août 2015 à 21:59, Christopher Wood > > a écrit : > > > My biggest problem: there isn't any workin

[Puppet Users] puppet agent 1.2.5 ?

It's marked as unreleased : https://tickets.puppetlabs.com/browse/PUP/fixforversion/14525/?selectedTab=com.atlassian.jira.plugins.jira-development-integration-plugin:release-report-tabpanel

Re: [Puppet Users] puppet agent 1.2.5 ?

n Thu, Oct 1, 2015 at 1:28 AM, Fabrice Bacchella > mailto:fabrice.bacche...@orange.fr>> wrote: > It's marked as unreleased : > https://tickets.puppetlabs.com/browse/PUP/fixforversion/14525/?selectedTab=com.atlassian.jira.plugins.jira-development-integration-pl

Re: [Puppet Users] puppet agent 1.2.5 ?

> Le 12 oct. 2015 à 18:01, Michael Stahnke a écrit : > With transparency comes the ability to see things that are not perfect. We > had a large conference last week where a very large portion of our employee > base was in attendance. We shipped the bits because it fixed a bug that some > peop

Re: [Puppet Users] puppet agent 1.2.5 ?

> Le 12 oct. 2015 à 19:12, Michael Stahnke a écrit : > > > > On Mon, Oct 12, 2015 at 9:51 AM, Fabrice Bacchella > wrote: > > > Le 12 oct. 2015 à 18:01, Michael Stahnke a écrit : > > > With transparency comes the ability to see things that are not per

[Puppet Users] upgrading puppedb, wrong schema number

I'm running puppetdb on ScientificLinux 6.7 (a RHEL clone). I upgraded from puppetdb-3.1.0 to puppetdb-3.2.2, but know I'm getting in the log : 2016-02-24 11:22:58,585 ERROR [p.t.internal] Error during service start!!! java.lang.IllegalStateException: Your PuppetDB database contains a schema mi

Re: [Puppet Users] upgrading puppedb, wrong schema number

abs/puppetdb/blob/3.2.2/src/puppetlabs/puppetdb/scf/migrate.clj#L1534 > > So ... why not just use 3.2.3 anyway? Since it looks like the > migration has taken place, and its the latest release. > > ken. > > On Wed, Feb 24, 2016 at 10:40 AM, Fabrice Bacchella > wrote: >&