[Puppet Users] linux domain machines - cert error

[empbilly]

Hello guys,

At my place of work we have some computer labs. In these laboratories each 
computer has the operating system windows and linux. Both systems are in 
our AD domain.

I did a lab of tests and I have a functional puppet server. I put some 
nodes as root of the system. Everything working perfectly.

When I log in with a domain user on linux machines and run the "puppet 
agent -t" command, a new certificate is generated, but an error occurs 
stating that it does not match the server's certificate.

How can I get around this and make it always the same certificate?

-- 
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/0a79ff67-320a-4b50-823d-a8c3364b291d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] puppetserver vardir configuration

[jcbollinger]

I had a bit of an unpleasant surprise today.  I discovered that my 
puppetserver-based master seems unwilling to put reports or other varying 
data where I tell it to do.

The docs  say:

Puppet Server honors almost all settings in puppet.conf and should pick 
> them up automatically. However, some Puppet Server settings differ from a 
> Ruby Puppet master’s puppet.conf settings; we’ve detailed these differences 
> [in the rest of the document].


That document makes no mention of the $vardir, $reportdir, or related 
settings, and I don't see anything that appears to be about them in the 
docs for the various puppetserver-specific config files, so I expect the 
master to read my $vardir and / or $reportdir setting from puppet.conf, and 
honor it.

I find instead that no matter whether I specify vardir and / or reportdir 
in the [master] section or in the [main] section of puppet.conf, 
puppetserver instead uses its default vardir, 
/opt/puppetlabs/server/data/puppetserver, and a reportdir relative to 
that.  This looks similar to SERVER-798 
, but that's pretty old, 
and it was anyway closed as "cannot reproduce".  I'm seeing this issue on 
the current latest puppet and puppetserver (5.5.1 and 5.3.1, respectively).

Am I missing something here?  That is, is there some other place to 
configure these details?


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/1ed22dfc-51b4-45c5-b4bd-56885901c16a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] PuppetDB: manually import reports

[Thomas Müller]

Am Donnerstag, 19. April 2018 19:18:34 UTC+2 schrieb Christopher Wood:
>
> To challenge an assumption, what are you gaining from having more than one 
> puppet infrastructure (puppetservers+puppetdb)? 
>
> Could you perhaps handle your dev stuff with another environment or set of 
> puppetservers under the same CA with the same puppetdb? 
>
> Is there any reason for a separate puppet infrastructure to live longer 
> than it takes to proof an upgrade for production? 
>

I can't just throw away the dev infra after preparing changes for prod 
because of non-technical reasons. i'm limiting the usage of the dev system 
as much as I can, but there will be system connected to this dev infra. but 
I also want the data in the prod puppetdb to have a single point to make 
queries/reports (third party departments) or run octocatalog-diff to run 
against real facts from any system. 

Another usecase could be to have a async puppetdb connection from the 
second datacenter. If the connection between the datacenters is not  stable 
enough to use a single puppetdb I would need to add a puppetdb per DC.Then 
I also would want to sync data to the central puppetdb instance.

- Thomas

 

-- 
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/359e0529-421d-4acf-9569-3b2902a5f452%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] PuppetDB: manually import reports

[Christopher Wood]

To challenge an assumption, what are you gaining from having more than one 
puppet infrastructure (puppetservers+puppetdb)?

Could you perhaps handle your dev stuff with another environment or set of 
puppetservers under the same CA with the same puppetdb?

Is there any reason for a separate puppet infrastructure to live longer than it 
takes to proof an upgrade for production?

On Thu, Apr 19, 2018 at 04:46:01AM -0700, Thomas Müller wrote:
>HI
> 
>I've got some prod puppetserver/puppetdb and some dev
>puppetserver/puppetdb. But to have the complete overview over all nodes
>with the prod puppetdb I'd like to import the reports from the dev
>puppetserver (stored by reports=store config) into the prod puppetdb.
> 
>is there some hidden tool to do so? I wasn't able to find anything in that
>direction.
> 
>Reading
>
> https://github.com/puppetlabs/puppetdb/blob/master/puppet/lib/puppet/reports/puppetdb.rb
>this could maybe adapted to read a yaml file and then send it to puppetdb.
> 
>- Thomas
> 
>--
>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 [1]puppet-users+unsubscr...@googlegroups.com.
>To view this discussion on the web visit
>
> [2]https://groups.google.com/d/msgid/puppet-users/d5a3b811-655f-4497-84de-a5693954d08e%40googlegroups.com.
>For more options, visit [3]https://groups.google.com/d/optout.
> 
> References
> 
>Visible links
>1. mailto:puppet-users+unsubscr...@googlegroups.com
>2. 
> https://groups.google.com/d/msgid/puppet-users/d5a3b811-655f-4497-84de-a5693954d08e%40googlegroups.com?utm_medium=email_source=footer
>3. 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/20180419171825.hpvbgkvkxyisl5ki%40iniquitous.heresiarch.ca.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: PuppetDB: manually import reports

