Re: [Puppet Users] odd puppet-lint config problems

2016-01-20 Thread Ramin K

On 1/20/16 1:33 PM, Garrett Honeycutt wrote:

Hi Ramin,

It sounds like you have a repo with a bunch of modules as opposed to one
repo per module. Recommend using a script that calls puppet-lint with
the arguments that you would like and integrating that into a pre-commit
check or a build pipeline.

I never use .puppt-lint.rc, instead you would normally have a
Rakefile[1] that would configure puppet-lint and run the tests with
`rake lint`.

See my last post under the subject 'Slightly Off-Topic: CI Test of
Puppet module fail' for how to configure it that way.

[1] - https://github.com/ghoneycutt/puppet-module-ssh/blob/master/Rakefile

Best regards,
-g



	Thanks for the hint. A Rakefile will work and would be a nice place to 
do environment sanity checks too.


Ramin

--
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/56A04E2B.2080600%40badapple.net.
For more options, visit https://groups.google.com/d/optout.


Re: [Puppet Users] German Umlauts in Catalog

2016-01-20 Thread Bjoern Meier
Hi Josh,

ok, I think I found the problem, thanks to your questions. Our codepages in 
Windows are CP850, But the manifests and the master are UTF-8. Can I change 
the codepage only for ruby to UTF-8? If so, how? I'm not this familiar with 
ruby.
>
>
Thanks for helping.

Greetings,
Björn

>

-- 
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/69e0bcc2-fda5-4152-895b-c824d0a6f6ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Puppet Users] German Umlauts in Catalog

2016-01-20 Thread Josh Cooper
On Tue, Jan 19, 2016 at 1:09 AM, Bjoern Meier 
wrote:

> Hi,
>
> how can I use - with a puppet 3.8.3 x64 Windows clients - a File Resource
>  with öüä character.
>
> The test on the Master works fine.
> On the Client I get: invalid byte sequence in US-ASCII and he cannot
> ensure present on the file.
>
> Thanks for helping me out.
>
> --
> 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/8b11d187-5dff-40fe-b37d-91a9d2001cef%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

If you are running `puppet agent` on Windows:

* what is the output of ruby -e "puts Encoding.default_external" on the
master and agent?
* what is the agent's code page, e.g. chcp
* can you provide a gist of `puppet agent --test --trace` on Windows,
showing the stacktrace?
* what encoding is the manifest stored in on the master?

If you are running `puppet apply`:

* what is the output of ruby -e "puts Encoding.default_external" on the
agent?
* what is the agent's code page, e.g. chcp
* can you provide a gist of `puppet apply  --trace` on Windows?
* what encoding is the manifest stored in on the agent?

Josh

-- 
Josh Cooper
Developer, Puppet Labs

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


Re: [Puppet Users] German Umlauts in Catalog

2016-01-20 Thread Bjoern Meier
Hi Josh,

ok, I think I found the problem, thanks to your Questions. Out Codepages in 
Windows are CP850, But the manifests and the Master are UTF-8. Can I change 
the coderpage only for ruby to UTF-8? If so, how? I'm not this familiar 
with ruby.
>
>
Thanks for Helping.

-- 
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/4d94630a-cf3e-4d37-8f8c-91f4ed2e58d3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Puppet Users] How to cope with accented characters in DisplayName using Puppet 3.8.x on Windows XP?

2016-01-20 Thread Josh Cooper
On Tue, Jan 12, 2016 at 8:13 AM, Tiago Delboni  wrote:

