[Puppet Users] puppet-agent 7 & 8 nightly builds for Alma Linux9 and Rocky 9 (ARM)

['Swati Yamgar' via Puppet Users]

Hello,

We are happy to announce that AlmaLinux 9 and Rocky Linux 9 (ARM) are now fully 
tested in our agent pipelines, so the Enterprise Linux 9 puppet-agent nightly 
builds can safely be used on these OSes.

Nightly release packages are available under 
nightlies.puppet.com/yum. Stable builds will 
also be available on yum.puppet.com starting with the 
next puppet-agent release.

Please try them out and let us know if you have any questions!

Thanks,
Swati Yamgar
Perforce Software | Software Engineer



This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.

-- 
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/PH7PR20MB439001355A6BDDEDA7BD3A6DF8A42%40PH7PR20MB4390.namprd20.prod.outlook.com.

[Puppet Users] puppet-agent 7 & 8 nightly builds for Alma Linux9 and Rocky 9 (x86_64)

['Amit Karsale' via Puppet Users]

Hello,

We are happy to announce that AlmaLinux 9 and Rocky Linux 9 x86_64 are now 
fully tested in our agent pipelines, so the Enterprise Linux 9 puppet-agent 
nightly builds can safely be used on these OSes.

Nightly release packages are available under 
nightlies.puppet.com/yum. Stable builds will 
also be available on yum.puppet.com starting with the 
next puppet-agent release.

Please try them out and let us know if you have any questions!

Thanks,
Amit Karsale
Perforce Software | Senior Software Engineer



This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.

-- 
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/CH3PR20MB6268E2CF3D4B712464D509CAF3D42%40CH3PR20MB6268.namprd20.prod.outlook.com.

[Puppet Users] puppet-agent 7 & 8 nightly builds for Ubuntu 24.04 (amd64 and aarch64)

['Shubham Shinde' via Puppet Users]

Hello,

We are happy to announce that puppet-agent nightly builds for Ubuntu 24.04 
(amd64 and aarch64) are now available at https://nightlies.puppet.com/apt/

Please try them out and let us know if you have any questions!

Thank you.




*Shubham Shinde | Software Engineer, PuppetPerforce Software*

-- 
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/6c6d4adc-901d-453d-a834-60d6e444cdc8n%40googlegroups.com.

[Puppet Users] Puppet agent 7 memory issue in Debian 11

[sathia narayanan]

We have recently upgraded from puppet agent 6 to puppet agent 7 in our 
infra. It seems on each run interval puppet process memory(RSS) is 
increasing steadily, goes beyond 1.1G which is very high. Whereas in centos 
7, this behaviour is not happening. Currently we are in puppet agent 7.30 
which is higher version. Ruby and its dependencies also in higher version. 
Kindly suggest on this.

-- 
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/efdda39d-2cca-4450-9fb9-a1ef9f7d486fn%40googlegroups.com.

[Puppet Users] puppet-agent 7 & 8 nightly builds for Amazon Linux2 (aarch64)

['Amit Karsale' via Puppet Users]

Hello,

We are happy to announce that puppet-agent nightly builds for Amazon Linux2 
(aarch64) are now available at https://nightlies.puppet.com/yum/

Please try them out and let us know if you have any questions!

Thank you.



Amit Karsale| Senior Software Engineer, Puppet
Perforce Software


This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.

-- 
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/CH3PR20MB6268B2BE6CD88C93DD28A5A7F3F32%40CH3PR20MB6268.namprd20.prod.outlook.com.

Re: [Puppet Users] puppet-agent 7 & 8 nightly builds for Fedora 40 (x86_64)

[Martin Alfke]

Hi Shubham,

Many thanks for the information about Fedora 40 Packages.
Can you also provide information regarding Debian 12 Packages (Puppetserver and 
PuppetDB are still missing)
https://github.com/puppetlabs/puppetserver/issues/2837

Best,
Martin


> On 29. May 2024, at 12:03, 'Shubham Shinde' via Puppet Users 
>  wrote:
> 
> Hello,
> 
> We are happy to announce that puppet-agent nightly builds for Fedora 40 
> (x86_64) are now available at https://nightlies.puppet.com/yum/
> 
> Please try them out and let us know if you have any questions!
> 
> Thank you.
> 
> 
> 
> Shubham Shinde | Software Engineer, Puppet
> Perforce Software
> 
> -- 
> 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/95b39baa-4143-44e4-abec-9b7c99fae5f5n%40googlegroups.com
>  
> .

-- 
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/AD59A2DB-5178-446B-A163-2ED2F0BB82C7%40gmail.com.

[Puppet Users] puppet-agent 7 & 8 nightly builds for Fedora 40 (x86_64)

['Shubham Shinde' via Puppet Users]

Hello,

We are happy to announce that puppet-agent nightly builds for Fedora 40 
(x86_64) are now available at https://nightlies.puppet.com/yum/

Please try them out and let us know if you have any questions!

Thank you.




*Shubham Shinde | Software Engineer, PuppetPerforce Software*

-- 
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/95b39baa-4143-44e4-abec-9b7c99fae5f5n%40googlegroups.com.

[Puppet Users] puppet-agent 7 & 8 nightly builds for Redhat9 Power 9(ppc64le)

['Swati Yamgar' via Puppet Users]

Hello,

We are happy to announce that puppet-agent nightly builds for Redhat9 Power 
9(ppc64le) are now available at https://nightlies.puppet.com

Please try them out and let us know if you have any questions!

Thank you.


--

Swati Yamgar (she/her) | Software Engineer, 
Puppet

Perforce 
Software
Visit us on: 
LinkedIn
 | 
Twitter
 | 
Facebook
 | 
YouTube



This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.

-- 
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/PH7PR20MB43909A70E711022ABDBA9BA9F8182%40PH7PR20MB4390.namprd20.prod.outlook.com.

[Puppet Users] puppet-agent 7 & 8 nightly builds for Debian 12 (ARM)

['Swati Yamgar' via Puppet Users]

Hello,

We are happy to announce that puppet-agent nightly builds for Debian 12 (ARM) 
are now available at 
https://nightlies.puppet.com/apt

Please try them out and let us know if you have any questions!

Thank you.



--

Swati Yamgar (she/her) | Software Engineer, 
Puppet

Perforce 
Software
Visit us on: 
LinkedIn
 | 
Twitter
 | 
Facebook
 | 
YouTube



This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.

-- 
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/PH7PR20MB439018033AA17DC5FC924163F8482%40PH7PR20MB4390.namprd20.prod.outlook.com.

[Puppet Users] puppet-agent 7 & 8 nightly builds for Debian 12 (x86-64)

['MaqsoodAhmad Ulde' via Puppet Users]

Hello,


We are happy to announce that puppet-agent nightly builds for Debian 12 
(x86-64) are now available at nightlies 
. 


Please try them out and let us know if you have any questions!

Thank you.


*Maqsood Ahmad Ulde | Senior Software Engineer, Puppet 
*

Perforce Software 


Visit us on: LinkedIn 

 | Twitter 

 | Facebook 

 | YouTube 

 | Slack 


 

-- 
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/ea4febc5-526a-4c33-b499-d27c911e4751n%40googlegroups.com.

[Puppet Users] puppet-agent 7 & 8 nightly builds for MacOS 14 ARM (Sonoma)

['Amit Karsale' via Puppet Users]

Hello,

We are happy to announce that puppet-agent nightly builds for MacOS 14 ARM 
(Sonoma)  are now available at https://nightlies.puppet.com/downloads/mac

Please try them out and let us know if you have any questions!


Thank you.

*Amit Karsale | Senior Software Engineer, Puppet 
*

Perforce Software 


Visit us on: LinkedIn 

 | Twitter 

 | Facebook 

 | YouTube 

 | Slack 


-- 
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/d7a28956-5268-4e49-b759-d0fc4f41b9f0n%40googlegroups.com.

[Puppet Users] puppet-agent 7 & 8 nightly builds for MacOS 14 (Sonoma) ×86_64

['MaqsoodAhmad Ulde' via Puppet Users]

Hello,

We are happy to announce that puppet-agent nightly builds for MacOS 14 
(Sonoma) x86_64 are now available at 
https://nightlies.puppet.com/downloads/mac

Please try them out and let us know if you have any questions!


Thank you.

*Maqsood Ahmad Ulde | Senior Software Engineer, Puppet 
*

Perforce Software 


Visit us on: LinkedIn 

 | Twitter 

 | Facebook 

 | YouTube 

 | Slack 


-- 
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/7330542a-c2a1-461e-8715-07ebbccf86aen%40googlegroups.com.

[Puppet Users] puppet-agent 7 & 8 nightly builds for Amazon Linux (ARM64 and x86_64)

['Shubham Shinde' via Puppet Users]

Hello,

We are happy to announce that puppet-agent nightly builds for Amazon Linux 
(ARM64 and x86_64) are now available at https://nightlies.puppet.com/yum/

Please try them out and let us know if you have any questions!

Thank you.


*Shubham Shinde | Software Engineer, PuppetPerforce Software*

-- 
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/6e3dea10-8afe-4f9b-8c33-c33400a2c8b3n%40googlegroups.com.

Re: [Puppet Users] puppet-agent 7 & 8 nightly builds for Debian 11 (ARM64)

['Saša Teković' via Puppet Users]

On Monday, November 27, 2023 at 10:22:37 AM UTC+1 dhei...@opentext.com 
wrote:

But was already frozen when Puppet 8 was released in April: 
https://wiki.debian.org/DebianBookworm#Before_the_release


Dirk, you are going off-topic. I'm asking Puppetlabs team when can we 
expect Puppet 8 packages for Debian 12.

My question doesn't concern Debian packaging team nor Debian freeze policy.

--
Sasa Tekovic

-- 
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/5da1fa3c-1738-42eb-bdee-2400ea1749f0n%40googlegroups.com.

Re: [Puppet Users] puppet-agent 7 & 8 nightly builds for Debian 11 (ARM64)

['Dirk Heinrichs' via Puppet Users]

Am Montag, dem 27.11.2023 um 01:04 -0800 schrieb 'Saša Teković' via Puppet 
Users:

I'm  aware of that. However, Puppet 8 packages are not available in Debian 12 
official repositories nor at apt.puppet.com.

Sure, that'S why I wrote "For Puppet 7".

It's strange, because Debian 12 was released way back in June 2023.

But was already frozen when Puppet 8 was released in April: 
https://wiki.debian.org/DebianBookworm#Before_the_release

Bye...

Dirk

--

Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
Phone: +49 2226 15966 18
Email: dhein...@opentext.com
Website: 
www.recommind.de
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet.

-- 
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/7194a8e2f4b8854feb86a3f8739152043b593b7e.camel%40opentext.com.

Re: [Puppet Users] puppet-agent 7 & 8 nightly builds for Debian 11 (ARM64)

['Saša Teković' via Puppet Users]

On Monday, November 27, 2023 at 9:54:36 AM UTC+1 dhei...@opentext.com wrote:

For Puppet 7, Debian 12 ships its own ones (for ALL architectures): 
https://packages.debian.org/search?keywords=puppet=names=stable=all

Bye...

Dirk


Hi Dirk,

I'm  aware of that. However, Puppet 8 packages are not available in Debian 
12 official repositories nor at apt.puppet.com.
It's strange, because Debian 12 was released way back in June 2023. This is 
a blocker for a lot of users that wish to upgrade to Puppet 8.

--
Sasa Tekovic

-- 
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/d5256ac3-69f2-4d1c-8530-f24ed6daedd4n%40googlegroups.com.

Re: [Puppet Users] puppet-agent 7 & 8 nightly builds for Debian 11 (ARM64)

['Dirk Heinrichs' via Puppet Users]

Am Montag, dem 27.11.2023 um 00:40 -0800 schrieb 'Saša Teković' via Puppet 
Users:

thank you for your work. Can you let us know when can we expect Debian 12 
(amd64 and arm64) packages?

For Puppet 7, Debian 12 ships its own ones (for ALL architectures): 
https://packages.debian.org/search?keywords=puppet=names=stable=all

Bye...

Dirk

--

Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
Phone: +49 2226 15966 18
Email: dhein...@opentext.com
Website: 
www.recommind.de
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet.

-- 
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/c32414ef450c2e64b65305a8e9ec135a737f4a2f.camel%40opentext.com.

[Puppet Users] puppet-agent 7 & 8 nightly builds for Debian 11 (ARM64)

['Shubham Shinde' via Puppet Users]

Hello,

We are happy to announce that puppet-agent nightly builds for Debian 11 
(ARM64) are now available at https://nightlies.puppet.com/apt/index.html

Please try them out and let us know if you have any questions!

Thank you.


*Shubham Shinde | Software Engineer, PuppetPerforce Software*

-- 
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/e64c97c6-fc5c-4437-8900-95881480fc28n%40googlegroups.com.

Re: [Puppet Users] puppet-agent gone for Ubuntu Jammy 22.04?

['Eric Griswold' via Puppet Users]

Hi Brad,

We've repaired the install for Jammy puppet-agent on amd64. We will not have 
arm64 support ready in puppet-agent until the next release: 8.3.0 & 7.27.0

Eric Griswold
Puppet Release Engineering


On 10/11/23 19:53, 'Brad Reaves' via Puppet Users wrote:
Hi all,

I am getting install failures on Jammy when I try to install the puppet-agent 
package where apt says the package cannot be found in the repo.

I have tried with both the main apt repo and the nightlies, and with both 
"puppet7" and the plain "puppet" (which I presume is the latest from v8.) All 
fail.

I'm building images with cloud-init, and the same cloud-init config that fails 
on Jammy succeeds on Focal 20.04.

When I manually search through the Packages files on the repo server, I indeed 
find a puppet-agent package listed for Focal but not Jammy. I'm running arm64, 
but the amd64 package lists seem to have the same problem, so I don't think 
this is an "unsupported architecture" issue.

This is not the old issue where Jammy wasn't listed in the install.sh script. 
The package name just isn't in the repo, apart from being referenced by other 
packages.

Is anyone else having this problem? Is there a workaround that isn't "use 
focal" or "build the agent yourself?"

Thanks!
Brad Reaves
--
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/b34922df-12de-4763-be3c-e2104b065e41n%40googlegroups.com.


CAUTION: This email originated from outside of the organization. Do not click 
on links or open attachments unless you recognize the sender and know the 
content is safe.



This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.

-- 
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/80787c07-9d1a-4a93-8133-4166ab52381e%40perforce.com.

Re: [Puppet Users] puppet-agent gone for Ubuntu Jammy 22.04?

['Eric Griswold' via Puppet Users]

Brad,

There's a problem with the apt repo on apt.puppet.com. We're looking into it 
now.

Eric Griswold
Puppet Release Engineering


On 10/11/23 19:53, 'Brad Reaves' via Puppet Users wrote:
Hi all,

I am getting install failures on Jammy when I try to install the puppet-agent 
package where apt says the package cannot be found in the repo.

I have tried with both the main apt repo and the nightlies, and with both 
"puppet7" and the plain "puppet" (which I presume is the latest from v8.) All 
fail.

I'm building images with cloud-init, and the same cloud-init config that fails 
on Jammy succeeds on Focal 20.04.

When I manually search through the Packages files on the repo server, I indeed 
find a puppet-agent package listed for Focal but not Jammy. I'm running arm64, 
but the amd64 package lists seem to have the same problem, so I don't think 
this is an "unsupported architecture" issue.

This is not the old issue where Jammy wasn't listed in the install.sh script. 
The package name just isn't in the repo, apart from being referenced by other 
packages.

Is anyone else having this problem? Is there a workaround that isn't "use 
focal" or "build the agent yourself?"

Thanks!
Brad Reaves
--
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/b34922df-12de-4763-be3c-e2104b065e41n%40googlegroups.com.


CAUTION: This email originated from outside of the organization. Do not click 
on links or open attachments unless you recognize the sender and know the 
content is safe.



This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.

-- 
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/1d52b8ec-f4a5-41b2-982b-4fbf3a537d32%40perforce.com.

[Puppet Users] puppet-agent gone for Ubuntu Jammy 22.04?

['Brad Reaves' via Puppet Users]

Hi all,

I am getting install failures on Jammy when I try to install the 
puppet-agent package where apt says the package cannot be found in the 
repo. 

I have tried with both the main apt repo and the nightlies, and with both 
"puppet7" and the plain "puppet" (which I presume is the latest from v8.) 
All fail.  

I'm building images with cloud-init, and the same cloud-init config that 
fails on Jammy succeeds on Focal 20.04.

When I manually search through the Packages files on the repo server, I 
indeed find a puppet-agent package listed for Focal but not Jammy. I'm 
running arm64, but the amd64 package lists seem to have the same problem, 
so I don't think this is an "unsupported architecture" issue.

This is not the old issue where Jammy wasn't listed in the install.sh 
script. The package name just isn't in the repo, apart from being 
referenced by other packages.

Is anyone else having this problem? Is there a workaround that isn't "use 
focal" or "build the agent yourself?"

Thanks!
Brad Reaves

-- 
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/b34922df-12de-4763-be3c-e2104b065e41n%40googlegroups.com.

[Puppet Users] puppet-agent 7 & 8 nighlty builds for Redhat9 (ARM64)

['Amit Karsale' via Puppet Users]

Hello,

We are happy to announce that puppet-agent nightly builds for Redhat9
(ARM64) are now available at https://nightlies.puppet.com/yum/index.html

Please try them out and let us know if you have any questions!


Thank you.

-- 



Amit Karsale | Senior Software Engineer, Puppet


Perforce Software


Visit us on: LinkedIn

| Twitter

| Facebook

| YouTube


-- 
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/CAGRe5XWWG1%2BXx3dNWz1nGCTsQs%2BhmVAe6RkXn6PfmCUNmnEUKw%40mail.gmail.com.

[Puppet Users] puppet-agent 7 & 8 nightly builds for Ubuntu 22.04 (ARM64)

