[Puppet Users] Upcoming changes to the rolling 'puppet' repos!
Hi all! Tomorrow morning (~9am Pacific) we'll be updating the rolling 'puppet' repos to point to the new 'puppet7' release from a couple of weeks ago. If you're already using the 'puppet' release packages (such as http://yum.puppetlabs.com/puppet-release-el-7.noarch.rpm), your repos will start pointing to puppet7 tomorrow. Let us know if you run into any issues! Thanks, Morgan -- Morgan Rhodes Release Engineering mor...@puppet.com she/her/hers -- 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%2BFnDv0T8TwwdDNj-HKnVd3v89sttCBd%2BR0vaENmUj4Vz6DeNA%40mail.gmail.com.
Re: [Puppet Users] where to download puppet agent 4.10?
Hi Peter, Puppet 4.10.x (puppet-agent 1.10.x) was never released for bionic as that stream went EOL in 2018. There are bionic packages available for puppet-agent 5 and above, though I'd recommend upgrading to at least puppet-agent 6 if possible, as 5.x will be going EOL soon. Morgan On Mon, Nov 30, 2020 at 8:15 AM pko...@themolecule.com < pko...@themolecule.com> wrote: > sorry...I've been all over http://release-archives.puppet.com/ > Can anyone tell me where to download puppet-agent v4.10? I particularly > need it for ubuntu bionic. > thx > -peter > > -- > 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/391fb88c-9cb8-4304-9a92-b9b5d8521a4fn%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/391fb88c-9cb8-4304-9a92-b9b5d8521a4fn%40googlegroups.com?utm_medium=email_source=footer> > . > -- Morgan Rhodes Release Engineering mor...@puppet.com she/her/hers -- 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%2BFnDv0obNzDXTbEzUj1EJ90f9RTq7Z3GzvJgsQGVdH-uYsL8g%40mail.gmail.com.
Re: [Puppet Users] Issue with puppet6 release packages
Hi Peter, Due to some issues with the rollout of the repos yesterday, we're going to leave the rolling 'puppet' repo pointing at puppet6 until at least November 30th so we don't cause unexpected upgrades for folks while we have many people out for US holidays. On Fri, Nov 20, 2020 at 12:58 PM Peter Meier wrote: > > * If /etc/yum.repos.d/puppet.repo exists -- you are affected. Unless > > you want to be subscribed to the repo with rolling updates, you > > should uninstall and reinstall the release package. > > * If /etc/yum.repos.d/puppet6.repo exists -- you are not affected. > > So what is the intend for rolling updates? > > Given https://yum.puppetlabs.com/puppet/el/7/x86_64/ does not anymore > contain the 7.0.0 release although it did for a while. > > ~pete > -- Morgan Rhodes Release Engineering mor...@puppet.com she/her/hers -- 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%2BFnDv0HYax58nJDHODAs_DCJuHdU%3DQZtG4kWfXESvoubaAeZw%40mail.gmail.com.
[Puppet Users] Issue with puppet6 release packages
Hi all, While we were shipping some updated release packages earlier today, we had some issues with the puppet6 release packages found at the top level of yum.puppetlabs.com and apt.puppetlabs.com. If you installed puppet6 release packages from those locations I strongly suggest uninstalling and reinstalling to avoid inadvertent upgrades to puppet7. Those files have been updated at this point, and the affected release packages were only incorrect for a few hours earlier today. If you want to verify whether or not your system is affected, you can check the following: *On rpm systems* - If /etc/yum.repos.d/puppet.repo exists -- you are affected. Unless you want to be subscribed to the repo with rolling updates, you should uninstall and reinstall the release package. - If /etc/yum.repos.d/puppet6.repo exists -- you are not affected. *On deb systems* - If /etc/apt/sources.list.d/puppet.list exists -- you are affected. You should uninstall the release package, manually remove /etc/apt/sources.list.d/puppet.list, and reinstall the release package - If /etc/apt/sources.list.d/puppet6.list exists -- you are not affected. Apologies for any issues caused by this, please feel free to reach out with any additional questions or concerns. -- Morgan Rhodes Release Engineering mor...@puppet.com she/her/hers -- 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%2BFnDv0V8vPw1iDfs%2BL4B0%2Bfz%3DVDUXaJzSE-QZjbRuOweX6g%2Bw%40mail.gmail.com.
Re: [EXTERNAL] - [Puppet Users] problems installing.
Hi Dirk, The `puppet-tools` repo contains bolt and pdk so that you can include that repo without worrying about upgrading your puppet-agent, puppetserver, etc packages. On Wed, Jul 22, 2020 at 10:39 PM 'Dirk Heinrichs' via Puppet Users < puppet-users@googlegroups.com> wrote: > Am Montag, den 20.07.2020, 12:52 -0700 schrieb Steve Redlich: > > root@lynx:/tmp# dpkg -i puppet-tools-release-bionic.deb > > > Hmm, that used to be "puppet-release-...". When has this been changed to > "puppet-tools-release-..."? > > BTW: Although this package doesn't have any dependencies, other packages > might have some, so it's better to use > > apt-get install ./package.deb > > to get them properly resolved. > > 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/496db2d9048e3cc18cffdc0dc916241c86ff2ed6.camel%40opentext.com > <https://groups.google.com/d/msgid/puppet-users/496db2d9048e3cc18cffdc0dc916241c86ff2ed6.camel%40opentext.com?utm_medium=email_source=footer> > . > -- Morgan Rhodes Release Engineering mor...@puppet.com she/her/hers -- 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%2BFnDv1eksPjmEKOdrj8knqf2mYm7nG54krBTpCi_vRa-mWj0g%40mail.gmail.com.
Re: [Puppet Users] Re: problems installing.
Hi Steve, What URL did you get the puppet-tools-release package from? I spun up an ubuntu 18.04 VM this morning and I was able to install the package from http://apt.puppetlabs.com/puppet-tools-release-bionic.deb without issue. Thanks, Morgan On Mon, Jul 20, 2020 at 9:59 PM Steve Redlich wrote: > After waiting a long time and playing unsuccessfuly with apt, I was able > to extract puppet-tools.list from the .deb using dpkg-deb and install it. > to help the next person with this problem, > > # Puppet Tools bionic Repository > deb http://apt.puppet.com bionic puppet-tools > > On Monday, July 20, 2020 at 2:00:29 PM UTC-7 Steve Redlich wrote: > >> I'm not able to setup the puppet apt repository on ubuntu 18.04 >> >> >> root@lynx:/tmp# dpkg -i puppet-tools-release-bionic.deb >> (Reading database ... 239282 files and directories currently installed.) >> Preparing to unpack puppet-tools-release-bionic.deb ... >> Unpacking puppet-tools-release (1.0.0-4bionic) over (1.0.0-4bionic) ... >> Setting up puppet-tools-release (1.0.0-4bionic) ... >> chmod: cannot access '/etc/apt/sources.list.d/puppet-tools.list': No such >> file or directory >> >> root@lynx:/tmp# touch /etc/apt/sources.list.d/puppet-tools.list >> root@lynx:/tmp# dpkg -i puppet-tools-release-bionic.deb >> (Reading database ... 239282 files and directories currently installed.) >> Preparing to unpack puppet-tools-release-bionic.deb ... >> Unpacking puppet-tools-release (1.0.0-4bionic) over (1.0.0-4bionic) ... >> Setting up puppet-tools-release (1.0.0-4bionic) ... >> root@lynx:/tmp# cat /etc/apt/sources.list.d/puppet-tools.list >> root@lynx:/tmp# >> (note empty file) >> I would appreciate it if someone could reply with a contents of the >> puppet-tools.list apt repository listing so I can get started with 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/cc44d63e-f1af-49b9-8073-49cfaf2ea06dn%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/cc44d63e-f1af-49b9-8073-49cfaf2ea06dn%40googlegroups.com?utm_medium=email_source=footer> > . > -- Morgan Rhodes Release Engineering mor...@puppet.com she/her/hers -- 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%2BFnDv3jXzuTdc8XE9z4vatETnxKT0wPDyOHv00x6nyyrDiDtQ%40mail.gmail.com.
Re: [Puppet Users] Question about Puppet and MCollective repositories at yum.puppetlabs.com
Hi Bill, They will stay on yum.puppetlabs.com for a bit, though we are working on getting a separate url with repos for old releases. Timing on that is still tbd, but there will be more communication as we know more. On Fri, Jun 26, 2020 at 12:49 PM 'William Bryce' via Puppet Users < puppet-users@googlegroups.com> wrote: > Hello, > > We have an application that uses Puppet 5.5 and mco and I have a > question. I realize that both of these products will be end of life in > November however will puppet labs keep both Puppet 5.5 and mco in > yum.puppetlabs.com repo or will they be removed? > > Thanks in advance. > > Bill. > > -- > 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/10392040-1998-48de-8117-faa76be17c18n%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/10392040-1998-48de-8117-faa76be17c18n%40googlegroups.com?utm_medium=email_source=footer> > . > -- Morgan Rhodes Release Engineering mor...@puppet.com she/her/hers -- 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%2BFnDv3j1%3DdN2b2yPJhDdM30LcbF%3DmY28FQ7d7E4O0O1sGEeKw%40mail.gmail.com.
Re: [Puppet Users] Where is source rpm for puppet6 open source rpm
Hi, We no longer provide source RPMs for puppet6 packages due to lack of support from the packaging tools we use. On Sat, Apr 18, 2020 at 1:28 PM hai wu wrote: > Where is source rpm for puppet6 open source rpms? I could not find them .. > > -- > 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%3DnZdo%2BC_q4EcfwgKcg9SdkT3QeqpaSJNT5bA61tr9JCZyaQ%40mail.gmail.com > . > -- Morgan Rhodes Release Engineering mor...@puppet.com she/her/hers -- 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%2BFnDv1o75DP2zZN%2BHdrSKfxoWsFAtiWX9Vh_RnWrG4TOw-YEA%40mail.gmail.com.
Re: [Puppet Users] How to get max-active-instances in container?
Hi Michael,
Hm, that should be working. Can you double-check for any typos in the
environment variables?
I'm running with the following and everything seems to be working as
expected:
diff --git a/docker-compose.yml b/docker-compose.yml
index 646da33..7fc4140 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -18,6 +18,7 @@ services:
- DNS_ALT_NAMES=puppet,puppet.${DOMAIN:-internal},${DNS_ALT_NAMES:-}
- PUPPERWARE_ANALYTICS_ENABLED=${PUPPERWARE_ANALYTICS_ENABLED:-true}
- PUPPETDB_SERVER_URLS=https://puppetdb.${DOMAIN:-internal}:8081
+ -
PUPPETSERVER_MAX_ACTIVE_INSTANCES=${PUPPETSERVER_MAX_ACTIVE_INSTANCES:-}
volumes:
- puppetserver-code:/etc/puppetlabs/code/
- puppetserver-config:/etc/puppetlabs/puppet/
$ cat .env
PUPPETSERVER_MAX_ACTIVE_INSTANCES=2
puppet_1| 2019-10-30 21:53:21,131 INFO [p.s.j.i.jruby-agents] Finished
creating JRubyInstance 2 of 2
For my tests I was using puppetserver 5.3.7.
On Wed, Oct 23, 2019 at 4:54 PM Michael Gale wrote:
> Hello,
>
> I am using https://github.com/puppetlabs/pupperware to deploy puppet
> server 5.3.7 and am having a hard time adjusting the jruby
> max-active-instances.
>
> I was following the docs from here:
> https://hub.docker.com/r/puppet/puppetserver/
> and set my environment var PUPPETSERVER_MAX_ACTIVE_INSTANCES to 4 in my
> .env file and updated my docker-compose.yml:
>
> --snip--
> - PUPPETSERVER_JAVA_ARGS=${PUPPETSERVER_JAVA_ARGS:-}
> -PUPPETSERVER_MAX_ACTIVE_INSTANCES=${PUPPETSERVER_MAX_ACTIVE_INSTANCES:-}
> --snip--
>
> I don't think it is working because in see the following in the logs:
> --snip--
> puppet_1| 2019-10-23 22:50:03,199 INFO [p.s.j.i.jruby-internal]
> Creating JRubyInstance with id 1.
> puppet_1| 2019-10-23 22:50:19,088 INFO [p.s.j.i.jruby-agents]
> Finished creating JRubyInstance 1 of 1
> --snip--
>
> Am I setting it correctly?
>
> Thanks
> Michael
>
> --
> 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%2BYXe5mAqk%2B7rnkJ%3DnqA0O3GdmrjuWpv7ngadzAiPYHyQti86Q%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CA%2BYXe5mAqk%2B7rnkJ%3DnqA0O3GdmrjuWpv7ngadzAiPYHyQti86Q%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
--
Morgan Rhodes
Release Engineering
mor...@puppet.com
she/her/hers
--
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%2BFnDv3cE8hv%2BjLw7bzG6qJFpby%3D0FjHYiiKvNBD9pqOzFqgfA%40mail.gmail.com.
Re: [Puppet Users] Re: [RFC] Changes to open-source container versioning
On Thu, Oct 17, 2019 at 1:03 PM A Manzer wrote: > On Thursday, October 17, 2019 at 3:10:36 PM UTC-4, Morgan Rhodes wrote: >> >> The "from source" builds aren't quite nightlies, since they get built on >> every commit/PR into master, so depending on how much development is >> happening it could end up built more often, and there's certainly more risk >> of picking up bugs. >> >> In this model the source builds aren't built based on a tag. We use `git >> describe` to come up with the tag for the container, but the code is from >> head/master. >> > > This makes sense, thanks. It's close-ish to a nightly. :-) > > Do you have a feel for whether or not it would be valuable to have a >> `6.7-edge` in addition to `edge`, where `6.7-edge` would be HEAD of master >> from the time 6.7.0 is tagged until the last commit before 6.8.0 is pushed? >> Thinking about it more it might make sense to just have `edge` as the >> latest from-source build and save the more granular/versioned tags for >> builds from packages. >> > > Sure! Tags are free right? Maybe there's something in 6.8 that someone > doesn't want so they'll stick to 6.7. Or maybe someone wants to test the > 6.7 stream beginning to end, which might overlap with the 6.8 stream which > they want to test too. Or maybe there will be a security update to 6.7 > after you start work on 6.8, so both will be going at once. I think > there's value in: > `6` > `6-edge` > `6.7` (or maybe even `6.7-latest`) > `6.7-edge` > `6.7.2` > `latest` > `edge` > Thanks for the feedback! > -- > 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/5e90fbe8-5d99-4aaa-8e8b-7af410d2a41c%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/5e90fbe8-5d99-4aaa-8e8b-7af410d2a41c%40googlegroups.com?utm_medium=email_source=footer> > . > -- Morgan Rhodes Release Engineering mor...@puppet.com she/her/hers -- 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%2BFnDv3ed1%3DgTe1aRfxZWmS6zGGFUinWcLt365bExZT6SZi_ag%40mail.gmail.com.
Re: [Puppet Users] Re: [RFC] Changes to open-source container versioning
On Thu, Oct 17, 2019 at 5:02 AM A Manzer wrote: > On Wednesday, October 16, 2019 at 5:44:27 PM UTC-4, Morgan Rhodes wrote: >> >> >> Is your confusion mostly around the fact that one of them is built from >> source and one from package, or that 6.7 is more of a floating tag? I know >> I've seen that pattern in some other upstream repos like centos, postgres, >> mysql, etc, but for those it might be 6.7 points to the latest 6.7.x that >> was shipped, rather than more like head/nightly. >> >> > It's mostly the from source, from package distiction. I'm not familiar > enough with Puppet's release cycle to know the distinction between a from > source build and a from package build. Are "from source" builds > essentially just nightlys? I think people are more familiar with keywords > such as "head", "master", "edge", or "nightly" and the tag should include > something like that. If they're not exactly nightly, but based on a tag in > the source, what differentiates a from source build and a from package > build? > The "from source" builds aren't quite nightlies, since they get built on every commit/PR into master, so depending on how much development is happening it could end up built more often, and there's certainly more risk of picking up bugs. In this model the source builds aren't built based on a tag. We use `git describe` to come up with the tag for the container, but the code is from head/master. If I were to look at these tags on Docker Hub, I'd expect them to represent > the following: > puppet/puppetserver:6.7 => The latest release in the 6.7 series, > moving from 6.7.0, through 6.7.1, etc. > puppet/puppetserver:6.7.0 => Exactly the release 6.7.0 and never changing > puppet/puppetserver:latest => The latest release of Puppet Server, moving > through minor *and* major versions. (Perhaps there's room for a > puppet/puppetserver:6 tag here) > puppet/puppetserver:edge => This one's less immediately obvious to me, > but after a moment I'd probably realize that it was some kind of nightly or > pre-release beta, especially given the tag date would be after the :latest > tag. > Do you have a feel for whether or not it would be valuable to have a `6.7-edge` in addition to `edge`, where `6.7-edge` would be HEAD of master from the time 6.7.0 is tagged until the last commit before 6.8.0 is pushed? Thinking about it more it might make sense to just have `edge` as the latest from-source build and save the more granular/versioned tags for builds from packages. > > > -- > 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/a07de248-a5dd-4e95-a9ae-0798c2c8a8ce%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/a07de248-a5dd-4e95-a9ae-0798c2c8a8ce%40googlegroups.com?utm_medium=email_source=footer> > . > -- Morgan Rhodes Release Engineering mor...@puppet.com she/her/hers -- 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%2BFnDv0DNrnL4rv2saRDCzLgUkSw0GX13KNmHYJB2%2Bm0WNy3fA%40mail.gmail.com.
Re: [Puppet Users] Re: [RFC] Changes to open-source container versioning
On Thu, Oct 17, 2019 at 1:51 AM Bart-Jan Vrielink wrote: > Hello, > > > I'm equally confused. For almost all containers I'm used to, if the tag is > just a version number, to me it indicates "built the same way as latest, > but a fixed snapshot". If it is not built the same way as latest, I would > expect the tag to include a label for that. So puppet/puppetserver:6.7-edge > is more in line with other vendors of Docker images. This only for the > first example in the table below, the others do make sense. > > > Great, thank you for the feedback, that seems reasonable. > > -Original message- > *From:* Morgan Rhodes > *Sent:* Wednesday 16th October 2019 23:44 > *To:* Puppet Users > *Subject:* Re: [Puppet Users] Re: [RFC] Changes to open-source container > versioning > > > > On Wed, Oct 16, 2019 at 4:32 AM A Manzer wrote: > >> I find this scheme confusing. I would be hard pressed to explain the >> difference between :6.7, built from *source*, and :6.7.0, built from a >> *package*. I also don't think it's clear that :6.7 would advance past >> :6.7.0 in time. >> > > Is your confusion mostly around the fact that one of them is built from > source and one from package, or that 6.7 is more of a floating tag? I know > I've seen that pattern in some other upstream repos like centos, postgres, > mysql, etc, but for those it might be 6.7 points to the latest 6.7.x that > was shipped, rather than more like head/nightly. > > >> >> I like the :edge and :latest tags. >> >> But I think I'd be happier with some kind of "nightly" specification on >> the source version (unless I've misunderstood). Maybe :6.7-nightly. That >> would make it more clear to me that it's a frequent build of the 6.7 >> branch, while 6.7.0 is a pinned version. >> >> On the whole though, I think it's a good change. Thank you! >> >> >> On Tuesday, October 15, 2019 at 2:56:49 PM UTC-4, Morgan Rhodes wrote: >>> >>> Hi all, >>> >>> *tl;dr* - We're trying to make the versioning scheme for our containers >>> more intuitive, changes summarized in the table below, see more details at >>> https://github.com/puppetlabs/puppetserver/pull/2188 >>> >>> build typecurrent tagnew tag >>> from source puppet/puppetserver:6.7.0 puppet/puppetserver:6.7 >>> from source (latest) puppet/puppetserver:latest puppet/puppetserver:edge >>> from package n/a puppet/puppetserver:6.7.0 >>> from package (latest) n/a puppet/puppetserver:latest >>> *Versioning* >>> >>> For a while now, our containers have included a package built from >>> source and versioned based on the most recent tag to the repo. While we >>> still think building from source provides value to our users, it's become >>> clear that they also need a way to pin to a specific, released version of >>> puppetserver and count on that container not being updated. To address >>> this, we're changing the versioning scheme for our container builds. >>> >>> When we build images from source, those images will be versioned with >>> X.Y versions based on the latest tag on master. So, for example, the >>> current image versioned puppet/puppetserver:6.6.0 would move to >>> puppet/puppetserver:6.6. This tag will continue to have rolling updates >>> until the next X or Y release. If you want to follow whatever the latest >>> version of the image from source is, you will want to pin to >>> puppet/puppetserver:edge. >>> >>> We will also start building and shipping images when puppetserver is >>> shipped publicly. These images will be tagged with an X.Y.Z version that >>> will match the version of puppetserver installed on that image. This tag >>> will not receive any updates. If you want to follow the latest released >>> version of puppetserver, you will want to pin to puppet/puppetserver:latest. >>> >>> *Other Changes for the puppetserver images* >>> >>> We are also looking into removing the puppetserver-standalone image. >>> I've added a `USE_PUPPETDB` environment variable that can be set to false >>> when running the puppetserver image to have the same behavior as the >>> current puppetserver-standalone image. >>> >>> *Questions / Comments / Concerns?* >>> >>> Please leave comments at >>> https://github.com/puppetlabs/puppetserver/pull/2188 or respond here. >>> >>> -- >>> Morgan Rhodes >>> Release Engineering >>> mor...@puppet.com >>> s
Re: [Puppet Users] Re: [RFC] Changes to open-source container versioning
On Wed, Oct 16, 2019 at 4:32 AM A Manzer wrote: > I find this scheme confusing. I would be hard pressed to explain the > difference between :6.7, built from *source*, and :6.7.0, built from a > *package*. I also don't think it's clear that :6.7 would advance past > :6.7.0 in time. > Is your confusion mostly around the fact that one of them is built from source and one from package, or that 6.7 is more of a floating tag? I know I've seen that pattern in some other upstream repos like centos, postgres, mysql, etc, but for those it might be 6.7 points to the latest 6.7.x that was shipped, rather than more like head/nightly. > > I like the :edge and :latest tags. > > But I think I'd be happier with some kind of "nightly" specification on > the source version (unless I've misunderstood). Maybe :6.7-nightly. That > would make it more clear to me that it's a frequent build of the 6.7 > branch, while 6.7.0 is a pinned version. > > On the whole though, I think it's a good change. Thank you! > > > On Tuesday, October 15, 2019 at 2:56:49 PM UTC-4, Morgan Rhodes wrote: >> >> Hi all, >> >> *tl;dr* - We're trying to make the versioning scheme for our containers >> more intuitive, changes summarized in the table below, see more details at >> https://github.com/puppetlabs/puppetserver/pull/2188 >> >> build typecurrent tagnew tag >> from source puppet/puppetserver:6.7.0 puppet/puppetserver:6.7 >> from source (latest) puppet/puppetserver:latest puppet/puppetserver:edge >> from package n/a puppet/puppetserver:6.7.0 >> from package (latest) n/a puppet/puppetserver:latest >> *Versioning* >> >> For a while now, our containers have included a package built from source >> and versioned based on the most recent tag to the repo. While we still >> think building from source provides value to our users, it's become clear >> that they also need a way to pin to a specific, released version of >> puppetserver and count on that container not being updated. To address >> this, we're changing the versioning scheme for our container builds. >> >> When we build images from source, those images will be versioned with X.Y >> versions based on the latest tag on master. So, for example, the current >> image versioned puppet/puppetserver:6.6.0 would move to >> puppet/puppetserver:6.6. This tag will continue to have rolling updates >> until the next X or Y release. If you want to follow whatever the latest >> version of the image from source is, you will want to pin to >> puppet/puppetserver:edge. >> >> We will also start building and shipping images when puppetserver is >> shipped publicly. These images will be tagged with an X.Y.Z version that >> will match the version of puppetserver installed on that image. This tag >> will not receive any updates. If you want to follow the latest released >> version of puppetserver, you will want to pin to puppet/puppetserver:latest. >> >> *Other Changes for the puppetserver images* >> >> We are also looking into removing the puppetserver-standalone image. I've >> added a `USE_PUPPETDB` environment variable that can be set to false when >> running the puppetserver image to have the same behavior as the current >> puppetserver-standalone image. >> >> *Questions / Comments / Concerns?* >> >> Please leave comments at >> https://github.com/puppetlabs/puppetserver/pull/2188 or respond here. >> >> -- >> Morgan Rhodes >> Release Engineering >> mor...@puppet.com >> she/her/hers >> > -- > 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/3c910a1c-3e50-43ed-a554-57fceb48b7d1%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/3c910a1c-3e50-43ed-a554-57fceb48b7d1%40googlegroups.com?utm_medium=email_source=footer> > . > -- Morgan Rhodes Release Engineering mor...@puppet.com she/her/hers -- 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%2BFnDv2sauptPNBM23BPgdwBOZPDe%2BGtbOi93ChQ%2B-YYei6B2Q%40mail.gmail.com.
[Puppet Users] [RFC] Changes to open-source container versioning
Hi all, *tl;dr* - We're trying to make the versioning scheme for our containers more intuitive, changes summarized in the table below, see more details at https://github.com/puppetlabs/puppetserver/pull/2188 build typecurrent tagnew tag from source puppet/puppetserver:6.7.0 puppet/puppetserver:6.7 from source (latest) puppet/puppetserver:latest puppet/puppetserver:edge from package n/a puppet/puppetserver:6.7.0 from package (latest) n/a puppet/puppetserver:latest *Versioning* For a while now, our containers have included a package built from source and versioned based on the most recent tag to the repo. While we still think building from source provides value to our users, it's become clear that they also need a way to pin to a specific, released version of puppetserver and count on that container not being updated. To address this, we're changing the versioning scheme for our container builds. When we build images from source, those images will be versioned with X.Y versions based on the latest tag on master. So, for example, the current image versioned puppet/puppetserver:6.6.0 would move to puppet/puppetserver:6.6. This tag will continue to have rolling updates until the next X or Y release. If you want to follow whatever the latest version of the image from source is, you will want to pin to puppet/puppetserver:edge. We will also start building and shipping images when puppetserver is shipped publicly. These images will be tagged with an X.Y.Z version that will match the version of puppetserver installed on that image. This tag will not receive any updates. If you want to follow the latest released version of puppetserver, you will want to pin to puppet/puppetserver:latest. *Other Changes for the puppetserver images* We are also looking into removing the puppetserver-standalone image. I've added a `USE_PUPPETDB` environment variable that can be set to false when running the puppetserver image to have the same behavior as the current puppetserver-standalone image. *Questions / Comments / Concerns?* Please leave comments at https://github.com/puppetlabs/puppetserver/pull/2188 or respond here. -- Morgan Rhodes Release Engineering mor...@puppet.com she/her/hers -- 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%2BFnDv30%2BpqVVR7wBtNfKUZnSm4k_XJ5BQyAqpndqfnLi6o_Ng%40mail.gmail.com.
Re: [Puppet Users] Re: [ACTION] Changes to release package links
Groups "Puppet Users" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to puppet...@googlegroups.com. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/puppet-users/c711eeca-239c-4022-8f4b-55f9ea577c8d%40googlegroups.com >>>>> <https://groups.google.com/d/msgid/puppet-users/c711eeca-239c-4022-8f4b-55f9ea577c8d%40googlegroups.com?utm_medium=email_source=footer> >>>>> . >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> >>>> -- >>>> *Molly Waggett* >>>> she/her/hers >>>> Release Engineer @ Puppet, Inc. >>>> >>> >>> >>> -- >>> *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/003ef1cb-1038-4a82-a9ab-8b2921dc999e%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/003ef1cb-1038-4a82-a9ab-8b2921dc999e%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Morgan Rhodes Release Engineering mor...@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/CA%2BFnDv0n1n_tUR2aG56CRGS1CzTtuD9ZXXm4%2BVU8jCDYE0njUg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Puppet apt repository broken?
The bionic repo should be working again. Let us know if you have any more issues. On Wed, May 15, 2019 at 1:45 PM Morgan Rhodes wrote: > Hi Peter, > > Apologies, we've been having some repo issues today. I'm getting the > bionic repository updated now and it should be done within the hour. I will > send another update here when it completes. > > On Wed, May 15, 2019 at 1:43 PM Peter Berghold > wrote: > >> Just this afternoon around 4PM I started noticing this happen in my >> Docker builds that incorporate loading the Puppet agent: >> W: Skipping acquire of configured file 'puppet/binary-all/Packages' as >> repository 'http://apt.puppetlabs.com bionic InRelease' doesn't have the >> component 'puppet' (component misspelt in sources.list?) >> W: Skipping acquire of configured file 'puppet/binary-amd64/Packages' as >> repository 'http://apt.puppetlabs.com bionic InRelease' doesn't have the >> component 'puppet' (component misspelt in sources.list?) >> Reading package lists... >> Building dependency tree... >> Reading state information... >> Package puppet-agent is not available, but is referred to by another >> package. >> This may mean that the package is missing, has been obsoleted, or >> is only available from another source >> >> E: Package 'puppet-agent' has no installation candidate >> >> same Docker build worked swimmingly earlier today and seems broken now >> with NOTHING changing in the build (except to add NTP). Any idea why this >> is happening and more importantly any idea when the issue will go away? >> >> >> >> -- >> >> Peter L. Berghold salty.cowd...@gmail.com >> >> http://devops.berghold.net >> >> >> -- >> 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/CAArvnv0TA-u%2BxM-8wxrQ9b8FOJ9ZCn_%3DBRR2bqjaimXSZm0jGQ%40mail.gmail.com >> <https://groups.google.com/d/msgid/puppet-users/CAArvnv0TA-u%2BxM-8wxrQ9b8FOJ9ZCn_%3DBRR2bqjaimXSZm0jGQ%40mail.gmail.com?utm_medium=email_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > -- > Morgan Rhodes > Release Engineering > mor...@puppet.com > -- Morgan Rhodes Release Engineering mor...@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/CA%2BFnDv05WW0i2z5sP7q0LyX65_TBR%3DiDOJYNddh%3DCAuxnaXVfA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Puppet apt repository broken?
Hi Peter, Apologies, we've been having some repo issues today. I'm getting the bionic repository updated now and it should be done within the hour. I will send another update here when it completes. On Wed, May 15, 2019 at 1:43 PM Peter Berghold wrote: > Just this afternoon around 4PM I started noticing this happen in my Docker > builds that incorporate loading the Puppet agent: > W: Skipping acquire of configured file 'puppet/binary-all/Packages' as > repository 'http://apt.puppetlabs.com bionic InRelease' doesn't have the > component 'puppet' (component misspelt in sources.list?) > W: Skipping acquire of configured file 'puppet/binary-amd64/Packages' as > repository 'http://apt.puppetlabs.com bionic InRelease' doesn't have the > component 'puppet' (component misspelt in sources.list?) > Reading package lists... > Building dependency tree... > Reading state information... > Package puppet-agent is not available, but is referred to by another > package. > This may mean that the package is missing, has been obsoleted, or > is only available from another source > > E: Package 'puppet-agent' has no installation candidate > > same Docker build worked swimmingly earlier today and seems broken now > with NOTHING changing in the build (except to add NTP). Any idea why this > is happening and more importantly any idea when the issue will go away? > > > > -- > > Peter L. Berghold salty.cowd...@gmail.com > > http://devops.berghold.net > > > -- > 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/CAArvnv0TA-u%2BxM-8wxrQ9b8FOJ9ZCn_%3DBRR2bqjaimXSZm0jGQ%40mail.gmail.com > <https://groups.google.com/d/msgid/puppet-users/CAArvnv0TA-u%2BxM-8wxrQ9b8FOJ9ZCn_%3DBRR2bqjaimXSZm0jGQ%40mail.gmail.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Morgan Rhodes Release Engineering mor...@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/CA%2BFnDv24Rs2%2BuQUKS2vLSZqk1cxRXfft6WOorxcy_14sTtDZGQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Puppet Certificate Issues
Hi Rohit, I don't have great ideas about what's going on in your environment. Are you using custom built containers or the puppet namespaced containers from hub.docker.com. You could try applying this patch ( https://github.com/puppetlabs/puppetdb/commit/a1ab2f50598f12ac51acb21f256232143891dbc1) and setting PUPPETSERVER_HOSTNAME in your docker-compose.yml to puppet4.psd401.net. In one of your earlier emails you mentioned you were using puppetserver 2.7, but it looks like in the compose file you attached you're using the puppet/puppetserver:latest, which is puppetserver 6.x, just want to make sure I know what versions of things you're running with here. The containers for puppetserver 2.7 / puppetdb 4.2 are definitely old, and with recent efforts we have made a number of changes and improvements to the containers and the compose stack ( https://github.com/puppetlabs/pupperware), but that work has been for puppetserver and puppetdb 5+. If you run `puppet agent -t` on your puppetserver container does it succeed? (docker-compose exec puppet puppet agent -t) On Wed, Nov 28, 2018 at 9:20 AM Rohit wrote: > Any idea if there are other steps I can consider? If not, should I simply > rebuild the system? If I do go this route, is there a way to backup all the > Puppet configurations set for servers and services that can be reimported > in a fresh install? Would it also be suggested to go a non-Docker route due > to stability? > > > On Thursday, November 15, 2018 at 1:33:43 PM UTC-8, Morgan Rhodes wrote: > >> Hi Rohit, >> >> No, unfortunately, it's not just a change in your docker-compose.yml. >> When you're generating the certs for your puppetserver, you'll want to make >> sure you're passing the `--dns_alt_names=`, so it would be >> something like: >> puppet cert generate puppet4.psd401.net --dns_alt_names=puppet, >> puppet.psd401.net >> >> Afterwards, you can confirm that your certificate has all of the altnames >> with `puppet cert list --all`, you should see something like: >> $ puppet cert list --all >> + "puppet4.psd401.net" (SHA256) (alt names: "DNS:puppet", >> "DNS:puppet4.psd401.net") >> >> On Tue, Nov 13, 2018 at 11:23 AM Rohit wrote: >> > Hello Morgan, >>> >>> Apologies for the late response here, some of our Puppet services had >>> started working but it looks like the same issue has arised and I am not >>> entirely sure why. I did check the docker-entrypoint.sh file and indeed see >>> the very exact response as you posted. However my question is for the >>> "altname" that you suggested, would I change this in the docker-compose.yml >>> file? I also realize the full docker-compose.yml did not show up in my >>> previous post but have attached it again in a separate file. >>> >>> >>> On Friday, October 19, 2018 at 4:38:12 PM UTC-7, Morgan Rhodes wrote: >>> >>>> When you look at the output of `puppet cert list all` does the >>>> certificate for your puppetmaster also include the alt name 'puppet'? >>>> (Something like 'alt names: "DNS:puppet", "DNS:testpuppet"'). If not, I'm >>>> guessing that's your problem. >>>> >>>> You mentioned in your earlier email that you were using puppetdb 4.2.0. >>>> I'm assuming you're running the puppet/puppetdb:4.2.0 container. To get the >>>> container entrypoint, I start the container manually with a custom >>>> entrypoint so I can look around, there should be a file >>>> 'docker-entrypoint.sh' in the root directory of the container. >>>> >>>> $ docker run --rm -it --entrypoint /bin/bash puppet/puppetdb:4.2.0 >>>> root@e09f677618d7:/# ls >>>> Dockerfile bin boot dev docker-entrypoint.sh etc home lib >>>> lib64 media mnt opt proc root run sbin srv sys tmp usr var >>>> root@e09f677618d7:/# cat docker-entrypoint.sh >>>> #!/bin/bash >>>> >>>> if [ ! -d "/etc/puppetlabs/puppetdb/ssl" ]; then >>>> while ! nc -z puppet 8140; do >>>> sleep 1 >>>> done >>>> set -e >>>> /opt/puppetlabs/bin/puppet agent --verbose --onetime --no-daemonize >>>> --waitforcert 120 >>>> /opt/puppetlabs/server/bin/puppetdb ssl-setup -f >>>> fi >>>> >>>> exec /opt/puppetlabs/server/bin/puppetdb "$@" >>>> root@e09f677618d7:/# >>>> >>>> The docker-entrypoint.sh script in that version of the container >>>> doesn't have any logic for a puppetserver with a non-
Re: [Puppet Users] Re: Puppet Certificate Issues
Hi Rohit, No, unfortunately, it's not just a change in your docker-compose.yml. When you're generating the certs for your puppetserver, you'll want to make sure you're passing the `--dns_alt_names=`, so it would be something like: puppet cert generate puppet4.psd401.net --dns_alt_names=puppet, puppet.psd401.net Afterwards, you can confirm that your certificate has all of the altnames with `puppet cert list --all`, you should see something like: $ puppet cert list --all + "puppet4.psd401.net" (SHA256) (alt names: "DNS:puppet", "DNS:puppet4.psd401.net") On Tue, Nov 13, 2018 at 11:23 AM Rohit wrote: > Hello Morgan, > > Apologies for the late response here, some of our Puppet services had > started working but it looks like the same issue has arised and I am not > entirely sure why. I did check the docker-entrypoint.sh file and indeed see > the very exact response as you posted. However my question is for the > "altname" that you suggested, would I change this in the docker-compose.yml > file? I also realize the full docker-compose.yml did not show up in my > previous post but have attached it again in a separate file. > > > On Friday, October 19, 2018 at 4:38:12 PM UTC-7, Morgan Rhodes wrote: > >> When you look at the output of `puppet cert list all` does the >> certificate for your puppetmaster also include the alt name 'puppet'? >> (Something like 'alt names: "DNS:puppet", "DNS:testpuppet"'). If not, I'm >> guessing that's your problem. >> >> You mentioned in your earlier email that you were using puppetdb 4.2.0. >> I'm assuming you're running the puppet/puppetdb:4.2.0 container. To get the >> container entrypoint, I start the container manually with a custom >> entrypoint so I can look around, there should be a file >> 'docker-entrypoint.sh' in the root directory of the container. >> >> $ docker run --rm -it --entrypoint /bin/bash puppet/puppetdb:4.2.0 >> root@e09f677618d7:/# ls >> Dockerfile bin boot dev docker-entrypoint.sh etc home lib lib64 >> media mnt opt proc root run sbin srv sys tmp usr var >> root@e09f677618d7:/# cat docker-entrypoint.sh >> #!/bin/bash >> >> if [ ! -d "/etc/puppetlabs/puppetdb/ssl" ]; then >> while ! nc -z puppet 8140; do >> sleep 1 >> done >> set -e >> /opt/puppetlabs/bin/puppet agent --verbose --onetime --no-daemonize >> --waitforcert 120 >> /opt/puppetlabs/server/bin/puppetdb ssl-setup -f >> fi >> >> exec /opt/puppetlabs/server/bin/puppetdb "$@" >> root@e09f677618d7:/# >> >> The docker-entrypoint.sh script in that version of the container doesn't >> have any logic for a puppetserver with a non-default name, which means when >> it runs `puppet agent --verbose --onetime --no-daemonize --waitforcert 120` >> it will connect to the host named 'puppet'. From the link you have set up >> in your docker-compose.yml, I'm assuming your puppetserver container name >> is 'puppet' with the hostname 'puppet4.psd401.net'. Since the container >> name is 'puppet', the puppetdb container is able to resolve 'puppet' as >> 'puppet4', so when it runs puppet agent -t it can connect to the host, >> but certificate validation will fail if puppet isn't listed as one of the >> valid altnames for the puppet container. >> >> On Fri, Oct 19, 2018 at 11:35 AM Rohit wrote: >> > >>>1. puppet_db is trying to connect our.puppet.domain, there is no >>>docker-entrypoint.sh script that I was able to find. >>> 1. For reference, this is the docker-compose.yml: >>> 2. >>> >>> puppetdb: >>> >>> container_name: puppet_db >>> >>> hostname: puppetdb.peninsula.wednet.edu >>> >>> dns: >>> >>>- 10.0.0.7 >>> >>> image: puppet/puppetdb:latest >>> >>> ports: >>> >>>- 8087:8080 >>> >>>- 8088:8081 >>> >>> depends_on: >>> >>>- puppet >>> >>> links: >>> >>>- puppet:puppet4.psd401.net >>> >>>- puppetdbpostgres:postgres >>> >>> volumes: >>> >>>- ./puppet-client.conf:/etc/puppetlabs/puppet/puppet.conf >>> >>>- ./puppetdb_conf:/etc/puppetlabs/puppetdb/conf.d >>> >>>- ./puppetdb_ssl:/etc/puppetlabs/puppet/ssl/ >>> >>> networks: &
Re: [Puppet Users] Re: Puppet Certificate Issues
When you look at the output of `puppet cert list all` does the certificate for your puppetmaster also include the alt name 'puppet'? (Something like 'alt names: "DNS:puppet", "DNS:testpuppet"'). If not, I'm guessing that's your problem. You mentioned in your earlier email that you were using puppetdb 4.2.0. I'm assuming you're running the puppet/puppetdb:4.2.0 container. To get the container entrypoint, I start the container manually with a custom entrypoint so I can look around, there should be a file 'docker-entrypoint.sh' in the root directory of the container. $ docker run --rm -it --entrypoint /bin/bash puppet/puppetdb:4.2.0 root@e09f677618d7:/# ls Dockerfile bin boot dev docker-entrypoint.sh etc home lib lib64 media mnt opt proc root run sbin srv sys tmp usr var root@e09f677618d7:/# cat docker-entrypoint.sh #!/bin/bash if [ ! -d "/etc/puppetlabs/puppetdb/ssl" ]; then while ! nc -z puppet 8140; do sleep 1 done set -e /opt/puppetlabs/bin/puppet agent --verbose --onetime --no-daemonize --waitforcert 120 /opt/puppetlabs/server/bin/puppetdb ssl-setup -f fi exec /opt/puppetlabs/server/bin/puppetdb "$@" root@e09f677618d7:/# The docker-entrypoint.sh script in that version of the container doesn't have any logic for a puppetserver with a non-default name, which means when it runs `puppet agent --verbose --onetime --no-daemonize --waitforcert 120` it will connect to the host named 'puppet'. From the link you have set up in your docker-compose.yml, I'm assuming your puppetserver container name is 'puppet' with the hostname 'puppet4.psd401.net'. Since the container name is 'puppet', the puppetdb container is able to resolve 'puppet' as 'puppet4', so when it runs puppet agent -t it can connect to the host, but certificate validation will fail if puppet isn't listed as one of the valid altnames for the puppet container. On Fri, Oct 19, 2018 at 11:35 AM Rohit wrote: > >1. puppet_db is trying to connect our.puppet.domain, there is no >docker-entrypoint.sh script that I was able to find. > 1. For reference, this is the docker-compose.yml: > 2. > > puppetdb: > > container_name: puppet_db > > hostname: puppetdb.peninsula.wednet.edu > > dns: > >- 10.0.0.7 > > image: puppet/puppetdb:latest > > ports: > >- 8087:8080 > >- 8088:8081 > > depends_on: > >- puppet > > links: > >- puppet:puppet4.psd401.net > >- puppetdbpostgres:postgres > > volumes: > >- ./puppet-client.conf:/etc/puppetlabs/puppet/puppet.conf > >- ./puppetdb_conf:/etc/puppetlabs/puppetdb/conf.d > >- ./puppetdb_ssl:/etc/puppetlabs/puppet/ssl/ > > networks: > >puppet: > > ipv4_address: 172.19.0.4 > > restart: always > > > 2. The hostname that the puppetdb container is trying to connect to >is indeed the one listed on the certificate name on the puppet servers > cert. > > > On Friday, October 19, 2018 at 10:09:56 AM UTC-7, Morgan Rhodes wrote: > >> A few things to verify: >> >> 1) what hostname is your puppetdb container trying to connect to >> puppetserver at? >> a) This should be in your docker-entrypoint.sh script in the puppetdb >> container. Likely either 'puppet' or '$PUPPETSERVER_HOSTNAME' depending on >> what variables you have set in your compose file and what version of the >> puppetdb container you have. >> >> 2) Is the hostname your puppetdb container is trying to connect to listed >> as one of the certificate names for your puppet server's cert? >> a) For example, in my puppetserver container when I run `puppet cert >> list --all` I see: >> >> + "testserver" (SHA256) >> F0:31:6D:1D:03:82:C0:84:0D:FA:2B:28:5B:52:CB:18:88:87:61:5F:5A:F5:7E:AB:A2:73:29:44:BC:57:D0:99 >> (alt names: "DNS:testserver", "DNS:foo") >> >> if my puppetdb container tries to connect to that host over any names >> other than 'testserver' or 'foo' I get a certificate verify failed error. >> >> >> On Fri, Oct 19, 2018 at 9:02 AM Rohit wrote: >> > Hello Morgan, >>> >>> If you are refferring to the cert being in the conf/ssl/certs folder, >>> then yes, our.puppet.domain.pem is in the folder. When running the 'puppet >>> cert list --all' I see three certificates (in the SHA256 format): >>> >>>- computername.our.puppet.domain >>>- our.puppet.domain >>>- servername.our.puppet.domain >>> >>>
Re: [Puppet Users] Re: Puppet Certificate Issues
A few things to verify: 1) what hostname is your puppetdb container trying to connect to puppetserver at? a) This should be in your docker-entrypoint.sh script in the puppetdb container. Likely either 'puppet' or '$PUPPETSERVER_HOSTNAME' depending on what variables you have set in your compose file and what version of the puppetdb container you have. 2) Is the hostname your puppetdb container is trying to connect to listed as one of the certificate names for your puppet server's cert? a) For example, in my puppetserver container when I run `puppet cert list --all` I see: + "testserver" (SHA256) F0:31:6D:1D:03:82:C0:84:0D:FA:2B:28:5B:52:CB:18:88:87:61:5F:5A:F5:7E:AB:A2:73:29:44:BC:57:D0:99 (alt names: "DNS:testserver", "DNS:foo") if my puppetdb container tries to connect to that host over any names other than 'testserver' or 'foo' I get a certificate verify failed error. On Fri, Oct 19, 2018 at 9:02 AM Rohit wrote: > Hello Morgan, > > If you are refferring to the cert being in the conf/ssl/certs folder, then > yes, our.puppet.domain.pem is in the folder. When running the 'puppet cert > list --all' I see three certificates (in the SHA256 format): > >- computername.our.puppet.domain >- our.puppet.domain >- servername.our.puppet.domain > > If it is a DNS issue, do I have to likely change something from the > docker-compose side? > > > On Thursday, October 18, 2018 at 2:14:54 PM UTC-7, Morgan Rhodes wrote: >> >> Hi Rohit, >> >> Is the hostname from `/CN=our.puppet.domain` showing up in your >> puppetserver's certificate? You can verify that with `puppet cert list >> --all` on the puppetserver container. This looks like a DNS issue. >> >> On Thursday, October 18, 2018 at 11:41:16 AM UTC-7, Rohit wrote: >>> >>> Hello, we currently have a puppet docker container setup and are >>> experiencing certificate issues. Basically, in our docker setup (on our >>> main server) I had generated and signed new certificates, but the puppet_db >>> container keeps restarting. Here are logs from the puppet_db container: >>> >>> ‘Error: Could not retrieve catalog from remote server: SSL_connect >>> returned=1 errno=0 state=error: certificate verify failed: [unable to get >>> local issuer certificate for /CN=our.puppet.domain] >>> Error: Could not retrieve catalog; skipping run >>> Error: Could not send report: SSL_connect returned=1 errno=0 >>> state=error: certificate verify failed: [unable to get local issuer >>> certificate for /CN=our.puppet.domain]’ >>> >>> I have tried series of steps to solve this problem as it looks like >>> Puppet is not functioning correctly as our servers are not properly >>> listening to the host server. Any idea what I can do to solve this problem? >>> For reference, we are running Puppet_DB version 4.2 and Puppet Server >>> version 2.7.2, all of which is set up on a docker container environment on >>> one server. >>> >> -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/899d2bf7-ceed-4d9e-bd24-c4ba2cc93928%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/899d2bf7-ceed-4d9e-bd24-c4ba2cc93928%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CA%2BFnDv15nGSpEuX7otQa%2B%3Dc9_FKW7YLB_FQzWWhJgRSvEHP%2BxA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Puppet Certificate Issues
Hi Rohit, Is the hostname from `/CN=our.puppet.domain` showing up in your puppetserver's certificate? You can verify that with `puppet cert list --all` on the puppetserver container. This looks like a DNS issue. On Thursday, October 18, 2018 at 11:41:16 AM UTC-7, Rohit wrote: > > Hello, we currently have a puppet docker container setup and are > experiencing certificate issues. Basically, in our docker setup (on our > main server) I had generated and signed new certificates, but the puppet_db > container keeps restarting. Here are logs from the puppet_db container: > > ‘Error: Could not retrieve catalog from remote server: SSL_connect > returned=1 errno=0 state=error: certificate verify failed: [unable to get > local issuer certificate for /CN=our.puppet.domain] > Error: Could not retrieve catalog; skipping run > Error: Could not send report: SSL_connect returned=1 errno=0 > state=error: certificate verify failed: [unable to get local issuer > certificate for /CN=our.puppet.domain]’ > > I have tried series of steps to solve this problem as it looks like Puppet > is not functioning correctly as our servers are not properly listening to > the host server. Any idea what I can do to solve this problem? For > reference, we are running Puppet_DB version 4.2 and Puppet Server version > 2.7.2, all of which is set up on a docker container environment on one > server. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/1a315e30-fd7f-4da8-ba52-52da56756311%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] release-archives.puppet.com is missing a dists folder
Hi Michael, Yes, this is intentional. In the current state of release-archives, the dists folder didn't actually contain valid repo metadata due to how files were archived. We have an upcoming project to make sure we have valid repositories for yum and apt on release-archives. On Thu, Oct 11, 2018 at 10:53 PM Michael Liao wrote: > Hi, I have an apt source set up for release-archives.puppet.com, but it > has now broken because the dists folder seems to have disappeared. Is this > intentional? > > -- > 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/31724b15-ae21-4e9f-a60c-cf8076561ce4%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/31724b15-ae21-4e9f-a60c-cf8076561ce4%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CA%2BFnDv00z0FtGULAvDA9m8m0d7ksJuuXYc7ZsmCTFjDR9mVtoA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Changes coming to puppet docker containers!
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/CA%2BFnDv39u%3DS-UJPz%2BOAUhnCxyP3%3D%3DAOAjuuqmeHdmcfXsVAv1Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Announce: Puppet Platform 5.3.6
Karsten, No, this is not intended, we're working on correcting this right now. There's a ticket at https://tickets.puppetlabs.com/browse/PA-1985. On Wed, Apr 18, 2018 at 7:12 AM Karsten Heymann <karsten.heym...@gmail.com> wrote: > Hi Garrett, > > > Am Mittwoch, 18. April 2018 07:01:15 UTC+2 schrieb Garrett Guillotte: >> >> Puppet agent 5.3.6 is a bug-fix release that includes updates for Puppet >> 5.3.6 <https://puppet.com/docs/puppet/5.3/release_notes.html>, >> > > Is the inclusion of puppet agent 5.3.6 in the PC1 repository intended? I > would guess no, as until now there were only puppet-agent 4.x versions in > there. http://apt.puppet.com/pool/stretch/PC1/p/puppet-agent/ > > BR > Karsten > > -- > 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/99939d44-fbbc-4f5f-a3ce-66e54596f427%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/99939d44-fbbc-4f5f-a3ce-66e54596f427%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CA%2BFnDv3nVz8WBVLi49SZC4-VmZP8m6tj1Jsd5aj6M8wHWA-14A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Announcement: Release of Bolt 0.17.2
Hello Everyone! Today we’re happy to announce the latest release of Bolt, wrapping up a feature release and bug fixes in version 0.17.2. New Features include: A --query option for selecting a node list via PQL. By default running Bolt via Orchestrator no longer requires that you add the modules to Bolt's modulepath. New string and array manipulation functions have been added to the Bolt Plan language. For the full CHANGELOG, please visit: https://puppet.com/docs/bolt/0.x/bolt_release_notes.html. To try this new version, follow the normal installation at https://puppet.com/docs/bolt/0.x/bolt_installing.html. Updated packages are also available via Yum and Apt. Thanks! -- 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/CA%2BFnDv2z%3DCKNrV1sFz6iQ-Y54f_MND60yZU-%2B%2BThfWJ42MyP1A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] /etc/sysconfig/puppetserver git source?
Hi Christopher, That file is generated during packaging and is generated from a template in the ezbake project. https://github.com/puppetlabs/ezbake/blob/master/resources/puppetlabs/lein-ezbake/template/foss/ext/default.erb On Wed, Jan 3, 2018 at 9:56 AM Christopher Wood <christopher_w...@pobox.com> wrote: > Is the source for /etc/sysconfig/puppetserver in the puppetserver rpm > stored in any public-facing git repository? If so, where? > > More details: > > I was reading the tuning guide (it's augment time again) and it occurred > to me to read the commit messages for this file to see how Puppet figured > out the defaults. That information may inform my own configurations. > > https://puppet.com/docs/puppetserver/5.1/tuning_guide.html > > I'm not actually a programmer, and couldn't find this file or obvious > source code in the puppetserver git repository if it is there. (Hints > welcome too!) > > https://github.com/puppetlabs/puppetserver > > Running puppetserver 5.1.4 here. > > -- > 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/20180103175542.2jt55rzf3hz3tpkp%40iniquitous.heresiarch.ca > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CA%2BFnDv3G5WtPSh95p7KW9nraEKBZx9Fo%3DEoRFgj5PNO5OO8-Dg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Puppet Enterprise 2017.3.1 is now available
Dear Puppet Enterprise Users, Puppet Enterprise 2017.3.1 is now available. This is a bugfix release of Puppet Enterprise. All users of Puppet Enterprise 2017.3.x are encouraged to upgrade when possible to Puppet Enterprise 2017.3.1. For information on the bug fixes in this release, see https://puppet.com/docs/pe/2017.3/release_notes/release_notes.html As a current Puppet Enterprise user, you can upgrade to this new version as part of your annual subscription. If upgrading, it is required to upgrade your master, puppetdb, and console servers first. As always, we want to hear about your experiences with Puppet Enterprise. If you have any questions about upgrading, be sure to get in touch with Puppet Support. See what's new in Puppet Enterprise 2017.3, including new task automation and package inspection capabilities: https://puppet.com/blog/taking-you-journey-automation-puppet-enterprise-20173 -- 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/CA%2BFnDv2yJs_53wsL0NRp6gu%3D_QMy-_L-kEqShDzQ5fyV%2BAMEtQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Puppet Enterprise 2017.3.1 is now available
Dear Puppet Enterprise Users, Puppet Enterprise 2017.3.1 is now available. This is a bugfix release of Puppet Enterprise. All users of Puppet Enterprise 2017.3.x are encouraged to upgrade when possible to Puppet Enterprise 2017.3.1. Puppet Enterprise 2017.3.1 includes fixes to address . For information on the bug fixes in this release, see https://puppet.com/docs/pe/2017.3/release_notes/release_notes.html As a current Puppet Enterprise user, you can upgrade to this new version as part of your annual subscription. If upgrading, it is required to upgrade your master, puppetdb, and console servers first. As always, we want to hear about your experiences with Puppet Enterprise. If you have any questions about upgrading, be sure to get in touch with Puppet Support. See what's new in Puppet Enterprise 2017.3, including new task automation and package inspection capabilities: https://puppet.com/blog/taking-you-journey-automation-puppet-enterprise-20173 -- 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/CA%2BFnDv2DZgRQO2ghg7vj2oKx5tNHqH8GryCDwCcEyk57OM0m%3DA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: apt/yum.downloads.puppetlabs.com CDN & rsync deprecation
Hi Andrew, Looks like some files were accidentally synced out. They've been cleaned up now. On Wed, May 24, 2017 at 10:53 AM Melissa Stone <meli...@puppet.com> wrote: > On Wed, May 24, 2017 at 10:49 AM Melissa Stone <meli...@puppet.com> wrote: > >> On Wed, May 24, 2017 at 4:16 AM Andrew Elwell <andrew.elw...@gmail.com> >> wrote: >> >>> >>> >>> On Thursday, 27 April 2017 02:31:42 UTC+8, Daniel Dreier wrote: >>>> >>>> I'm sorry we broke people's rsync-based repository mirroring. I should >>>> have communicated this change well in advance. To get you all mirroring our >>>> repositories again, I've configured rsync.puppet.com. You can sync >>>> from it using a command like: >>>> >>>> rsync -av --copy-links --del rsync://rsync.puppet.com/packages/yum/ >>>> /tmp/yum/ >>>> rsync -av --copy-links --del rsync://rsync.puppet.com/packages/apt/ >>>> /tmp/apt/ >>>> >>>> Please let me know if you have any trouble with the new rsync service >>>> >>> >>> Yes. >>> >>> aelwell@galaxy-1:~$ rsync rsync://rsync.puppet.com/packages/apt/dists/ >>> drwxrwxr-x 4,096 2017/01/18 09:05:57 . >>> drwxrwxr-x 4,096 2015/11/13 08:51:24 >>> cumulus-20151112165122938545665 >>> drwxrwxr-x 4,096 2015/11/18 03:21:38 >>> cumulus-20151117105654400831046 >>> drwxrwxr-x 4,096 2015/11/18 08:27:29 >>> cumulus-20151117152326887946964 >>> drwxrwxr-x 4,096 2017/05/11 21:58:14 cumulus >>> drwxrwxr-x 4,096 2017/05/11 21:58:14 huaweios >>> drwxrwxr-x 4,096 2015/11/13 08:51:22 >>> jessie-20151112165118307861024 >>> drwxrwxr-x 4,096 2015/11/18 03:21:54 >>> jessie-20151117110350179683670 >>> drwxrwxr-x 4,096 2015/11/18 08:28:03 >>> jessie-20151117152857377466419 >>> drwxrwxr-x 4,096 2017/05/11 21:58:14 jessie >>> etc >>> >>> it seems to be pulling in all your nightly builds which aren't visible >>> in the web interface >>> http://apt.puppetlabs.com/dists/ >>> >> Hi Andrew, >> >> The nightly builds should be visible from the web interface (i.e., >> http://apt.puppetlabs.com/dists/trusty/puppet5-nightly/). We recently >> added these nightly builds in to allow folks to test the new puppet5 >> platform. You can check out Eric0's blog post on the nightly repos at >> https://puppet.com/blog/new-nightly-package-repositories-for-open-source-puppet >> > > Ah, I see now you were asking about the freight directories that aren't > visible (i.e., jessie-20151112165118307861024). We're digging into this now. > >> >>> >>> >>> >>> -- >>> 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/0ebb5ec5-eaa3-414e-aeef-eb4eb7436687%40googlegroups.com >>> <https://groups.google.com/d/msgid/puppet-users/0ebb5ec5-eaa3-414e-aeef-eb4eb7436687%40googlegroups.com?utm_medium=email_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> *Melissa Stone* >> release engineering >> meli...@puppet.com | @melissaapiedra >> > -- > *Melissa Stone* > release engineering > meli...@puppet.com | @melissaapiedra > > -- > 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/CAHEe_kqgtRE3OcAzaTODZkXVm%2BO%2BUuNfqQh7XyvOADqNduYwSw%40mail.gmail.com > <https://groups.google.com/d/msgid/puppet-users/CAHEe_kqgtRE3OcAzaTODZkXVm%2BO%2BUuNfqQh7XyvOADqNduYwSw%40mail.gmail.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Morgan Rhodes mor...@puppet.com Release Engineer PuppetConf 2017 <https://puppet.com/puppetconf>, 10-12 October San Francisco, California Save $328, register by 30 June w/ early adopter discount <https://www.eventbrite.com/e/puppetconf-2017-10-12-october-tickets-28617829699?discount=earlyadopter> -- 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%2BFnDv1YTpAEpt3jm0NWF_Dazk4%2BTB3aLMGkq_9iH%3Dy-efPKsA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] The repository 'http://apt.puppetlabs.com xenial Release' is not signed.
Hi Dirk, Looks like we had some bad metadata cached in our CDN, but this should be resolved now. There's more information in this ticket: https://tickets.puppetlabs.com/browse/CPR-419 Morgan On Thu, Apr 27, 2017 at 3:56 AM Dirk Heinrichs <dhein...@opentext.com> wrote: > Hi, > > I'm currently facing this error when I try to apt-get update after > installing puppetlabs-release-pc1-xenial.deb (also tried the latest one > from the pool: puppetlabs-release-pc1_1.1.0-4xenial_all.deb). Please fix. > > Thanks a lot, > > Dirk > -- > *Dirk Heinrichs* > Senior Systems Engineer, Delivery Pipeline > OpenTextTM Discovery | Recommind > *Email*: dirk.heinri...@recommind.com > *Website*: www.recommind.de > > Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach > > Vertretungsberechtigte Geschäftsführer John Marshall Doolittle, Gordon > Davies, Roger Illing, 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/13e3ab42-9941-3063-ebe5-88a3567f8620%40opentext.com > <https://groups.google.com/d/msgid/puppet-users/13e3ab42-9941-3063-ebe5-88a3567f8620%40opentext.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Morgan Rhodes mor...@puppet.com Release Engineer PuppetConf 2017 <https://puppet.com/puppetconf>, 10-12 October San Francisco, California Save $328, register by 30 June w/ early adopter discount <https://www.eventbrite.com/e/puppetconf-2017-10-12-october-tickets-28617829699?discount=earlyadopter> -- 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%2BFnDv2OxA%2B7yPVmGhf0g1Y0XOrYw-4fRB6%2BOyrjwHJfmkXK_g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] [Announce] Vulnerability in MCollective Puppet Agent plugin
All, Today we announced a vulnerability in the MCollective Puppet Agent plugin <https://puppet.com/security/cve/cve-2017-2290>. This vulnerability affects Windows installations of mcollective-puppet-agent 1.12.0. It has been resolved in mcollective-puppet-agent 1.12.1. Puppet Enterprise users are not affected. -- 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/CA%2BFnDv1PX-Gzexs69dmtM5g-11MvVLOa_1fM0BA%3D7oADLZ7cmQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Announce: Puppet Enterprise 2016.4.3 is available
Dear Puppet Enterprise Users, Puppet Enterprise 2016.4.3 is now available. This is a security and bugfix release of Puppet Enterprise. All users of Puppet Enterprise 2016.4 are encouraged to upgrade when possible to Puppet Enterprise 2016.4.3. Puppet Enterprise 2016.4.3 includes fixes to address security vulnerabilities in Java, as well as a number of other bugfixes and improvements. For information on the bug fixes in this release, see https://docs.puppet.com/pe/2016.4/release_notes.html As a current Puppet Enterprise user, you can upgrade to this new version as part of your annual subscription. If upgrading, it is required to upgrade your master, puppetdb, and console servers first. As always, we want to hear about your experiences with Puppet Enterprise. If you have any questions about upgrading, be sure to get in touch with Puppet Support. -- 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/CA%2BFnDv0gKRtugLpoYVcgX6oztg6Rn4DcFsEJYPs%3DEdYypeU2mQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Announce: Puppet Enterprise 2016.5.2 is available
Dear Puppet Enterprise Users, Puppet Enterprise 2016.5.2 is now available. This is a security and bugfix release of Puppet Enterprise. All users of Puppet Enterprise 2016.5 are encouraged to upgrade when possible to Puppet Enterprise 2016.5.2. Puppet Enterprise 2016.5.2 includes fixes to address security vulnerabilities in Java, as well as a number of other bugfixes and improvements. For information on the bug fixes in this release, see https://docs.puppet.com/pe/2016.5/release_notes.html As a current Puppet Enterprise user, you can upgrade to this new version as part of your annual subscription. If upgrading, it is required to upgrade your master, puppetdb, and console servers first. As always, we want to hear about your experiences with Puppet Enterprise. If you have any questions about upgrading, be sure to get in touch with Puppet Support. -- 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/CA%2BFnDv32362hfDZZQjjRQ8ahsi3aEy2D8QfdJKUY6MtRr14TOg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Introducing high availability to Puppet Enterprise
Hi, With our latest release <https://puppet.com/blog/high-availability-new-puppet-enterprise-2016-5>, Puppet Enterprise 2016.5 introduces high availability to eliminate a single point of failure for Puppet and provide automated failover and redundancy in the event of an outage. This ensures that Puppet continues to manage infrastructure and enforce configurations even if an outage affects the hardware on which Puppet runs. Other highlights include: - Environment Isolation - This will prevent catalog compilation problems when you have custom Puppet code that differs between environments. - Corrective change reporting in event inspection view - Gain visibility into intentional and corrective changes via the event inspection view in the Puppet Enterprise web UI. As a reminder, Puppet Enterprise 2016.4, released in October, has been designated as our long-term support (LTS) release, meaning you can expect full support, security updates and fixes for 24 months. View our support lifecycle <https://puppet.com/misc/puppet-enterprise-lifecycle> to see which release version is right for you. You can also view our on-demand webinar, What’s New in Puppet Enterprise 2016.5, to learn more and see the product in action: [Watch the webinar <https://puppet.com/resources/webinar/whats-new-puppet-enterprise-20165>] Thanks, Puppet cont...@puppet.com -- 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/CA%2BFnDv2KJ6-fWvsBMndVN7nfiqBj5rbns-YFED5%3Dj5zsxBLeHA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Announce: Puppet Enterprise 2016.4.0 is available
Hello - Today we announced the major updates to Puppet Enterprise <https://puppet.com/blog/docker-image-build-orchestration-corrective-change-reporting-puppet-enterprise-2016-4>, which give you the power to use automation as the bridge to your future, whether that's moving to the cloud or adopting containers in production. With our latest release, Puppet is laying the foundation for DevOps practices by making it easier than ever to gain situational awareness and orchestrate software change confidently, no matter what your infrastructure runs on. Updates include: - Visualize intentional vs. corrective changes - Get detailed visibility into why changes occur and whether those changes are intentional or due to unexpected configuration drift with new reporting in the Puppet Enterprise web UI. - Orchestrate phased deployments - Significant enhancements to Puppet’s orchestration capabilities enable you to easily segment your infrastructure and run phased, canary deployments to as many servers at a time as you define. Using the Puppet orchestrator, it is now possible to segment infrastructure based on characteristics such as location, operating system, specific configurations applied, or any additional facts, and run ordered deployments to targeted portions of your infrastructure. - Puppet & Docker - Automate the container build process using Puppet as you define, build, and deploy containers into production environments. - VMware vRealize integration - A new Integration with VMware's vRealize Suite (vRA/vRO) significantly reduces lead times by enabling fully automated, self-service provisioning workflows. - Jenkins integration - A new integration with Jenkins lets you scale your DevOps practice by building continuous delivery pipelines and orchestrating infrastructure deployment with an integrated toolchain. Puppet Enterprise 2016.4 has been designated as our long-term support (LTS) release, meaning you can expect full support, security updates and fixes for 24-months. Make sure to upgrade to Puppet Enterprise 2016.4, and check out the new features in our release notes <https://docs.puppet.com/pe/latest/release_notes.html> to see how we use data analytics for continuous product improvement. You can also register for our webinar, What’s New in Puppet Enterprise on 3 November 2016 to learn more and see the product in action: http://info.puppet.com/2365-Whats-New-PE-2016.4-Register.html -Puppet -- Morgan Rhodes mor...@puppet.com Release Engineer -- PuppetConf 2016 <https://puppet.com/puppetconf>, 19 - 21 October, San Diego, California *Register to attend or sign up to view the Live Stream <https://puppet.com/puppetconf/registration-pricing>* -- 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%2BFnDv0FYno9DQq88pPEtrs93-F0nugUGmu8boztwEkJuVRA4Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Announce: Puppet Agent 1.5.3 Available
Puppet Agent 1.5.3 is now available. This release adds support for Fedora 24 and also includes some bugfixes for Puppet, Facter, and PXP Agent. Check out the full release notes here: https://docs.puppet.com/puppet/latest/reference/release_notes_agent.html To install or upgrade puppet-agent, follow the getting started directions: http://docs.puppetlabs.com/puppet/latest/reference/index.html -- Morgan Rhodes mor...@puppet.com Release Engineer -- PuppetConf 2016 <https://puppet.com/puppetconf>, 19 - 21 October, San Diego, California *Summer Savings - Register by 15 September and save $240 <https://puppetconf2016.eventbrite.com/?discount=SummerSavings>* -- 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%2BFnDv3-upc3qBM8r_P%3DChP%3DGrg%3DZZexVoCZGPtEc0i%3DQnBw7g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Announce: puppet-agent 1.4.2 is available
Puppet Agent 1.4.2 is now available! This is a bugfix release that addresses issues found after the 1.4.1 release, including a security-relevant fix for Ruby Puppet Masters <https://puppet.com/security/cve/cve-2016-2785>. This release also includes new packages for Ubuntu 16.04 and Huawei devices and drops support for Debian 6, Ubuntu 15.04, and Fedora 21. See the release notes for the puppet agent package here: http://docs.puppetlabs.com/puppet/latest/reference/release_notes_agent.html To install or upgrade puppet-agent, follow the getting started directions: http://docs.puppetlabs.com/puppet/latest/reference/index.html -- 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/CA%2BFnDv1m1LS5F5piTr5Ux052L7Nfiu3N1WUYfuGQOYkPVxD-vQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Announce: Puppet Enterprise 3.8.4 is available
Dear Puppet Enterprise Users, Puppet Enterprise 3.8.4 is now available. Puppet Enterprise 3.8.4 is a security and bug-fix release of Puppet Enterprise. This release contains updated versions of OpenSSL, Java, Rails, ActiveMQ, Ruby, and Passenger with fixes for security issues. For information on these and other fixes in this release, please see https://docs.puppetlabs.com/pe/3.8/release_notes.html. As a current Puppet Enterprise user, you can upgrade to this new version as part of your annual subscription. If upgrading, it is recommended to upgrade your master and console servers first. As always, we want to hear about your experiences with Puppet Enterprise. If you have any questions about upgrading, be sure to get in touch with Puppet Labs Support. -- Morgan Rhodes mor...@puppetlabs.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/CA%2BFnDv2bvKNyQTRB%2BndfpSq7KMaQbu2y%3DBsQTfXnpqtrs8kpaA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Announce: Puppet Enterprise 2015.3.2 is available
Dear Puppet Enterprise Users, Puppet Enterprise 2015.3.2 is now available. Puppet Enterprise 2015.3.2 is a security and bug-fix release of Puppet Enterprise. This release contains updated versions of OpenSSL, Java, ActiveMQ, and Ruby with fixes for security issues, as well as a security fix for Puppet Server. In addition, this release adds support for Ubuntu 15.10 and Cisco IOS-XR agents to the 2015.3 series. For information on these and other fixes in this release, please see https://docs.puppetlabs.com/pe/2015.3/release_notes.html. As a current Puppet Enterprise user, you can upgrade to this new version as part of your annual subscription. If upgrading, it is recommended to upgrade your master and console servers first. As always, we want to hear about your experiences with Puppet Enterprise. If you have any questions about upgrading, be sure to get in touch with Puppet Labs Support. -- Morgan Rhodes mor...@puppetlabs.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/CA%2BFnDv3irBJrrJAdt3bQOT0sZtVkj5e%3DjW%3DaFL1XbDM68vE%2BJg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Announce: puppet-agent 1.3.5 available
Puppet Agent 1.3.5 is now available! This is a security release that updates OpenSSL to 1.0.2f. See the release notes for the puppet agent package here: http://docs.puppetlabs.com/puppet/latest/reference/release_notes_agent.html To install or upgrade puppet-agent, follow the getting started directions: http://docs.puppetlabs.com/puppet/latest/reference/index.html -- Morgan Rhodes mor...@puppetlabs.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/CA%2BFnDv1b-L9e4R%3DrY_%2B6kCdi68MUgdz623wXrTni7gaDdTU_0g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Announce: Puppet 3.8.6 available
Puppet 3.8.6 is now available. This is a security release that updates OpenSSL to 1.0.2f for the Windows MSIs. There are no changes for non-Windows platforms. See the full release notes here: http://docs.puppetlabs.com/puppet/3.8/reference/release_notes.html For installation and upgrade instructions, see this doc: http://docs.puppetlabs.com/puppet/3.8/reference/pre_install.html -- Morgan Rhodes mor...@puppetlabs.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/CA%2BFnDv3vV0_E%2BH_QJJxLqGi2pMuHJAp_f6iZp%3D3c6LERRT1tvQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Announce: Puppet 3.8.5 available
On Wed, Jan 27, 2016 at 2:58 PM Eric Sorenson <eric.soren...@puppetlabs.com> wrote: > Puppet 3.8.5 is now available. This is a bugfix release that contains > performance improvements to catalog compilation and Mac OS X service > management, along with fixes for Windows agents and the Puppet 4 language > parser. See the full release notes here: > > http://docs.puppetlabs.com/puppet/3.8/reference/release_notes.html > > For installation and upgrade instructions, see this doc: > > http://docs.puppetlabs.com/puppet/3.8/reference/pre_install.html > > A special community shout-out for this release to Github user 'earsdown' > for the PR to fix PUP-5212, which added HTTP proxy support to the PIP > package provider. > > Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0 > puppet platform // coffee // techno // bicycles > > -- > 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/162976e8-f3a4-4af5-a211-a0900f3b4aa5%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/162976e8-f3a4-4af5-a211-a0900f3b4aa5%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > Puppet 3.8.5 for Windows included an updated version of Ruby to address CVE-2015-7551. More information is available at https://puppetlabs.com/security/cve/ruby-dec-2015-security-fixes. -- Morgan Rhodes mor...@puppetlabs.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/CA%2BFnDv2QjH8SD-xaTUH0TO7nzFz5-JPbDGsD761tcU5b2NYGUA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Announce: puppet-agent 1.3.4 available
On Mon, Jan 25, 2016 at 5:55 PM Eric Sorenson <eric.soren...@puppetlabs.com> wrote: > Puppet Agent 1.3.4 is now available! This is a bugfix release of the > all-in-one Puppet 4 based installer, which bundles Ruby, Facter, Puppet, > and other components into a single package for all supported operating > systems. > > Notable changes in this release: > * Support for Ubuntu 'Wily Werewolf' > * Puppet 4.3.2 - big batch of bugfixes, for everything from the new > "puppet lookup" command to catalog performance profiling to the > yumrepo provider. Plus bonus speed boosts for all catalog compilation! > See full Puppet release notes for details: > https://docs.puppetlabs.com/puppet/latest/reference/release_notes.html > * Facter and Hiera got version bumps to support the new Ubuntu packages; > Facter has one functionality fix (FACT-1246) but Hiera does not contain > code changes. > > See the release notes for the puppet agent package here: > http://docs.puppetlabs.com/puppet/latest/reference/release_notes_agent.html > > To install or upgrade puppet-agent, follow the getting started directions: > http://docs.puppetlabs.com/puppet/latest/reference/index.html > > Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0 > puppet platform // coffee // techno // bicycles > > -- > 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/232a99d4-176e-4052-bfd3-554793a1c05b%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/232a99d4-176e-4052-bfd3-554793a1c05b%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > Puppet Agent 1.3.4 included updates to OpenSSL to address the December Security Announcement. More information is available at https://puppetlabs.com/security/cve/openssl-dec-2015-security-fixes. -- Morgan Rhodes mor...@puppetlabs.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/CA%2BFnDv1NrxHPSiWwSJce%3DMFOezi1mPwtw%3DzKiEzSc%3Dr8RDo9KA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] [Post Mortem] Outage on apt.puppetlabs.com and yum.puppetlabs.com
*Timeline* Failures began: 24 Nov 2015 1900 GMT Notifications of failures began: 24 Nov 2015 1930 GMT Service restored for apt: 24 Nov 2015 2000 GMT Service partially restored for yum: 24 Nov 2015 2200 GMT Service fully restored: 24 Nov 2015 2320 GMT *Impact* For some part of the outage (depending on the platform) repositories on yum.puppetlabs.com and apt.puppetlabs.com were unusable due to missing content, resulting in 404 errors for both repository metadata and packages. Several users contacted us via IRC, Twitter, JIRA, and other means. What happened? Puppet Labs manages a number of servers that run our public package repository infrastructure. One of these servers was recently taken down for emergency maintenance by our provider (which was not disruptive). After maintenance was completed, we manually initiated a synchronization job to update the package contents and metadata on this server. Due to human error this sync was run in reverse, from the out-of-date node to an up-to-date node. As this process is destructive[1], it resulted in loss of data and corruption of repository metadata. What we did to restore service As part of recent efforts to improve how we ship software to our apt repositories, a complete backup of those repositories already exists on disk. Shortly after triaging the issue we were able to restore apt.puppetlabs.com from that copy. To restore the yum repositories we had to initiate a synchronization job from an internal system. The synchronization job took a considerable amount of time due to the number of rpm packages and yum metadata that needed to be restored. Next steps To remediate this in the future we’re continuing to update our release automation and process to better leverage staging infrastructure before changes are shipped to production infrastructure. This will help ensure that we always have a complete copy of our repositories that can be redeployed in case of emergency. We’re also implementing improved monitoring of this infrastructure and the package repositories it serves. This outage exposed some deficiencies in how we communicate issues like this and we are committed to developing a better communication plan for future incidents. We apologize for the outage, Puppet Labs Release Engineering --- [1] - The synchronization process is destructive (not strictly additive) in order to remove stale metadata when new packages are published -- Morgan Rhodes mor...@puppetlabs.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/CA%2BFnDv1yEVy%3D8nEn6Gb289yFQ%2B2F5Rmtc%3DdtWwz%3DGA_B5-vjWg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Multiple puppetmasters using DNS round-robin
Hi, I'm trying to set it up so that my puppet clients can connect to any of a group of puppetmasters set up with aliases to a common hostname and DNS round-robin. The round-robin setup seems to be working, as I can see ping, gethostbyname, etc connecting cyclically to each of the puppetmasters. However, running puppetd on the clients always result in the request going to a single puppetmaster. Has anyone been able to get this working? I'm running with puppet 0.24.9. Thanks! Morgan -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