> UPDATE:
>
> We were able to build Ruby 2.1.7 on XP and run Puppet successfully with it.
> "
> However, we observed the same behaviour regarding accented characters in
> DisplayName: Puppet 3.8.4, even with Ruby 2.1.7, keeps installing the
> package on every run. :(
>
>

One thing to check is whether `puppet resource package` reports the same
name and version as what you're specifying in your manifest? If the name or
version don't match exactly, then puppet will think the package is not
installed, and will try to (re)install each time.

The next thing I'd try is to programmatically call puppet to get a package
listing. Run the "Start Command Prompt for Puppet" (as an administrator on
UAC systems), and execute the following:

C:\Windows\system32>irb
irb(main):001:0> require 'puppet'
=> true
irb(main):002:0> require 'puppet/type/package'
=> true
irb(main):003:0> require 'pp'
=> true
irb(main):004:0> pp Puppet::Type::Package::ProviderWindows.instances.map
{|provider| "#{provider.package.name}, #{provider.package.version}" }
["doxygen 1.8.8, 1.8.8",
 "Microsoft Visual J# 2.0 Redistributable Package - SE (x64), ",
 "Microsoft Windows SDK for Windows 7 (7.0), 7.0.7600.16385.40715",
 "Windows Azure Emulator - v2.2  \u2013  \u2013  \u2013, 2.2.6492.2",
 "NSClient++ (x64), 0.3.9.328",
  ...
]

More than likely you are running into yet another ruby registry bug that we
worked around in https://tickets.puppetlabs.com/browse/PUP-3837, The
particular issue is that calling Win32::Registry#each_key does not
correctly handle unicode. See
https://tickets.puppetlabs.com/browse/PUP-3837?focusedCommentId=131991=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-131991
for more details.


>
> Em segunda-feira, 11 de janeiro de 2016 14:28:11 UTC-2, Tiago Delboni
> escreveu:
>>
>> I was able to build Ruby 2.1.7 on XP using mingw32, along with the gems
>> listed in %ProgramFiles%\Puppet
>> Labs\Puppet\sys\ruby\lib\ruby\gems\1.9.0\gems
>> However, as I am illiterate on Ruby, I'm not sure I dealt properly with
>> the dependencies. Simply replacing %ProgramFiles%\Puppet
>> Labs\Puppet\sys\ruby with the new built does not work:
>>
>> C:\>puppet --version
>> C:/Arquivos de programas/Puppet
>> Labs/Puppet/sys/ruby/lib/ruby/gems/2.1.0/gems/win32-security-0.3.2/lib/win32/security.rb:61:in
>> `block in elevated_security?': ParÔmetro incorreto. - GetTokenInformation
>> (SystemCallError)
>> from C:/Arquivos de programas/Puppet
>> Labs/Puppet/sys/ruby/lib/ruby/gems/2.1.0/gems/win32-security-0.3.2/lib/win32/security.rb:41:in
>> `initialize'
>> from C:/Arquivos de programas/Puppet
>> Labs/Puppet/sys/ruby/lib/ruby/gems/2.1.0/gems/win32-security-0.3.2/lib/win32/security.rb:41:in
>> `new'
>> from C:/Arquivos de programas/Puppet
>> Labs/Puppet/sys/ruby/lib/ruby/gems/2.1.0/gems/win32-security-0.3.2/lib/win32/security.rb:41:in
>> `elevated_security?'
>> from C:/Arquivos de programas/Puppet
>> Labs/Puppet/facter/lib/facter/util/windows_root.rb:5:in `root?'
>> from C:/Arquivos de programas/Puppet
>> Labs/Puppet/facter/lib/facter/util/config.rb:41:in
>> `setup_default_ext_facts_dirs'
>> from C:/Arquivos de programas/Puppet
>> Labs/Puppet/facter/lib/facter/util/config.rb:69:in `'
>> from C:/Arquivos de programas/Puppet
>> Labs/Puppet/facter/lib/facter/util/config.rb:5:in `'
>> from C:/Arquivos de programas/Puppet
>> Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
>> `require'
>> from C:/Arquivos de programas/Puppet
>> Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
>> `require'
>> from C:/Arquivos de programas/Puppet
>> Labs/Puppet/facter/lib/facter/util/resolution.rb:2:in `'
>> from C:/Arquivos de programas/Puppet
>> Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
>> `require'
>> from C:/Arquivos de programas/Puppet
>> Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
>> `require'
>> from C:/Arquivos de programas/Puppet
>> Labs/Puppet/facter/lib/facter/util/fact.rb:2:in `'
>> from C:/Arquivos de programas/Puppet
>> Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
>> `require'
>> from C:/Arquivos de programas/Puppet
>> Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
>> `require'
>> from C:/Arquivos de programas/Puppet
>> Labs/Puppet/facter/lib/facter.rb:35:in `'
>> from C:/Arquivos de programas/Puppet
>> Labs/Puppet/facter/lib/facter.rb:30:in `'
>> from C:/Arquivos de programas/Puppet
>> Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
>> `require'
>> from C:/Arquivos de programas/Puppet
>> Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
>> `require'
>> from 

Re: [Puppet Users] Slightly Off-Topic: CI Test of Puppet module fail

2016-01-20 Thread Garrett Honeycutt
On 1/19/16 7:31 AM, Gareth Rushgrove wrote:
> The error from Travis suggests a linting issue, specifically:
> 
> manifests/config/mysql.pp - WARNING: ensure found on line but it's
> not the first attribute on line 24
> 
> My guess for why you're not seeing that locally, but it's coming up in
> Travis is that the version of puppet-lint is unspecified. I'd wager
> that locally you have an older version, but Travis is installing the
> latest.
> 
> https://github.com/thbe/puppet-bacula/blob/master/Gemfile#L7
> 
> Looking at this more closely however the plot thickens. It looks like
> it might be a bug in puppet-lint.
> 
> https://github.com/thbe/puppet-bacula/blob/master/manifests/config/mysql.pp#L24
> 
> The code referenced does use ensure, but as an attribute of a nested
> data structure, not as a parameter.
> 
> Two options present:
> 
> * Add a control comment to ignore the check for that line, described
> here: http://puppet-lint.com/controlcomments/
> * Determine the local version of puppet-lint that is passing the check
> and pin to that version in your Gemfile
> 
> I'd also open the issue over on
> https://github.com/rodjek/puppet-lint/issues as I think it's a bug.
> 
> Cheers (and definitely not off-topic. This list is for pretty-much
> anything that's useful to users of Puppet in my view.
> 
> Gareth
> 
> On 19 January 2016 at 11:54, Thomas Bendler  wrote:
>>
>> Hello,
>>
>> I have a small problem with a Puppet module I've wrote. The module is:
>>
>> https://forge.puppetlabs.com/thbe/bacula
>>
>> When I check the module locally with:
>>
>> bundle exec rake validate && bundle exec rake lint && bundle exec rake spec
>> SPEC_OPTS='--format documentation'
>>
>> it says everything is fine. When I deploy the module on my test box, it work
>> fine. When I pass my commit to Travis CI, it fail:
>>
>> https://travis-ci.org/thbe/puppet-bacula/builds/103322979
>>
>> Any Ideas?
>>
>> Regards Thomas
>> --
>> Linux ... enjoy the ride!

Hi,

puppet-lint is not actively maintained - the last commit is April 11th,
2015. If you install it from rubygems, the latest release is 1.1.0
though GitHub reads that there have been 58 commits to master since then.

In order to get the latest version, you need to install from git. Here's
the line to use in your Gemfile

  gem 'puppet-lint', :git => 'https://github.com/rodjek/puppet-lint.git'

If you are interested in extending your style with other community
puppet-lint plugins, here is what I use in my Gemfile's

  gem 'puppet-lint-absolute_classname-check'
  gem 'puppet-lint-alias-check'
  gem 'puppet-lint-empty_string-check'
  gem 'puppet-lint-file_ensure-check'
  gem 'puppet-lint-file_source_rights-check'
  gem 'puppet-lint-fileserver-check'
  gem 'puppet-lint-leading_zero-check'
  gem 'puppet-lint-spaceship_operator_without_tag-check'
  gem 'puppet-lint-trailing_comma-check'
  gem 'puppet-lint-undef_in_function-check'
  gem 'puppet-lint-unquoted_string-check'
  gem 'puppet-lint-variable_contains_upcase'

Best regards,
-g

-- 
Garrett Honeycutt
@learnpuppet
Puppet Training with LearnPuppet.com
Mobile: +1.206.414.8658

-- 
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/569FD76E.2040808%40garretthoneycutt.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] Re: Puppet Custom Provider. Class level and instance level methods/variable access issues

2016-01-20 Thread Dragu Emil
I am having the same problem, trying to use the value of a 'param' in 
self.instances method.
Did you find a way to do this?

-- 
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/ee568593-63e2-42ec-bcac-15aa80c109a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Puppet Users] odd puppet-lint config problems