['Saurabh Pandit' via Puppet Users]

Hello, 

We are happy to announce that puppet-agent nightly builds for Ubuntu 22.04 
(ARM64) are now available at nightlies 


Please try them out and let us know if you have any questions!
Thank you.


*Saurabh Pandit | Senior Software Engineer, PuppetPerforce Software*

-- 
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/83cf3d72-cc93-4f75-af21-ee4829ea91c9n%40googlegroups.com.

[Puppet Users] puppet-agent-ubuntu DockerHub outdated

[Nathaniel Black]

Hello!

We use Docker puppet/puppet-agent-ubuntu:latest in CI/CD pipelines to 
perform actions like lint and validate checks, but I have noticed that the 
repo is becoming quite outdated.

https://hub.docker.com/r/puppet/puppet-agent-ubuntu/tags

The last release was 9 months ago with version 7.20:
puppet-agent-ubuntu:7.20.0

Is this going to be updated some time?

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/036723bb-cd25-4dd0-a79d-317635fc65bbn%40googlegroups.com.

[Puppet Users] puppet-agent 7 & 8 nightly builds for MacOS 13 (Ventura) ×86_64

['Amit Karsale' via Puppet Users]

 

Hello,

We are happy to announce that puppet-agent nightly builds for MacOS 13 
(Ventura) x86_64 are now available at 
https://nightlies.puppet.com/downloads/mac

Please try them out and let us know if you have any questions!


Thank you.

*Amit Karsale | Senior Software Engineer, **Puppet* 


*Perforce Software* 


Visit us on: LinkedIn 

 | Twitter 

 | Facebook 

 | YouTube 



-- 
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/93da376b-befc-4a16-bd0f-4815f62f2cdcn%40googlegroups.com.

[Puppet Users] Puppet Agent 8 and Puppet Server 7 compatibility?

[Bob Negri]

Does anyone know if the puppet 8 agent can interact with a puppet 7 
server/master and puppetdb?

Thank you!

-- 
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/61815eda-062d-45a2-927f-f3739a8304a8n%40googlegroups.com.

[Puppet Users] puppet-agent 7 & 8 nightly builds for MacOS 13 (ARM)

['Swati Yamgar' via Puppet Users]

Hello,

We are happy to announce that puppet-agent nightly builds for MacOS 13 (ARM) 
are now available at https://nightlies.puppet.com/downloads/mac.

Please try them out and let us know if you have any questions!

Thank you.

--

Swati Yamgar (she/her) | Software Engineer, 
Puppet

Perforce 
Software
Visit us on: 
LinkedIn
 | 
Twitter
 | 
Facebook
 | 
YouTube



This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.

-- 
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/PH7PR20MB43900E5154549C95DEA7486AF808A%40PH7PR20MB4390.namprd20.prod.outlook.com.

Re: [Puppet Users] Puppet agent is not running on Windows 11

[Stephanos Economides]

Hi Jimm,

Thank you for your help.  Following is the content of my puppet.conf, do 
you suggest a specific action on my behalf to solve this problem?

C:\Windows\System32>puppet config print

agent_catalog_run_lockfile = 
C:/ProgramData/PuppetLabs/puppet/cache/state/agent_catalog_run.lock
agent_disabled_lockfile = 
C:/ProgramData/PuppetLabs/puppet/cache/state/agent_disabled.lock
allow_duplicate_certs = false
always_retry_plugins = true
autoflush = true
autosign = C:/ProgramData/PuppetLabs/puppet/etc/autosign.conf
basemodulepath = C:/ProgramData/PuppetLabs/code/modules;C:/Program 
Files/Puppet Labs/Puppet/puppet/modules
binder_config =
bucketdir = C:/ProgramData/PuppetLabs/puppet/cache/bucket
ca_fingerprint =
ca_name = Puppet CA: laptop-j2mk58hv
ca_port = 8140
ca_server = puppet
ca_ttl = 15768
cacert = C:/Windows/System32/ca_crt.pem
cacrl = C:/Windows/System32/ca_crl.pem
cadir = C:/Windows/System32
cakey = C:/Windows/System32/ca_key.pem
capub = C:/Windows/System32/ca_pub.pem
catalog_cache_terminus =
catalog_terminus = compiler
cert_inventory = C:/Windows/System32/inventory.txt
certdir = C:/ProgramData/PuppetLabs/puppet/etc/ssl/certs
certificate_revocation = chain
certname = laptop-j2mk58hv
ciphers = 
ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA256:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256
classfile = C:/ProgramData/PuppetLabs/puppet/cache/state/classes.txt
client_datadir = C:/ProgramData/PuppetLabs/puppet/cache/client_data
clientbucketdir = C:/ProgramData/PuppetLabs/puppet/cache/clientbucket
clientyamldir = C:/ProgramData/PuppetLabs/puppet/cache/client_yaml
code =
codedir = C:/ProgramData/PuppetLabs/code
color = ansi
confdir = C:/ProgramData/PuppetLabs/puppet/etc
config = C:/ProgramData/PuppetLabs/puppet/etc/puppet.conf
config_file_name = puppet.conf
config_version =
configprint =
crl_refresh_interval =
csr_attributes = C:/ProgramData/PuppetLabs/puppet/etc/csr_attributes.yaml
csrdir = C:/Windows/System32/requests
daemonize = false
data_binding_terminus = hiera
default_file_terminus = rest
default_manifest = ./manifests
default_schedules = true
deviceconfdir = C:/ProgramData/PuppetLabs/puppet/etc/devices
deviceconfig = C:/ProgramData/PuppetLabs/puppet/etc/device.conf
devicedir = C:/ProgramData/PuppetLabs/puppet/cache/devices
diff =
diff_args = -u
digest_algorithm = sha256
disable_i18n = true
disable_per_environment_manifest = false
disable_warnings = []
dns_alt_names =
document_all = false
environment = production
environment_data_provider =
environment_timeout = 0
environmentpath = C:/ProgramData/PuppetLabs/code/environments
evaltrace = false
external_nodes = none
fact_name_length_soft_limit = 2560
fact_value_length_soft_limit = 4096
factpath = 
C:/ProgramData/PuppetLabs/puppet/cache/lib/facter;C:/ProgramData/PuppetLabs/puppet/cache/facts
facts_terminus = facter
fileserverconfig = C:/ProgramData/PuppetLabs/puppet/etc/fileserver.conf
filetimeout = 15
forge_authorization =
freeze_main = false
genconfig = false
genmanifest = false
graph = false
graphdir = C:/ProgramData/PuppetLabs/puppet/cache/state/graphs
group = puppet
hiera_config = C:/ProgramData/PuppetLabs/puppet/etc/hiera.yaml
hostcert = 
C:/ProgramData/PuppetLabs/puppet/etc/ssl/certs/laptop-j2mk58hv.pem
hostcrl = C:/ProgramData/PuppetLabs/puppet/etc/ssl/crl.pem
hostcsr = 
C:/ProgramData/PuppetLabs/puppet/etc/ssl/certificate_requests/laptop-j2mk58hv.pem
hostprivkey = 
C:/ProgramData/PuppetLabs/puppet/etc/ssl/private_keys/laptop-j2mk58hv.pem
hostpubkey = 
C:/ProgramData/PuppetLabs/puppet/etc/ssl/public_keys/laptop-j2mk58hv.pem
http_connect_timeout = 120
http_debug = false
http_extra_headers = []
http_keepalive_timeout = 4
http_proxy_host = none
http_proxy_password = none
http_proxy_port = 3128
http_proxy_user = none
http_read_timeout = 600
http_user_agent = Puppet/7.20.0 Ruby/2.7.6-p219 (x64-mingw32)
ignore_plugin_errors = false
ignoremissingtypes = false
ignoreschedules = false
key_type = rsa
keylength = 4096
lastrunfile = C:/ProgramData/PuppetLabs/puppet/public/last_run_summary.yaml
lastrunreport = 
C:/ProgramData/PuppetLabs/puppet/cache/state/last_run_report.yaml
ldapattrs = all
ldapbase =
ldapclassattrs = puppetclass
ldapparentattr = parentnode
ldappassword =
ldapport = 389
ldapserver = ldap
ldapssl = false
ldapstackedattrs = puppetvar
ldapstring = (&(objectclass=puppetClient)(cn=%s))
ldaptls = false
ldapuser =
libdir = C:/ProgramData/PuppetLabs/puppet/cache/lib
localcacert = C:/ProgramData/PuppetLabs/puppet/etc/ssl/certs/ca.pem
localedest = C:/ProgramData/PuppetLabs/puppet/cache/locales

Re: [Puppet Users] Puppet agent is not running on Windows 11

[Stephanos Economides]

Thank you Martin for your feedback,

Best,

On Tuesday, November 1, 2022 at 9:39:52 AM UTC+2 Martin Alfke wrote:

> Hi Stephan’s,,
>
> You can not run puppetserver on Windows.
> Puppetserver is a Linux only process.
>
> If you run Windows only, you can make use of the puppetserver docker 
> container.
>
> hth,
> Martin
>
>
> On 31. Oct 2022, at 17:32, Stephanos Economides  
> wrote:
>
> Hi Puppet Users,
>
> I am a new user of the puppet software and I ask your help to tackle the 
> following problem:
>
> I have installed the puppet agent 7.20.0 as a standalone node that won't 
> connect to a master, on my notebook (Windows 11 Home).  
>
> I tried to run the puppet agent and I received an error (screenshot: 
> puppet_agent_error_1).
>
> Then  I used the "puppet agent --test" command from cmd (run it as 
> administrator) and  I received an error (screenshot: puppet_agent_error_2).
>
> Then I used the "puppet resource service puppetserver ensure=running" 
> command from cmd (run it as administrator) and I received the error "Error: 
> Will not start disabled service puppetserver without managing enable. 
> Specify 'enable => false' to override.".  I tried to override by using the 
> command "puppet resource service puppetserver enable=false" and then I used 
> again the "puppet resource service puppetserver ensure=running" command but 
> in vain (screenshot: puppet_agent_error_3).
>
> Then I created an inbound rule on Windows firewall for port 8140 but again 
> I received the same error "Error: Connection to 
> https://puppet:8140/puppet-ca/v1 failed, trying next route: Request to 
> https://puppet:8140/puppet-ca/v1 failed after 2.698 seconds: Failed to 
> open TCP connection to puppet:8140 (getaddrinfo: No such host is known. )".
>
> Lastly, I deactivated temporarily my Avast software but again connection 
> to puppet:8140 failed.
>
> Could you please help me to resolve this issue?
>
> Thank you in advance for your time.
>
> Best regards,
>
> Stephanos
>
> -- 
> 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/4918e75e-85ed-48cc-b650-617f0280c505n%40googlegroups.com
>  
> 
> .
> 
> 
>
>
>

-- 
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/96aa80e3-4c76-4301-b7ca-59ae9228a146n%40googlegroups.com.

Re: [Puppet Users] Puppet agent is not running on Windows 11

[Jim Moser]

What does the contents of your puppet.conf look like on the host. It
appears that the agent is trying to reach the hostname puppet but cannot
resolve the name in DNS or on the local host file. You should have entries
in the puppet.conf that looks something like this

[main]
server=myserver.mydomain.com

[agent]
certname=mynode.mydomain.com

On Mon, Oct 31, 2022, 12:05 PM Stephanos Economides <
noveltymarket...@gmail.com> wrote:

> Hi Puppet Users,
>
> I am a new user of the puppet software and I ask your help to tackle the
> following problem:
>
> I have installed the puppet agent 7.20.0 as a standalone node that won't
> connect to a master, on my notebook (Windows 11 Home).
>
> I tried to run the puppet agent and I received an error (screenshot:
> puppet_agent_error_1).
>
> Then  I used the "puppet agent --test" command from cmd (run it as
> administrator) and  I received an error (screenshot: puppet_agent_error_2).
>
> Then I used the "puppet resource service puppetserver ensure=running"
> command from cmd (run it as administrator) and I received the error "Error:
> Will not start disabled service puppetserver without managing enable.
> Specify 'enable => false' to override.".  I tried to override by using the
> command "puppet resource service puppetserver enable=false" and then I used
> again the "puppet resource service puppetserver ensure=running" command but
> in vain (screenshot: puppet_agent_error_3).
>
> Then I created an inbound rule on Windows firewall for port 8140 but again
> I received the same error "Error: Connection to
> https://puppet:8140/puppet-ca/v1 failed, trying next route: Request to
> https://puppet:8140/puppet-ca/v1 failed after 2.698 seconds: Failed to
> open TCP connection to puppet:8140 (getaddrinfo: No such host is known. )".
>
> Lastly, I deactivated temporarily my Avast software but again connection
> to puppet:8140 failed.
>
> Could you please help me to resolve this issue?
>
> Thank you in advance for your time.
>
> Best regards,
>
> Stephanos
>
> --
> 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/4918e75e-85ed-48cc-b650-617f0280c505n%40googlegroups.com
> 
> .
>

-- 
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/CADnkZSOKH9JF3%2BxLnhzN6Z2GDhHgv4%2B5d%3DZWQqTet8YOsjdRBw%40mail.gmail.com.

Re: [Puppet Users] Puppet agent is not running on Windows 11

[Martin Alfke]

Hi Stephan’s,,

You can not run puppetserver on Windows.
Puppetserver is a Linux only process.

If you run Windows only, you can make use of the puppetserver docker container.

hth,
Martin


> On 31. Oct 2022, at 17:32, Stephanos Economides  
> wrote:
> 
> Hi Puppet Users,
> 
> I am a new user of the puppet software and I ask your help to tackle the 
> following problem:
> 
> I have installed the puppet agent 7.20.0 as a standalone node that won't 
> connect to a master, on my notebook (Windows 11 Home).  
> 
> I tried to run the puppet agent and I received an error (screenshot: 
> puppet_agent_error_1).
> 
> Then  I used the "puppet agent --test" command from cmd (run it as 
> administrator) and  I received an error (screenshot: puppet_agent_error_2).
> 
> Then I used the "puppet resource service puppetserver ensure=running" command 
> from cmd (run it as administrator) and I received the error "Error: Will not 
> start disabled service puppetserver without managing enable. Specify 'enable 
> => false' to override.".  I tried to override by using the command "puppet 
> resource service puppetserver enable=false" and then I used again the "puppet 
> resource service puppetserver ensure=running" command but in vain 
> (screenshot: puppet_agent_error_3).
> 
> Then I created an inbound rule on Windows firewall for port 8140 but again I 
> received the same error "Error: Connection to 
> https://puppet:8140/puppet-ca/v1 failed, trying next route: Request to 
> https://puppet:8140/puppet-ca/v1 failed after 2.698 seconds: Failed to open 
> TCP connection to puppet:8140 (getaddrinfo: No such host is known. )".
> 
> Lastly, I deactivated temporarily my Avast software but again connection to 
> puppet:8140 failed.
> 
> Could you please help me to resolve this issue?
> 
> Thank you in advance for your time.
> 
> Best regards,
> 
> Stephanos
> 
> -- 
> 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/4918e75e-85ed-48cc-b650-617f0280c505n%40googlegroups.com
>  
> .
> 

-- 
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/4498CD1D-BCA3-45AF-AC17-D54A671B8633%40gmail.com.

[Puppet Users] puppet-agent 6 & 7 nightly builds for Fedora 36 (x86_64)

[Aria Li]

Hello,

We are happy to announce that puppet-agent nightly builds for Fedora 36
(x86_64) are now available at https://nightlies.puppet.com/yum/.

Please try them out and let us know if you have any questions!

Thank you,
-- 

Aria Li (she/her) | Associate Software Engineer, Puppet


Perforce Software

Visit us on: LinkedIn

| Twitter

| Facebook

| YouTube


-- 
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/CAM74YgDjaXu5HWQSX6FdCUZnHgSOPtWXcuDnQJtV4G3_U1AE0Q%40mail.gmail.com.

[Puppet Users] puppet-agent nightly builds for Windows 11 Enterprise

[Michael Hashizume]

Hello,

We are happy to announce that puppet-agent nightly builds are now tested
against Windows 11 Enterprise. Builds are available at
nightlies.puppetlabs.com/downloads/.

Please try them out and let us know if you have any questions.

Thank you,



Michael Hashizume (he/his) | Software Engineer, Puppet


Perforce Software


Visit us on: LinkedIn

| Twitter

| Facebook

| YouTube


-- 
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/CALi7aKaebZwjoLcmP35NX8M7OXDgGzQD8rHhDupgY%2Bx2vCAPxw%40mail.gmail.com.

[Puppet Users] puppet-agent 6 & 7 nightly builds for Ubuntu 22.04 (AMD64)

[Aria Li]

Hello,

We are happy to announce that puppet-agent nightly builds for Ubuntu 22.04
(AMD64) are now available at http://nightlies.puppetlabs.com/apt/.

Please try them out and let us know if you have any questions!

Thank you,

-- 

Aria Li (she/her) | Associate Software Engineer, Puppet


Perforce Software


P: +1 123.456.7890 | M: +1 123.456.7890 (optional)
Visit us on: LinkedIn

| Twitter

| Facebook

| YouTube


-- 
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/CAM74YgDvBLuDupq2QSs9Cd4F5Su8%3DnEwX5rP5jntERtAPzB9bg%40mail.gmail.com.

[Puppet Users] puppet-agent 6 & 7 nightly builds for macOS 12 (M1)

[Aria Li]

Hello,

We are happy to announce that puppet-agent nightly builds for macOS 12 (M1)
are now available at nightlies.puppetlabs.com/downloads/.

Please try them out and let us know if you have any questions!

Thank you,

*Aria Li (she/her)*
Associate Software Engineer, Puppet Agent
aria...@puppet.com

-- 
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/CAM74YgAERnZL96xdfAnAZ3rpMBRmS%2B_%3Dy_dVnfsaoHHhfsVv5Q%40mail.gmail.com.