[Michael Watters]

Puppetdb data is all stored in postgresql so you should be able to copy the 
reports table from one server to the other.  For example, run this on your 
prod node.

pg_dump -h puppetdb-dev -U puppetdb -W -d puppetdb -t reports | psql -U 
puppetdb puppetdb

I'm not sure if you need more than just the reports table though.

On Thursday, April 19, 2018 at 7:46:01 AM UTC-4, Thomas Müller wrote:
>
> HI 
>
> I've got some prod puppetserver/puppetdb and some dev 
> puppetserver/puppetdb. But to have the complete overview over all nodes 
> with the prod puppetdb I'd like to import the reports from the dev 
> puppetserver (stored by reports=store config) into the prod puppetdb.
>
> is there some hidden tool to do so? I wasn't able to find anything in that 
> direction. 
>
> Reading 
> https://github.com/puppetlabs/puppetdb/blob/master/puppet/lib/puppet/reports/puppetdb.rb
>  
> this could maybe adapted to read a yaml file and then send it to puppetdb.
>
> - Thomas 
>

-- 
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/d08210de-d968-49d4-8c85-6f8060aa05c4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Updated manifest, now get Failed to apply catalog: "\xF8\xDD" on UTF-16LE on Windows

[jcbollinger]

On Wednesday, April 18, 2018 at 2:49:37 PM UTC-5, jmp242 wrote:
>
> I just got back to this. I tried re-installing the Windows 10 VM, tried a 
> different hostgroup in Foreman, seems like it's a catalog problem of some 
> sort. 
> puppet agent --trace gives no output for me.
>
> puppet agent --debug around the error gives:
> Debug: Prefetching chocolatey resources for package
> Debug: Executing: 'C:\ProgramData\chocolatey\bin\choco.exe pin list'
> Debug: Executing 'C:\ProgramData\chocolatey\bin\choco.exe list -lo -r'
> Debug: Executing 'C:\ProgramData\chocolatey\bin\choco.exe upgrade --noop 
> chocolatey.extension -r'
> Debug: Class[Yum]: The container Stage[main] will propagate my refresh 
> event
> Debug: Prefetching windows resources for package
> Debug: Unable to convert value 
> "{\x00B\x003\x00A\x00F\x00C\x006\x000\x008\x00-\x00D\x008\x001\x001\x00-\x000\x000\x000\x003\x00-\x004\x000\x005\x000\x00-\x002\x001\x00F\x00B\x002\x005\x00B\x004\x008\x00D\x006\x00E\x00}\x00\x00\x00\x00\x00{\xEEs\vj\x93\x00\x00H\x14t\x00\x18.t\x00d\x00l\x00l\x00\x00\x00~\xEEr\x0Fb\x93\x00\b\xD0\xC3\xF2w`8t\x00\x00
>  
> \xD9u\b 
> \xD9ul~\xD8uX\xDC\x8Bu\x00\x00\x00\x00\x00\x000\x000$t\x00\x02\x00\x00\x00v\xEEr\ag\x93\x00\f?\x0E\x00\x00\t\x04\x00\x00\x00\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x00(:t\x00\xB0:t\x00@\xCDs\x00
>  
> \xCCs\x00(Kt\x00hMt\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00(;t\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\xE8\x03\x00\x00\x00\x00\x00\x00\xD8Dt\x00\x06\x03\x00\x00"
> .force_encoding("UTF-16LE") to encoding UTF-8 due to 
> # "X\xDC" on UTF-16LE>
> Debug: Storing state
> Debug: Stored state in 0.08 seconds
> Error: Failed to apply catalog: "X\xDC" on UTF-16LE
>
>
> Notepad++ shows the manifests used here (as far as I'm able to tell) are 
> both UTF-8... 
>


When I said the problem is more likely to be in the manifests than in 
Puppet itself, I didn't mean specifically that the manifests might be 
encoded wrongly, although there are potential issues of that kind.  That 
Notepad++ thinks they are encoded in UTF-8 is a relevant detail, but not 
indicative of anything one way or the other.

The debug messages you presented are more useful, though.  Supposing that 
you haven't cut anything out, it looks like you have a chunk of *binary* 
data that Puppet is for some reason trying to interpret as text.  The 
embedded sequences of multiple consecutive 0 bytes are a dead giveaway that 
it's binary.  I'm uncertain whether Puppet is expecting from context that 
the byte sequence is UTF-16-encoded text, or whether it is guessing based 
on the content, but the byte sequence overall does not conform to any of 
the UTFs, and it does not look like text in any of ASCII-compatible 
single-byte encoding, either.

Since this appears to be happening while Puppet is pre-fetching resources, 
I am forced to revise my opinion that the problem is somewhere among your 
manifests.  Your manifests are probably not responsible for this, except 
inasmuch as they declare at least one Package resource that explicitly or 
implicitly uses the default 'windows' provider.  That's a flaw only if you 
intended to do differently.

Inasmuch as the problem appears to occur in the scope of prefetching 
'windows' packages, it is probably right to attribute it to Puppet.  But 
Puppet's 'windows' package provider generally works as advertised, so it 
seems likely that something about the current state of the target machine 
is contributing.


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/fa856915-87a7-4bf8-8173-2474e6cc9f7a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Brackets in hiera yaml

[jcbollinger]

On Wednesday, April 18, 2018 at 9:37:50 AM UTC-5, MartinW wrote:
>
>
> Hi John
>
> Thanks for the reply
>
> The hiera is generated by a custom Ruby script. I have tried tweaking it 
> to output both with quotes and without but it didn't help
>


And you should stick with the version that quotes the whole string, but as 
I said before, that's for better protection against potential *other* 
issues, not for solving this one.
 

>
> The end config file on the server is being created with an 
> Ensure_resources statement like this:
>  
>
ensure_resources('icinga2::object::host', 
> lookup('profile::icinga2_master::monitoring::objects::servers'), {'ensure' 
> => 'present'})
>
>
Attributing the config file creation to the ensure_resources() call is like 
attributing your tax preparer's work to his landlord.  Ensure_resources() is 
one way to tell Puppet to engage specific resources to do the job -- in 
this case, resources of type icinga2::object::host.  But that resource type 
belongs to a third-party module, and the problem is in that module and 
specific to it.

We might be able to help you solve the problem or find a better workaround, 
but that starts with you telling us which version of which icinga2 module 
you are using, and where to find it (on the Forge, ideally).


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/be65dd60-26ad-4688-a298-ec66d4222f66%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Environment variable setting while using a module

[Ugo Bellavance]

On Thursday, April 19, 2018 at 7:50:30 AM UTC-4, Thomas Müller wrote:
>
> Hi Ugo
>
> Am Freitag, 30. März 2018 17:27:28 UTC+2 schrieb Ugo Bellavance:
>>
>> Hi,
>>
>> I'm using the puppetlabs-postgresql module and it works very well, but I 
>> want to make it work with a non-standard version of postgresql (from Red 
>> Hat Software Collections) because I would like to use Postgresql 9.6 on 
>> RHEL 7.  Almost everything is working, but I get errors from some commands 
>> that cannot find a shared object.  This is caused by the fact that Software 
>> Collections package use non-standard paths for their files.  For example, 
>> postgresql binaries are in opt/rh/rh-postgresql96/root/usr/bin/ than 
>> /usr/bin/.  Here's the kind of errors I get:
>>
>> /opt/rh/rh-postgresql96/root/usr/bin/psql: error while loading shared 
>> libraries: libpq.so.rh-postgresql96-5: cannot open shared object file: No 
>> such file or directory
>>
>>
>> I've used the pl-postgresql module successfully this way:
>
>
> https://gist.github.com/vinzent/448fa47032a6f050fb4c501cc741ccad#file-puppetdb-postgresql-9-5-example-pp
>

Hi,

That looks great, but is that in the puppetdb module or in the postgresql 
module? 

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/2932b0eb-ab4d-432d-ae91-1f0fb3e8d86a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Environment variable setting while using a module

[Thomas Mueller]

On 04/19/2018 02:21 PM, Ugo Bellavance wrote:
>
>
> On Thursday, April 19, 2018 at 7:50:30 AM UTC-4, Thomas Müller wrote:
>
> Hi Ugo
>
> Am Freitag, 30. März 2018 17:27:28 UTC+2 schrieb Ugo Bellavance:
>
> Hi,
>
> I'm using the puppetlabs-postgresql module and it works very
> well, but I want to make it work with a non-standard version
> of postgresql (from Red Hat Software Collections) because I
> would like to use Postgresql 9.6 on RHEL 7.  Almost everything
> is working, but I get errors from some commands that cannot
> find a shared object.  This is caused by the fact that
> Software Collections package use non-standard paths for their
> files.  For example, postgresql binaries are in
> opt/rh/rh-postgresql96/root/usr/bin/ than /usr/bin/.  Here's
> the kind of errors I get:
>
> /opt/rh/rh-postgresql96/root/usr/bin/psql: error while loading
> shared libraries: libpq.so.rh-postgresql96-5: cannot open
> shared object file: No such file or directory
>
>
> I've used the pl-postgresql module successfully this way:
>
> 
> https://gist.github.com/vinzent/448fa47032a6f050fb4c501cc741ccad#file-puppetdb-postgresql-9-5-example-pp
> 
> 
>
>
> Hi,
>
> That looks great, but is that in the puppetdb module or in the
> postgresql module? 
>

I was configuring postgresql SCL for use with the puppetdb module.

the important part  you is the postgresql::globals class that defines
all necessary pathes that the postgresql SCL uses.

- Thomas

-- 
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/610d006e-1b7a-6f1f-4435-6ab9bcb4a300%40chaschperli.ch.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet "package" resource type for multi-file installer

[Christopher Wood]

Sounds like this thing would be useful?

https://forge.puppet.com/puppet/archive

On Wed, Apr 18, 2018 at 07:55:40PM -0700, Ty Young wrote:
>I'm still ramping up on Puppet 5.4.0, but I'm stuck on something.
> 
>I have a customer needing to automate installation of a software package
>on Windows nodes. The installer is most easily transported as a .zip file,
>but (obviously) would need to be unzipped before running the enclosed .bat
>file to perform the installation. 
> 
>Any suggestions?  
> 
>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 [1]puppet-users+unsubscr...@googlegroups.com.
>To view this discussion on the web visit
>
> [2]https://groups.google.com/d/msgid/puppet-users/f8366287-59aa-46db-b20b-8e180b3b24a8%40googlegroups.com.
>For more options, visit [3]https://groups.google.com/d/optout.
> 
> References
> 
>Visible links
>1. mailto:puppet-users+unsubscr...@googlegroups.com
>2. 
> https://groups.google.com/d/msgid/puppet-users/f8366287-59aa-46db-b20b-8e180b3b24a8%40googlegroups.com?utm_medium=email_source=footer
>3. 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/20180419115652.aufc267tf2a4x643%40iniquitous.heresiarch.ca.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: puppet "package" resource type for multi-file installer

[Thomas Müller]

Am Donnerstag, 19. April 2018 04:55:40 UTC+2 schrieb Ty Young:
>
> I'm still ramping up on Puppet 5.4.0, but I'm stuck on something.
>
> I have a customer needing to automate installation of a software package 
> on Windows nodes. The installer is most easily transported as a .zip file, 
> but (obviously) would need to be unzipped before running the enclosed .bat 
> file to perform the installation.  
>
>
puppet-archive (https://forge.puppet.com/puppet/archive) could help you 
solve the transfering/un-zip-ing part.

If you are adventurous you might start to use chocolatey: 
https://github.com/chocolatey/choco/wiki/CreatePackages  and 
https://forge.puppet.com/chocolatey/chocolatey - which really helps do 
streamline the installation part.

- Thomas

-- 
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/6d7f67fe-33dd-4d84-8776-c5a4142553ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Environment variable setting while using a module

[Thomas Müller]

Hi Ugo

Am Freitag, 30. März 2018 17:27:28 UTC+2 schrieb Ugo Bellavance:
>
> Hi,
>
> I'm using the puppetlabs-postgresql module and it works very well, but I 
> want to make it work with a non-standard version of postgresql (from Red 
> Hat Software Collections) because I would like to use Postgresql 9.6 on 
> RHEL 7.  Almost everything is working, but I get errors from some commands 
> that cannot find a shared object.  This is caused by the fact that Software 
> Collections package use non-standard paths for their files.  For example, 
> postgresql binaries are in opt/rh/rh-postgresql96/root/usr/bin/ than 
> /usr/bin/.  Here's the kind of errors I get:
>
> /opt/rh/rh-postgresql96/root/usr/bin/psql: error while loading shared 
> libraries: libpq.so.rh-postgresql96-5: cannot open shared object file: No 
> such file or directory
>
>
> I've used the pl-postgresql module successfully this way:

https://gist.github.com/vinzent/448fa47032a6f050fb4c501cc741ccad#file-puppetdb-postgresql-9-5-example-pp

The patch is already included in forge releases.

- Thomas 

-- 
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/f8b78088-431b-47f2-b735-65a0acbd1995%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] PuppetDB: manually import reports

[Thomas Müller]

HI 

I've got some prod puppetserver/puppetdb and some dev 
puppetserver/puppetdb. But to have the complete overview over all nodes 
with the prod puppetdb I'd like to import the reports from the dev 
puppetserver (stored by reports=store config) into the prod puppetdb.

is there some hidden tool to do so? I wasn't able to find anything in that 
direction. 

Reading 
https://github.com/puppetlabs/puppetdb/blob/master/puppet/lib/puppet/reports/puppetdb.rb
 
this could maybe adapted to read a yaml file and then send it to puppetdb.

- Thomas 

-- 
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/d5a3b811-655f-4497-84de-a5693954d08e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Announce: Puppet agent 1.10.12

[Brent Clark]

Good day Eric

Thanks for replying and sorting out the issue.

Regards

Brent


On 18/04/2018 17:19, Eric Sorenson wrote:
Yep, this was an error in the build/ship process - we're scrubbing 
them out now. Sorry for the confusion.


--eric0

On Wednesday, April 18, 2018 at 12:25:23 AM UTC-7, Brent wrote:

Just a question

Shouldn't the puppet 5 packages not be in
http://apt.puppetlabs.com/pool/stretch/PC1/p/puppet-agent/
 removed?

Regards

Brent

On 18/04/2018 09:18, Brent Clark wrote:


Good day Guys

Anyone else having a problem where the upgrade tries to jump to
version 5.3.6-1stretch?

I just want 1.10.12RELEASE.

Regards

Brent


On 18/04/2018 07:00, Garrett Guillotte wrote:


Puppet agent 1.10.12 is a bug-fix release that includes updates
for Puppet 4.10.11
, Facter
3.6.10 ,
Hiera 3.3.3 (which contains no user-facing changes), and
pxp-agent 1.5.7. It also contains updates to curl and fixes for
Ruby security issues. For details, see
https://puppet.com/docs/puppet/4.10/release_notes_agent.html


There was no public Puppet agent 1.10.11 release.

-- 
*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/CAP7LywFVkyGtvb4_3epVpdJN%2B1gOFzvekxouZrpBVSf26u4ekg%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/2311bd85-003a-4bda-8bbf-7d8f9cc6f63c%40googlegroups.com 
.

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


--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/868bcad1-b1a1-8212-9e6d-0bdb84e15ae4%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Changes coming to puppet docker containers!

[Felix Barbeira]

Nice to hear that! I can't wait to see the puppetserver officially running 
in k8s!

El jueves, 19 de abril de 2018, 0:01:55 (UTC+2), Morgan Rhodes escribió:
>
> Hello,
>
> I’m excited to announce that work is starting on a project to provide 
> supported docker containers running the Puppet Platform server stack.
>
> The initial work for this project will build on the work in 
> puppet-in-docker [1]. Ultimately, that repository is going to be deprecated 
> in favor of moving the individual container build scripts into their parent 
> project (i.e., the information in 
> https://github.com/puppetlabs/puppet-in-docker/tree/master/puppetserver 
> will move into https://github.com/puppetlabs/puppetserver ). The 
> container builds will be integrated with the normal packaging builds, thus 
> making them available at the same time (and without the manual 
> intervention) as the OS-specific packaging. The containers that will be 
> migrating into their parent projects will be Puppet Server, PuppetDB, 
> PostgreSQL, and r10k.
>
> As part of this work we’re going to be dropping support for a few of the 
> existing containers published on docker hub [2], puppetboard and 
> puppetexplorer. If you’re interested in taking over ownership of either of 
> these containers, let us know.
>
> The epic with tickets for the initial phase of this work is 
> https://tickets.puppetlabs.com/browse/CPR-560, you can follow along there 
> for progress and updates. There will be linked epics as we move forward 
> with planning and scoping for additional phases of development.
>
> If you’re already running puppet server components in containers, we’d 
> love to hear from you. Especially if you have any information on particular 
> pain points or unexpected issues you’ve run into.
>
> 
>
> 1. https://github.com/puppetlabs/puppet-in-docker
> 2. https://hub.docker.com/u/puppet 
> -- 
> Morgan Rhodes
> mor...@puppet.com
> Release Engineer
>

-- 
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/4c7501d2-b4e3-4003-a86b-c51623ec85ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.