2016-01-20 Thread Garrett Honeycutt
On 1/20/16 4:17 PM, Ramin K wrote:
> I'm doing some work around distributing a puppet-lint wrapper
> internally. Ideally I want a wrapper that reads a custom .puppet-lint.rc
> within the repo and the rc file is --only-checks so we can enable new
> checks as the codebase is ready to be stricter.
> 
> The problems I'm running into are
> 
> 1. .puppet-lint.rc seems to be additive loading ~/.puppet-lint.rc,
> ./.puppet-lint.rc AND --conf path/to/.puppet-lint.rc
> 
> 2. .puppet-lint.rc doesn't support --only-checks syntax
> 
> Has anyone done something similar and did you have to modify optparse.rb
> and other Ruby code with puppet-lint to get it to work?
> 
> Ramin
> 

Hi Ramin,

It sounds like you have a repo with a bunch of modules as opposed to one
repo per module. Recommend using a script that calls puppet-lint with
the arguments that you would like and integrating that into a pre-commit
check or a build pipeline.

I never use .puppt-lint.rc, instead you would normally have a
Rakefile[1] that would configure puppet-lint and run the tests with
`rake lint`.

See my last post under the subject 'Slightly Off-Topic: CI Test of
Puppet module fail' for how to configure it that way.

[1] - https://github.com/ghoneycutt/puppet-module-ssh/blob/master/Rakefile