[Puppet Users] puppet-agent 6 & 7 nightly builds for macOS 12 (Monterey) x86-64

[Aria Li]

Hello,

We are happy to announce that puppet-agent nightly builds for macOS 12
(Monterey) x86-64 are now available at nightlies.puppetlabs.com/downloads/.

Please try them out and let us know if you have any questions!

Thank you,

*Aria Li (she/her)*
Associate Software Engineer, Puppet Agent
aria...@puppet.com

-- 
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/CAM74YgB1eNts9V2MO-DydRygTARdqq6Crr-a0X%2B0Qv8ooujZxw%40mail.gmail.com.

[Puppet Users] puppet-agent 6 & 7 nightly builds for Red Hat Enterprise Linux 9 (beta) x86-64

[Michael Hashizume]

Hello,

We are happy to announce that puppet-agent nightly builds for Red Hat
Enterprise Linux 9 (beta) x86-64 are now available at
nightlies.puppetlabs.com/yum/.

Please try them out and let us know if you have any questions!

Thank you,

*Michael Hashizume*
Software Engineer, Puppet Agent
michael.hashiz...@puppet.com

-- 
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/CALi7aKZ7woNS%3D56v6R4Y05MNw5f5Q9Y867QZZiRy8gNqqPQprg%40mail.gmail.com.

[Puppet Users] puppet-agent 6 & 7 nightly builds for Alma and Rocky Linux 8

[Gabriel Nagy]

Hello,

We are happy to announce that AlmaLinux and Rocky Linux 8 64-bit are now
fully tested in our agent pipelines, so the Enterprise Linux 8 puppet-agent
nightly builds can safely be used on these OSes.

Nightly release packages are available under nightlies.puppet.com/yum.
Stable builds will also be available on yum.puppet.com starting with the
next puppet-agent release.

Please try them out and let us know if you have any questions!

Gabriel Nagy
Software Engineer - Puppet

-- 
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/CAALo1wHyYeZb%2B87vC32-V4LSYz1BjzRHMOq-PD2AJT-hwDpLxg%40mail.gmail.com.

Re: [Puppet Users] puppet-agent 6 & 7 nightly builds for Ubuntu 18.04 Bionic ARM64 architecture

['Dirk Heinrichs' via Puppet Users]

Am Dienstag, den 17.08.2021, 18:36 +0300 schrieb Gabriel Nagy:

> We are happy to announce that puppet-agent nightly builds for Ubuntu
> 18.04 Bionic ARM64 (aarch64) architecture are now available under
> 
> nightlies.puppet.com/apt. Stable builds will also be available on 
> apt.puppet.com starting with a future puppet-agent release.

What about 20.04? Any plans for Debian (10, 11) arm64 packages? See 
https://tickets.puppetlabs.com/browse/PA-3840

Bye...

Dirk
-- 
Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
Phone: +49 2226 15966 18
Email: dhein...@opentext.com
Website: www.recommind.de
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet.

-- 
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/58d376240908e43a28aa8bb8bca917315b16a88b.camel%40opentext.com.


signature.asc
Description: This is a digitally signed message part

[Puppet Users] puppet-agent 6 & 7 nightly builds for Ubuntu 18.04 Bionic ARM64 architecture

[Gabriel Nagy]

Hello,

We are happy to announce that puppet-agent nightly builds for Ubuntu 18.04
Bionic ARM64 (aarch64) architecture are now available under
nightlies.puppet.com/apt. Stable builds will also be available on
apt.puppet.com starting with a future puppet-agent release.

Please try them out and let us know if you have any questions!

Gabriel Nagy
Software Engineer - Puppet

-- 
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/CAALo1wHK31DWgdPOqEGRAwQ_yyDNHQ4CjC%2B1mM-xMv8616UY5A%40mail.gmail.com.

[Puppet Users] puppet-agent 6 & 7 nightly builds for macOS 11 M1/arm64

[Gabriel Nagy]

Hello,

We are happy to announce that puppet-agent nightly builds for macOS 11
(arm64/M1) are now available under nightlies.puppet.com/downloads/mac.
Please note that these builds are *NOT* tested on a nightly basis in our
CI, so you might run into issues here and there (you can follow PA-3904
 to keep track of our
progress to fix the current failing tests). We do not yet have an estimated
date for stable builds availability.

Please try them out and let us know if you have any questions!

Gabriel Nagy
Software Engineer - Puppet

-- 
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/CAALo1wG2CCd4LG%3Di%3D5kRrFP%3Dr7Bub9wUi0C86OTbbd7bP-1CfQ%40mail.gmail.com.

[Puppet Users] puppet-agent 6 & 7 nightly builds for Debian 11 Bullseye amd64

[Ciprian Badescu]

Hello,

We are happy to announce that puppet-agent nightly builds for Debian 11
Bullseye (amd64) are now available at nightlies.puppetlabs.com/apt/.

Please try them out and let us know if you have any questions!

Ciprian

-- 
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/CAKRR8C1fQ5bOgogpA3cgKjyQ31UFAQt_j01GU_MZ%2BShO2A-wmQ%40mail.gmail.com.

[Puppet Users] puppet-agent 6 & 7 nightly builds for Fedora 34 64-bit

[Gabriel Nagy]

Hello,

We are happy to announce that puppet-agent nightly builds for Fedora 34
(64-bit) are now available under nightlies.puppet.com/yum. Stable builds
will also be available on yum.puppet.com starting with the next
puppet-agent release.

Please try them out and let us know if you have any questions!

Gabriel Nagy
Software Engineer - Puppet

-- 
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/CAALo1wGqtG6f%3DACGpGBAQcpTf%2B2_8iODAcqMwRATrTSVH8Bwbg%40mail.gmail.com.

[Puppet Users] puppet-agent 6 & 7 nightly builds for EL 8 Power architecture

[Gabriel Nagy]

Hello,

We are happy to announce that puppet-agent nightly builds for Enterprise
Linux 8 Power (ppc64le) architecture are now available under
nightlies.puppet.com/yum. Stable builds will also be available on
yum.puppet.com starting with the next puppet-agent release.

Please try them out and let us know if you have any questions!

Gabriel Nagy
Software Engineer - Puppet

-- 
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/CAALo1wGCa9%3DRs3V3C73yt0KeBTqmkm5v_6EonkH9vcu5tZx0Lw%40mail.gmail.com.

[Puppet Users] Puppet agent run error "couldnt find valid string"

[nand...@gmail.com]

Hi all,

PE server version : PE 2019.8.5
Puppet agent version : 6.21.1 

Actually i have added profile class which calls hosts class and pass 
parameters to it .Then its been assigned to individual  nodegroup on 
console .
we were facing below 500 error while puppet agent run and that looks like 
validation of parameter as string .

I suspect this could be of Undef parameter validation but not sure what 
could be rectify this issue .

Can someone help me on what could be the error ?

Profile class :

class profile::ldap_hosts () {

 

  class { '::hosts':

  host_entries => {

"ldaps1-dev.com.net" => { ensure => 'absent' },

"ldaps2-dev.com.net  " => { ensure => 'absent' },

" ldaps3-dev.com.net " => { ensure => 'absent' },

" ldaps4-dev.com.net  " => { ensure => 'absent' },

}

}

 

}
hosts class :

# == Class: hosts

#

# Manage /etc/hosts

#

