[Puppet Users] Re: Puppet server failing on invalid UTF-8 facts

[Federico Agnelli]

Hi Peter,

attached you can find the output of dmidecode and another file with the 
output of the cat command.

Thanks,
Federico


Il giorno lunedì 20 luglio 2015 22:24:18 UTC+2, Peter Huene ha scritto:
>
>
> On Monday, July 20, 2015 at 1:23:20 PM UTC-7, Peter Huene wrote:
>>
>> On Monday, July 20, 2015 at 1:16:07 PM UTC-7, Federico Agnelli wrote:
>>>
>>> Hi Giorgio,
>>>
>>> I have the same problem with a puppet client on Intel NUC5i5RYH.
>>> All other clients (on different hardware) with the same puppet version 
>>> work fine.
>>>
>>> My puppet version for both agent and server is 4.2.0. Version 4.1.0 was 
>>> ok.
>>>
>>
>> It looks like Facter is expecting the contents of those files to be 
>> UTF-8, which may not be the correct thing to do.  Could you install/run the 
>> dmiencode utility and paste the output?  Also, cat the same files Giorgio 
>> did and attach as a file (the characters are coming through as invalid 
>> characters in Google Groups).  Thanks!
>>
>
> Correction: the utility is *dmidecode*.
>  
>
>>  
>>
>>>
>>> Did you find a fix?
>>>
>>> Thanks,
>>> Federico
>>>
>>

-- 
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/164d75be-37df-47aa-a341-a093cda95cdb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
# dmidecode 2.12
SMBIOS 2.8 present.
86 structures occupying 3951 bytes.
Table at 0x000EC7B0.

Handle 0x, DMI type 0, 24 bytes
BIOS Information
Vendor: Intel Corporation
Version: RYBDWi35.86A.0137.2015.0107.1700
Release Date: 01/07/2015
Address: 0xF
Runtime Size: 64 kB
ROM Size: 6528 kB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 5.6

Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: .
Product Name: .
Version: .
Serial Number: .
UUID: D1EEA700-7277-11E3-A8F2-B8AEED753A8D
Wake-up Type: Power Switch
SKU Number: .
Family: .

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: Intel Corporation
Product Name: NUC5i5RYB
Version: H40999-502
Serial Number: GERY51400SRF
Asset Tag: .
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: To be filled by O.E.M.
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0

Handle 0x0003, DMI type 3, 25 bytes
Chassis Information
Manufacturer: .
Type: Desktop
Lock: Not Present
Version: .
Serial Number: .
Asset Tag: .
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
OEM Information: 0x
Height: Unspecified
Number Of Power Cords: 1
Contained Elements: 1
 (0)
SKU Number: To be filled by O.E.M.

Handle 0x0004, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1A1
Internal Connector Type: None
External Reference Designator: PS2Mouse
External Connector Type: PS/2
Port Type: Mouse Port

Handle 0x0005, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1A1
Internal Connector Type: None
External Reference Designator: Keyboard
External Connector Type: PS/2
Port Type: Keyboard Port

Handle 0x0006, DMI type 8, 9 bytes
Port Connector Information
Internal Referen

[Puppet Users] Re: puppet failover

[Malla Reddy Alakonda]

Hello Rene, 


Can you help me in setting up High availability for my puppet master, can 
you share any doc that will help me   

-- 
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/df0d9cf8-93c8-4ce7-9584-196c042bbcef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Anyone really using Postgres for a Hiera backend?

[Tom De Vylder]

Puppet-Community [1] would be a prime example to take over the maintainership.

[1] https://github.com/puppet-community/ 

Tom