Best regards,
-g

-- 
Garrett Honeycutt
@learnpuppet
Puppet Training with LearnPuppet.com
Mobile: +1.206.414.8658

-- 
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/569FFD3E.4040802%40garretthoneycutt.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] helloworld

2016-01-20 Thread Alex M
Hi, i have Puppet 3.7.2 on Debian 8.2 x64. I added host Windows Server 2012 
R2 into Puppet. Now i would like to do test manifest (Forder c:/test/ 
: present on WS)

#cat /etc/puppet/modules/helloword/manifests/init.pp
class helloworld {
file { 'c:/test/hello.txt':
content => "Hello World!",
}
}


# ll /etc/puppet/modules/helloword/manifests/init.pp
-rw-r--r-- 1 root root 81 Jan 20 17:12 /etc/puppet/modules/helloword/
manifests/init.pp


i run *puppet agent --test* on WS 2012 R2 and receive an error:

C:\>puppet agent --test
Info: Retrieving pluginfacts
Info: Retrieving plugin
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
Could not find class helloworld for test1.domain.company.com on node test1.
domain.company.com
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

how i can fix it?

if i disable this manifest:

C:\>puppet agent --test
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Caching catalog for test1.domain.company.com
Info: Applying configuration version '1453308350'
Notice: Finished catalog run in 0.08 seconds


Thank you!

-- 
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/0c0d7f90-08ba-45c8-94a3-06abdb8afb7e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Puppet Users] helloworld

2016-01-20 Thread Carthik Sharma
helloword versus helloworld (missing l) :)

On Wed, Jan 20, 2016 at 8:46 AM, Alex M 
wrote:

> Hi, i have Puppet 3.7.2 on Debian 8.2 x64. I added host Windows Server
> 2012 R2 into Puppet. Now i would like to do test manifest (Forder c:/test/
> : present on WS)
>
> #cat /etc/puppet/modules/helloword/manifests/init.pp
> class helloworld {
> file { 'c:/test/hello.txt':
> content => "Hello World!",
> }
> }
>
>
> # ll /etc/puppet/modules/helloword/manifests/init.pp
> -rw-r--r-- 1 root root 81 Jan 20 17:12 /etc/puppet/modules/helloword/
> manifests/init.pp
>
>
> 
> i run *puppet agent --test* on WS 2012 R2 and receive an error:
>
> C:\>puppet agent --test
> Info: Retrieving pluginfacts
> Info: Retrieving plugin
> Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
> Could not find class helloworld for test1.domain.company.com on node test1
> .domain.company.com
> Warning: Not using cache on failed catalog
> Error: Could not retrieve catalog; skipping run
>
> how i can fix it?
>
> if i disable this manifest:
>
> C:\>puppet agent --test
> Info: Retrieving pluginfacts
> Info: Retrieving plugin
> Info: Caching catalog for test1.domain.company.com
> Info: Applying configuration version '1453308350'
> Notice: Finished catalog run in 0.08 seconds
>
>
> Thank you!
>
> --
> 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/0c0d7f90-08ba-45c8-94a3-06abdb8afb7e%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/CAOzFSfHM%3DzgmBGoVywfe8qjr5x7wkxxdU2GX%3DoUkHywxzpXeFw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] odd puppet-lint config problems

2016-01-20 Thread Ramin K
I'm doing some work around distributing a puppet-lint wrapper 
internally. Ideally I want a wrapper that reads a custom .puppet-lint.rc 
within the repo and the rc file is --only-checks so we can enable new 
checks as the codebase is ready to be stricter.


The problems I'm running into are

1. .puppet-lint.rc seems to be additive loading ~/.puppet-lint.rc, 
./.puppet-lint.rc AND --conf path/to/.puppet-lint.rc


2. .puppet-lint.rc doesn't support --only-checks syntax

Has anyone done something similar and did you have to modify optparse.rb 
and other Ruby code with puppet-lint to get it to work?


Ramin

--
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/569FF95F.1010704%40badapple.net.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] puppet open source 3.8.2 - /etc/puppet/environments not following a symlink environment

2016-01-20 Thread live_d
Hi,

I'm using directory environments in puppet and its working well. I've been 
trying to setup a symlink under /etc/puppet/environments, to link to a 
directory in my home area so i can develop code away from the main puppet 
directory tree. When i create the symbolic link and run puppet on my node 
it fails. Information below.l I guess I;m missing something.

[root@puppet environments]# pwd
/etc/puppet/environments

