Re: [Puppet Users] Announce: Puppet Platform 5.3.4 is now available

[Josh Cooper]

On Tue, Feb 6, 2018 at 3:04 AM, SCHAER Frederic 
wrote:

> Hi,
>
>
>
> On my dev puppetserver, I have  :
>
> # puppet config print environmentpath
>
> /puppet/code/envs
>
>
>
> # grep env /etc/puppetlabs/puppet/puppet.conf
>
> environmentpath = /puppet/code/envs
>
> environment = preprod
>
>
>
> (yes, the puppetserver for dev hosts is in env preprod ;) )
>
>
>
> On all client nodes referring to that puppetserver, I see since today :
>
> # puppet agent -t
>
> Warning: Unable to fetch my node definition, but the agent run will
> continue:
>
> Warning: Could not intern from application/json: Could not find a
> directory environment named 'dev' anywhere in the path:
> /etc/puppetlabs/code/environments. Does the directory exist?
>
> Info: Retrieving pluginfacts
>
> (…)
>
> And configuration goes on as before. If I change something in puppet, the
> change is seen despite the warning.
>
>
>
>
>
> If I downgrade the puppet-server, this changes nothing.
>
> If I downgrade the puppet-agent, the warning goes away. But configuration
> fails because of some unfound ruby gems – that’s new:
>
> Error: Could not convert change ensure to string: No such file or
> directory @ rb_sysopen - /opt/puppetlabs/puppet/lib/
> ruby/gems/2.4.0/gems/fast_gettext-1.1.0/lib/fast_gettext/vendor/empty.mo
>
> Error: No such file or directory @ rb_sysopen - /opt/puppetlabs/puppet/lib/
> ruby/gems/2.4.0/gems/fast_gettext-1.1.0/lib/fast_gettext/vendor/empty.mo
>
>
>
>
>
> The puppet agent indeed has a default config  that I did not specify – and
> don’t want to, I’m running with a puppetserver :
>
> # puppet config print environmentpath
>
> /etc/puppetlabs/code/environments
>
> # grep env /etc/puppetlabs/puppet/puppet.conf
>
> environment = dev
>
>
>
>
>
>
>
> ð  Question : what am I doing wrong ?
>
>
>

This was a regression in puppet-agent 5.3.4 involving non-default
environments[1]. It will be fixed in puppet-agent 5.3.5. We have many
acceptance tests for this functionality, but unfortunately they did not
catch this particular failure mode when the initial node request fails.
We'll be updating those tests to avoid regressing in the future[2].

Thanks
>
>
>
>
>
> *De :* puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com]
> *De la part de* Molly Waggett
> *Envoyé :* lundi 5 février 2018 21:10
> *À :* puppet-users@googlegroups.com
> *Objet :* [Puppet Users] Announce: Puppet Platform 5.3.4 is now available
>
>
>
> This is a bug-fix release of Puppet Platform. All three components -
> puppet-agent, PuppetDB, and Puppet Server - have been updated.
>
>
>
> This release of Puppet Agent updates Puppet to 5.3.4 and Facter to 3.9.4.
> Puppet 5.3.4 adds two new settings, `sourceaddress` and `runtimeout`. It
> also adds module translation distribution to pluginsync, improves Japanese
> localization, and fixes several bugs. This release also adds support for
> macOS 10.13 (High Sierra), EL 7 on arm64, and Amazon Linux 2. For details,
> see the Puppet Agent
>  release
> notes.
>
>
>
> PuppetDB 5.1.4 and Puppet Server 5.1.5 add Debian 9 (Stretch) packages, as
> well as additional bug fixes. For details, see the Puppet Server
>  and PuppetDB
>  release notes.
>
>
>
> Thanks!
>
>
>
> --
>
> *Molly Waggett*
>
> Release Engineer @ Puppet, Inc.
>
> --
> 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/CAFOE68B9vb1VfqAoq6S%2BOmmV6987S61n2NNxkHtCpxpXoEkC
> XQ%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/CAB586860327CB498EF79903967FEA231A7A720B%40E-EXDAGE-A0.
> extra.cea.fr
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

Josh

[1] https://tickets.puppetlabs.com/browse/PUP-8419
[2] https://tickets.puppetlabs.com/browse/PUP-8459

-- 
Josh Cooper | Software Engineer
j...@puppet.com | @coopjn

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" 

Re: [Puppet Users] Puppet 4 EOL?

[Sven vd]

Thanks, very clear answers

