On Tue, Jun 3, 2014 at 2:40 PM, Felix Frank <felix.fr...@alumni.tu-berlin.de > wrote:
> On 06/03/2014 12:18 PM, Andrei-Florian Staicu wrote: > > > > More bad news: facter-2.0.1-1.el6 on both of them. > > Ummm... did I already say thanks for your help :) > > Well that would have been premature because I'm about at my wit's end. > > There is a chance you are hitting a latent bug with 3.6. Are you using > parser=future? If so, try without it (and report the issue please!) > > You said that you had the same problem during another update - was that > to 3.6 as well? No, no experimental features in use. The other update I tried was from 3.2.4 to 3.3.0, detailed here: https://groups.google.com/forum/#!msg/puppet-users/ujRKmWtfHUA/c0empDpcVjcJ Hmm... looking at the ticket opened from that email (22614), I'm seeing this on my puppet server: [root@SERVER ~]# gem list puppet *** LOCAL GEMS *** puppet (3.1.1) puppet-cleaner (0.3.1, 0.2.0, 0.1.1) puppet-lint (0.3.2) However, I don't understand if that has any effect on the puppet master, or who/what installed it. As I said, puppet was happily running at version 3.2.4, even with this gem installed. [root@SERVER~]# rpm -qa | grep ruby | grep puppet [root@SERVER~]# -- 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 this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CANK4U2o5FROzv-auyG2VY1fBFZ5QrZ7ECtrs5%3DQH3KtRNQ4FgQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