> On 13 Jul 2015, at 15:45, Erik Dalén  wrote:
> 
> Yeah, I'm not really using puppet server (yet at least) or the postgres hiera 
> backend. So if someone else wants to take over maintainership of it I can 
> transfer the repo ownership.
> 
> On Tue, 19 May 2015 at 18:51 Tony Thayer  > wrote:
> Actually, I just realized I was using my own fork of the original: 
> https://github.com/tthayer/hiera-psql 
> 
> I'm not using it actively anymore and I doubt my previous employer is still 
> using it either. There is an open issue stating that it doesn't work with the 
> new puppetserver, too: https://github.com/dalen/hiera-psql/issues/7 
> 
> 
> On Wednesday, May 13, 2015 at 9:45:55 AM UTC-7, leam hall wrote:
> Just wondering. I found some options but don't see any under current 
> development. 
> 
> Leam
> 
> 
> -- 
> Mind on a Mission 
> 
> -- 
> 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/6a3391ec-22d7-4f43-b7f0-7036ee722869%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .
> 
> -- 
> 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/CAAAzDLd-WGbX3iceb99NJF_b%2BgCjNFe8oHjqE%3DH8ZXW--K%3D1FA%40mail.gmail.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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/0D52B176-0638-4939-A8A2-ED66EC9FB222%40penumbra.be.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Puppet server failing on invalid UTF-8 facts

[Peter Huene]

On Wed, Jul 22, 2015 at 3:01 AM, Federico Agnelli 
wrote:

> Hi Peter,
>
> attached you can find the output of dmidecode and another file with the
> output of the cat command.
>

It looks like, for whatever reason, those values were set by the
manufacturer to 0xFF 0xFF 0xFF ...

dmidecode outputs a series of dots to represent these invalid characters.
I've opened https://tickets.puppetlabs.com/browse/FACT-1140 to track this
issue so that Facter fixes it in a similar way.

I should have a fix into the stable branch soon, but unfortunately it won't
make it into the about-to-be-released Facter 3.0.2.

Thanks!


>
> Thanks,
> Federico
>
>
> Il giorno lunedì 20 luglio 2015 22:24:18 UTC+2, Peter Huene ha scritto:
>>
>>
>> On Monday, July 20, 2015 at 1:23:20 PM UTC-7, Peter Huene wrote:
>>>
>>> On Monday, July 20, 2015 at 1:16:07 PM UTC-7, Federico Agnelli wrote:

 Hi Giorgio,

 I have the same problem with a puppet client on Intel NUC5i5RYH.
 All other clients (on different hardware) with the same puppet version
 work fine.

 My puppet version for both agent and server is 4.2.0. Version 4.1.0 was
 ok.

>>>
>>> It looks like Facter is expecting the contents of those files to be
>>> UTF-8, which may not be the correct thing to do.  Could you install/run the
>>> dmiencode utility and paste the output?  Also, cat the same files Giorgio
>>> did and attach as a file (the characters are coming through as invalid
>>> characters in Google Groups).  Thanks!
>>>
>>
>> Correction: the utility is *dmidecode*.
>>
>>
>>>
>>>

 Did you find a fix?

 Thanks,
 Federico

>>>  --
> 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/164d75be-37df-47aa-a341-a093cda95cdb%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Join us at **PuppetConf 2015, October 5-9 in Portland, OR - *www.

2015.puppetconf.com


*Register early to save 40%!*

-- 
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/CACZQQfM9X-iWwZHSDb9g1vWqs5%3DZf%3Dm5jqtigHQj5qe3B_mY1Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: How can I install ruby193 gems on CentOS 6 with softwarecollections (SCL)?

[Ilja Bobkevic]

I guess you're left with doing exec. Something like this should work:

exec { 'ruby193_scl_install_blah':

  command => "scl enable ruby193 'gem install --bindir /usr/bin --no-rdoc 
--no-ri blah'",
  path=> ['/bin','/usr/bin'],
  unless  => "scl enable ruby193 'gem list'| grep -qs blah"
}