For reference, you can map puppet versions with PE releases by checking the 
overview page 
https://puppet.com/docs/pe/2017.3/overview/component_versions_in_recent_pe_releases.html


On Monday, February 12, 2018 at 6:20:25 PM UTC+1, Eric Sorenson wrote:
>
> Close, the PE2016.4 LTS uses Puppet 4 and is supported through October 
> 2018. 
>
> --eric0
>
> On Monday, February 12, 2018 at 9:15:20 AM UTC-8, R.I. Pienaar wrote:
>>
>>
>>
>> On Mon, 12 Feb 2018, at 17:43, Sven vd wrote: 
>> > Hi, 
>> > 
>> > Currently our infrastructure and code is written with and run by puppet 
>> 4 
>> > opensource. 
>> > 
>> > We are using https://yum.puppetlabs.com/el/7/PC1/x86_64/ repos for 
>> updates 
>> > of our installed software, puppetserver, puppetdb, puppet agent. 
>> > 
>> > Since puppet 5 was released the puppet 5 packages shifted to another 
>> repo 
>> > https://yum.puppetlabs.com/puppet/el/7/x86_64/. We are not using this 
>> repo 
>> > since we are currently on puppet 4 codebase. 
>> > 
>> > So the question is, how long will the 
>> > https://yum.puppetlabs.com/el/7/PC1/x86_64/  repo get updates 
>> (security 
>> > fixed, improvements etc) and when is open source puppet 4 considered 
>> End Of 
>> > Life? 
>>
>>
>> if you look at the Puppet Enterprise support cycle and figure out which 
>> is the last one with Puppet 4 then you will know when 4 will be EOL.  If I 
>> read it right it looks to be around July 2018. 
>>
>> Upgrade to Puppet 5 from 4 is pretty trivial, so should be easy for you 
>> to follow along. 
>>
>> -- 
>> R.I.Pienaar / www.devco.net / @ripienaar 
>>
>

-- 
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/878055c3-84ab-4019-a1bd-bb504c064e82%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet 4 EOL?

[Eric Sorenson]

Close, the PE2016.4 LTS uses Puppet 4 and is supported through October 
2018. 

--eric0

On Monday, February 12, 2018 at 9:15:20 AM UTC-8, R.I. Pienaar wrote:
>
>
>
> On Mon, 12 Feb 2018, at 17:43, Sven vd wrote: 
> > Hi, 
> > 
> > Currently our infrastructure and code is written with and run by puppet 
> 4 
> > opensource. 
> > 
> > We are using https://yum.puppetlabs.com/el/7/PC1/x86_64/ repos for 
> updates 
> > of our installed software, puppetserver, puppetdb, puppet agent. 
> > 
> > Since puppet 5 was released the puppet 5 packages shifted to another 
> repo 
> > https://yum.puppetlabs.com/puppet/el/7/x86_64/. We are not using this 
> repo 
> > since we are currently on puppet 4 codebase. 
> > 
> > So the question is, how long will the 
> > https://yum.puppetlabs.com/el/7/PC1/x86_64/  repo get updates (security 
> > fixed, improvements etc) and when is open source puppet 4 considered End 
> Of 
> > Life? 
>
>
> if you look at the Puppet Enterprise support cycle and figure out which is 
> the last one with Puppet 4 then you will know when 4 will be EOL.  If I 
> read it right it looks to be around July 2018. 
>
> Upgrade to Puppet 5 from 4 is pretty trivial, so should be easy for you to 
> follow along. 
>
> -- 
> R.I.Pienaar / www.devco.net / @ripienaar 
>

-- 
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/cdf21006-55db-4f07-bf9b-4463435495fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet 4 EOL?

[R.I.Pienaar]

On Mon, 12 Feb 2018, at 17:43, Sven vd wrote:
> Hi,
> 
> Currently our infrastructure and code is written with and run by puppet 4 
> opensource.
> 
> We are using https://yum.puppetlabs.com/el/7/PC1/x86_64/ repos for updates 
> of our installed software, puppetserver, puppetdb, puppet agent.
> 
> Since puppet 5 was released the puppet 5 packages shifted to another repo 
> https://yum.puppetlabs.com/puppet/el/7/x86_64/. We are not using this repo 
> since we are currently on puppet 4 codebase.
> 
> So the question is, how long will the 
> https://yum.puppetlabs.com/el/7/PC1/x86_64/  repo get updates (security 
> fixed, improvements etc) and when is open source puppet 4 considered End Of 
> Life?


