Hi Matthew:
On Tue, Nov 24, 2015 at 12:02 PM, Matthew Ceroni
wrote:
> Working on migrating my manifests to work with Puppet 4.0. Currently on
> 3.8 and have started to experiment with the future parser (probably not so
> much future anymore).
>
> I am stuck on an error that is being reported.
>
Hi Matthew,
On Tue, Nov 24, 2015 at 4:35 PM, Matthew Ceroni
wrote:
> I am having an issue accessing elements of a hash.
>
> First, it is defined in hiera as such:
>
> lb::rules:
> VCC: rule1
> GR: rule2
>
> I retrieve the value using
>
> $lb_rules = hiera('lb::rules')
>
> Then I simply try t
I am having an issue accessing elements of a hash.
First, it is defined in hiera as such:
lb::rules:
VCC: rule1
GR: rule2
I retrieve the value using
$lb_rules = hiera('lb::rules')
Then I simply try to print out one of the values
ex:
notify { "$lb_rules[VCC]": }
But get
Error 400 on
Assessed risk level: Low
Previous versions of the puppetlabs-ntp module did not default to using
'disable monitor', which is one of the two configurations required to fully
mitigate CVE-2013-5211. The module by default would set 'noquery' for all
remote hosts, but the system would still be vulnera
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 recently released p
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.com i
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 service has bee
Working on migrating my manifests to work with Puppet 4.0. Currently on 3.8
and have started to experiment with the future parser (probably not so much
future anymore).
I am stuck on an error that is being reported.
Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Evalua
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.
>
> Projected timeframe for
All,
We're currently experiencing an unplanned outage on apt.puppetlabs.com and
yum.puppetlabs.com.
Projected timeframe for this outage is one hour, so we hope to have service
restored by 2100 GMT.
I will send out an update when service has been restored or if there are
any status changes.
--
Hi Peter,
Thank you very much! it was right on my face. I can not believe i was
looking at it and couldn't see it!
Thanks again
Sara
On Tuesday, November 24, 2015 at 11:20:30 AM UTC-5, Peter Kristolaitis
wrote:
>
> You have an extra octet in the regex.
>
> That regex would match "10.0.167.x
Hello All,
i am trying to use a range of ip address in below manner. the ip address
ranges are 10.167.26.x, 10.167.25.x,10.167.5.x and 10.167.6.x
when i use the below it doesnt work.
please help!
Thanks,
Sara
if $::ipaddress =~ /^10\.0\.167\.\d{1,2}\.\d{1,3}$/ {
include user::groups
You have an extra octet in the regex.
That regex would match "10.0.167.xx.yyy". Take out the "0\." after the
"10\.".
On 11/23/2015 05:08 PM, sahara...@gmail.com wrote:
if $::ipaddress =~ /^10\.0\.167\.\d{1,2}\.\d{1,3}$/ {
include user::groups
include user::sysadmin
--
I got the case where the backslash should be used. If you have a string
that is too long (> 80 characters) you can solve it by writing
$watchdog_txt="httpd -f /u1/cust1/www/conf/httpd.conf | /sbin/httpd -f\
/u1/cust1/www/conf/httpd.conf"
On Thu, Nov 19, 2015 at 2:29 PM, wrote:
> It works now
14 matches
Mail list logo