There might be already defined type for it out there (e.g. 
https://forge.puppetlabs.com/treydock/scl)

// Ilja

Den tisdag 14 juli 2015 kl. 20:56:14 UTC+2 skrev Stefan Lasiewski:
>
> From the silence, I'm going to guess that the gem provider cannot install 
> gems from Ruby installed from the Software Collections.
>
> I did find a somewhat-related bug: '[PUP-3613] Add a parameter to the 
> exec resource to support running commands in software collections without 
> always using "scl enable"' 
> 
>
> -= Stefan
>
> On Tuesday, July 7, 2015 at 12:22:37 PM UTC-7, Stefan Lasiewski wrote:
>>
>> Hello,
>>
>> I have a CentOS 6 system running Puppet 3.8, and I use SCL (Software 
>> Collections ) to install some 
>> packages like http24 and ruby193.
>>
>> I am having trouble using Puppet's gem provider to install gems with 
>> ruby193.
>>
>> I have a manifest like this:
>>
>>
>>   package { ['ruby193', 'ruby193-ruby-devel', 'ruby193-rubygem-bundler']: 
>>
>> ensure  => present, 
>>  
>> require => Class['::company_yum::softwarecollections'], 
>>
>>   } 
>>  
>>   # Install Compass for webapp   
>>   
>>   package { ['sass', 'compass']: 
>> 
>> ensure   => 'installed', 
>> 
>> provider => 'gem',   
>> 
>> require  => Package['ruby193-ruby-devel'],   
>> 
>>   }
>>
>>  
>> But it seems that Puppet does not know about the location of the 
>> ruby193-ruby-devel headers, and I would need to use the SCL version of 
>> ruby193 gem, not /usr/bin/gem.
>>
>>
>> Notice: /Stage[main]/Class_webhost::Silverstripe/Package[ruby193-ruby-
>> devel]/ensure: created
>>
>> Error: Execution of '/usr/bin/gem install --no-rdoc --no-ri compass' 
>> returned 1: ERROR:  Error installing compass:
>>
>> ERROR: Failed to build gem native extension.
>>
>>
>> /usr/bin/ruby extconf.rb
>>
>> mkmf.rb can't find header files for ruby at /usr/lib/ruby/ruby.h
>>
>>
>> Gem files will remain installed in /usr/lib/ruby/gems/1.8/gems/ffi-1.9.10 
>> for inspection.
>>
>> Results logged to 
>> /usr/lib/ruby/gems/1.8/gems/ffi-1.9.10/ext/ffi_c/gem_make.out
>>
>> Building native extensions.  This could take a while...
>>
>> Error: /Stage[main]/Class_webhost::Silverstripe/Package[compass]/ensure: 
>> change from absent to present failed: Execution of '/usr/bin/gem install 
>> --no-rdoc --no-ri compass' returned 1: ERROR:  Error installing compass:
>>
>> ERROR: Failed to build gem native extension.
>>
>>
>> /usr/bin/ruby extconf.rb
>>
>> mkmf.rb can't find header files for ruby at /usr/lib/ruby/ruby.h
>>
>>
>>
>> Gem files will remain installed in /usr/lib/ruby/gems/1.8/gems/ffi-1.9.10 
>> for inspection.
>>
>> Results logged to /usr/lib/ruby/gems/1.8/gems/ffi-1.9.10/ext/ffi_c/
>> gem_make.out
>>
>> Building native extensions.  This could take a while...
>>
>> ...
>>
>> Notice: Finished catalog run in 50.02 seconds
>>
>>
>> The ruby193-ruby-devel headers live under /opt/rh/ruby193/ :
>>
>> [root@webhost ~]# find /opt/rh/ruby193/root/ -name ruby.h
>> /opt/rh/ruby193/root/usr/include/ruby/ruby.h
>> /opt/rh/ruby193/root/usr/include/ruby.h
>> [root@webhost ~]# 
>>
>>
>>
>> How can I use the Puppet gem provider to work with ruby193 installed by 
>> SCL?
>>
>> Thanks,
>>
>> -= Stefan
>>
>

-- 
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/f367cfaf-a38b-4ea2-8775-954ca23b65fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] is there any way to get rspec to tell you the contents of the catalog on a failure?