if you look at the Puppet Enterprise support cycle and figure out which is the 
last one with Puppet 4 then you will know when 4 will be EOL.  If I read it 
right it looks to be around July 2018.

Upgrade to Puppet 5 from 4 is pretty trivial, so should be easy for you to 
follow along.

-- 
R.I.Pienaar / www.devco.net / @ripienaar

-- 
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/1518455707.2368530.1268211688.6F454C24%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet 4 EOL?

[Sven vd]

Hi,

Currently our infrastructure and code is written with and run by puppet 4 
opensource.

We are using https://yum.puppetlabs.com/el/7/PC1/x86_64/ repos for updates 
of our installed software, puppetserver, puppetdb, puppet agent.

Since puppet 5 was released the puppet 5 packages shifted to another repo 
https://yum.puppetlabs.com/puppet/el/7/x86_64/. We are not using this repo 
since we are currently on puppet 4 codebase.

So the question is, how long will the 
https://yum.puppetlabs.com/el/7/PC1/x86_64/  repo get updates (security 
fixed, improvements etc) and when is open source puppet 4 considered End Of 
Life?

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/e5b5fe94-8cac-4431-a41c-ee2d3dd8d473%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Error related to Puppet Netscaler Module

[Mohd Reehan]

Hello Team, 

i am getting below error when trying to do puppet run. i am not sure how to 
solve this, can pointers would be helpful. 

