Re: [Puppet Users] strange line wrapping behavior

[Tobias Koeck]

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. Thanks for your informative answers.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Puppet Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/puppet-users/7v-N9oHHZh8/unsubscribe.
> To unsubscribe from this group and all its topics, 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/6b3d3567-c290-42ce-83b0-da474ef27c4e%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [Puppet Users] using ip range in default.pp

[Peter Kristolaitis]

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


--
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/56548E40.6050004%40alter3d.ca.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] using ip range in default.pp

[sahara301]

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
include user::sysadmin
include sudoers
include user::dev
  }

-- 
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/38abfc81-7c31-43a3-9f06-4966fe9d921b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] using ip range in default.pp

[sahara301]

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.xx.yyy".  Take out the "0\." after the 
> "10\.". 
>
>
> On 11/23/2015 05:08 PM, saha...@gmail.com  wrote: 
> > 
> > 
> >  if $::ipaddress =~ /^10\.0\.167\.\d{1,2}\.\d{1,3}$/ { 
> > include user::groups 
> > include user::sysadmin 
>
>

-- 
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/9ce38d79-8ffe-4b9d-b6bf-96fa78ef0b1f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Unplanned outage on apt.puppetlabs.com and yum.puppetlabs.com

[Morgan Haskel]

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.

-- 
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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CA%2BFnDv1ohh46x-C-GwBos5DnKqOs85q%2BB%2B4MPPevgxeueqBT4w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Unplanned outage on apt.puppetlabs.com and yum.puppetlabs.com

[Morgan Haskel]

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 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.
>
> --
> Morgan Haskel
> mor...@puppetlabs.com
> Release Engineer
>
-- 
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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CA%2BFnDv2JRy%3Do6RNSsJ8MNEkSfUDgNJ6Am86RsAT2PyKSF1kD9w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Migrating to future parser (on 3.8) in preparation for upgrade to 4.0

[Matthew Ceroni]

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:
Evaluation Error: Error while evaluating a Function Call, ensure parameter
must be specified at
/etc/puppet/environments/sandbox/modules/sudo/manifests/init.pp:51:2 on
node op1227

The code is a simple check and fail if not met

if ! ($ensure in [ 'present', 'absent' ]) {
fail("sudo 'ensure' parameter must be set to either 'absent' or
'present'")
}

It isn't liking something about the function call fail.

Any help would be appreciated.

Thanks

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

[Puppet Users] Re: Unplanned outage on apt.puppetlabs.com and yum.puppetlabs.com

[Morgan Haskel]

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 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 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.
>>
>> --
>> Morgan Haskel
>> mor...@puppetlabs.com
>> Release Engineer
>>
> --
> Morgan Haskel
> mor...@puppetlabs.com
> Release Engineer
>
-- 
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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CA%2BFnDv2A3Nskjpaz8-etby67nojC0RMrOs8usH6W99KD6i4WDg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Unplanned outage on apt.puppetlabs.com and yum.puppetlabs.com

[Morgan Haskel]

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 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 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 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.
>>>
>>> --
>>> Morgan Haskel
>>> mor...@puppetlabs.com
>>> Release Engineer
>>>
>> --
>> Morgan Haskel
>> mor...@puppetlabs.com
>> Release Engineer
>>
> --
> Morgan Haskel
> mor...@puppetlabs.com
> Release Engineer
>
-- 
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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CA%2BFnDv1e1H3q0SGE-efC61xQLQA083NEji6iQLgPUWfPZh3i_w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Unplanned outage on apt.puppetlabs.com and yum.puppetlabs.com

[Morgan Haskel]

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 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 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 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 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.

 --
 Morgan Haskel
 mor...@puppetlabs.com
 Release Engineer

>>> --
>>> Morgan Haskel
>>> mor...@puppetlabs.com
>>> Release Engineer
>>>
>> --
>> Morgan Haskel
>> mor...@puppetlabs.com
>> Release Engineer
>>
> --
> Morgan Haskel
> mor...@puppetlabs.com
> Release Engineer
>
-- 
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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CA%2BFnDv09mSEYK78_44VKpxo2brhdwoBS0KzaqheVo8SWWL5RtQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Security Advisory: puppetlabs-ntp default configuration does not fully mitigate CVE-2013-5211

[Morgan Haskel]

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 vulnerable to local attacks.

With the puppetlabs-ntp 4.1.1 release, the default value for the
'disable_monitor' parameter is set to 'true' for all platforms.

No action is required unless you are manually setting 'disable_monitor' to
false or you need monitoring 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" 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%2BFnDv0rgnh5p3%3DjFwUDoYo1hWS5rHMA3doQKNa8k8PO7kW1Fw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Data Type: Hashes

[Matthew Ceroni]

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 SERVER: Evaluation Error: Missing title. The title expression
resulted in undef at
/etc/puppet/environments/sandbox/manifests/site.pp:14:11

If I don't specify a key and instead do

notify { "$lb_rules": }

I get

Error 400 on SERVER: Evaluation Error: Illegal title type at index 0.
Expected String, got Hash[String, String]

Confirming that lb_rules is a hash.

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

Re: [Puppet Users] Data Type: Hashes

[Peter Huene]

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 to print out one of the values
> ex:
>
>  notify { "$lb_rules[VCC]": }
>

VCC (without quotes) is a type name in the Puppet Language because it
starts with a capitalized letter.

Try using single quotes around VCC, like so:

```
notify { "$lb_rules['VCC']": }
```


>
> But get
>
> Error 400 on SERVER: Evaluation Error: Missing title. The title expression
> resulted in undef at
> /etc/puppet/environments/sandbox/manifests/site.pp:14:11
>
> If I don't specify a key and instead do
>
> notify { "$lb_rules": }
>
> I get
>
> Error 400 on SERVER: Evaluation Error: Illegal title type at index 0.
> Expected String, got Hash[String, String]
>
> Confirming that lb_rules is a hash.
>
>
>
>
> --
> 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%2BNsY5jkQAEyamw7yauG2FWA6ktqeWGOVRZBCKaS_pW%2BYqS0OQ%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CACZQQfMUPbmXm_DSzQgu%3DXBrrvkAVMcNtcHnpq-SOp7VaKsW%2Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Migrating to future parser (on 3.8) in preparation for upgrade to 4.0

[Peter Huene]

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.
>
> Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
> Evaluation Error: Error while evaluating a Function Call, ensure parameter
> must be specified at
> /etc/puppet/environments/sandbox/modules/sudo/manifests/init.pp:51:2 on
> node op1227
>
> The code is a simple check and fail if not met
>
> if ! ($ensure in [ 'present', 'absent' ]) {
> fail("sudo 'ensure' parameter must be set to either 'absent' or
> 'present'")
> }
>
>
Fail is expected to fail the parse, but I'd expect the given error message
to match up with what was returned by the server.

What's the value of $ensure at evaluation time?  Perhaps changing the error
message to something like "'$ensure' is not a valid value for parameter
\$ensure: expected either 'absent' or 'present'" so it's easily displayed
in the error might help debug this.


> It isn't liking something about the function call fail.
>
> Any help would be appreciated.
>
> Thanks
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CA%2BNsY5iN4%3DjYvXnppOdnw_KLNZZtunauoF8kodryXLwYcohEhA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

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