[Hunter Haugen]

When I get a vague failure, such as "expect File[/whatever] to be in the
catalog" and don't know why it's not, I put a pry in the `it` block before
the test failure and re-run. It will drop you into a pry prompt and you can
inspect the catalog manually by running `catalogue` and look for anything
that looks weird.

There is no great way to dump the catalog on failure automatically though.

On Mon, Jul 20, 2015 at 5:31 PM Johnson Earls 
wrote:

> Another rspec question:
>
> Is there any way to get rspec to tell you, when a test fails, what the
> contents of the catalog was, at a high level at least, that generated the
> failure?
>
> I've got a code block that looks right to me, and an rspec test that looks
> right to me.  the test is failing and I have no idea why.  Maybe seeing the
> contents of the catalog would help me figure out what's going on.
>
> Thanks in advance,
> - Johnson
>
> --
> 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/f60d5256-2333-4953-8228-5da675f8679d%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAJaQvGBdyx%2BUNhLAzc0878V5bq--5N06ZAUm6PEzoUBhXsDi_Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Puppet server failing on invalid UTF-8 facts

[Federico Agnelli]

Thanks to you Peter!
Bye,
Fede

Il giorno mercoledì 22 luglio 2015 17:26:55 UTC+2, Peter Huene ha scritto:
>
> On Wed, Jul 22, 2015 at 3:01 AM, Federico Agnelli  > wrote:
>
>> Hi Peter,
>>
>> attached you can find the output of dmidecode and another file with the 
>> output of the cat command.
>>
>
> It looks like, for whatever reason, those values were set by the 
> manufacturer to 0xFF 0xFF 0xFF ...
>
> dmidecode outputs a series of dots to represent these invalid characters.  
> I've opened https://tickets.puppetlabs.com/browse/FACT-1140 to track this 
> issue so that Facter fixes it in a similar way.
>
> I should have a fix into the stable branch soon, but unfortunately it 
> won't make it into the about-to-be-released Facter 3.0.2.
>
> Thanks!
>  
>
>>
>> Thanks,
>> Federico
>>
>>
>> Il giorno lunedì 20 luglio 2015 22:24:18 UTC+2, Peter Huene ha scritto:
>>>
>>>
>>> On Monday, July 20, 2015 at 1:23:20 PM UTC-7, Peter Huene wrote:

 On Monday, July 20, 2015 at 1:16:07 PM UTC-7, Federico Agnelli wrote:
>
> Hi Giorgio,
>
> I have the same problem with a puppet client on Intel NUC5i5RYH.
> All other clients (on different hardware) with the same puppet version 
> work fine.
>
> My puppet version for both agent and server is 4.2.0. Version 4.1.0 
> was ok.
>

 It looks like Facter is expecting the contents of those files to be 
 UTF-8, which may not be the correct thing to do.  Could you install/run 
 the 
 dmiencode utility and paste the output?  Also, cat the same files Giorgio 
 did and attach as a file (the characters are coming through as invalid 
 characters in Google Groups).  Thanks!

>>>
>>> Correction: the utility is *dmidecode*.
>>>  
>>>
  

>
> Did you find a fix?
>
> Thanks,
> Federico
>
  -- 
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/164d75be-37df-47aa-a341-a093cda95cdb%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> *Join us at **PuppetConf 2015, October 5-9 in Portland, OR - *www. 
> 
> 2015.puppetconf.com 
> 
>  
> *Register early to save 40%!*
>  

-- 
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/22bee3de-13fe-4bdd-98f7-72fb409b24c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Possibly bug in Puppetlabs/Registry module

[Rob Reynolds]