class hosts (

  $collect_all   = false,

  $enable_ipv4_localhost = true,

  $enable_ipv6_localhost = false,

  $enable_fqdn_entry = false,

  $use_fqdn  = true,

  $fqdn_host_aliases = $::hostname,

  $localhost_aliases = ['localhost',

'localhost4',

'localhost4.localdomain4'],

  $localhost6_aliases= ['localhost6',

'localhost6.localdomain6'],

  $purge_hosts   = false,

  $target= '/etc/hosts',

  $host_entries  = undef,

) {

 

 

  # validate type and convert string to boolean if necessary

  if is_string($collect_all) {

$collect_all_real = str2bool($collect_all)

  } else {

$collect_all_real = $collect_all

  }

 

  # validate type and convert string to boolean if necessary

  if is_string($enable_ipv4_localhost) {

$ipv4_localhost_enabled = str2bool($enable_ipv4_localhost)

  } else {

$ipv4_localhost_enabled = $enable_ipv4_localhost

  }

 

  # validate type and convert string to boolean if necessary

  if is_string($enable_ipv6_localhost) {

$ipv6_localhost_enabled = str2bool($enable_ipv6_localhost)

  } else {

$ipv6_localhost_enabled = $enable_ipv6_localhost

  }

 

  # validate type and convert string to boolean if necessary

  if is_string($enable_fqdn_entry) {

$fqdn_entry_enabled = str2bool($enable_fqdn_entry)

  } else {

$fqdn_entry_enabled = $enable_fqdn_entry

  }

 

  # validate type and convert string to boolean if necessary

  if is_string($use_fqdn) {

$use_fqdn_real = str2bool($use_fqdn)

  } else {

$use_fqdn_real = $use_fqdn

  }

 

  # validate type and convert string to boolean if necessary

  if is_string($purge_hosts) {

$purge_hosts_enabled = str2bool($purge_hosts)

  } else {

$purge_hosts_enabled = $purge_hosts

  }

 

  if $ipv4_localhost_enabled == true {

$localhost_ensure = 'present'

$localhost_ip = '127.0.0.1'

$my_localhost_aliases = $localhost_aliases

  } else {

$localhost_ensure = 'absent'

$localhost_ip = '127.0.0.1'

$my_localhost_aliases = undef

  }

 

  if $ipv6_localhost_enabled == true {

$localhost6_ensure = 'present'

$localhost6_ip = '::1'

$my_localhost6_aliases = $localhost6_aliases

  } else {

$localhost6_ensure = 'absent'

$localhost6_ip = '::1'

$my_localhost6_aliases = undef

  }

 

  if !is_string($my_localhost_aliases) and !is_array($my_localhost_aliases) 
{

fail('hosts::localhost_aliases must be a string or an array.')

  }

 

  if !is_string($my_localhost6_aliases) and 
!is_array($my_localhost6_aliases) {

fail('hosts::localhost6_aliases must be a string or an array.')

  }

 

  if $fqdn_entry_enabled == true {

$fqdn_ensure  = 'present'

$my_fqdn_host_aliases = $fqdn_host_aliases

$fqdn_ip  = $::ipaddress

  } else {

$fqdn_ensure  = 'absent'

$my_fqdn_host_aliases = []

$fqdn_ip  = $::ipaddress

  }

 

  Host {

target => $target,

  }

 

  host { 'localhost':

ensure => 'absent',

  }

 

  host { 'localhost.localdomain':

ensure   => $localhost_ensure,

host_aliases => $my_localhost_aliases,

ip   => $localhost_ip,

  }

 

  host { 'localhost6.localdomain6':

ensure   => $localhost6_ensure,

host_aliases => $my_localhost6_aliases,

ip   => $localhost6_ip,

  }

 

  if $use_fqdn_real == true {

@@host { $::fqdn:

  ensure   => $fqdn_ensure,

  host_aliases => $my_fqdn_host_aliases,

  ip   => $fqdn_ip,

}

 

case $collect_all_real {

  # collect all the exported Host resources

  true:  {

Host <<| |>>

  }

  # only collect the exported entry above

  default: {

Host <<| title == $::fqdn |>>

  }

}

  }

 

  resources { 'host':

Re: [Puppet Users] Puppet Agent Gem Install

[Martin Alfke]

Hi Tony,

yes, restarting puppetserver is required once you install a puppetserver gem.

Good to know that it is working.

Happy puppetizing,
Martin



> On 21. Oct 2020, at 18:44, Tony Wu  wrote:
> 
> Hi Martin,
> 
> Got it to work, it was indeed server side as you stated. Perhaps I just 
> forgot to restart it? I have no idea.
> 
> Much appreciated for your reply.
> 
> Take care,
> 
> Tony Wu
> 
>> On Oct 21, 2020, at 8:31 AM, Tony Wu > > wrote:
>> 
>> I did that too, but that still didn’t work. Let me double check again.
>> 
>> Best,
>> 
>> Tony Wu
>> 
>>> On Oct 20, 2020, at 10:51 PM, Martin Alfke >> > wrote:
>>> 
>>> Hi Tony,
>>> 
>>> puppet functions are executed on the puppet server.
>>> You need to install the gem within the puppet server
>>> 
>>> puppetserver gem install my gem
>>> 
>>> Hth,
>>> Martin
>>> 
>>> 
 On 20. Oct 2020, at 21:37, Tony Wu >>> > wrote:
 
 Hi,
 
 I have a agent side function that requires a gem, so I did:
 
 /opt/puppetlabs/puppet/bin/gem install my_gem
 
 If I do list, it shows the gem as being installed, but when invoking the 
 function it can't find it. Any suggestion?
 
 Thanks very much.
 
 -- 
 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/6b114e8d-8147-42d5-85a4-aa0ad381de25n%40googlegroups.com
  
 .
>>> 
>>> 
>>> -- 
>>> 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/14FED81F-75D7-4A60-B1DF-27FE8CC1D10C%40gmail.com
>>>  
>>> .
>> 
> 
> 
> -- 
> 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/9918480A-E045-4C00-92C2-B690ED1E3331%40gmail.com
>  
> .

-- 
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/4FF0AA96-15A4-47F5-A53F-E3FABD176480%40gmail.com.

Re: [Puppet Users] Puppet Agent Gem Install

[Tony Wu]

Hi Martin,

Got it to work, it was indeed server side as you stated. Perhaps I just forgot 
to restart it? I have no idea.

Much appreciated for your reply.

Take care,

Tony Wu

> On Oct 21, 2020, at 8:31 AM, Tony Wu  wrote:
> 
> I did that too, but that still didn’t work. Let me double check again.
> 
> Best,
> 
> Tony Wu
> 
>> On Oct 20, 2020, at 10:51 PM, Martin Alfke > > wrote:
>> 
>> Hi Tony,
>> 
>> puppet functions are executed on the puppet server.
>> You need to install the gem within the puppet server
>> 
>> puppetserver gem install my gem
>> 
>> Hth,
>> Martin
>> 
>> 
>>> On 20. Oct 2020, at 21:37, Tony Wu >> > wrote:
>>> 
>>> Hi,
>>> 
>>> I have a agent side function that requires a gem, so I did:
>>> 
>>> /opt/puppetlabs/puppet/bin/gem install my_gem
>>> 
>>> If I do list, it shows the gem as being installed, but when invoking the 
>>> function it can't find it. Any suggestion?
>>> 
>>> Thanks very much.
>>> 
>>> -- 
>>> 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/6b114e8d-8147-42d5-85a4-aa0ad381de25n%40googlegroups.com
>>>  
>>> .
>> 
>> 
>> -- 
>> 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/14FED81F-75D7-4A60-B1DF-27FE8CC1D10C%40gmail.com
>>  
>> .
> 

-- 
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/9918480A-E045-4C00-92C2-B690ED1E3331%40gmail.com.

Re: [Puppet Users] Puppet Agent Gem Install

[Tony Wu]

I did that too, but that still didn’t work. Let me double check again.

Best,

Tony Wu

> On Oct 20, 2020, at 10:51 PM, Martin Alfke  wrote:
> 
> Hi Tony,
> 
> puppet functions are executed on the puppet server.
> You need to install the gem within the puppet server
> 
> puppetserver gem install my gem
> 
> Hth,
> Martin
> 
> 
>> On 20. Oct 2020, at 21:37, Tony Wu > > wrote:
>> 
>> Hi,
>> 
>> I have a agent side function that requires a gem, so I did:
>> 
>> /opt/puppetlabs/puppet/bin/gem install my_gem
>> 
>> If I do list, it shows the gem as being installed, but when invoking the 
>> function it can't find it. Any suggestion?
>> 
>> Thanks very much.
>> 
>> -- 
>> 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/6b114e8d-8147-42d5-85a4-aa0ad381de25n%40googlegroups.com
>>  
>> .
> 
> 
> -- 
> 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/14FED81F-75D7-4A60-B1DF-27FE8CC1D10C%40gmail.com
>  
> .

-- 
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/607EF169-4FAF-460F-8FB2-94759F19E519%40gmail.com.

Re: [Puppet Users] Puppet Agent Gem Install

[Martin Alfke]

Hi Tony,

puppet functions are executed on the puppet server.
You need to install the gem within the puppet server

puppetserver gem install my gem

Hth,
Martin


> On 20. Oct 2020, at 21:37, Tony Wu  wrote:
> 
> Hi,
> 
> I have a agent side function that requires a gem, so I did:
> 
> /opt/puppetlabs/puppet/bin/gem install my_gem
> 
> If I do list, it shows the gem as being installed, but when invoking the 
> function it can't find it. Any suggestion?
> 
> Thanks very much.
> 
> -- 
> 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/6b114e8d-8147-42d5-85a4-aa0ad381de25n%40googlegroups.com
>  
> .

-- 
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/14FED81F-75D7-4A60-B1DF-27FE8CC1D10C%40gmail.com.

[Puppet Users] Puppet Agent Gem Install

[Tony Wu]

Hi,

I have a agent side function that requires a gem, so I did:

/opt/puppetlabs/puppet/bin/gem install my_gem

If I do list, it shows the gem as being installed, but when invoking the 
function it can't find it. Any suggestion?

Thanks very much.

-- 
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/6b114e8d-8147-42d5-85a4-aa0ad381de25n%40googlegroups.com.

[Puppet Users] puppet-agent version compatibility with puppet-server

[hai wu]

I am using puppet-server 6.7.1, and thinking if it would be ok to go
ahead and start using latest puppet-agent 6.12.0.

Is this latest puppet-agent 6.12.0 compatible with puppet-server 6.7.1?

Thanks,
Hai

-- 
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/CAJ1%3DnZeSLATWJ%2BGgqyA6o%2BL__a_GHavYk4-NwwV6WohrAq11LQ%40mail.gmail.com.

[Puppet Users] Puppet Agent 6.X on Debian 10 armel

[Frédéric Lespez]

Hi,

I would like to install a Puppet Agent 6.X on a Debian 10 armel platform.
There is no official package from Puppetlabs and only Puppet Agent 5.5 is 
packaged in Debian.

So I am looking for to build myself a Puppet Agent 6.X for Debian 10 armel.

I have found these two repositories:
https://github.com/puppetlabs/puppet-agent
https://github.com/puppetlabs/puppet-runtime

But these build systems need access to internal Puppetlabs infrastructure 
(Like Puppetlabs Artifactory instances).

Doesn't anybody could give a lead on how to achieve this ?

Thanks in advance.
Regards,
Fred

-- 
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/8e722c65-a5b9-4af6-ac80-b1caedb91219%40googlegroups.com.

Re: [Puppet Users] Puppet agent fails collect packages for puppet "Cannot collect packages for Puppet::Type::package::ProviderYum provider; Failed to list packages"

[Josh Cooper]

On Wed, Oct 16, 2019 at 9:28 AM Ashwinkumar Kandasamy <
kashwinkuma...@gmail.com> wrote:

> Hi all,
>  In my puppet enterprise machine when ever i run the puppet agent -t
> command it shows below error,
>  # puppet agent -t
> Info: Using configured environment 'production'
> Info: Retrieving pluginfacts
> Info: Retrieving plugin
> Info: Retrieving locales
> Info: Loading facts
> Error: Cannot collect packages for Puppet::Type:[image: :package:]:ProviderYum
> provider; Failed to list packages
> Info: Caching catalog for ,puppetmaster>
> Info: Applying configuration version '1571212307'
> Error: Could not prefetch package provider 'yum': Failed to list packages
> Error: Failed to apply catalog: Failed to list packages
>
>
> PE version -2019.0
>
> --
> 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/a41bc387-75f1-499c-9683-ed423d783240%40googlegroups.com
> 
> .
>

Try running "puppet resource package --param provider --debug" to see which
yum command fails.

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

-- 
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%2Bu97u%3D1wPXzPQrSP5aZe3fJG2rp8gV9%2B960%3DrBrQV0koXR6mw%40mail.gmail.com.

[Puppet Users] Puppet agent fails collect packages for puppet "Cannot collect packages for Puppet::Type::package::ProviderYum provider; Failed to list packages"

[Ashwinkumar Kandasamy]

Hi all,
 In my puppet enterprise machine when ever i run the puppet agent -t 
command it shows below error,
 # puppet agent -t
Info: Using configured environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Retrieving locales
Info: Loading facts
Error: Cannot collect packages for Puppet::Type:[image: :package:]:ProviderYum 
provider; Failed to list packages
Info: Caching catalog for ,puppetmaster>
Info: Applying configuration version '1571212307'
Error: Could not prefetch package provider 'yum': Failed to list packages
Error: Failed to apply catalog: Failed to list packages


PE version -2019.0

-- 
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/a41bc387-75f1-499c-9683-ed423d783240%40googlegroups.com.

Re: [EXTERNAL] - [Puppet Users] Puppet agent is not applying changes

[Josh Cooper]

Yes agreed, there are two issues on that:
https://tickets.puppetlabs.com/browse/SERVER-1717 and
https://tickets.puppetlabs.com/browse/PUP-7102. We tried to fix it earlier,
but had to revert due to acceptance test failures. The need for world
readable (or changing the owner or group to puppet) is because puppetserver
runs as the puppet user.

On Tue, Oct 1, 2019 at 8:57 AM Dan Crisp  wrote:

> Thanks to all that contributed.  I managed to solve the issue.  Transpires
> that the permissions  on the files and directories (0640 for the most part)
> was not sufficient.  I had to ensure that all files in question had 0644
> and directories at 0755 permissions set to get this to work.  A simple
> permission denied error somewhere among the logs would of been helpful!!
>
> Thanks again,
> Dan.
>
> On Sunday, September 29, 2019 at 9:19:13 PM UTC+1, Andreas Ntaflos wrote:
>>
>> On 28.09.19 12:15, Martin Alfke wrote:
>> > Hi Dirk,
>> >
>> > you are including class accounts within node default classification.
>> > The accounts module does not do anything unless you add data to it.
>> >
>> > Please look at https://github.com/puppetlabs/puppetlabs-accounts and
>> check if the following example is working:
>>
>> It doesn't look like Dan is using the puppetlabs-accounts module. His
>> accounts module just creates a user and a group (copy/pasting the code
>> from the initial post):
>>
>> # more
>> /etc/puppetlabs/code/environments/production/modules/accounts/manifests/init.pp
>>
>> class accounts {
>>
>>   include accounts::groups
>>
>>   user { 'djc72uk':
>> ensure  => present,
>> home=> '/home/djc72uk',
>> shell   => '/bin/bash',
>> managehome  => true,
>> gid => 'djc72uk',
>>   }
>>
>> }
>>
>> # more
>> /etc/puppetlabs/code/environments/production/modules/accounts/manifests/groups.pp
>>
>> class accounts::groups {
>>
>>   group { 'djc72uk':
>> ensure  => present,
>>   }
>> }
>>
>> Andreas
>>
>> --
> 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/4a709aee-0057-4498-92f8-7b24ec4a31b4%40googlegroups.com
> 
> .
>


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

Join us for Puppetize PDX  9-10 October.

-- 
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%2Bu97umX0td38gQ4WOY7qAgVkPFujDxFrxPkjk1PySweGd-%3Dng%40mail.gmail.com.

Re: [EXTERNAL] - [Puppet Users] Puppet agent is not applying changes

[Dan Crisp]

Thanks to all that contributed.  I managed to solve the issue.  Transpires 
that the permissions  on the files and directories (0640 for the most part) 
was not sufficient.  I had to ensure that all files in question had 0644 
and directories at 0755 permissions set to get this to work.  A simple 
permission denied error somewhere among the logs would of been helpful!!

Thanks again,
Dan.

On Sunday, September 29, 2019 at 9:19:13 PM UTC+1, Andreas Ntaflos wrote:
>
> On 28.09.19 12:15, Martin Alfke wrote: 
> > Hi Dirk, 
> > 
> > you are including class accounts within node default classification. 
> > The accounts module does not do anything unless you add data to it. 
> > 
> > Please look at https://github.com/puppetlabs/puppetlabs-accounts and 
> check if the following example is working: 
>
> It doesn't look like Dan is using the puppetlabs-accounts module. His 
> accounts module just creates a user and a group (copy/pasting the code 
> from the initial post): 
>
> # more 
> /etc/puppetlabs/code/environments/production/modules/accounts/manifests/init.pp
>  
>
> class accounts { 
>
>   include accounts::groups 
>
>   user { 'djc72uk': 
> ensure  => present, 
> home=> '/home/djc72uk', 
> shell   => '/bin/bash', 
> managehome  => true, 
> gid => 'djc72uk', 
>   } 
>
> } 
>
> # more 
> /etc/puppetlabs/code/environments/production/modules/accounts/manifests/groups.pp
>  
>
> class accounts::groups { 
>
>   group { 'djc72uk': 
> ensure  => present, 
>   } 
> } 
>
> Andreas 
>
>

-- 
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/4a709aee-0057-4498-92f8-7b24ec4a31b4%40googlegroups.com.

Re: [EXTERNAL] - [Puppet Users] Puppet agent is not applying changes

[Dan Crisp]

Thanks to all that contributed.  I managed to solve the issue.  Transpires 
that the permissions  on the files and directories (0644 for the most part) 
was not sufficient.  I had to ensure that all files in question had 0644 
and directories at 0755 permissions set to get this to work.  A simple 
permission denied error somewhere among the logs would of been helpful!!

Thanks again,
Dan.

On Sunday, September 29, 2019 at 9:19:13 PM UTC+1, Andreas Ntaflos wrote:
>
> On 28.09.19 12:15, Martin Alfke wrote: 
> > Hi Dirk, 
> > 
> > you are including class accounts within node default classification. 
> > The accounts module does not do anything unless you add data to it. 
> > 
> > Please look at https://github.com/puppetlabs/puppetlabs-accounts and 
> check if the following example is working: 
>
> It doesn't look like Dan is using the puppetlabs-accounts module. His 
> accounts module just creates a user and a group (copy/pasting the code 
> from the initial post): 
>
> # more 
> /etc/puppetlabs/code/environments/production/modules/accounts/manifests/init.pp
>  
>
> class accounts { 
>
>   include accounts::groups 
>
>   user { 'djc72uk': 
> ensure  => present, 
> home=> '/home/djc72uk', 
> shell   => '/bin/bash', 
> managehome  => true, 
> gid => 'djc72uk', 
>   } 
>
> } 
>
> # more 
> /etc/puppetlabs/code/environments/production/modules/accounts/manifests/groups.pp
>  
>
> class accounts::groups { 
>
>   group { 'djc72uk': 
> ensure  => present, 
>   } 
> } 
>
> Andreas 
>
>

-- 
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/afc42c9d-0604-4cfc-86eb-356ea9619594%40googlegroups.com.

Re: [EXTERNAL] - [Puppet Users] Puppet agent is not applying changes

[Andreas Ntaflos]

On 28.09.19 12:15, Martin Alfke wrote:
> Hi Dirk,
> 
> you are including class accounts within node default classification.
> The accounts module does not do anything unless you add data to it.
> 
> Please look at https://github.com/puppetlabs/puppetlabs-accounts and check if 
> the following example is working:

It doesn't look like Dan is using the puppetlabs-accounts module. His
accounts module just creates a user and a group (copy/pasting the code
from the initial post):

# more
/etc/puppetlabs/code/environments/production/modules/accounts/manifests/init.pp
class accounts {

  include accounts::groups

  user { 'djc72uk':
ensure  => present,
home=> '/home/djc72uk',
shell   => '/bin/bash',
managehome  => true,
gid => 'djc72uk',
  }

}

# more
/etc/puppetlabs/code/environments/production/modules/accounts/manifests/groups.pp
class accounts::groups {

  group { 'djc72uk':
ensure  => present,
  }
}

Andreas

-- 
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/f8268645-38fd-16c9-9485-60ca93debfaa%40ptmx.org.


signature.asc
Description: OpenPGP digital signature

Re: [EXTERNAL] - [Puppet Users] Puppet agent is not applying changes

[Martin Alfke]

Hi Dirk,

you are including class accounts within node default classification.
The accounts module does not do anything unless you add data to it.

Please look at https://github.com/puppetlabs/puppetlabs-accounts and check if 
the following example is working:

node default {
  accounts::user { 'dan': }
  accounts::user { 'morgan': }
}

This should create two accounts on the nodes:
User 'dan' and user 'morgen'

hth,
Martin


> On 27. Sep 2019, at 23:01, Andreas Ntaflos  wrote:
> 
> On 27.09.19 18:11, Dan Crisp wrote:
>> Thanks for the reply John,
>> 
>> The issue still persists unfortunately.
>> 
>> I've ensured that Selinux isn't enforcing on both the server side and
>> client and then restarted the Puppet service on the master server.  The
>> server logs whilst running the agent read as follows:
> 
> Are you positive the user and group really haven't been created?
> 
> And have you changed
> 
> node 'default' { ... }
> 
> to
> 
> node default { ... }
> 
> i.e. without the single quotes, as suggested? And afterwards restarted
> the Puppetserver process by means of, e.g. systemctl restart puppetserver?
> 
> If so, and this hasn't helped, you may want to try to narrow the problem
> down by simplifying the default node manifest even more, by making
> site.pp look like this (verbatim):
> 
> node default {
>  fail('Failing deliberately on default node manifest')
> }
> 
> Don't forget to restart the Puppetserver after that to make sure the
> change is picked up.
> 
> When you then run the Puppet agent on the troublesome node it should
> fail hard with the message defined above. If it does then you know at
> least that site.pp is read and a catalog is created and applied for that
> node. If it does not then there must be something else amiss that is not
> obvious from the information and details you posted.
> 
> HTH
> 
> Andreas
> 
> -- 
> 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/48f7aa63-ed60-d5c8-d36c-d302c01d4130%40ptmx.org.

-- 
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/D57301FD-70C8-4C9B-B504-CD7C8AFF2E0C%40gmail.com.

Re: [EXTERNAL] - [Puppet Users] Puppet agent is not applying changes

[Andreas Ntaflos]

On 27.09.19 18:11, Dan Crisp wrote:
> Thanks for the reply John,
> 
> The issue still persists unfortunately.
> 
> I've ensured that Selinux isn't enforcing on both the server side and
> client and then restarted the Puppet service on the master server.  The
> server logs whilst running the agent read as follows:

Are you positive the user and group really haven't been created?

And have you changed

node 'default' { ... }

to

node default { ... }

i.e. without the single quotes, as suggested? And afterwards restarted
the Puppetserver process by means of, e.g. systemctl restart puppetserver?

If so, and this hasn't helped, you may want to try to narrow the problem
down by simplifying the default node manifest even more, by making
site.pp look like this (verbatim):

node default {
  fail('Failing deliberately on default node manifest')
}

Don't forget to restart the Puppetserver after that to make sure the
change is picked up.

When you then run the Puppet agent on the troublesome node it should
fail hard with the message defined above. If it does then you know at
least that site.pp is read and a catalog is created and applied for that
node. If it does not then there must be something else amiss that is not
obvious from the information and details you posted.

HTH

Andreas

-- 
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/48f7aa63-ed60-d5c8-d36c-d302c01d4130%40ptmx.org.


signature.asc
Description: OpenPGP digital signature

Re: [EXTERNAL] - [Puppet Users] Puppet agent is not applying changes

[Dan Crisp]

Thanks for the reply John,

The issue still persists unfortunately.

I've ensured that Selinux isn't enforcing on both the server side and 
client and then restarted the Puppet service on the master server.  The 
server logs whilst running the agent read as follows:

10.20.25.83 - - - 27/Sep/2019:16:06:43 + "GET 
/puppet/v3/node/lhcadvdeveye05.fixnetix.com?environment=production_uuid=4d2c88b1-2aec-45a5-bc7e-407c2ad8229e_on_404=true
 
HTTP/1.1" 200 13535 10.20.25.83 10.20.25.83 8140 109
10.20.25.83 - - - 27/Sep/2019:16:06:43 + "GET 
/puppet/v3/file_metadatas/pluginfacts?environment=production=follow=true_permissions=use=.svn=CVS=.git=.hg_type=md5
 
HTTP/1.1" 200 220 10.20.25.83 10.20.25.83 8140 25
10.20.25.83 - - - 27/Sep/2019:16:06:43 + "GET 
/puppet/v3/file_metadatas/plugins?environment=production=follow=true_permissions=ignore=.svn=CVS=.git=.hg_type=md5
 
HTTP/1.1" 200 224 10.20.25.83 10.20.25.83 8140 16
10.20.25.83 - - - 27/Sep/2019:16:06:44 + "GET 
/puppet/v3/file_metadatas/locales?environment=production=follow=true_permissions=ignore=.svn=CVS=.git=.hg=%2A.pot=config.yaml_type=md5
 
HTTP/1.1" 200 224 10.20.25.83 10.20.25.83 8140 20
2019-09-27 16:06:44,620 INFO  [puppetserver] Puppet Compiled catalog for 
lhcadvdeveye05.fixnetix.com in environment production in 0.10 seconds
10.20.25.83 - - - 27/Sep/2019:16:06:44 + "POST 
/puppet/v3/catalog/lhcadvdeveye05.fixnetix.com?environment=production 
HTTP/1.1" 200 612 10.20.25.83 10.20.25.83 8140 249
10.20.25.83 - - - 27/Sep/2019:16:06:45 + "PUT 
/puppet/v3/report/lhcadvdeveye05.fixnetix.com?environment=production& 
HTTP/1.1" 200 9 10.20.25.83 10.20.25.83 8140 92

Unfortunately, I don't see anything untoward here nor anything helpful that 
contributes to resolving the issue.

Thanks,
Dan.

On Friday, September 27, 2019 at 2:21:32 PM UTC+1, jcbollinger wrote:
>
>
>
> On Friday, September 27, 2019 at 7:20:51 AM UTC-5, Dan Crisp wrote:
>>
>> Please see below.  Apologies, there is a lot of detail here:
>>
>> Debug: Using settings: adding file resource 'confdir': 
>> 'File[/etc/puppetlabs/puppet]{:path=>"/etc/puppetlabs/puppet", 
>> :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
>>
>
> [...]
>
> If the (elided) log messages presented were *all* the log messages 
> emitted, then they depict the agent applying an empty catalog, which is of 
> course consistent with not changing anything.  All the resources shown are 
> generated locally by the agent.  You should be able to confirm that by 
> looking at the catalog itself, which you will find, by default, in a file 
> in /opt/puppetlabs/puppet/cache/client_data/catalog.
>
> If you're making changes to your manifest set but not seeing any effect at 
> the agent then there are several possibilities, but the most likely issue 
> is server-side caching.  Before tweaking the cache configuration, however, 
> the easiest way to test this hypothesis is to flush the cache by restarting 
> the puppetserver service on the master.  (That's not the only way, but it's 
> quick and easy, and you don't need to learn anything new to do it.)
>
> If that indeed solves the problem then you'll want to adjust the 
> environment_timeout 
>  
> configuration setting on the master.  For the time being, I would suggest 
> setting it to 0 to disable caching altogether.  This is also supposed to be 
> the default if the setting is not explicitly specified, however.
>
> ---
>
> If that doesn't turn out to be the issue, then do have a look at the 
> master's logs.  You should confirm that it is logging catalog requests from 
> the agent in question (else they must be going to a different master), and 
> you should look for any messages providing a clue about the issue.  It may 
> be helpful to turn up puppetserver's log level to get more detailed 
> information.
>
> If that's also unavailing then my last suggestion would be to confirm that 
> the puppetserver process can successfully access everything in the 
> environment directory.  Check file ownership, mode, ACLs, SELinux context, 
> and anything else that affects whether the puppetserver can read the files 
> and traverse (all) the directories.  I would pay special attention to your 
> one manifest file, because that's the most likely one to be messed up in 
> this regard.
>
>
> 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/558c4849-87b4-41d9-b5a7-97e3e7e0896c%40googlegroups.com.

Re: [EXTERNAL] - [Puppet Users] Puppet agent is not applying changes

[jcbollinger]

On Friday, September 27, 2019 at 7:20:51 AM UTC-5, Dan Crisp wrote:
>
> Please see below.  Apologies, there is a lot of detail here:
>
> Debug: Using settings: adding file resource 'confdir': 
> 'File[/etc/puppetlabs/puppet]{:path=>"/etc/puppetlabs/puppet", 
> :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
>

[...]

If the (elided) log messages presented were *all* the log messages emitted, 
then they depict the agent applying an empty catalog, which is of course 
consistent with not changing anything.  All the resources shown are 
generated locally by the agent.  You should be able to confirm that by 
looking at the catalog itself, which you will find, by default, in a file 
in /opt/puppetlabs/puppet/cache/client_data/catalog.

If you're making changes to your manifest set but not seeing any effect at 
the agent then there are several possibilities, but the most likely issue 
is server-side caching.  Before tweaking the cache configuration, however, 
the easiest way to test this hypothesis is to flush the cache by restarting 
the puppetserver service on the master.  (That's not the only way, but it's 
quick and easy, and you don't need to learn anything new to do it.)

If that indeed solves the problem then you'll want to adjust the 
environment_timeout 
 
configuration setting on the master.  For the time being, I would suggest 
setting it to 0 to disable caching altogether.  This is also supposed to be 
the default if the setting is not explicitly specified, however.

---

If that doesn't turn out to be the issue, then do have a look at the 
master's logs.  You should confirm that it is logging catalog requests from 
the agent in question (else they must be going to a different master), and 
you should look for any messages providing a clue about the issue.  It may 
be helpful to turn up puppetserver's log level to get more detailed 
information.

If that's also unavailing then my last suggestion would be to confirm that 
the puppetserver process can successfully access everything in the 
environment directory.  Check file ownership, mode, ACLs, SELinux context, 
and anything else that affects whether the puppetserver can read the files 
and traverse (all) the directories.  I would pay special attention to your 
one manifest file, because that's the most likely one to be messed up in 
this regard.


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/bd705228-5459-43c6-9032-104dace92dee%40googlegroups.com.

Re: [Puppet Users] Puppet agent is not applying changes

[Dan Crisp]

No.  I only have 
/etc/puppetlabs/code/environments/production/manifests/site.pp

On Friday, September 27, 2019 at 1:03:20 PM UTC+1, Dirk Heinrichs wrote:
>
> Am Freitag, den 27.09.2019, 11:50 + schrieb Dirk Heinrichs:
>
> Am Freitag, den 27.09.2019, 03:43 -0700 schrieb Dan Crisp:
>
> This file does nothing.  All the lines therein are commented out.  In 
> fact, I have in the past moved this file out of the way then put it back 
> just to rule out it was doing anything weird.
>
>
> OK, just wanted to make sure it doesn't contain any strange configuration 
> for that environment. Not sure what else could be the problem. Could you 
> run the agent with --debug and post the relevant lines involving your user 
> resource (if any)?
>
>
> Oh, and do you, by chance, have a file 
> /etc/puppetlabs/code/manifests/site.pp? Mine has just the following content 
> (might as well be empty):
>
> # site.pp must exist (puppet #15106, foreman #1708)
>
> Bye...
>
> Dirk
>
> -- 
>
> *Dirk Heinrichs*
> Senior Systems Engineer, Delivery Pipeline
> OpenText ™ Discovery | Recommind
> *Phone*: +49 2226 15966 18
> *Email*: dhei...@opentext.com 
> *Website*: www.recommind.de
> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
> Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
> Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
> This e-mail may contain confidential and/or privileged information. If you 
> are not the intended recipient (or have received this e-mail in error) 
> please notify the sender immediately and destroy this e-mail. Any 
> unauthorized copying, disclosure or distribution of the material in this 
> e-mail is strictly forbidden
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail 
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und 
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte 
> Weitergabe dieser Mail sind nicht gestattet.
>

-- 
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/4a476fc2-2daf-493f-9767-dee4bcb70576%40googlegroups.com.

Re: [EXTERNAL] - [Puppet Users] Puppet agent is not applying changes

[Dan Crisp]

Please see below.  Apologies, there is a lot of detail here:

Debug: Using settings: adding file resource 'confdir': 
'File[/etc/puppetlabs/puppet]{:path=>"/etc/puppetlabs/puppet", 
:ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'codedir': 
'File[/etc/puppetlabs/code]{:path=>"/etc/puppetlabs/code", 
:ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'vardir': 
'File[/opt/puppetlabs/puppet/cache]{:path=>"/opt/puppetlabs/puppet/cache", 
:owner=>"root", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, 
:backup=>false}'
Debug: Using settings: adding file resource 'logdir': 
'File[/var/log/puppetlabs/puppet]{:path=>"/var/log/puppetlabs/puppet", 
:mode=>"750", :owner=>"root", :ensure=>:directory, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'statedir': 
'File[/opt/puppetlabs/puppet/cache/state]{:path=>"/opt/puppetlabs/puppet/cache/state",
 
:mode=>"1755", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, 
:backup=>false}'
Debug: Using settings: adding file resource 'rundir': 
'File[/var/run/puppetlabs]{:path=>"/var/run/puppetlabs", :mode=>"755", 
:owner=>"root", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, 
:backup=>false}'
Debug: Using settings: adding file resource 'libdir': 
'File[/opt/puppetlabs/puppet/cache/lib]{:path=>"/opt/puppetlabs/puppet/cache/lib",
 
:ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'hiera_config': 
'File[/etc/puppetlabs/puppet/hiera.yaml]{:path=>"/etc/puppetlabs/puppet/hiera.yaml",
 
:ensure=>:file, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'preview_outputdir': 
'File[/opt/puppetlabs/puppet/cache/preview]{:path=>"/opt/puppetlabs/puppet/cache/preview",
 
:mode=>"750", :owner=>"root", :ensure=>:directory, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'certdir': 
'File[/etc/puppetlabs/puppet/ssl/certs]{:path=>"/etc/puppetlabs/puppet/ssl/certs",
 
:mode=>"755", :owner=>"root", :ensure=>:directory, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'ssldir': 
'File[/etc/puppetlabs/puppet/ssl]{:path=>"/etc/puppetlabs/puppet/ssl", 
:mode=>"771", :owner=>"root", :ensure=>:directory, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'publickeydir': 
'File[/etc/puppetlabs/puppet/ssl/public_keys]{:path=>"/etc/puppetlabs/puppet/ssl/public_keys",
 
:mode=>"755", :owner=>"root", :ensure=>:directory, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'requestdir': 
'File[/etc/puppetlabs/puppet/ssl/certificate_requests]{:path=>"/etc/puppetlabs/puppet/ssl/certificate_requests",
 
:mode=>"755", :owner=>"root", :ensure=>:directory, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'privatekeydir': 
'File[/etc/puppetlabs/puppet/ssl/private_keys]{:path=>"/etc/puppetlabs/puppet/ssl/private_keys",
 
:mode=>"750", :owner=>"root", :ensure=>:directory, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'privatedir': 
'File[/etc/puppetlabs/puppet/ssl/private]{:path=>"/etc/puppetlabs/puppet/ssl/private",
 
:mode=>"750", :owner=>"root", :ensure=>:directory, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'hostcert': 
'File[/etc/puppetlabs/puppet/ssl/certs/lhcadvdeveye05.fixnetix.com.pem]{:path=>"/etc/puppetlabs/puppet/ssl/certs/lhcadvdeveye05.fixnetix.com.pem",
 
:mode=>"644", :owner=>"root", :ensure=>:file, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'hostprivkey': 
'File[/etc/puppetlabs/puppet/ssl/private_keys/lhcadvdeveye05.fixnetix.com.pem]{:path=>"/etc/puppetlabs/puppet/ssl/private_keys/lhcadvdeveye05.fixnetix.com.pem",
 
:mode=>"640", :owner=>"root", :ensure=>:file, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'localcacert': 
'File[/etc/puppetlabs/puppet/ssl/certs/ca.pem]{:path=>"/etc/puppetlabs/puppet/ssl/certs/ca.pem",
 
:mode=>"644", :owner=>"root", :ensure=>:file, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'hostcrl': 
'File[/etc/puppetlabs/puppet/ssl/crl.pem]{:path=>"/etc/puppetlabs/puppet/ssl/crl.pem",
 
:mode=>"644", :owner=>"root", :ensure=>:file, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'statefile': 
'File[/opt/puppetlabs/puppet/cache/state/state.yaml]{:path=>"/opt/puppetlabs/puppet/cache/state/state.yaml",
 
:mode=>"660", :ensure=>:file, :loglevel=>:debug, :links=>:follow, 
:backup=>false}'
Debug: Using settings: 

