ion on the web visit
> https://groups.google.com/d/msgid/puppet-users/bb493bd4-0e0c-4a0d-91d5-3ca99dba55fc%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/bb493bd4-0e0c-4a0d-91d5-3ca99dba55fc%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> F
onitoring enabled in your environment.
Please see
https://puppetlabs.com/security/cve/puppetlabs-ntp-nov-2015-advisory for
more information.
--
Morgan Haskel
mor...@puppetlabs.com
Release Engineer
--
You received this message because you are subscribed to the Google Groups
"Puppet Users&qu
puppet-server 2.2.0 has been redeployed to yum.puppetlabs.com. Please let
us know if you have any issues.
On Tue, Nov 24, 2015 at 2:11 PM Morgan Haskel wrote:
> All,
>
> At this point the metadata mismatches on yum.puppetlabs.com have been
> resolved. We are still missing the recen
All,
At this point the metadata mismatches on yum.puppetlabs.com have been
resolved. We are still missing the recently released puppet-server 2.2.0
from the repository but that will be up shortly.
On Tue, Nov 24, 2015 at 1:01 PM Morgan Haskel wrote:
> The data transfer for yum.puppetlabs.
The data transfer for yum.puppetlabs.com is taking longer than expected. We
are still working on it but limited to the time the transfer takes. I'll
send another update once yum.puppetlabs.com has been restored.
On Tue, Nov 24, 2015 at 12:02 PM Morgan Haskel
wrote:
> At this time ser
At this time service has been restored for apt.puppetlabs.com. The fix for
yum.puppetlabs.com is underway.
On Tue, Nov 24, 2015 at 11:54 AM Morgan Haskel
wrote:
> All,
>
> We're currently experiencing an unplanned outage on apt.puppetlabs.com
> and yum.puppetlabs.com.
>
&
anges.
--
Morgan Haskel
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.co
Engineering
---
[1] puppet-agent 1.3.0 is on the public download sites as of ~1845 GMT
11/18.
[2] We’re also looking into replacing freight, because our repository has
scaled well past the size of where freight was an ideal tool for us/
--
Morgan Haskel
mor...@puppetlabs.com
Release Engin
sty/main/binary-amd64/Packages> Hash
> Sum mismatch*
>
> *E: Some index files failed to download. They have been ignored, or old
> ones used instead.*
>
> This is as of Tue Nov 17 22:51:24 UTC 2015.
>
> On Wednesday, 18 November 2015 07:52:08 UTC+11, Morgan Haskel wrote:
>
&
Apt.puppetlabs.com is back up at this time. Please let us know if you see
any strange behavior.
Morgan
On Tue, Nov 17, 2015 at 12:43 PM Morgan Haskel
wrote:
> All,
>
> We're currently having issues with apt.puppetlabs.com and all of the
> repositories hosted there are unavail
or we know more.
Morgan
--
Morgan Haskel
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...@googl
an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/9f4937cc-e8f3-4307-9082-7d7b1df109d5%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/9f4937cc-e8f3-4307-9082-7d7b1df1
On Thu, Aug 20, 2015 at 4:21 PM Vince Skahan wrote:
> On Thursday, August 20, 2015 at 3:40:59 PM UTC-7, Morgan Haskel wrote:
>>
>> Hi Vince,
>>
>> This sounds like an issue with the MODULE, could you please submit a
>> ticket at https://tickets.puppetlabs.com/br
"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/93a38d17-4b04-4706-b9f0-bb15
new version.
--
Morgan Haskel
mor...@puppetlabs.com
Module Engineer
*PuppetConf 2015 <http://2015.puppetconf.com/> is coming to Portland,
Oregon! Join us October 5-9.*
*Register now to take advantage of the Early Adopter discount
<https://www.eventbrite.com/e/puppetconf-2015-october-5-9
l',
> 'connectionTimeout' => '2'
> }
> }->
> tomcat::config::server::connector { 'https-443':
> port => '443',
> protocol => 'HTTP/1.1',
> additional_attributes => {
> &
doing this?
>
> Trey
>
> On Monday, August 25, 2014 3:01:00 PM UTC-4, Morgan Haskel wrote:
>
>> Trey,
>>
>> The '>= 1.0.0' is referring to the libaugeas version, and it's based on
>> the `augeasversion` fact. You'll need to have augeas insta
ps://groups.google.com/d/msgid/puppet-users/7b385fdc-8660-4765-89ae-dd7fdca2f4d1%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/7b385fdc-8660-4765-89ae-dd7fdca2f4d1%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https:
t: http://www.github.com/juasiepo
> GPG key = 0xA110F4FE
> Key Fingerprint = DF53 7415 0936 244E 9B00 6E66 E934 3406 A110 F4FE
>
> ----------
>
>
> 2014-05-20 22:55 GMT+02:00 Morgan Haskel :
> > Ju
--
> 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
We released puppetlabs-rabbitmq 4.0.0 today with several new features and
bug fixes.
Let us know if you have any issues!
On Fri, May 16, 2014 at 12:23 PM, Morgan Haskel wrote:
> Steve,
>
> We can cut a new release. Is there anything outstanding you need to have
> merged in befor
Steve,
We can cut a new release. Is there anything outstanding you need to have
merged in before we do that?
Thanks,
Morgan
On Wednesday, May 14, 2014 11:54:34 AM UTC-4, Stephen Boissiere wrote:
>
> Hi all, I'm hoping somebody can tell me if a new release of the Rabbit MQ
> plugin is imminent
Thanks!
On Wed, Dec 15, 2010 at 4:14 PM, James Turnbull wrote:
> Morgan Haskel wrote:
> > Hi All,
> >
> > I have a script that I want to run at the end of my puppet run after
> > every run. Is there a way to create a 'cleanup' stage that will run
> >
Hi All,
I have a script that I want to run at the end of my puppet run after
every run. Is there a way to create a 'cleanup' stage that will run
at the end of the stage even if there are failures in previous stages?
Thanks,
Morgan
--
You received this message because you are subscribed to the
24 matches
Mail list logo