Given we've discovered a bug in 3.7.5 and have recalled it for an incorrect
version of Ruby[1], it's possible this issue was limited to just Puppet
3.7.5. Registry could be one thing that would likely have a large effect
given the amount of changes we put in to make registry work again on Ruby
2.1.x.

[1]
https://groups.google.com/forum/#!msg/puppet-dev/VtqadVFJKLM/e28O_so11fMJ

On Fri, May 1, 2015 at 2:58 PM, Rob Reynolds  wrote:

>
>
> On Fri, May 1, 2015 at 12:59 PM, Mark Wolek  wrote:
>
>> C:\Users\Administrator>puppet apply --version
>> 3.7.5
>>
>> C:/ProgramData/PuppetLabs/puppet/etc/modules
>> └─┬ puppetlabs-registry (v1.1.0)
>>   └── puppetlabs-stdlib (v4.6.0)
>>
>>
>> No puppetmaster server is involved.
>>
>> Thanks!
>>
>
> It's possible we may have a bug. I created MODULES-2005[1] to follow up.
> Thanks!
>
> [1] https://tickets.puppetlabs.com/browse/MODULES-2005
>
>
>>
>>
>> On Tuesday, April 28, 2015 at 12:38:23 PM UTC-5, Rob Reynolds wrote:
>>>
>>>
>>>
>>> On Mon, Apr 27, 2015 at 11:28 AM, Mark Wolek  wrote:
>>>
 Thanks John! It appears to open a ticket I do so on the GitHub site by
 logging in, is this correct?

 The reason for suspecting the lack of string termination is due to what
 we see in the Registry GUI, which is random characters and words after the
 string, then you hit Refresh on the page, the random characters and strings
 change.

 It does seem specific to a hyphen being in the string, but I will test
 again to be certain.

>>>
>>> Hi Mark,
>>>  What version of the registry module are you using? What version of the
>>> Puppet agent are you on? The issues you stated above were known issues that
>>> we believe we have corrected in newer versions of Puppet.
>>>
>>> We also vendor Ruby into the Puppet Installer for Windows (and we've
>>> done this almost since the first release supporting Windows), so we can
>>> usually rule out Ruby compatibilities in some respects, but not always with
>>> modules.
>>>
>>>
>>>

 Thanks!
 Mark


 On Monday, April 27, 2015 at 9:06:31 AM UTC-5, jcbollinger wrote:
>
>
>
> On Friday, April 24, 2015 at 1:52:17 PM UTC-5, Mark Wolek wrote:
>>
>> We believe this has something to do with puppet inserting strings
>> that are not null terminated, but I've had no luck at all adding
>> termination to the string...  have tried single and double quoting it.  
>> \x0
>> \00 \000 so many types of termination tried but nothing seems to do the
>> trick...
>>
>>
>
> Having examined the source of the latest version of this module, I can
> tell you that Puppet relies on registry support from the Ruby standard
> library to handle the low-level details of registry manipulation.  As far
> as I can tell, Puppet's own code does not do any parsing or processing of
> registry values that would be sensitive to a hyphen character in the
> string.  Were you speculating about that being related to the problem, or
> do you in fact see different results when the array elements do not 
> contain
> hyphens?
>
> I am anyway inclined to think that the problem is NOT wrong string
> termination, at least of the values you specify in your manifest, because
> Get-ItemProperty is giving you an array value in which the first element
> appears completely correct.  The problem could, however, be related to
> incorrectly specifying the size of the *array* to Windows, or failing
> to provide an array terminator (I'm not much of a registry tinkerer, so 
> I'm
> not sure which would actually be applicable).
>
> I encourage you to file a ticket against the module.  I am uncertain
> whether the issue is there or in the Ruby standard library because the 
> docs
> of the relevant library class suffer from the vagueness typical of Ruby
> docs, but the module maintainers are best positioned to evaluate that.
> Even if the problem turns out to be in the underlying Ruby library, it 
> does
> not appear that the module's tests include any that exercise setting or
> retrieving values of type "array", and a ticket against the module
> *should* result at least in addition of such tests.
>
>
> John
>
>  --
 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...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/c0503ad5-5d72-48ed-868f-522491f93e78%40googlegroups.com
 
 .

 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>>
