date:20150925

Re: [Puppet Users] Forge ACL Module 1.1.1 on Windows 7 x64 SP1

2015-09-25 Thread jmp242

Well . . . It doesn't give me anything else helpful. Out of 142KB of log, 
this seems relevant:

 { identity => 'NT AUTHORITY\SYSTEM', rights => ["full"], affects => 
'self_only' },  
 { identity => 'NT AUTHORITY\SYSTEM', rights => ["full"], affects => 
'self_only' },  
 { identity => 'NT AUTHORITY\SYSTEM', rights => ["full"], affects => 
'self_only' },  
 { identity => 'NT AUTHORITY\SYSTEM', rights => ["full"], affects => 
'self_only' },  
 { identity => 'NT AUTHORITY\SYSTEM', rights => ["full"], affects => 
'self_only' },  
 { identity => 'NT AUTHORITY\SYSTEM', rights => ["full"], affects => 
'self_only' },  
 { identity => 'NT AUTHORITY\SYSTEM', rights => ["full"], affects => 
'self_only' },  
 { identity => 'NT AUTHORITY\SYSTEM', rights => ["full"], affects => 
'self_only' },  
 { identity => 'NT AUTHORITY\SYSTEM', rights => ["full"], affects => 
'self_only' },  
 { identity => 'NT AUTHORITY\SYSTEM', rights => ["full"], affects => 
'self_only' },  
 { identity => 'NT AUTHORITY\SYSTEM', rights => ["full"], affects => 
'self_only' },  
 { identity => 'NT AUTHORITY\SYSTEM', rights => ["full"], affects => 
'self_only' },  
 { identity => 'NT AUTHORITY\SYSTEM', rights => ["full"], affects => 
'self_only' },  
 { identity => 'NT AUTHORITY\SYSTEM', rights => ["full"], affects => 
'self_only' },  
 { identity => 'NT AUTHORITY\SYSTEM', rights => ["full"], affects => 
'self_only' },  
 { identity => 'NT AUTHORITY\SYSTEM', rights => ["full"], affects => 
'self_only' },  
 { identity => 'NT AUTHORITY\SYSTEM', rights => ["mask_specific"], mask => 
'2032063', affects => 'self_only' },  
 { identity => 'NT AUTHORITY\SYSTEM', rights => ["write", "read", "execute"
], affects => 'self_only' },  
 { identity => 'Everyone', rights => ["read", "execute"], affects => 
'self_only' } 
] to [ 
 { identity => 'NT AUTHORITY\SYSTEM', rights => ["full"], affects => 
'self_only' },  
 { identity => 'BUILTIN\Administrators', rights => ["full"], affects => 
'self_only' },  
 { identity => 'BUILTIN\Users', rights => ["read", "execute"], affects => 
'self_only' },  
 { identity => 'Everyone', rights => ["read", "execute"], affects => 
'self_only' } 
] [0m 
 [1;31mError: /Stage[main]/Yum/Acl[chocolatey.config]: Could not evaluate: 
The parameter is incorrect. - ReportEvent


The  { identity => 'NT AUTHORITY\SYSTEM', rights => ["full"], affects => 
'self_only' },  
repeats several hundred times that I didn't bother to paste here.

I am going to test with your simpler version to see if it makes a 
difference...

On Friday, September 25, 2015 at 3:12:42 AM UTC-4, Rob Reynolds wrote:
>
>
>
> On Thu, Sep 24, 2015 at 7:25 AM, jmp242  
> wrote:
>
>> So per my previous post, I'm now trying to replace the file POSIX 
>> permissions with ACLs. I'm apparently missing something though. I want to 
>> replicate what I had before in the new supported method, i.e.:
>>
>> owner   => 'SYSTEM',
>> group   => 'Administrators',
>> mode=> '0775',
>>
>>
>> So I tried doing:
>> acl { 'chocolatey.config':
>> target  => 
>> 'C:/ProgramData/chocolatey/config/chocolatey.config',
>> purge   => false,
>> permissions => [
>>   {
>> identity=> 'SYSTEM',
>> rights  => [
>>   'full'],
>> perm_type   => 'allow',
>> child_types => 'all',
>> affects => 'all'
>>   }
>>   ,
>>   {
>> identity=> 'Administrators',
>> rights  => [
>>   'full'],
>> perm_type   => 'allow',
>> child_types => 'all',
>> affects => 'all'
>>   }
>>   ,
>>   {
>> identity=> 'Users',
>> rights  => [
>>   'read',
>>   'execute'],
>> perm_type   => 'allow',
>> child_types => 'all',
>> affects => 'all'
>>   }
>>   ],
>> owner   => 'SYSTEM', # Creator_Owner specific, doesn't 
>> manage unless specified
>> group   => 'Administrators', # Creator_Group specific, 
>> doesn't manage unless specified
>> inherit_parent_permissions => true,
>> require => File['chocolatey.config'],
>>   }
>>
>>
>> As I understand the documentation, this seems to map, mind you - being 
>> far more verbose and complicated - to the original permissions. 
>>
>
> Sure, it's a LOT more verbose if you add all of the defaults in. Leaving 
> out the defaults and considering that acl already does autorequires on a 
> file with the same path (we'll leave the requires in), this looks a lot 
> better:
>
> acl { 'c:/ProgramData/chocolatey/config/chocolatey.config':
>   permissions => [
>{ identity => 'SYSTEM', rights => ['full']},
>{ identity => 'Administrators', rights => ['full']},
>{ identity => 'Users', rights => ['read', 'execute']},
>   require =>

[Puppet Users] puppet 2015.2 installation problem on Centos 6.5

2015-09-25 Thread bo sun

Hi guys,

this is my first try of puppet, but installation failed as log shows below:

** /opt/puppetlabs/puppet/bin/erb -T - 
'/tmp/pe-installer-piDZHaqs/install/erb/puppet_enterprise.pp.erb' 
'/tmp/pe-installer-piDZHaqs/install/erb/pe_repo.pp.erb'| { 
PATH=/opt/puppetlabs/puppet/bin:/opt/puppetlabs/puppet/share/installer/vendor/ruby/2.1.0/bin:/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin:/usr/sbin:/usr/bin:/sbin:/bin
 
/opt/puppetlabs/puppet/bin/puppet apply  --no-report   
   --no-storeconfigs 
 --modulepath=/opt/puppetlabs/puppet/modules 
 --detailed-exitcodes  2>&1 >&3| 
sed-e '/Warning: You cannot collect without 
storeconfigs being set/d'-e '/Warning: You cannot 
collect exported resources without storeconfigs being set/d'   
 -e '/Warning: Not collecting exported resources without 
storeconfigs/d'; rc=${PIPESTATUS[0]}; test ${rc} -eq 0 
|| test ${rc} -eq 2  ; } 3>&1
Error: Evaluation Error: Error while evaluating a Function Call, 
Net::ReadTimeout at 
/opt/puppetlabs/puppet/modules/pe_repo/manifests/repo.pp:55:11 on node 
cnbjnms001.bjlab.cn.ao.ericsson.se

I'm not familiar with ruby script so it's really a big trouble for me to 
fix it. Any one who can help me please do me a favor, really appreciate and 
thanks in advance.

BR/

-- 
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/d4295e87-9203-49aa-92f7-a3f372ce7c72%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] r10k module prefetch questions

2015-09-25 Thread Christopher Wood

(Not a programmer, please bear with me. I couldn't find answers in the code for
1.5.1 or 2.0.3.)

How often does r10k update its cache? It looks like once per invocation.

Is there a way of telling an r10k invocation to use the cache directly?

I could use local git repositories presync'ed myself per testing, but if
there's a way around separately presync'ing that would be better. Presync'ing a
new module would mean that somebody would have to update a server config item
and only then update their puppetfile.

Backstory:

I attempted a monolithic->r10k conversion yesterday in preprod and it didn't go
well and I rolled back. I think I attempted too many environments with too many
modules in each environment, for starters. The initial sync took very long and
I had inode usage issues on two smaller puppetmasters. I was also attempting
separate control repos rather than separate branches of a single control repo
for better ACL'ing.

I also noticed that each "r10k puppetfile install" spawned two git processes
per module. As near as I could tell there was one to fetch the cache via https
and another to fetch the actual module, again connecting via https while using
the cache. In our environment this is pretty slow.

(Plenty of experience to learn from, at least.)

--
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/20150925180255.GA14616%40iniquitous.heresiarch.ca.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Forge ACL Module 1.1.1 on Windows 7 x64 SP1

2015-09-25 Thread Rob Reynolds

So let's remove target and give it a shot.

acl { 'c:/ProgramData/chocolatey/config/chocolatey.config':

On Fri, Sep 25, 2015 at 1:31 PM, jmp242  wrote:

> I tried with the simplified version:
> Enter code here...  acl { 'chocolatey.config':
> target  =>
> 'C:/ProgramData/chocolatey/config/chocolatey.config',
> permissions => [
>   {
> identity => 'SYSTEM',
> rights   => [
>   'full']
>   }
>   ,
>   {
> identity => 'Administrators',
> rights   => [
>   'full']
>   }
>   ,
>   {
> identity => 'Users',
> rights   => [
>   'read',
>   'execute']
>   }
>   ],
> require => File['chocolatey.config'],
>   }
>
> I got the same error. Unless the problem is using
> target=>
>
> I'm at a loss
>
> --
> 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/d944ede0-c388-4669-b433-866dc495a667%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Rob Reynolds
Developer, Puppet Labs

*PuppetConf 2015 ** is right around the
corner! Join us October 5-9 in Portland, OR. **Register 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/CAMJiBK7CQgBm6xDQHPE54VgcE3tmoeiVK-HgabhSB9P_2r6H8g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Forge ACL Module 1.1.1 on Windows 7 x64 SP1

2015-09-25 Thread Rob Reynolds

Actually I just went back and looked

[1;31mError: /Stage[main]/Yum/Acl[chocolatey.config]: Could not evaluate:
The parameter is incorrect. -ReportEvent

Yum?

On Fri, Sep 25, 2015 at 3:38 PM, Rob Reynolds  wrote:

> So let's remove target and give it a shot.
>
> acl { 'c:/ProgramData/chocolatey/config/chocolatey.config':
>
> On Fri, Sep 25, 2015 at 1:31 PM, jmp242  wrote:
>
>> I tried with the simplified version:
>> Enter code here...  acl { 'chocolatey.config':
>> target  =>
>> 'C:/ProgramData/chocolatey/config/chocolatey.config',
>> permissions => [
>>   {
>> identity => 'SYSTEM',
>> rights   => [
>>   'full']
>>   }
>>   ,
>>   {
>> identity => 'Administrators',
>> rights   => [
>>   'full']
>>   }
>>   ,
>>   {
>> identity => 'Users',
>> rights   => [
>>   'read',
>>   'execute']
>>   }
>>   ],
>> require => File['chocolatey.config'],
>>   }
>>
>> I got the same error. Unless the problem is using
>> target=>
>>
>> I'm at a loss
>>
>> --
>> 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/d944ede0-c388-4669-b433-866dc495a667%40googlegroups.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Rob Reynolds
> Developer, Puppet Labs
>
> *PuppetConf 2015 ** is right around the
> corner! Join us October 5-9 in Portland, OR. **Register now
> **.*
>



-- 
Rob Reynolds
Developer, Puppet Labs

*PuppetConf 2015 ** is right around the
corner! Join us October 5-9 in Portland, OR. **Register 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/CAMJiBK7NPzHRTy3J%2BuZiqrhXjEN%2BMG42Nj5C%2Bfy9uZevqFFBqw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet 4, rspec, and stages

2015-09-25 Thread Sean McKinley

Hah! That's a valid point. Unfortunately for me, the actual manifest has 
the comma after the password (I just failed when obscuring it, apparently).

On Thursday, September 24, 2015 at 8:33:48 PM UTC-7, red wrote:
>
> You might need a comma after 'obscured_because_security' :)
>
> On Thu, Sep 24, 2015 at 3:40 PM, Sean McKinley  > wrote:
>
>> We recently upgraded to PE2015, and as such have upgraded our local 
>> puppet gems to match (4.2.2). Unfortunately a few of our specs that were 
>> previously passing are now failing, mostly in regards to stages:
>>
>> "Evaluation Error: Error while evaluating a Function Call, Could not find 
>> stage first specified by Class[Ipa::client]"
>>
>> The class is fairly simple:
>>
>> class ipa::client(
>>   $principal = 'host_manager',
>>   $password = 'obscured_because_security'
>>   $stage = first,
>>  ){
>>
>> Has anyone run into this yet by chance?
>>
>> -- 
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/02ebfaec-04b8-4f5c-89f8-6f81a9827f2b%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/2c653d19-6491-4bf1-91bb-c40bbc9ac906%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet 4, rspec, and stages

2015-09-25 Thread Philip Wigg

> We recently upgraded to PE2015, and as such have upgraded our local puppet
> gems to match (4.2.2). Unfortunately a few of our specs that were previously
> passing are now failing, mostly in regards to stages:
>
> "Evaluation Error: Error while evaluating a Function Call, Could not find
> stage first specified by Class[Ipa::client]"
>
> The class is fairly simple:
>
> class ipa::client(
>   $principal = 'host_manager',
>   $password = 'obscured_because_security'
>   $stage = first,
>  ){
>
> Has anyone run into this yet by chance?

I don't totally understand this.

You seem to have a parameterised class which takes $stage as a parameter?

I would expect 'stage' to be used as a metaparameter in resource-like
class declaration as in:-

https://docs.puppetlabs.com/puppet/latest/reference/lang_run_stages.html

Cheers,
Phil.

-- 
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/CAA54UtO792a%3D7LEm-t2uOwPREV4-9dhy84LU1Mh6y2SpZTjq6Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Check code quality with SonarQube

2015-09-25 Thread Mike Skint

Just checking in David,  wondering about the future parser progress. How is 
it going? 

 Also may have found a bug, though it may be down to the future parser.  
I'm seeing a parse error in sonarqube for a manifest that runs fine under 
puppet 3.x and puppet with the future parser enabled.

On Friday, August 21, 2015 at 12:58:41 AM UTC-7, David Racodon wrote:
>
> Thank you Mike! ... and thanks to Iain as well who's co-developing the 
> plugin with me.
>
> Glad you like it!
>
> As a bonus, I also released a JSON plugin. It provides similar 
> https://github.com/puppet-community/metadata-json-lint checks, plus 
> additional checks such as enforcing a specific license or author. See 
> https://github.com/racodond/sonar-json-plugin/releases/tag/1.0
>
>
> David RACODON
> Freelance QA Consultant
> LinkedIn  | Twitter 
> 
>
> On Thu, Aug 20, 2015 at 11:26 PM, Mike Skint  > wrote:
>
>> David,
>>
>> what an outstanding tool!  so so sweet!
>>
>> thank you!
>>
>>
>>
>>
>>
>> On Thursday, August 20, 2015 at 1:51:09 PM UTC-7, David Racodon wrote:
>>>
>>> Hi Mike,
>>>
>>> How does sonarqube differ from puppet-lint
>>>
>>>
>>> SonarQube provides more checks than puppet-lint and similar checks have 
>>> fewer false negatives.
>>> Checks are not only coding style related. There are checks:
>>>
>>>- to detect potential bugs: duplicated hash keys should be removed, 
>>>duplicated parameters should be removed, ...
>>>- to warn about deprecated structures: deprecated node inheritance 
>>>should not be used, ...
>>>- to point out complex code: case and selectors statements should 
>>>not be nested, classes and defines should not be too complex, ...
>>>- to point out pitfalls: if...elsif structures should be terminated 
>>>by an else statement, empty blocks should be removed, ...
>>>- ...
>>>
>>> and a lot more valuable checks are being implemented.
>>>
>>> As stated before, it comes with a nice web interface to browse issues, 
>>> it computes metrics (lines of code, complexity, comments lines, number of 
>>> resources, ...), it keeps history, you can focus on new code, you can get 
>>> an overview of your entire Puppet code base, it checks for duplication, it 
>>> computes technical debt, the analysis is way faster, etc.
>>>
>>> The best way to discover how SonarQube can bring you value is to either 
>>> browse the demo instance at http://nemo.sonarqube.org or install it and 
>>> give it a try on your source code. By the way, I just built a package to 
>>> analyze your Puppet code in less than two minutes. So feel free to give it 
>>> a try: 
>>> https://github.com/racodond/package-test-sonarqube-puppet/archive/master.zip
>>>
>>>
>>>  also does it test for the future parser?
>>>
>>>
>>> Not in this first version but we're working hard on it.
>>>
>>> Cheers, 
>>>
>>> David RACODON
>>> Freelance QA Consultant
>>> LinkedIn  | Twitter 
>>> 
>>>
>>> On Thu, Aug 20, 2015 at 7:47 PM, Mike Skint  wrote:
>>>
 This is interesting,  thanks.  

 How does sonarqube differ from puppet-lint, also does it test for the 
 future parser?

 cheers.

 On Tuesday, August 18, 2015 at 11:13:11 PM UTC-7, David Racodon wrote:
>
> Hi,
>
> Iain and I developed a SonarQube  plugin 
> to check code quality of Puppet modules. This first version comes with 
> over 
> 40 rules spanning from potential bugs to coding style guidelines. It 
> fully 
> benefits from all the nice features coming with SonarQube 
> : efficient web interface to browse 
> issues and metrics, ability to focus your effort on new code (added or 
> modified) only, computation of technical debt and a lot more.
>
> It is fully open source and free. So, feel free to give it a try. The 
> release is available at: 
> https://github.com/iwarapter/sonar-puppet/releases/tag/1.0. To get 
> started with SonarQube, see 
> http://docs.sonarqube.org/display/SONAR/Documentation.
>
> Any feedback is more than welcome!
>
> Meanwhile, we'll keep adding new features.
>
> Enjoy!
>
> Iain Adams and David Racodon
>
> David RACODON
> Freelance QA Consultant
> LinkedIn  | 
> Twitter 
>
 -- 
 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...@googlegroups.com.
 To view this discussion on the web visit

[Puppet Users] Re: Forge ACL Module 1.1.1 on Windows 7 x64 SP1

2015-09-25 Thread jmp242

I tried with the simplified version:
Enter code here...  acl { 'chocolatey.config':
target  => 'C:/ProgramData/chocolatey/config/chocolatey.config',
permissions => [
  {
identity => 'SYSTEM',
rights   => [
  'full']
  }
  ,
  {
identity => 'Administrators',
rights   => [
  'full']
  }
  ,
  {
identity => 'Users',
rights   => [
  'read',
  'execute']
  }
  ],
require => File['chocolatey.config'],
  }

I got the same error. Unless the problem is using 
target=>

I'm at a loss

-- 
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/d944ede0-c388-4669-b433-866dc495a667%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Forge ACL Module 1.1.1 on Windows 7 x64 SP1

2015-09-25 Thread Rob Reynolds

On Thu, Sep 24, 2015 at 7:25 AM, jmp242  wrote:

> So per my previous post, I'm now trying to replace the file POSIX
> permissions with ACLs. I'm apparently missing something though. I want to
> replicate what I had before in the new supported method, i.e.:
>
> owner   => 'SYSTEM',
> group   => 'Administrators',
> mode=> '0775',
>
>
> So I tried doing:
> acl { 'chocolatey.config':
> target  =>
> 'C:/ProgramData/chocolatey/config/chocolatey.config',
> purge   => false,
> permissions => [
>   {
> identity=> 'SYSTEM',
> rights  => [
>   'full'],
> perm_type   => 'allow',
> child_types => 'all',
> affects => 'all'
>   }
>   ,
>   {
> identity=> 'Administrators',
> rights  => [
>   'full'],
> perm_type   => 'allow',
> child_types => 'all',
> affects => 'all'
>   }
>   ,
>   {
> identity=> 'Users',
> rights  => [
>   'read',
>   'execute'],
> perm_type   => 'allow',
> child_types => 'all',
> affects => 'all'
>   }
>   ],
> owner   => 'SYSTEM', # Creator_Owner specific, doesn't manage
> unless specified
> group   => 'Administrators', # Creator_Group specific,
> doesn't manage unless specified
> inherit_parent_permissions => true,
> require => File['chocolatey.config'],
>   }
>
>
> As I understand the documentation, this seems to map, mind you - being far
> more verbose and complicated - to the original permissions.
>

Sure, it's a LOT more verbose if you add all of the defaults in. Leaving
out the defaults and considering that acl already does autorequires on a
file with the same path (we'll leave the requires in), this looks a lot
better:

acl { 'c:/ProgramData/chocolatey/config/chocolatey.config':
  permissions => [
   { identity => 'SYSTEM', rights => ['full']},
   { identity => 'Administrators', rights => ['full']},
   { identity => 'Users', rights => ['read', 'execute']},
  require => File['chocolatey.config'],
}




> However, I get errors:
> Could not evaluate: The parameter is incorrect. - ReportEvent
>
> This doesn't really help me figure out what I did wrong here...
>


Not really sure what caused this. Might be good to see this with a `--debug
--trace --verbose` run to see what may be causing the issue.



>
>
> --
> 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/a49f14bc-6804-4ba8-a033-752a6da2a9cb%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Rob Reynolds
Developer, Puppet Labs

*PuppetConf 2015 ** is right around the
corner! Join us October 5-9 in Portland, OR. **Register 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/CAMJiBK45VpjwwUeUb%2BbVYJC8cLEyQt-50QJEiJcWV-jthEvJGA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Forge ACL Module 1.1.1 on Windows 7 x64 SP1

[Puppet Users] puppet 2015.2 installation problem on Centos 6.5

[Puppet Users] r10k module prefetch questions

Re: [Puppet Users] Re: Forge ACL Module 1.1.1 on Windows 7 x64 SP1

Re: [Puppet Users] Re: Forge ACL Module 1.1.1 on Windows 7 x64 SP1

Re: [Puppet Users] Puppet 4, rspec, and stages

Re: [Puppet Users] Puppet 4, rspec, and stages

Re: [Puppet Users] Re: Check code quality with SonarQube

[Puppet Users] Re: Forge ACL Module 1.1.1 on Windows 7 x64 SP1

Re: [Puppet Users] Forge ACL Module 1.1.1 on Windows 7 x64 SP1

10 matches

Site Navigation

Mail list logo

Footer information