[root@puppet environments]# ls -al
total 16
drwxr-xr-x. 4 root root 4096 Jan 15 19:02 .
drwxr-xr-x. 7 root root 4096 Dec 22 08:14 ..
-rw-r--r--. 1 root root0 Aug 27 23:06 develop
drwxr-xr-x. 4 root root 4096 Aug 27 23:06 development
lrwxrwxrwx. 1 root root   31 Jan 15 19:02 production -> 
/home/live/puppet/production/
drwxr-xr-x. 4 root root 4096 Aug 21 14:13 production_OLD

[root@puppet environments]# ls -al production
lrwxrwxrwx. 1 root root 31 Jan 15 19:02 production -> 
/home/live/puppet/production/
[root@puppet environments]# 

[root@puppet environments]# ls -al production/
total 20
drwxr-xr-x. 4 live live 4096 Jan 15 15:43 .
drwxrwxr-x. 4 live live 4096 Jan 15 15:37 ..
-rw-r--r--. 1 live live   83 Aug 21 14:13 environment.conf
drwxr-xr-x. 2 live live 4096 Nov 24 19:29 manifests
drwxr-xr-x. 4 live live 4096 Aug 21 14:13 modules

The error:

[root@Atlassian facts.d]# puppet agent -t --environment production
Info: Retrieving pluginfacts
Error: /File[/var/lib/puppet/facts.d]: Could not evaluate: Could not 
retrieve information from environment production source(s) 
puppet://puppet.mydomain.com/pluginfacts
Info: Retrieving plugin
Error: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve 
information from environment production source(s) 
puppet://puppet.mydomain.com/plugins
Notice: /File[/var/lib/puppet/lib/puppet]: Dependency 
File[/var/lib/puppet/lib] has failures: true
Warning: /File[/var/lib/puppet/lib/puppet]: Skipping because of failed 
dependencies
Notice: /File[/var/lib/puppet/lib/puppet/provider]: Dependency 
File[/var/lib/puppet/lib] has failures: true
Warning: /File[/var/lib/puppet/lib/puppet/provider]: Skipping because of 
failed dependencies
Notice: /File[/var/lib/puppet/lib/puppet/provider/file_line]: Dependency 
File[/var/lib/puppet/lib] has failures: true
Warning: /File[/var/lib/puppet/lib/puppet/provider/file_line]: Skipping 
because of failed dependencies
Notice: /File[/var/lib/puppet/lib/puppet/parser]: Dependency 
File[/var/lib/puppet/lib] has failures: true
Warning: /File[/var/lib/puppet/lib/puppet/parser]: Skipping because of 
failed dependencies
Notice: /File[/var/lib/puppet/lib/puppet/parser/functions]: Dependency 
File[/var/lib/puppet/lib] has failures: true
Warning: /File[/var/lib/puppet/lib/puppet/parser/functions]: Skipping 
because of failed dependencies
Notice: 
/File[/var/lib/puppet/lib/puppet/parser/functions/ensure_packages.rb]: 
Dependency File[/var/lib/puppet/lib] has failures: true
Warning: 
/File[/var/lib/puppet/lib/puppet/parser/functions/ensure_packages.rb]: 
Skipping because of failed dependencies
Notice: 
/File[/var/lib/puppet/lib/puppet/parser/functions/validate_hash.rb]: 
Dependency File[/var/lib/puppet/lib] has failures: true
Warning: 
/File[/var/lib/puppet/lib/puppet/parser/functions/validate_hash.rb]: 
Skipping because of failed dependencies
Notice: /File[/var/lib/puppet/lib/puppet/parser/functions/count.rb]: 
Dependency File[/var/lib/puppet/lib] has failures: true
Warning: /File[/var/lib/puppet/lib/puppet/parser/functions/count.rb]: 
Skipping because of failed dependencies
Notice: 
/File[/var/lib/puppet/lib/puppet/parser/functions/validate_bool.rb]: 
Dependency File[/var/lib/puppet/lib] has failures: true
Warning: 
/File[/var/lib/puppet/lib/puppet/parser/functions/validate_bool.rb]: 
Skipping because of failed dependencies
Notice: 
/File[/var/lib/puppet/lib/puppet/parser/functions/get_module_path.rb]: 
Dependency File[/var/lib/puppet/lib] has failures: true
Warning: 
/File[/var/lib/puppet/lib/puppet/parser/functions/get_module_path.rb]: 
Skipping because of failed dependencies
Notice: 
/File[/var/lib/puppet/lib/puppet/parser/functions/is_ip_address.rb]: 
Dependency File[/var/lib/puppet/lib] has failures: true
...

I hope someone can point me in the right direction.

Happy to provide more information.

Regards

Live

-- 
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/dd199e55-4b53-4d51-a96a-4f6873e6859c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.