>>> --
>>> Rob Reynolds
>>> Developer, 

[Puppet Users] Module Autoload issues

[Matthew Ceroni]

I am attempting to use the following module

-- 
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/CA%2BNsY5j%3DpNdcA%3D9T_avrEGOC_bogEmH%3D58HUUnrCJ%3Dn9mr%2B%2BoA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Kevin Corcoran]

On Tue, Jul 21, 2015 at 9:33 AM, Felix Frank <
felix.fr...@alumni.tu-berlin.de> wrote:

>  On 07/21/2015 04:14 PM, jcbollinger wrote:
>
>
>> 2)
>> I read in the changelog that the older clients should work with the
>> backward compatibility, but is it worth even trying? Or should I just push
>> out the updated puppet client wherever I can before adding the server into
>> my new build? (not hard to do in my environment)
>>
>
>
> It's worth trying if upgrading the clients when you upgrade the master
> would present a challenge.  Even if you plan to update everything in one
> fell swoop, it may be to your advantage to rely on the newer master serving
> older clients at least for the duration of the upgrade.
>
>
> Hi,
>
> I don't think that Puppet 3 agents can work with the Puppet 4 master.
> There were incompatible changes to the catalog format.
>
> A Puppet 4 upgrade needs to encompass your whole infrastructure. As such,
> I'd advise to try and not throw it in with other changes.
>
> Cheers,
> Felix
>


Hi,

We added a new feature in Puppet Server 2.1.0 which allows it to be used
with Puppet 3 agents (as well as Puppet 4 agents, of course).

https://docs.puppetlabs.com/puppetserver/latest/release_notes.html#whats-new-in-puppet-server-21

- Kevin

-- 
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/CAF-bMBdcWq3B_nkLoB5H2EOgkc2N7-BpEJV3pBRv-qUokcXGyw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Felix Frank]

On 07/22/2015 11:06 PM, Kevin Corcoran wrote:
> Hi,
>
> We added a new feature in Puppet Server 2.1.0 which allows it to be
> used with Puppet 3 agents (as well as Puppet 4 agents, of course).
>
> https://docs.puppetlabs.com/puppetserver/latest/release_notes.html#whats-new-in-puppet-server-21
>
> - Kevin

Mind. Blown.

No really, that is great news!

Thanks,
Felix

-- 
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/55B00A92.108%40Alumni.TU-Berlin.de.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Announce: puppet_agent module 0.2.0 released

[Michael Smith]

The puppet_agent module 0.2.0 is available.

The puppet_agent module is intended to ease the transition of agents from
Puppet 3.8 to Puppet 4 (using the puppet-agent package). It works with both
master and master-less setups, but expects your existing Puppet
installation to be installed via packages.

https://forge.puppetlabs.com/puppetlabs/puppet_agent
https://github.com/puppetlabs/puppetlabs-puppet_agent

The 0.2.0 release has support for most platforms for which we release both
Puppet 3.x and Puppet-Agent packages:
- Windows Server 2003, 2003R2, 2008, 2008R2, 2012, 2012R2
- Windows 7, 8
- RHEL 5, 6, 7
- CentOS 5, 6, 7
- Ubuntu 12.04, 14.04
- Debian 6, 7

The module currently installs the latest puppet-agent module available from
puppetlabs.com, although a specific source URL can be provided with the
source parameter.

The goal is to automate the agent side of upgrading from Puppet 3.x
.
Note that Puppet Server 2.1 supports backwards compatibility with Puppet 3
agents

.

-- 
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/CABy1mMKGn7ekUmcOkSeVzSHPcq-Ydwtw7EzzjojzPwU6nF214w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Stack Kororā]