Re: [Puppet Users] Puppet agent is not applying changes

[Dirk Heinrichs]

Am Freitag, den 27.09.2019, 11:50 + schrieb Dirk Heinrichs:

Am Freitag, den 27.09.2019, 03:43 -0700 schrieb Dan Crisp:

This file does nothing.  All the lines therein are commented out.  In fact, I 
have in the past moved this file out of the way then put it back just to rule 
out it was doing anything weird.

OK, just wanted to make sure it doesn't contain any strange configuration for 
that environment. Not sure what else could be the problem. Could you run the 
agent with --debug and post the relevant lines involving your user resource (if 
any)?

Oh, and do you, by chance, have a file /etc/puppetlabs/code/manifests/site.pp? 
Mine has just the following content (might as well be empty):

# site.pp must exist (puppet #15106, foreman #1708)

Bye...

Dirk

--

Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
Phone: +49 2226 15966 18
Email: dhein...@opentext.com
Website: www.recommind.de
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet.

-- 
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/df404847db203d12ac6374f9876c8a6a1db64c16.camel%40opentext.com.

Re: [Puppet Users] Puppet agent is not applying changes

[Dirk Heinrichs]

Am Freitag, den 27.09.2019, 03:43 -0700 schrieb Dan Crisp:

This file does nothing.  All the lines therein are commented out.  In fact, I 
have in the past moved this file out of the way then put it back just to rule 
out it was doing anything weird.

OK, just wanted to make sure it doesn't contain any strange configuration for 
that environment. Not sure what else could be the problem. Could you run the 
agent with --debug and post the relevant lines involving your user resource (if 
any)?

Bye...

Dirk

--

Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
Phone: +49 2226 15966 18
Email: dhein...@opentext.com
Website: www.recommind.de
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet.

-- 
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/c7f180603abc390a27d88a494bd172675a6d4e28.camel%40opentext.com.

Re: [EXTERNAL] - [Puppet Users] Puppet agent is not applying changes

[Dan Crisp]

This file does nothing.  All the lines therein are commented out.  In fact, 
I have in the past moved this file out of the way then put it back just to 
rule out it was doing anything weird.

Dan.

On Friday, September 27, 2019 at 10:58:49 AM UTC+1, Dirk Heinrichs wrote:
>
> Am Donnerstag, den 26.09.2019, 06:20 -0700 schrieb Dan Crisp:
>
> /etc/puppetlabs/code/environments/production:
> total 20
> -rw-r--r--. 1 root root  808 Sep 25 20:47 environment.conf
>
>
> What does this one contain? I don't have these in my environments.
>
> Bye...
>
> Dirk
>
> -- 
>
> *Dirk Heinrichs*
> Senior Systems Engineer, Delivery Pipeline
> OpenText ™ Discovery | Recommind
> *Phone*: +49 2226 15966 18
> *Email*: dhei...@opentext.com 
> *Website*: www.recommind.de
> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
> Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
> Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
> This e-mail may contain confidential and/or privileged information. If you 
> are not the intended recipient (or have received this e-mail in error) 
> please notify the sender immediately and destroy this e-mail. Any 
> unauthorized copying, disclosure or distribution of the material in this 
> e-mail is strictly forbidden
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail 
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und 
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte 
> Weitergabe dieser Mail sind nicht gestattet.
>

-- 
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/d431a657-2a6c-4c19-9eb1-46298447d025%40googlegroups.com.

Re: [EXTERNAL] - [Puppet Users] Puppet agent is not applying changes

[Dirk Heinrichs]

Am Donnerstag, den 26.09.2019, 06:20 -0700 schrieb Dan Crisp:

/etc/puppetlabs/code/environments/production:
total 20
-rw-r--r--. 1 root root  808 Sep 25 20:47 environment.conf

What does this one contain? I don't have these in my environments.

Bye...

Dirk

--

Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
Phone: +49 2226 15966 18
Email: dhein...@opentext.com
Website: www.recommind.de
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet.

-- 
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/9df7ad5e0e508fd9e4767896d50fd884a1b1ebe2.camel%40opentext.com.

Re: [Puppet Users] Puppet agent is not applying changes

[Dan Crisp]

Thank you Dirk.  However the same issue persists.  I even intentionally 
updated the site.pp with invalid syntax hoping that consequently, the agent 
run would fail and through a error.  The site.pp was updated like so:

node default {}
  include accounts
}
}

Agent still runs:

# puppet agent --no-daemonize --verbose --onetime
Info: Using configured environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Retrieving locales
Info: Caching catalog for lhcadvdeveye05.xxx.com
Info: Applying configuration version '1569503223'
Notice: Applied catalog in 0.15 seconds