Info: starting applying configuration to int-ams-ns01 at 
http://int-ams-ns01:80/nitro/v1/
Info: Using configured environment 'staging'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Caching catalog for int-ams-ns01
Info: Applying configuration version '1518449028'
*Error: Could not set 'present' on ensure: REST failure: HTTP status code 
409 detected.  Body of failure is: { "errorcode": 273, "message": "Resource 
already exists", "severity": "ERROR" } at 
/etc/puppetlabs/code/environments/staging/modules/ns/manifests/init.pp:262*
*Error: Could not set 'present' on ensure: REST failure: HTTP status code 
409 detected.  Body of failure is: { "errorcode": 273, "message": "Resource 
already exists", "severity": "ERROR" } at 
/etc/puppetlabs/code/environments/staging/modules/ns/manifests/init.pp:262*
*Wrapped exception:*
*REST failure: HTTP status code 409 detected.  Body of failure is: { 
"errorcode": 273, "message": "Resource already exists", "severity": "ERROR" 
}*
*Error: 
/Stage[main]/Ns/Netscaler_lbvserver[VS_dashboard_aerdata_com_re]/ensure: 
change from 'absent' to 'present' failed: Could not set 'present' on 
ensure: REST failure: HTTP status code 409 detected.  Body of failure is: { 
"errorcode": 273, "message": "Resource already exists", "severity": "ERROR" 
} at 
/etc/puppetlabs/code/environments/staging/modules/ns/manifests/init.pp:262*
*Notice: 
/Stage[main]/Ns/Netscaler_lbvserver[VS_management_aerdata_com_redir]/redirect_url:
 
redirect_url changed 'https://management.uat.aerdata.loc' to ''*
*Error: 
/Stage[main]/Ns/Netscaler_lbvserver[VS_management_aerdata_com_redir]: Could 
not evaluate: REST failure: HTTP status code 599 detected.  Body of failure 
is: { "errorcode": 1107, "message": "String too short [redirectURL, 1]", 
"severity": "ERROR" }*
*Error: Could not set 'present' on ensure: REST failure: HTTP status code 
599 detected.  Body of failure is: { "errorcode": 1540, "message": 
"Certificate does not exist", "severity": "ERROR" } at 
/etc/puppetlabs/code/environments/staging/modules/ns/manifests/init.pp:482*
*Error: Could not set 'present' on ensure: REST failure: HTTP status code 
599 detected.  Body of failure is: { "errorcode": 1540, "message": 
"Certificate does not exist", "severity": "ERROR" } at 
/etc/puppetlabs/code/environments/staging/modules/ns/manifests/init.pp:482*
*Wrapped exception:*
*REST failure: HTTP status code 599 detected.  Body of failure is: { 
"errorcode": 1540, "message": "Certificate does not exist", "severity": 
"ERROR" }*
*Error: 
/Stage[main]/Ns/Netscaler_sslvserver[CS_management_aerdata_com_local/${ns_mgt_cert}]/ensure:
 
change from 'absent' to 'present' failed: Could not set 'present' on 
ensure: REST failure: HTTP status code 599 detected.  Body of failure is: { 
"errorcode": 1540, "message": "Certificate does not exist", "severity": 
"ERROR" } at 
/etc/puppetlabs/code/environments/staging/modules/ns/manifests/init.pp:482*
*Error: Could not set 'present' on ensure: REST failure: HTTP status code 
599 detected.  Body of failure is: { "errorcode": 1540, "message": 
"Certificate does not exist", "severity": "ERROR" } at 
/etc/puppetlabs/code/environments/staging/modules/ns/manifests/init.pp:817*
*Error: Could not set 'present' on ensure: REST failure: HTTP status code 
599 detected.  Body of failure is: { "errorcode": 1540, "message": 
"Certificate does not exist", "severity": "ERROR" } at 
/etc/puppetlabs/code/environments/staging/modules/ns/manifests/init.pp:817*
*Wrapped exception:*
*REST failure: HTTP status code 599 detected.  Body of failure is: { 
"errorcode": 1540, "message": "Certificate does not exist", "severity": 
"ERROR" }*
*Error: 
/Stage[main]/Ns/Netscaler_sslvserver[VS_qliksense_aerdata_com_auth/${ns_vs_cert}]/ensure:
 
change from 'absent' to 'present' failed: Could not set 'present' on 
ensure: REST failure: HTTP status code 599 detected.  Body of failure is: { 
"errorcode": 1540, "message": "Certificate does not exist", "severity": 
"ERROR" } at 
/etc/puppetlabs/code/environments/staging/modules/ns/manifests/init.pp:817*
*Error: Could not set 'present' on ensure: REST failure: HTTP status code 
599 detected.  Body of failure is: { "errorcode": 1823, "message": "Invalid 
domain name syntax", "severity": "ERROR" } at 
/etc/puppetlabs/code/environments/staging/modules/ns/manifests/init.pp:1316*
*Error: Could not set 'present' on ensure: REST failure: HTTP status code 
599 detected.  Body of failure is: { "errorcode": 1823, "message": "Invalid 
domain name syntax", "severity": "ERROR" } at 
/etc/puppetlabs/code/environments/staging/modules/ns/manifests/init.pp:1316*
*Wrapped exception:*
*REST failure: HTTP status code 599 detected.  Body of failure is: { 
"errorcode": 1823, "message": "Invalid domain name syntax", "severity": 
"ERROR" }*
*Error: /Stage[main]/Ns/Netscaler_server[0]/ensure: change 

[Puppet Users] Re: How manage tag (exported ressources)

[jcbollinger]

On Friday, February 9, 2018 at 4:00:48 PM UTC-6, Albert Shih wrote:
>
> Hi, 
>
> I would like to know how you or what's best practice to manage tag in 
> exported resources. 
>
> For example I have two hosts H1 and H2->100, and I want export file_line 
> from H2->100 
> to H1. 
>
> So or I use a standardized tag (like "for_${::fqdn}" whatever the kind of 
> resource) than in H1 I can very easily imported those resource. Or I need 
> share a information between those two hosts (and I don't know how to do 
> that properly when I have lot of exported resources). 
>
> What's best way ? 
>


I would start by generalizing the problem a bit.  *Why* do you want to 
export a resource from H1 to H2->100?  There are two aspects that I would 
recommend being reflected by one or more tags:

   1. File_line is a very generic resource.  It will likely be helpful, 
   therefore, to tag instances with something that narrows that type in a 
   meaningful way.  For example, if there were not already a Host resource 
   type, then you might use File_line tagged with something like "hosts_line" 
   for the same purpose.
   2. Since you specifically want one host to collect this resource, it 
   sounds like there is a question of scope that might be appropriately 
   reflected by a tag.  It is unlikely that H1's *identity* is an 
   appropriate descriptor for that scope, however.  The scope in question 
   might be a data center, a compute cluster, an application, or similar.  
   That's what should be reflected by tagging.  Or maybe you don't actually 
   need a scope narrower than your whole site after all.

This permits you to decouple H1 and H2->100 from each other, making the 
whole arrangement both clearer and more flexible.  H2->100 does not need to 
know or care which node(s), if any, are going to collect the resources it 
exports, and it doesn't need to do anything differently if that changes.  
On the H1 side, the purpose of collecting the particular resources it does 
is clearer.


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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/513f17a8-473c-4b4d-bf09-7b6a8cf376eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.