On Wednesday, July 22, 2015 at 4:06:51 PM UTC-5, Kevin Corcoran wrote:
>
>
> We added a new feature in Puppet Server 2.1.0 which allows it to be used 
> with Puppet 3 agents (as well as Puppet 4 agents, of course).
>
>
> https://docs.puppetlabs.com/puppetserver/latest/release_notes.html#whats-new-in-puppet-server-21
>

Awesome; that is good news! Thanks!


Just as an update to my progress, I found a few modules that work really 
well to replace some of my not-so-good-but-functional modules. :-)

It also appears to me that puppet dashboard is not yet ready for 4. Anyone 
have any thoughts on that?

Thanks!

-- 
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/585c975d-810b-4307-ab15-47d5bb04c322%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppetserver does not sign its certificate

[Kevin Corcoran]

Hi Felix,

I tried to reproduce your problem on a fresh Debian 7 VM, but couldn't.

Have you been running the agent on this machine?  If so, I suspect you're
hitting this issue: https://tickets.puppetlabs.com/browse/SERVER-528

Cheers,
- Kevin

-- 
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/CAF-bMBekUktu6QZRiLBBdPhzT2AhsrTV4mO%2B-R9EPDi-6XRkPw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Announce: Puppet Agent 1.2.2, Facter 3.0.2, Puppet 4.2.1

[Jorie Tappa]

I’m happy to announce the next All-in-One Puppet Agent release! This
release includes new versions of Facter and Puppet, and is now downloadable
through the Puppet Collection 1 repository.


   -

   Facter 3.0.2 fixes several regressions in Facter 3.0.0 and implements
   new features to support legacy workflows. Release notes here:
   http://docs.puppetlabs.com/facter/3.0/release_notes.html


   -

   Puppet 4.2.1 contains several bug fixes. Read the release notes:
   http://docs.puppetlabs.com/puppet/4.2/reference/release_notes.html


Get installation instructions and read about Puppet Collections, our
Linux-distribution-style repositories for Puppet related projects, here:
https://puppetlabs.com/blog/welcome-puppet-collections

-- 
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/CALjrZaxZcYspNAk49hG2My2kpw24ryKRtoZeq1sMEa4HgWJMRA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Status of activemq

[Ellison Marks]

So, I'm going through the dance of upgrading to puppet 4.2 from 3.8 on 
CentOS 6, and I've run into a few things that brought up some questions. 
During the install, I ran into a number of collisions and incompatibilities 
between pc1 and the existing packages, but pertinent to this issue, I had 
to uninstall the old puppetlabs-release package in favor of the pc1 release 
package, as they were both claiming ownership of the signing key. It's 
mostly worked out, however, now I'm at the point where I'm working on 
migrating mcollective. Aside from some hiccups with involving 
incompatibilities with the new facter, I've got things talking to each 
other. Now though, I'm wondering about activemq. I've still got the version 
I had installed from the puppetlabs-deps repo, and it's working, I'm just 
not sure where I'm supposed to get updates at this point.

-- 
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/16492e87-eb64-45a1-9dc5-6d861560fafd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] How to enable/create environments for new puppetserver setup (not puppetmaster)

[Gene Fontanilla]

Hi Puppet users,

I am testing out the new puppetserver vs the apache/passenger setup for the 
master,
problem is that when i created a new environment I am unable to start 
puppetserver.

Anything i need to know?

checking the logs the main error i keep on getting is 


ERROR [puppet-server] /File[/etc/puppet/modules/production]/ensure change 
> from absent to directory failed: Could not set 'directory' on ensure: 
> Permission denied - /etc/puppet/modules/production
> 2015-07-23 14:26:34,427

 

> ERROR [p.t.internal] shutdown-on-error triggered because of exception!
>
>
Thanks! and regards
Gene

-- 
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/8e73d2b1-a9ab-4875-8e72-942952d6c534%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.