On Friday, September 27, 2019 at 10:22:56 AM UTC+1, Dirk Heinrichs wrote:
>
> Am Donnerstag, den 26.09.2019, 06:20 -0700 schrieb Dan Crisp:
>
> node 'default' {
>
>
> Should be "node default {"
>
> HTH...
>
> Dirk
>
> -- 
>
> *Dirk Heinrichs*
> Senior Systems Engineer, Delivery Pipeline
> OpenText ™ Discovery | Recommind
> *Phone*: +49 2226 15966 18
> *Email*: dhei...@opentext.com 
> *Website*: www.recommind.de
> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
> Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
> Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
> This e-mail may contain confidential and/or privileged information. If you 
> are not the intended recipient (or have received this e-mail in error) 
> please notify the sender immediately and destroy this e-mail. Any 
> unauthorized copying, disclosure or distribution of the material in this 
> e-mail is strictly forbidden
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail 
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und 
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte 
> Weitergabe dieser Mail sind nicht gestattet.
>

-- 
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/4995e256-5300-49a7-bebc-1629b7c3f20a%40googlegroups.com.

Re: [Puppet Users] Puppet agent is not applying changes

[Dirk Heinrichs]

Am Donnerstag, den 26.09.2019, 06:20 -0700 schrieb Dan Crisp:

node 'default' {

Should be "node default {"

HTH...

Dirk

--

Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
Phone: +49 2226 15966 18
Email: dhein...@opentext.com
Website: www.recommind.de
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet.

-- 
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/666a3429b694987ce498b1b573eb763d2653015e.camel%40opentext.com.

Re: [Puppet Users] Puppet agent is not applying changes

[Dan Crisp]

Hello Josh,

Thanks for the reply.  Still no luck I'm afraid after changing what you 
suggested.  I even changed node to be fqdn (quoted & unquoted) and that 
didn't work either.  Which again makes me think, for some reason, it's not 
being read due to perhaps being the the wrong place.

Thanks,
Dan.


On Thursday, September 26, 2019 at 7:13:48 PM UTC+1, Josh Cooper wrote:
>
> Hi Dan,
>
> I think the problem is that default should not be quoted (see 
> https://puppet.com/docs/puppet/latest/lang_node_definitions.html#syntax):
>
> If you do node "default", then puppet will only apply the class if the 
> node's fqdn is "default".
>
> Josh
>
> On Thu, Sep 26, 2019 at 9:55 AM Dan Crisp > 
> wrote:
>
>> Hello all,
>>
>> Been at this problem I have for nearly a week now and it's driving 
>> crazy!!!  I hope it's simply a case of someone with some fresh eyes taking 
>> a look and showing me the error of my ways.  
>>
>> Before I continue with the Puppet deployment, for testing purposes, I 
>> just want to create a single user namely djc72uk on a single server.  The 
>> servers name is lhcadvdeveye05 and you can see below that it has 
>> successfully generated a certificate:
>>
>> # puppetserver ca list --all
>> Signed Certificates:
>> lhcadvdeveye05.x.com   (SHA256)  
>> F1:07:CD:17:8F:0B:B5:AF:79:8A:13:F3:BA:CA:90:1A:1D:67:2C:74:C2:7F:25:3B:88:E9:34:C5:FB:50:CD:7D
>> puppet.fixnetix.com   (SHA256)  
>> 7D:2E:79:6D:DE:97:A7:B0:5D:EB:48:37:3D:B1:0F:B2:C3:E1:7F:ED:70:D9:EC:2D:71:BE:53:4A:7C:9B:B6:81
>>   
>>  alt names: ["DNS:puppet", "DNS:puppet.xx.com"]
>>
>> I'm seeing the following output from the servers when I run the agent:
>>
>> # puppet agent --no-daemonize --verbose --onetime
>> Info: Using configured environment 'production'
>> Info: Retrieving pluginfacts
>> Info: Retrieving plugin
>> Info: Retrieving locales
>> Info: Caching catalog for lhcadvdeveye05.xx.com
>> Info: Applying configuration version '1569503223'
>> Notice: Applied catalog in 0.24 seconds
>>
>> Looks all good here other than it's not applying the module I created 
>> namely accounts (see below within the puppet environment).
>>
>> *Puppet Server Environment*:
>>
>> # puppet config print confdir
>> /etc/puppetlabs/puppet
>>
>> # ll /etc/puppetlabs/puppet
>> total 48
>> drwxr-xr-x. 1 puppet puppet 4096 Sep 25 22:34 ./
>> drwxr-xr-x. 1 root   root   4096 Sep 24 12:16 ../
>> -rw-r--r--. 1 puppet puppet 5487 Sep 23 22:22 auth.conf
>> -rw-r--r--. 1 puppet puppet  161 Sep 23 22:22 hiera.yaml
>> -rw-r--r--. 1 puppet puppet  697 Sep 25 22:34 puppet.conf
>>
>> # more /etc/puppetlabs/puppet/puppet.conf
>> [master]
>> vardir = /opt/puppetlabs/server/data/puppetserver
>> logdir = /var/log/puppetlabs/puppetserver
>> rundir = /var/run/puppetlabs/puppetserver
>> pidfile = /var/run/puppetlabs/puppetserver/puppetserver.pid
>> codedir = /etc/puppetlabs/code
>> environmentpath = $codedir/environments
>> autosign = true
>>
>> # puppet config print codedir
>> /etc/puppetlabs/code
>>
>> # puppet config print environmentpath
>> /etc/puppetlabs/code/environments
>>
>> # puppet config print modulepath
>>
>> /etc/puppetlabs/code/environments/production/modules:/etc/puppetlabs/code/modules:/opt/puppetlabs/puppet/modules
>>
>> # puppet module list --tree
>> /etc/puppetlabs/code/environments/production/modules
>> └── accounts (???)
>> /etc/puppetlabs/code/modules (no modules installed)
>> /opt/puppetlabs/puppet/modules (no modules installed)
>>
>> # puppet config print manifest
>> /etc/puppetlabs/code/environments/production/manifests
>>
>> # ls -lR /etc/puppetlabs/code
>> /etc/puppetlabs/code:
>> total 8
>> drwxr-xr-x. 3 root root 4096 Sep 25 21:02 environments
>> drwxr-xr-x. 2 root root 4096 Sep 25 21:02 modules
>>
>> /etc/puppetlabs/code/environments:
>> total 4
>> drwxr-xr-x. 5 root root 4096 Sep 25 20:47 production
>>
>> /etc/puppetlabs/code/environments/production:
>> total 20
>> -rw-r--r--. 1 root root  808 Sep 25 20:47 environment.conf
>> -rw-r--r--. 1 root root  518 Sep 17 22:22 hiera.yaml
>> drwxr-xr-x. 2 root root 4096 Sep 24 20:34 manifests
>> drwxr-xr-x. 3 root root 4096 Sep 24 19:57 modules
>>
>>
>> /etc/puppetlabs/code/environments/production/manifests:
>> total 4
>> -rw-r--r--. 1 root root 40 Sep 24 20:34 site.pp
>>
>> /etc/puppetlabs/code/environments/production/modules:
>> total 4
>> drwxr-x---. 5 root root 4096 Sep 25 21:18 accounts
>>
>> /etc/puppetlabs/code/environments/production/modules/accounts:
>> total 12
>> drwxr-x---. 2 root root 4096 Sep 24 20:38 manifests
>>
>> /etc/puppetlabs/code/environments/production/modules/accounts/manifests:
>> total 8
>> -rw-r-. 1 root root  77 Sep 24 20:38 groups.pp
>> -rw-r-. 1 root root 224 Sep 24 20:01 init.pp
>>
>> /etc/puppetlabs/code/modules:
>> total 0
>>
>> # more /etc/puppetlabs/code/environments/production/manifests/site.pp
>> node 'default' {
>>   include accounts
>> }
>>
>> # more 
>> /etc/puppetlabs/code/environments/production/modules/accounts/manifests/init.pp

Re: [Puppet Users] Puppet agent is not applying changes

[Josh Cooper]

Hi Dan,

I think the problem is that default should not be quoted (see
https://puppet.com/docs/puppet/latest/lang_node_definitions.html#syntax):

If you do node "default", then puppet will only apply the class if the
node's fqdn is "default".

Josh

On Thu, Sep 26, 2019 at 9:55 AM Dan Crisp  wrote:

> Hello all,
>
> Been at this problem I have for nearly a week now and it's driving
> crazy!!!  I hope it's simply a case of someone with some fresh eyes taking
> a look and showing me the error of my ways.
>
> Before I continue with the Puppet deployment, for testing purposes, I just
> want to create a single user namely djc72uk on a single server.  The
> servers name is lhcadvdeveye05 and you can see below that it has
> successfully generated a certificate:
>
> # puppetserver ca list --all
> Signed Certificates:
> lhcadvdeveye05.x.com   (SHA256)
> F1:07:CD:17:8F:0B:B5:AF:79:8A:13:F3:BA:CA:90:1A:1D:67:2C:74:C2:7F:25:3B:88:E9:34:C5:FB:50:CD:7D
> puppet.fixnetix.com   (SHA256)
> 7D:2E:79:6D:DE:97:A7:B0:5D:EB:48:37:3D:B1:0F:B2:C3:E1:7F:ED:70:D9:EC:2D:71:BE:53:4A:7C:9B:B6:81
>  alt names: ["DNS:puppet", "DNS:puppet.xx.com"]
>
> I'm seeing the following output from the servers when I run the agent:
>
> # puppet agent --no-daemonize --verbose --onetime
> Info: Using configured environment 'production'
> Info: Retrieving pluginfacts
> Info: Retrieving plugin
> Info: Retrieving locales
> Info: Caching catalog for lhcadvdeveye05.xx.com
> Info: Applying configuration version '1569503223'
> Notice: Applied catalog in 0.24 seconds
>
> Looks all good here other than it's not applying the module I created
> namely accounts (see below within the puppet environment).
>
> *Puppet Server Environment*:
>
> # puppet config print confdir
> /etc/puppetlabs/puppet
>
> # ll /etc/puppetlabs/puppet
> total 48
> drwxr-xr-x. 1 puppet puppet 4096 Sep 25 22:34 ./
> drwxr-xr-x. 1 root   root   4096 Sep 24 12:16 ../
> -rw-r--r--. 1 puppet puppet 5487 Sep 23 22:22 auth.conf
> -rw-r--r--. 1 puppet puppet  161 Sep 23 22:22 hiera.yaml
> -rw-r--r--. 1 puppet puppet  697 Sep 25 22:34 puppet.conf
>
> # more /etc/puppetlabs/puppet/puppet.conf
> [master]
> vardir = /opt/puppetlabs/server/data/puppetserver
> logdir = /var/log/puppetlabs/puppetserver
> rundir = /var/run/puppetlabs/puppetserver
> pidfile = /var/run/puppetlabs/puppetserver/puppetserver.pid
> codedir = /etc/puppetlabs/code
> environmentpath = $codedir/environments
> autosign = true
>
> # puppet config print codedir
> /etc/puppetlabs/code
>
> # puppet config print environmentpath
> /etc/puppetlabs/code/environments
>
> # puppet config print modulepath
>
> /etc/puppetlabs/code/environments/production/modules:/etc/puppetlabs/code/modules:/opt/puppetlabs/puppet/modules
>
> # puppet module list --tree
> /etc/puppetlabs/code/environments/production/modules
> └── accounts (???)
> /etc/puppetlabs/code/modules (no modules installed)
> /opt/puppetlabs/puppet/modules (no modules installed)
>
> # puppet config print manifest
> /etc/puppetlabs/code/environments/production/manifests
>
> # ls -lR /etc/puppetlabs/code
> /etc/puppetlabs/code:
> total 8
> drwxr-xr-x. 3 root root 4096 Sep 25 21:02 environments
> drwxr-xr-x. 2 root root 4096 Sep 25 21:02 modules
>
> /etc/puppetlabs/code/environments:
> total 4
> drwxr-xr-x. 5 root root 4096 Sep 25 20:47 production
>
> /etc/puppetlabs/code/environments/production:
> total 20
> -rw-r--r--. 1 root root  808 Sep 25 20:47 environment.conf
> -rw-r--r--. 1 root root  518 Sep 17 22:22 hiera.yaml
> drwxr-xr-x. 2 root root 4096 Sep 24 20:34 manifests
> drwxr-xr-x. 3 root root 4096 Sep 24 19:57 modules
>
>
> /etc/puppetlabs/code/environments/production/manifests:
> total 4
> -rw-r--r--. 1 root root 40 Sep 24 20:34 site.pp
>
> /etc/puppetlabs/code/environments/production/modules:
> total 4
> drwxr-x---. 5 root root 4096 Sep 25 21:18 accounts
>
> /etc/puppetlabs/code/environments/production/modules/accounts:
> total 12
> drwxr-x---. 2 root root 4096 Sep 24 20:38 manifests
>
> /etc/puppetlabs/code/environments/production/modules/accounts/manifests:
> total 8
> -rw-r-. 1 root root  77 Sep 24 20:38 groups.pp
> -rw-r-. 1 root root 224 Sep 24 20:01 init.pp
>
> /etc/puppetlabs/code/modules:
> total 0
>
> # more /etc/puppetlabs/code/environments/production/manifests/site.pp
> node 'default' {
>   include accounts
> }
>
> # more
> /etc/puppetlabs/code/environments/production/modules/accounts/manifests/init.pp
> class accounts {
>
>   include accounts::groups
>
>   user { 'djc72uk':
> ensure  => present,
> home=> '/home/djc72uk',
> shell   => '/bin/bash',
> managehome  => true,
> gid => 'djc72uk',
>   }
>
> }
>
> # more
> /etc/puppetlabs/code/environments/production/modules/accounts/manifests/groups.pp
> class accounts::groups {
>
>   group { 'djc72uk':
> ensure  => present,
>   }
> }
>
> My gut feel is that the site.pp file is in the wrong place and therefore
> not being read however, based on 

[Puppet Users] Puppet agent is not applying changes

[Dan Crisp]

Hello all,

Been at this problem I have for nearly a week now and it's driving 
crazy!!!  I hope it's simply a case of someone with some fresh eyes taking 
a look and showing me the error of my ways.  

Before I continue with the Puppet deployment, for testing purposes, I just 
want to create a single user namely djc72uk on a single server.  The 
servers name is lhcadvdeveye05 and you can see below that it has 
successfully generated a certificate:

# puppetserver ca list --all
Signed Certificates:
lhcadvdeveye05.x.com   (SHA256)  
F1:07:CD:17:8F:0B:B5:AF:79:8A:13:F3:BA:CA:90:1A:1D:67:2C:74:C2:7F:25:3B:88:E9:34:C5:FB:50:CD:7D
puppet.fixnetix.com   (SHA256)  
7D:2E:79:6D:DE:97:A7:B0:5D:EB:48:37:3D:B1:0F:B2:C3:E1:7F:ED:70:D9:EC:2D:71:BE:53:4A:7C:9B:B6:81
  
 alt names: ["DNS:puppet", "DNS:puppet.xx.com"]

I'm seeing the following output from the servers when I run the agent:

# puppet agent --no-daemonize --verbose --onetime
Info: Using configured environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Retrieving locales
Info: Caching catalog for lhcadvdeveye05.xx.com
Info: Applying configuration version '1569503223'
Notice: Applied catalog in 0.24 seconds

Looks all good here other than it's not applying the module I created 
namely accounts (see below within the puppet environment).

*Puppet Server Environment*:

# puppet config print confdir
/etc/puppetlabs/puppet

# ll /etc/puppetlabs/puppet
total 48
drwxr-xr-x. 1 puppet puppet 4096 Sep 25 22:34 ./
drwxr-xr-x. 1 root   root   4096 Sep 24 12:16 ../
-rw-r--r--. 1 puppet puppet 5487 Sep 23 22:22 auth.conf
-rw-r--r--. 1 puppet puppet  161 Sep 23 22:22 hiera.yaml
-rw-r--r--. 1 puppet puppet  697 Sep 25 22:34 puppet.conf

# more /etc/puppetlabs/puppet/puppet.conf
[master]
vardir = /opt/puppetlabs/server/data/puppetserver
logdir = /var/log/puppetlabs/puppetserver
rundir = /var/run/puppetlabs/puppetserver
pidfile = /var/run/puppetlabs/puppetserver/puppetserver.pid
codedir = /etc/puppetlabs/code
environmentpath = $codedir/environments
autosign = true

# puppet config print codedir
/etc/puppetlabs/code

# puppet config print environmentpath
/etc/puppetlabs/code/environments

# puppet config print modulepath
/etc/puppetlabs/code/environments/production/modules:/etc/puppetlabs/code/modules:/opt/puppetlabs/puppet/modules

# puppet module list --tree
/etc/puppetlabs/code/environments/production/modules
└── accounts (???)
/etc/puppetlabs/code/modules (no modules installed)
/opt/puppetlabs/puppet/modules (no modules installed)

# puppet config print manifest
/etc/puppetlabs/code/environments/production/manifests

# ls -lR /etc/puppetlabs/code
/etc/puppetlabs/code:
total 8
drwxr-xr-x. 3 root root 4096 Sep 25 21:02 environments
drwxr-xr-x. 2 root root 4096 Sep 25 21:02 modules

/etc/puppetlabs/code/environments:
total 4
drwxr-xr-x. 5 root root 4096 Sep 25 20:47 production

/etc/puppetlabs/code/environments/production:
total 20
-rw-r--r--. 1 root root  808 Sep 25 20:47 environment.conf
-rw-r--r--. 1 root root  518 Sep 17 22:22 hiera.yaml
drwxr-xr-x. 2 root root 4096 Sep 24 20:34 manifests
drwxr-xr-x. 3 root root 4096 Sep 24 19:57 modules


/etc/puppetlabs/code/environments/production/manifests:
total 4
-rw-r--r--. 1 root root 40 Sep 24 20:34 site.pp

/etc/puppetlabs/code/environments/production/modules:
total 4
drwxr-x---. 5 root root 4096 Sep 25 21:18 accounts

/etc/puppetlabs/code/environments/production/modules/accounts:
total 12
drwxr-x---. 2 root root 4096 Sep 24 20:38 manifests

/etc/puppetlabs/code/environments/production/modules/accounts/manifests:
total 8
-rw-r-. 1 root root  77 Sep 24 20:38 groups.pp
-rw-r-. 1 root root 224 Sep 24 20:01 init.pp

/etc/puppetlabs/code/modules:
total 0

# more /etc/puppetlabs/code/environments/production/manifests/site.pp
node 'default' {
  include accounts
}

# more 
/etc/puppetlabs/code/environments/production/modules/accounts/manifests/init.pp
class accounts {

  include accounts::groups

  user { 'djc72uk':
ensure  => present,
home=> '/home/djc72uk',
shell   => '/bin/bash',
managehome  => true,
gid => 'djc72uk',
  }

}

# more 
/etc/puppetlabs/code/environments/production/modules/accounts/manifests/groups.pp
class accounts::groups {

  group { 'djc72uk':
ensure  => present,
  }
}

My gut feel is that the site.pp file is in the wrong place and therefore 
not being read however, based on the above environment details, I'm 
struggling to see how that's possible.

Any help will be appreciated here.

Many Thanks,
Dan,

-- 
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/34731f49-113f-4529-989d-18dd1dbe8e3d%40googlegroups.com.

Re: [Puppet Users] Puppet agent hangs on "Executing: '/sbin/service nfs start'

[Bret Wortman]

It must have been a long day yesterday. I thought this was something Puppet 
was doing internally. I'm closing in on the root cause now.

On Thursday, August 29, 2019 at 1:45:03 AM UTC-4, Dirk Heinrichs wrote:
>
> Am Mittwoch, den 28.08.2019, 11:49 -0700 schrieb Bret Wortman:
>
> Debug: Executing: '/sbin/service nfs start'
>
>
> First thing to try: Does it also hang if you run the command manually? 
> Maybe it's a problem with that specific service.
>
> Bye...
>
> Dirk
>
> -- 
>
> *Dirk Heinrichs*
> Senior Systems Engineer, Delivery Pipeline
> OpenText ™ Discovery | Recommind
> *Phone*: +49 2226 15966 18
> *Email*: dhei...@opentext.com 
> *Website*: www.recommind.de
> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
> Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
> Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
> This e-mail may contain confidential and/or privileged information. If you 
> are not the intended recipient (or have received this e-mail in error) 
> please notify the sender immediately and destroy this e-mail. Any 
> unauthorized copying, disclosure or distribution of the material in this 
> e-mail is strictly forbidden
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail 
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und 
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte 
> Weitergabe dieser Mail sind nicht gestattet.
>

-- 
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/ae218244-ba5d-43ac-8493-0c1ddff4c97b%40googlegroups.com.

Re: [Puppet Users] Puppet agent hangs on "Executing: '/sbin/service nfs start'

[Dirk Heinrichs]

Am Mittwoch, den 28.08.2019, 11:49 -0700 schrieb Bret Wortman:

Debug: Executing: '/sbin/service nfs start'

First thing to try: Does it also hang if you run the command manually? Maybe 
it's a problem with that specific service.

Bye...

Dirk

--

Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
Phone: +49 2226 15966 18
Email: dhein...@opentext.com
Website: www.recommind.de
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet.

-- 
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/84b0fc121e6f80f1bfccc323e0528a0abd72612d.camel%40opentext.com.

[Puppet Users] Puppet agent hangs on "Executing: '/sbin/service nfs start'

[Bret Wortman]

My agent is 6.6.0 and my server is 6.4.0, so I realize this may be a 
mismatch problem, though why the repos have advanced the agent past the 
server, I don't know.

Anyway:

My agents on C6 are now hanging and refusing to progress. This happens 
randomly; some part of the catalog will get applied but not all. When I 
just now tried to debug one, it hangs reliably at the following:

# puppet agent -t --debug
:
:
Debug: Executing: '/sbin/service nfs status'
Debug: Executing: '/sbin/chkconfig nfs'
Debug: Executing: '/sbin/service nfs start'

Has anyone else seen this? It's new to me...

Thanks!


Bret Wortman
The Damascus Group LLC

-- 
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/69c5b56c-ceb3-4b59-8bc1-5631baba7a8f%40googlegroups.com.

[Puppet Users] Puppet agent not loading facts when run on puppetserver

[Eirik Øverby]

Hi,

We just started our trials with puppet6 (upgrading from puppet5) on FreeBSD, 
and while we think we have a pretty good grip on most things that we need to 
do, there is one mind-bending problem we're having: When running the Puppet 
Agent on the Puppetserver instance itself, it never prints "Loading facts.." 
and then errors out complaining about unassigned variables (like 
$operatingsystemrelease, for instance).

Running 'puppet facts' only gives this:

# puppet facts
{
  "name": "puppet.pmn.nyc.modirum.com",
  "values": {
"trusted": {
  "domain": "pmn.nyc.modirum.com",
  "certname": "puppet.pmn.nyc.modirum.com",
  "hostname": "puppet",
  "extensions": {
  },
  "authenticated": "remote"
}
  },
  "timestamp": "2019-06-17T10:02:03.156284600+00:00"
}

On any other node, we get the usual huge amount of data. Interestingly, running 
'facter -p' also gives the expected result.

Running 'puppet facts --debug' shows indications that it is attempting to laod 
facts (see snippets below), but they aren't printed at the end. Facts caching 
is not the issue (there is no facter config on the puppetserver node, so no 
caching is taking place).

The configuration is exactly the same we've used for puppet5, where the agent 
runs happily on the puppetserver. It has simply been a matter of pkg delete 
puppet* puppetdb* / pkg install puppet6 puppetserver6 puppetdb6 
puppetdb-terminus6.

I have a vage recollection of having seen this problem before, but it's many 
years ago and I have an even more vague recollection (as in none at all) of 
what was done to fix it. It's probably unrelated anyway.

/Eirik

# puppet facts --debug 2>&1 | less -R

Debug: Facter: fact "networking" has resolved to {
  domain => "pmn.nyc.modirum.com",
  fqdn => "puppet.pmn.nyc.modirum.com",
  hostname => "puppet",
  interfaces => {
em0 => {
  bindings => [
{
...

and on to...

Debug: Facter: executing command: /bin/freebsd-version
Debug: Facter: 11.2-RELEASE-p9
Debug: Facter: process exited with status code 0.
Debug: Facter: fact "osfamily" has resolved to "FreeBSD".
Debug: Facter: fact "operatingsystemmajrelease" has resolved to "11".
Debug: Facter: fact "operatingsystemrelease" has resolved to "11.2-RELEASE-p9".
Debug: Facter: fact "hardwaremodel" has resolved to "amd64".
Debug: Facter: fact "architecture" has resolved to "amd64".
Debug: Facter: fact "operatingsystem" has resolved to "FreeBSD".
Debug: Facter: fact "os" has resolved to {
  architecture => "amd64",
  family => "FreeBSD",
  hardware => "amd64",
  name => "FreeBSD",
  release => {
full => "11.2-RELEASE-p9",
major => "11",
minor => "2-RELEASE-p9"
  }
}.

-- 
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/1143BED7-65E0-4280-AE35-85261481BA7B%40anduin.net.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] puppet agent fails to self-restart on config change

[SCHAER Frederic]

Hi,

For some time now, we've seen this kind of logs in our machines :
(note: we do manage the puppet agent config with puppet)

Mar 29 13:25:50 gate01 puppet-agent[2684]: Processing restart
Mar 29 13:25:50 gate01 puppet-agent[2684]: Puppet::Agent::Locker.running? is 
deprecated as it is inherently unsafe. The only safe way to know if the lock is 
locked is to try lock and perform some action and then handle the LockError 
that may result.
Mar 29 13:25:50 gate01 puppet-agent[2684]:(location: 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/agent/locker.rb:37:in 
`running?')
Mar 29 13:25:51 gate01 puppet-agent[38303]: Applied catalog in 16.78 seconds
Mar 29 13:26:00 gate01 puppet-agent[2684]: Config file 
/etc/puppetlabs/puppet/puppet.conf changed; triggering re-parse of all config 
files.
Mar 29 13:44:16 gate01 puppet-agent[2684]: Shutdown/restart in progress 
(:restart_requested); skipping run

Than puppet never runs again because of this stuck restart until we manually 
restart the agent.
puppet-agent-5.5.12 here.

This happens on both el6 and el7 hosts.

Bad thing is that this even happens when puppet is upgraded during our install 
process ... and we get freshly installed nodes with stuck puppets...
Off course, this did not happen before.

Would anyone know of a way to get rid of this damn "can't restart" loop ?

Regards

Frédéric Schaer
CEA/Saclay
DRF/IRFU/DEDIP/LIS

-- 
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/CAB586860327CB498EF79903967FEA231ABC903E%40E-EXDAGE-A0.extra.cea.fr.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] 'puppet agent -t'

[Matthias Steffens]

> This message indicates, that the agent has created a certificate, has sent 
> the CSR to the master and is now waiting for the master to sign the 
> certificate.
>
> Log in to your puppetmaster.
>
> Check puppet and puppetserver version.
> puppetserver --version
> puppet --version
>
> If you are running puppetserver 6:
>
> puppetserver  ca list
>
> This should show you an waiting singing request.
>
> sign with
>
> puppetserver ca sign 
>
> Usualy the certname is the fqdn of the agent.
>
> If you run puppet 5: please upgrade.
>
>
I've the following versions installed:






*root@puppet-master:~# puppetserver --versionpuppetserver version: 
6.3.0root@puppet-master:~# puppet --version6.4.0root@puppet-master:~#*
 

> I added a comment below covering your puppet.conf regarding reports 
> configuration:
>
>
> I didn't understand this, because I thought I'm doing an signing request 
> with my '*puppet agent -t*' !?
>
> My Configuration looks like this:
>
> *Puppet-Master:*
>
> - Installed PuppetDB:
> ---> Configuration-File for puppetdb: /etc/puppetlabs/puppet/puppetdb.conf:
>
> *[main]*
> *server_urls = https://puppet-master.local:8081 
> *
>
> - Installed Puppetserver / Puppet:
> ---> Configuration-File for puppetdb: /etc/puppetlabs/puppet/puppet.conf:
>
> [main]
> server = puppet-master.local
> # This file can be used to override the default puppet settings.
> # See the following links for more details on what settings are available:
> # - https://puppet.com/docs/puppet/latest/config_important_settings.html
> # - https://puppet.com/docs/puppet/latest/config_about_settings.html
> # - https://puppet.com/docs/puppet/latest/config_file_main.html
> # - https://puppet.com/docs/puppet/latest/configuration.html
> [master]
> vardir = /opt/puppetlabs/server/data/puppetserver
> logdir = /var/log/puppetlabs/puppetserver
> rundir = /var/run/puppetlabs/puppetserver
> pidfile = /var/run/puppetlabs/puppetserver/puppetserver.pid
> codedir = /etc/puppetlabs/code
> storeconfigs = true
> storeconfigs_backend = puppetdb
> reports = store,puppetdb
>
>
> please don't use two locations to store reports.
> puppetdb is the modern place where to store them.
>

I changed it to the follwing in my puppet.conf:









*[master]vardir = /opt/puppetlabs/server/data/puppetserverlogdir = 
/var/log/puppetlabs/puppetserverrundir = 
/var/run/puppetlabs/puppetserverpidfile = 
/var/run/puppetlabs/puppetserver/puppetserver.pidcodedir = 
/etc/puppetlabs/codestoreconfigs = truestoreconfigs_backend = 
puppetdbreports = puppetdb*


 

> Use a webfrontend to visualize the reports (Puppet Enterprise, The 
> Foreman, Puppet Board).
> store places reports into file system. Usually this is only growing and 
> never cleaned up!
> [...]
>
> When I've now installed my puppetserver and an running puppetd (it looks 
to me like it's gonna work or am I wrong?) can I nowly install Foreman for 
example?
 

-- 
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/d5a50317-f394-423f-adc2-7fbc4f68a545%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] 'puppet agent -t'

[Matthias Steffens]

>
> When your agent didn't create a cert yet, you need to specify an 
>> additional option that'll create the cert and wait for the master to 
>> sign the certificate signing request: 
>>
>> puppet agent -t --waitforcert 10 
>>
>> the integer value to the argument is the number of seconds to wait for 
>> each iteration (I think the number of iterations made before exiting is 
>> limited). 
>>
>> for me 10s is usually a good value, but you can play with this to find 
>> something that gives you the appropriate time to sign certs on the 
>> master (e.g. you probably do want to verify that the client's 
>> certificate fingerprint is what the puppetmaster knows). 
>>
>
>
I've tried this but it doesn't work for me :(... Therefore I switched back 
to an old Snapshot of my VM and know 
my 'puppet agent -t' works fine. 

But now my 'puppet agent -t' responds the following:











*root@puppet-node:~# puppet agent -tWarning: Unable to fetch my node 
definition, but the agent run will continue:Warning: Error 500 on SERVER: 
Server Error: Could not retrieve facts for puppet-node.local: Failed to 
find facts from PuppetDB at puppet-master.local:8140: Failed to execute 
'/pdb/query/v4/nodes/puppet-node.local/facts' on at least 1 of the 
following 'server_urls': https://192.168.117.20:8081Info: Retrieving 
pluginfactsInfo: Retrieving pluginInfo: Retrieving localesInfo: Loading 
factsError: Could not retrieve catalog from remote server: Error 500 on 
SERVER: Server Error: Failed to execute 
'/pdb/cmd/v1?checksum=fbe20bc4a742836d2b0c0951e875e3b9ec7011bd=5=puppet-node.local=replace_facts=2019-03-28T09:42:35.432Z'
 
on at least 1 of the following 'server_urls': 
https://192.168.117.20:8081Warning: Not using cache on failed catalogError: 
Could not retrieve catalog; skipping runroot@puppet-node:~#*

What means the Output "
*Could not retrieve facts for puppet-node.local: Failed to find facts from 
PuppetDB at puppet-master.local:8140"?*

-- 
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/adca69e0-cb9c-4072-b4a2-3be9c0542e97%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] 'puppet agent -t'

[Martin Alfke]

Hi Matthias,

On Mar 26 2019, at 5:40 pm, Matthias Steffens  wrote:
> Hi!
>
> I'm trying to get a new certificate for my puppet agent and therefore I tried 
> to do an 'puppet agent -t' an I got the following:
>
> root@puppet-node:/etc/puppetlabs/puppet/ssl/certs# puppet agent -t
> Exiting; no certificate found and waitforcert is disabled
>
>
>

This message indicates, that the agent has created a certificate, has sent the 
CSR to the master and is now waiting for the master to sign the certificate.
Log in to your puppetmaster.
Check puppet and puppetserver version.
puppetserver --version
puppet --version

If you are running puppetserver 6:
puppetserver ca list
This should show you an waiting singing request.
sign with
puppetserver ca sign 
Usualy the certname is the fqdn of the agent.
If you run puppet 5: please upgrade.
I added a comment below covering your puppet.conf regarding reports 
configuration:
>
> I didn't understand this, because I thought I'm doing an signing request with 
> my 'puppet agent -t' !?
>
> My Configuration looks like this:
>
> Puppet-Master:
>
> - Installed PuppetDB:
> ---> Configuration-File for puppetdb: /etc/puppetlabs/puppet/puppetdb.conf:
>
> [main]
> server_urls = https://puppet-master.local:8081
>
>
> - Installed Puppetserver / Puppet:
> ---> Configuration-File for puppetdb: /etc/puppetlabs/puppet/puppet.conf:
>
> [main]
> server = puppet-master.local
> # This file can be used to override the default puppet settings.
> # See the following links for more details on what settings are available:
> # - https://puppet.com/docs/puppet/latest/config_important_settings.html
> # - https://puppet.com/docs/puppet/latest/config_about_settings.html
> # - https://puppet.com/docs/puppet/latest/config_file_main.html
> # - https://puppet.com/docs/puppet/latest/configuration.html
> [master]
> vardir = /opt/puppetlabs/server/data/puppetserver
> logdir = /var/log/puppetlabs/puppetserver
> rundir = /var/run/puppetlabs/puppetserver
> pidfile = /var/run/puppetlabs/puppetserver/puppetserver.pid
> codedir = /etc/puppetlabs/code
> storeconfigs = true
> storeconfigs_backend = puppetdb
> reports = store,puppetdb
>
>
>

please don't use two locations to store reports.
puppetdb is the modern place where to store them.
Use a webfrontend to visualize the reports (Puppet Enterprise, The Foreman, 
Puppet Board).
store places reports into file system. Usually this is only growing and never 
cleaned up!
[...]
> Matthias
>
>
>

hth,
Martin

-- 
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/79AE5801-83A2-48BF-9E6C-0521D4720E5B%40getmailspring.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] 'puppet agent -t'

[Gabriel Filion]

Hi there,

On 2019-03-26 12:40 p.m., Matthias Steffens wrote:
> I'm trying to get a new certificate for my puppet agent and therefore I 
> tried to do an '*puppet agent -t*' an I got the following:
> 
> 
> *root@puppet-node:/etc/puppetlabs/puppet/ssl/certs# puppet agent -tExiting; 
> no certificate found and waitforcert is disabled*

When your agent didn't create a cert yet, you need to specify an
additional option that'll create the cert and wait for the master to
sign the certificate signing request:

puppet agent -t --waitforcert 10

the integer value to the argument is the number of seconds to wait for
each iteration (I think the number of iterations made before exiting is
limited).

for me 10s is usually a good value, but you can play with this to find
something that gives you the appropriate time to sign certs on the
master (e.g. you probably do want to verify that the client's
certificate fingerprint is what the puppetmaster knows).

-- 
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/3d003378-818e-6465-f18a-5573f3d38daa%40lelutin.ca.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

[Puppet Users] 'puppet agent -t'

[Matthias Steffens]

Hi! 

I'm trying to get a new certificate for my puppet agent and therefore I 
tried to do an '*puppet agent -t*' an I got the following:


*root@puppet-node:/etc/puppetlabs/puppet/ssl/certs# puppet agent -tExiting; 
no certificate found and waitforcert is disabled*

I didn't understand this, because I thought I'm doing an signing request 
with my '*puppet agent -t*' !?

My Configuration looks like this:

*Puppet-Master:*

- Installed PuppetDB: 
---> Configuration-File for puppetdb: /etc/puppetlabs/puppet/puppetdb.conf:


*[main]server_urls = https://puppet-master.local:8081*

- Installed Puppetserver / Puppet:
---> Configuration-File for puppetdb: /etc/puppetlabs/puppet/puppet.conf:

[main]
server = puppet-master.local
# This file can be used to override the default puppet settings.
# See the following links for more details on what settings are available:
# - https://puppet.com/docs/puppet/latest/config_important_settings.html
# - https://puppet.com/docs/puppet/latest/config_about_settings.html
# - https://puppet.com/docs/puppet/latest/config_file_main.html
# - https://puppet.com/docs/puppet/latest/configuration.html
[master]
vardir = /opt/puppetlabs/server/data/puppetserver
logdir = /var/log/puppetlabs/puppetserver
rundir = /var/run/puppetlabs/puppetserver
pidfile = /var/run/puppetlabs/puppetserver/puppetserver.pid
codedir = /etc/puppetlabs/code
storeconfigs = true
storeconfigs_backend = puppetdb
reports = store,puppetdb

[user]
http_proxy="http://proxy..de:8080"
HTTP_PROXY="http://proxy..de:8080"
https_proxy="http://proxy..de:8080"


- Configuration-File 'routes.yaml':
---
master:
  facts:
terminus: puppetdb
cache: yaml

When I do an 'netstat -tulpn' I got the following:

root@puppet-master:/etc/puppetlabs/puppet# netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address   Foreign Address 
State   PID/Program name
tcp0  0 0.0.0.0:22  0.0.0.0:*   
LISTEN  740/sshd
tcp0  0 127.0.0.1:5432  0.0.0.0:*   
LISTEN  4282/postgres
tcp6   0  0 :::8140 :::*
LISTEN  3653/java
tcp6   0  0 127.0.0.1:8080  :::*
LISTEN  3866/java
tcp6   0  0 :::8081 :::*
LISTEN  3866/java
tcp6   0  0 :::22   :::*
LISTEN  740/sshd
tcp6   0  0 ::1:5432:::*
LISTEN  4282/postgres
root@puppet-master:/etc/puppetlabs/puppet#


Can somone explain me why I've doent't get an Certificate on my Node?

Thanks for your help and reply,

Matthias

-- 
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/53df7774-c9de-48a5-ae54-eceb7f55a5d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet agent 1.10.14, 5.3.8, and 5.5.3 are now available

[Branan Riley]

Hi Dirk,

The 1.10.x agent (and thus all of PC1) is in an extended support phase
right now, coinciding with the PE 2016.4 lifecycle:
https://puppet.com/misc/puppet-enterprise-lifecycle. This means it is
receiving critical fixes only, and we are not adding new platforms to it.
The current plan is to end-of-life it completely in October.

Puppet 5.5 is part of the next PE LTS, and will be receiving bugfixes until
2020 as part of our support for that release. Our recommendation is that
you update to Puppet 5.

I can't find an announcement that we've sent to this list, so I think this
is on us. I apologize for that, and will look in to getting a message sent
out communicating the extended support status more broadly.

On Thu, Jun 14, 2018 at 10:39 PM Dirk Heinrichs 
wrote:

> *From:* puppet-users@googlegroups.com [mailto:
> puppet-users@googlegroups.com] *On Behalf Of *Molly Waggett
>
> > There are Bionic packages in the puppet-agent 5.5.x stream:
> http://apt.puppetlabs.com/pool/bionic/puppet5/p/puppet-agent/
> 
>
>
>
> Yes, Puppet 5 ones. What about PC1?
>
>
>
> Bye...
>
>
>
> Dirk
>
> --
>
> *Molly Waggett*
>
> she/her/hers
>
> 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/CAFOE68Aj5V%2Bd0jt4OcZ5MyxrAhG2RR7FrMrGd--i44BK59rF5A%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/DM3PR15MB08771E4373DBAA9EEB09C7C4AA7C0%40DM3PR15MB0877.namprd15.prod.outlook.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Regards,

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

Re: [Puppet Users] Puppet agent 1.10.14, 5.3.8, and 5.5.3 are now available

[Dirk Heinrichs]

From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On 
Behalf Of Molly Waggett

> There are Bionic packages in the puppet-agent 5.5.x stream: 
> http://apt.puppetlabs.com/pool/bionic/puppet5/p/puppet-agent/

Yes, Puppet 5 ones. What about PC1?

Bye...

Dirk
--
Molly Waggett
she/her/hers
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/CAFOE68Aj5V%2Bd0jt4OcZ5MyxrAhG2RR7FrMrGd--i44BK59rF5A%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/DM3PR15MB08771E4373DBAA9EEB09C7C4AA7C0%40DM3PR15MB0877.namprd15.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet agent 1.10.14, 5.3.8, and 5.5.3 are now available

[Molly Waggett]

Dirk,

There are Bionic packages in the puppet-agent 5.5.x stream:
http://apt.puppetlabs.com/pool/bionic/puppet5/p/puppet-agent/


On Wed, Jun 13, 2018 at 10:58 PM, Dirk Heinrichs 
wrote:

> From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com]
> On Behalf Of Garrett Guillotte
>
> > • Puppet agent 1.10.13 and 1.10.14
>
> What about Ubuntu Bionic (18.04)?
>
> Bye...
>
> Dirk
>
> --
> 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/DM3PR15MB08772366FF7077E797B4AB7FAA7D0%40DM3PR15MB0877.
> namprd15.prod.outlook.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Molly Waggett*
she/her/hers
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/CAFOE68Aj5V%2Bd0jt4OcZ5MyxrAhG2RR7FrMrGd--i44BK59rF5A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

RE: [Puppet Users] Puppet agent 1.10.14, 5.3.8, and 5.5.3 are now available

[Dirk Heinrichs]

From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On 
Behalf Of Garrett Guillotte

> • Puppet agent 1.10.13 and 1.10.14

What about Ubuntu Bionic (18.04)?

Bye...

Dirk

-- 
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/DM3PR15MB08772366FF7077E797B4AB7FAA7D0%40DM3PR15MB0877.namprd15.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet agent 1.10.14, 5.3.8, and 5.5.3 are now available

[Garrett Guillotte]

Puppet agent 1.10.14, 5.3.8, and 5.5.3 resolve a critical Windows installer
issue  introduced in agent
1.10.13, 5.3.7, and 5.5.2 that could cause incorrect permissions to be
applied across entire filesystems of Windows nodes under certain unusual
re-installation scenarios, including those applied by Chocolatey and
Foreman.

This release also includes the same fixes for security vulnerabilities that
were included in 1.10.13, 5.3.7, and 5.5.2, which were pulled due to the
Windows installer bug:

   - CVE-2018-6513 
   - CVE-2018-6514 
   - CVE-2018-6515 
   - CVE-2018-6516 

For details, see the release notes for today's releases as well as the
previous Platform releases:

   - Puppet agent 5.5.2 and 5.5.3
   
   - Puppet agent 5.3.7 and 5.3.8
   
   - Puppet agent 1.10.13 and 1.10.14
   



-- 
*Garrett Guillotte*
Technical Writer
garrett.guillo...@puppet.com

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

[Puppet Users] Puppet agent 1.10.13 and Puppet Platform 5.3.7 and 5.5.2 are now available

[Garrett Guillotte]

Puppet Platform 5.5.2 is a bug-fix release that includes updates for Puppet
5.5.2, Facter 3.11.2, MCollective 2.12.2, and pxp-agent 1.9.2. For details,
see https://puppet.com/docs/puppet/5.5/release_notes_agent.html.

This release resolves significant security issues with Windows agents, and
Windows users should update as soon as possible. For details, see these
CVEs at https://puppet.com/security/cve/:

   - CVE-2018-6513
   - CVE-2018-6516
   - CVE-2018-6515
   - CVE-2018-6514

PuppetDB 5.2.3 and Puppet Server 5.3.2 are minor bug-fix releases. For
details, see https://puppet.com/docs/puppetdb/5.2/release_notes.html and
https://puppet.com/docs/puppetserver/5.3/release_notes.html.
--

Puppet Platform 5.3.7 is a bug-fix release that includes updates for Puppet
5.3.7. For details, see
https://puppet.com/docs/puppet/5.3/release_notes_agent.html.

This release resolves significant security issues with Windows agents, and
Windows users should update as soon as possible. For details, see these
CVEs at https://puppet.com/security/cve/:

   - CVE-2018-6513
   - CVE-2018-6516
   - CVE-2018-6515
   - CVE-2018-6514

PuppetDB and Puppet Server were not updated in this Platform release.

--

Puppet agent 1.10.13 is a bug-fix release that includes updates for Puppet
4.10.12. For details, see [
https://puppet.com/docs/puppet/4.10/release_notes_agent.html].

This release resolves significant security issues with Windows agents, and
Windows users should update as soon as possible. For details, see these
CVEs at https://puppet.com/security/cve/:

   - CVE-2018-6513
   - CVE-2018-6516
   - CVE-2018-6515
   - CVE-2018-6514

-- 
*Garrett Guillotte*
Technical Writer
garrett.guillo...@puppet.com

-- 
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/CAP7LywFsgKm6nKYKtO_%2B0orX7C_5e5Eo_nxdqZ%2BGh7b%2B-PyB0w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet agent platform removals

[enis . inan]

Hi Dirk,

Ubuntu 18.04 LTS should have nightly puppet-agent packages available soon, 
with full-fledged support landing sometime this summer. We will follow up 
on this thread when the nightlies are available.


-Enis

On Tuesday, May 8, 2018 at 11:20:53 PM UTC-7, Dirk Heinrichs wrote:
>
> Hi,
>
>  
>
> what about platform *additions*, namely Ubuntu 18.04 LTS (Bionic Beaver)?
>
>  
>
> Bye...
>
>  
>
> Dirk
>
> -- 
> 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/CA%2BmjRjBV8i1RbwmbxsTti_gczwfzuBR3gDBSW6qT6GUYVU7nbg%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/adb61c87-5751-4d6f-869e-3a908e2fd54f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet agent platform removals

[Dirk Heinrichs]

Hi,

what about platform *additions*, namely Ubuntu 18.04 LTS (Bionic Beaver)?

Bye...

Dirk
--
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%2BmjRjBV8i1RbwmbxsTti_gczwfzuBR3gDBSW6qT6GUYVU7nbg%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/SN6PR15MB241681440A6CB1CF10AFBBECAA990%40SN6PR15MB2416.namprd15.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet agent platform removals

[Enis Inan]

*We are no longer supporting Debian 7 (Wheezy), Fedora 25, Scientific Linux
5, Mac OS 10.10 (Yosemite) and 10.11 (El Capitan), and Windows Vista for PE
2018.1 and later. However these OS versions continue to be supported in PE
2017.3 and PE 2016.4. Note: Windows Server 2008 is still supported in PE
2018.1 and Puppet agent 5.5.Debian 7 will EOL on 31 May 2018 [1]. It is
currently available in Puppet agent 5.5.1, but will be removed for Puppet
agent 5.5.2, and unavailable for PE 2018.1. All other aforementioned OS
versions were removed in Puppet agent 5.5.1.These agent removals free up
capacity for us to add new OS versions as they are made available from
vendors throughout 2018. Stay tuned for Ubuntu 18.04 coming soon; see
https://tickets.puppetlabs.com/browse/PA-1869
 if you’d like to track its
current status.[1] - https://www.debian.org/News/2016/20160425
*

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

Re: [Puppet Users] Puppet agent and non-LTS Ubuntu releases policy change

[Aécio]

Hello, Scott!

It is a prudent decision.

Aécio Pires
Book of Puppet => novatec.com.br/livros/puppet
Book of Zabbix => novatec.com.br/livros/zabbix

2018-01-02 19:43 GMT-03:00 Scott Garman :

> Hi all,
>
> Some of you have probably noticed that our latest official puppet-agent
> release for Ubuntu was for version 16.10 "Yakkety", which is currently end
> of life and no longer supported. Due to the short lifecycle of non-LTS
> Ubuntu releases (9 months), and the backlog that the Puppet Platform OS
> team is working on, we've made the decision to no longer release official
> puppet-agent builds for non-LTS Ubuntu releases.
>
> I will note however that so far it has been possible to use the LTS 16.04
> "Xenial" puppet-agent package on Ubuntu 17.04 and 17.10, they're just not
> officially supported. This is a workaround that may be useful to be aware
> of until the next LTS release of Ubuntu 18.04 "Bionic" comes out in April.
>
> This policy change doesn't impact other platforms that are currently
> supported with a lifecycle of more than 12 months. For example, Fedora
> releases have a 13-month lifecycle, and we intend to keep releasing
> packages for them. Likewise for Debian releases, CentOS/RHEL, etc.
>
> The Platform OS team at Puppet has an ever-growing list of platforms to
> support on an ongoing basis. We believe that focusing our efforts on
> existing platforms with at least a year-long lifecycle will result in the
> greatest return on effort we can offer to the community.
>
> Scott Garman
>
>
>
>
>
>
>
> --
> 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/ms
> gid/puppet-users/13140f25-1373-730e-a757-87af1d991ed7%40puppet.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/CALCxXJi0sHN0gLHdJ4z-j7LDp3EN_41RUU17aiGdU_2_bFQXhg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet agent and non-LTS Ubuntu releases policy change

[Scott Garman]

Hi all,

Some of you have probably noticed that our latest official puppet-agent 
release for Ubuntu was for version 16.10 "Yakkety", which is currently 
end of life and no longer supported. Due to the short lifecycle of 
non-LTS Ubuntu releases (9 months), and the backlog that the Puppet 
Platform OS team is working on, we've made the decision to no longer 
release official puppet-agent builds for non-LTS Ubuntu releases.


I will note however that so far it has been possible to use the LTS 
16.04 "Xenial" puppet-agent package on Ubuntu 17.04 and 17.10, they're 
just not officially supported. This is a workaround that may be useful 
to be aware of until the next LTS release of Ubuntu 18.04 "Bionic" comes 
out in April.


This policy change doesn't impact other platforms that are currently 
supported with a lifecycle of more than 12 months. For example, Fedora 
releases have a 13-month lifecycle, and we intend to keep releasing 
packages for them. Likewise for Debian releases, CentOS/RHEL, etc.


The Platform OS team at Puppet has an ever-growing list of platforms to 
support on an ongoing basis. We believe that focusing our efforts on 
existing platforms with at least a year-long lifecycle will result in 
the greatest return on effort we can offer to the community.


Scott Garman







--
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/13140f25-1373-730e-a757-87af1d991ed7%40puppet.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet Agent Hang when PuppetServer Crashes...

[R.I.Pienaar]

On Mon, 1 Jan 2018, at 23:51, Matt Wise wrote:
> *Puppet Agent: 5.3.2*
> *Puppet Server: 5.1.4 - Packaged in Docker, running on Amazon ECS*
> 
> So we've recently started rolling over from our ancient Puppet 3.x system
> to a new Puppet 5.x service. The new service consists of a PuppetServer
> Docker Image (5.1.4) running in Amazon ECS, and our hosts booting up and
> running Puppet Agent 5.3.2. At this point in the migration, we're running
> ~150-200 hosts on the new Puppet5 system and we replace ~30-80 of them
> daily.
> 
> We are currently tracking down a problem with our PuppetServers and their
> memory usage, which is causing the containers to be OOM'd a few times a day
> (~10 OOMs a day across ~20 containers). While we know that we need to fix
> this, we've seen a scary behavior on the Puppet Agent side that we could
> use some advice with.
> 
> It seems that at least a few times a day now we will get a server hung in
> the boot process. The `puppet agent -t ...` process will just hang midway
> through the run. It seems that these hangs happen when the backend
> underlying PuppetServer process that they were connected to gets OOMed and
> goes away. Obviously the OOM is a problem.. but frankly I am more concerned
> with the Puppet Agent getting wedged for hours and hours without making any
> progress.
> 
> It seems that when this failure happens, the puppet agent does not ever
> time out. It never fails, or throws an error. It just hangs. We've had
> these hangs last upwards of 4-5 hours before our systems are automatically
> terminated.
> 
> We've enabled debug logging, but haven't caught one of these failures yet
> with debug mode turned on. In the mean time, are there any  known
> regressions or configuration tweaks we need to make to Puppet Agent 5.x
> more quick to fail or resilient in this case? I could obviously try to
> build in some wrapper around Puppet to catch this behavior .. but I am
> hoping that there are just some settings we need to tweak.

I see this often for other kinds of interruptions like network interruptions etc

I do recall a number of bugs around this to make it more robust, you might want 
to try searching Puppet jita 


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

[Puppet Users] Puppet Agent Hang when PuppetServer Crashes...

[Matt Wise]

*Puppet Agent: 5.3.2*
*Puppet Server: 5.1.4 - Packaged in Docker, running on Amazon ECS*

So we've recently started rolling over from our ancient Puppet 3.x system
to a new Puppet 5.x service. The new service consists of a PuppetServer
Docker Image (5.1.4) running in Amazon ECS, and our hosts booting up and
running Puppet Agent 5.3.2. At this point in the migration, we're running
~150-200 hosts on the new Puppet5 system and we replace ~30-80 of them
daily.

We are currently tracking down a problem with our PuppetServers and their
memory usage, which is causing the containers to be OOM'd a few times a day
(~10 OOMs a day across ~20 containers). While we know that we need to fix
this, we've seen a scary behavior on the Puppet Agent side that we could
use some advice with.

It seems that at least a few times a day now we will get a server hung in
the boot process. The `puppet agent -t ...` process will just hang midway
through the run. It seems that these hangs happen when the backend
underlying PuppetServer process that they were connected to gets OOMed and
goes away. Obviously the OOM is a problem.. but frankly I am more concerned
with the Puppet Agent getting wedged for hours and hours without making any
progress.

It seems that when this failure happens, the puppet agent does not ever
time out. It never fails, or throws an error. It just hangs. We've had
these hangs last upwards of 4-5 hours before our systems are automatically
terminated.

We've enabled debug logging, but haven't caught one of these failures yet
with debug mode turned on. In the mean time, are there any  known
regressions or configuration tweaks we need to make to Puppet Agent 5.x
more quick to fail or resilient in this case? I could obviously try to
build in some wrapper around Puppet to catch this behavior .. but I am
hoping that there are just some settings we need to tweak.

Any thoughts?

-- 
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%2B9wXBTjih5N%3Dc%2B8H3UYnH2Jq7fpOPPY3-kmxoxP891W6xLBfQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet agent on vmware ESXi

[Rob Nelson]

There is no agent that can run on ESXi. It may look like Linux, but it
isn’t, so there’s no native client.

There are some VMware modules on the forge that may be of interest. If you
want to manage the hosts, as opposed to some sort of cloud provisioned,
then you should probably look at Host Profiles, PowerCLI, PyVMOMI, and
other vSphere APIs. Hope that helps.

On Thu, Nov 9, 2017 at 5:07 AM Angel L. Mateo  wrote:

> Hello,
>
> I've been using puppet (OSE) for a long time. Now I would like to
> run
> puppet agent on my vmware ESXi servers. On this platform there is no
> puppet package and I haven't found the way to install it (although I
> have found puppet modules to configure them).
>
> Is there any documentation about installing agent on this platform?
>
> --
> Angel L. Mateo Martínez
> Sección de Telemática
> Área de Tecnologías de la Información
> y las Comunicaciones Aplicadas (ATICA)
> http://www.um.es/atica
> Tfo: 868889150
> Fax: 86337
>
> --
> 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/00a3b837-a133-b122-02f3-edeb5a4dd4fb%40um.es
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Rob Nelson

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

[Puppet Users] Puppet agent on vmware ESXi

[Angel L. Mateo]

Hello,

	I've been using puppet (OSE) for a long time. Now I would like to run 
puppet agent on my vmware ESXi servers. On this platform there is no 
puppet package and I haven't found the way to install it (although I 
have found puppet modules to configure them).


Is there any documentation about installing agent on this platform?

--
Angel L. Mateo Martínez
Sección de Telemática
Área de Tecnologías de la Información
y las Comunicaciones Aplicadas (ATICA)
http://www.um.es/atica
Tfo: 868889150
Fax: 86337

--
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/00a3b837-a133-b122-02f3-edeb5a4dd4fb%40um.es.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet agent 4.10.9 released

[Garrett Guillotte]

We released Puppet agent 4.10.9 on Monday, Nov. 6. This is a bug-fix
release of Puppet agent that updates cURL to 7.56.1, updates its
certificate authority (CA) certificate bundle, and updates Ruby and
rubygems to address several security vulnerabilities.

This release of Puppet agent also contains several Puppet and Facter bug
fixes, and updates Puppet to 4.10.9, Facter to 3.6.8, and MCollective to
version 2.10.6.

For details, please see the agent release notes at
https://puppet.com/docs/puppet/4.10/release_notes_agent.html.

-- 
*Garrett Guillotte*
Technical Writer
garrett.guillo...@puppet.com

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

[Puppet Users] Puppet agent 1.10.8 released

[Michelle Fredette]

Today we release Puppet agent 1.10.8.

This release contains a bug fix in Puppet 4.10.8 and a versioning fix in
the Windows package. No other components are updated.

Read the Puppet agent release notes for full details:
https://docs.puppet.com/puppet/4.10/release_notes_
agent.html#puppet-agent-1108



---
Michelle Fredette
Manager, Technical Publications

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