Re: [Puppet Users] Re: Puppet Manifest Involving Multiple Nodes
Thanks a ton Felix.. On Mon, Sep 15, 2014 at 8:10 PM, Felix Frank felix.fr...@alumni.tu-berlin.de wrote: Hi, designs like this are rather difficult to achieve with Puppet. They rely on the paradigm of a scripting engine, with Puppet is not! Puppet works best once you attain a state of affairs which you can confidently apply to your agents. It would perhaps be easiest to do the preliminary steps outside of Puppet. 1. Deploy files to the test instance. 2. Validate, rollback on failure, bail out. 3. Push files to Puppet VCS. Puppet will can then handle the production deployment for you. HTH, Felix On 09/15/2014 04:13 PM, Rakesh Kathpal wrote: Any help ? On Fri, Sep 12, 2014 at 1:45 PM, Rakesh Kathpal rkath...@gmail.com mailto:rkath...@gmail.com wrote: Hi, I need to copy of set of files to 10 / 20 nodes but the process is as follows Copy all files on 1 agent Validate the files If successful only then copy files to other servers else revert changes on first node itself and stop I understand that I can do this for one node but am really confused as to how can control the behavior on multiple nodes. Thanks, RK. -- 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/5416FA70.8010609%40alumni.tu-berlin.de . 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/CAEJrXMWxEG3V7E-21oYTuqz6sEf11p62vXcDgWe4X-r8R7TKHg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Unmet dependencies: puppetmaster 3.7.0-1puppetlabs1
Hello all, I noticed this error today which is related to unmet dependencies for Puppet 3.7.0-1puppetlabs1 on Ubuntu Trusty. It's worth noting this was working perfectly as recently as a few days ago and today with no code changes there are dependency problems. I've actually noticed this in the past with 3.6.2 as well and upgraded to 3.7.0 to fix it, but this should not be happening when I'm specifying a explicit Puppet version because I don't want to always have to upgrade to keep things sane. Anybody else experiencing this problem? Or any ideas? Maybe I am doing something wrong. *Error: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install puppetmaster-passenger=3.7.0-1puppetlabs1' returned 100: Reading package lists...* *Building dependency tree...* *Reading state information...* *Some packages could not be installed. This may mean that you have* *requested an impossible situation or if you are using the unstable* *distribution that some required packages have not yet been created* *or been moved out of Incoming.* *The following information may help to resolve the situation:* *The following packages have unmet dependencies:* * puppetmaster-passenger : Depends: puppetmaster-common (= 3.7.0-1puppetlabs1) but it is not going to be installed* *E: Unable to correct problems, you have held broken packages.* *Wrapped exception:* *Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install puppetmaster-passenger=3.7.0-1puppetlabs1' returned 100: Reading package lists...* *Building dependency tree...* *Reading state information...* *Some packages could not be installed. This may mean that you have* *requested an impossible situation or if you are using the unstable* *distribution that some required packages have not yet been created* *or been moved out of Incoming.* *The following information may help to resolve the situation:* *The following packages have unmet dependencies:* * puppetmaster-passenger : Depends: puppetmaster-common (= 3.7.0-1puppetlabs1) but it is not going to be installed* *E: Unable to correct problems, you have held broken packages.* *Error: /Stage[main]/Puppetmaster::Install/Package[puppetmaster-passenger]/ensure: change from purged to 3.7.0-1puppetlabs1 failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install puppetmaster-passenger=3.7.0-1puppetlabs1' returned 100: Reading package lists...* *Building dependency tree...* *Reading state information...* *Some packages could not be installed. This may mean that you have* *requested an impossible situation or if you are using the unstable* *distribution that some required packages have not yet been created* *or been moved out of Incoming.* *The following information may help to resolve the situation:* *The following packages have unmet dependencies:* * puppetmaster-passenger : Depends: puppetmaster-common (= 3.7.0-1puppetlabs1) but it is not going to be installed* *E: Unable to correct problems, you have held broken packages.* *Error: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install puppetmaster=3.7.0-1puppetlabs1' returned 100: Reading package lists...* *Building dependency tree...* *Reading state information...* *Some packages could not be installed. This may mean that you have* *requested an impossible situation or if you are using the unstable* *distribution that some required packages have not yet been created* *or been moved out of Incoming.* *The following information may help to resolve the situation:* *The following packages have unmet dependencies:* * puppetmaster : Depends: puppetmaster-common (= 3.7.0-1puppetlabs1) but it is not going to be installed* *E: Unable to correct problems, you have held broken packages.* *Wrapped exception:* *Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install puppetmaster=3.7.0-1puppetlabs1' returned 100: Reading package lists...* *Building dependency tree...* *Reading state information...* *Some packages could not be installed. This may mean that you have* *requested an impossible situation or if you are using the unstable* *distribution that some required packages have not yet been created* *or been moved out of Incoming.* *The following information may help to resolve the situation:* *The following packages have unmet dependencies:* * puppetmaster : Depends: puppetmaster-common (= 3.7.0-1puppetlabs1) but it is not going to be installed* *E: Unable to correct problems, you have held broken packages.* *Error: /Stage[main]/Puppetmaster::Install/Package[puppetmaster]/ensure: change from purged to 3.7.0-1puppetlabs1 failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install puppetmaster=3.7.0-1puppetlabs1'
[Puppet Users] Re: Unmet dependencies: puppetmaster 3.7.0-1puppetlabs1
I think it's also worth noting that Puppet 3.7.1 was released today. See https://docs.puppetlabs.com/puppet/3.7/reference/release_notes.html#puppet-371. This doesn't seem like a coincidence. - Taylor On Tuesday, September 16, 2014 1:08:47 AM UTC-7, Taylor Leese wrote: Hello all, I noticed this error today which is related to unmet dependencies for Puppet 3.7.0-1puppetlabs1 on Ubuntu Trusty. It's worth noting this was working perfectly as recently as a few days ago and today with no code changes there are dependency problems. I've actually noticed this in the past with 3.6.2 as well and upgraded to 3.7.0 to fix it, but this should not be happening when I'm specifying a explicit Puppet version because I don't want to always have to upgrade to keep things sane. Anybody else experiencing this problem? Or any ideas? Maybe I am doing something wrong. *Error: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install puppetmaster-passenger=3.7.0-1puppetlabs1' returned 100: Reading package lists...* *Building dependency tree...* *Reading state information...* *Some packages could not be installed. This may mean that you have* *requested an impossible situation or if you are using the unstable* *distribution that some required packages have not yet been created* *or been moved out of Incoming.* *The following information may help to resolve the situation:* *The following packages have unmet dependencies:* * puppetmaster-passenger : Depends: puppetmaster-common (= 3.7.0-1puppetlabs1) but it is not going to be installed* *E: Unable to correct problems, you have held broken packages.* *Wrapped exception:* *Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install puppetmaster-passenger=3.7.0-1puppetlabs1' returned 100: Reading package lists...* *Building dependency tree...* *Reading state information...* *Some packages could not be installed. This may mean that you have* *requested an impossible situation or if you are using the unstable* *distribution that some required packages have not yet been created* *or been moved out of Incoming.* *The following information may help to resolve the situation:* *The following packages have unmet dependencies:* * puppetmaster-passenger : Depends: puppetmaster-common (= 3.7.0-1puppetlabs1) but it is not going to be installed* *E: Unable to correct problems, you have held broken packages.* *Error: /Stage[main]/Puppetmaster::Install/Package[puppetmaster-passenger]/ensure: change from purged to 3.7.0-1puppetlabs1 failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install puppetmaster-passenger=3.7.0-1puppetlabs1' returned 100: Reading package lists...* *Building dependency tree...* *Reading state information...* *Some packages could not be installed. This may mean that you have* *requested an impossible situation or if you are using the unstable* *distribution that some required packages have not yet been created* *or been moved out of Incoming.* *The following information may help to resolve the situation:* *The following packages have unmet dependencies:* * puppetmaster-passenger : Depends: puppetmaster-common (= 3.7.0-1puppetlabs1) but it is not going to be installed* *E: Unable to correct problems, you have held broken packages.* *Error: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install puppetmaster=3.7.0-1puppetlabs1' returned 100: Reading package lists...* *Building dependency tree...* *Reading state information...* *Some packages could not be installed. This may mean that you have* *requested an impossible situation or if you are using the unstable* *distribution that some required packages have not yet been created* *or been moved out of Incoming.* *The following information may help to resolve the situation:* *The following packages have unmet dependencies:* * puppetmaster : Depends: puppetmaster-common (= 3.7.0-1puppetlabs1) but it is not going to be installed* *E: Unable to correct problems, you have held broken packages.* *Wrapped exception:* *Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install puppetmaster=3.7.0-1puppetlabs1' returned 100: Reading package lists...* *Building dependency tree...* *Reading state information...* *Some packages could not be installed. This may mean that you have* *requested an impossible situation or if you are using the unstable* *distribution that some required packages have not yet been created* *or been moved out of Incoming.* *The following information may help to resolve the situation:* *The following packages have unmet dependencies:* * puppetmaster : Depends: puppetmaster-common (= 3.7.0-1puppetlabs1) but it is not
Re: [Puppet Users] Re: New Powershell Desired Configuration Module
yes it is. Auto-generated types and spec tests for the types. https://github.com/msutter/puppet-dsc/blob/master/README_BUILD.md The build is ok on osx, but I'm working on the build on Linux and still have some encoding issues. Cheers Le mardi 16 septembre 2014 01:12:23 UTC+2, Rob Reynolds a écrit : On Mon, Sep 15, 2014 at 1:48 PM, Rich Siegel rism...@gmail.com javascript: wrote: This is so AWESOME!! +1! On Monday, September 15, 2014 5:19:12 AM UTC-4, Marc Sutter wrote: Hi all, Just wanted to let you know that I wrote a module for DSC. This is a big help to configure Windows 2008+ boxes. https://forge.puppetlabs.com/msutter/dsc Marc, Whoa... is that autogenerated types and providers? Cheers Marc -- 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 javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/e94ca3fb-0268-4217-8d47-7d5273c7c004%40googlegroups.com https://groups.google.com/d/msgid/puppet-users/e94ca3fb-0268-4217-8d47-7d5273c7c004%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Rob Reynolds Developer, Puppet Labs *Join us at PuppetConf 2014 http://www.puppetconf.com/, September 20-24 in San Francisco* -- 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/4a25e9c1-b742-4cb1-8309-ae0727ade9cd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Trouble with Facter
Overnight my Facter seems to reporting new errors. As far as I can see, neither Puppet, Facter, MCollective or the facts in question were updated, so I'm struggling to find a cause. The problem as exacerbated because MCollective is emailing me with the same error every 15 minutes. This error is printed when I run facter: Error loading fact /var/lib/puppet/lib/facter/warranty.rb: no such file to load -- facter/util/warranty The fact is provided by this module (my module, but not my code) https://forge.puppetlabs.com/jgazeley/dell The file /var/lib/puppet/lib/facter/warranty.rb does exist on my system and is readable as is the referenced submodule in /var/lib/puppet/lib/facter/util/warranty.rb , so I am not sure what is causing the problem. I'm using Puppet 3.7.1, Facter 2.2.0, MCollective 2.6.0 and jgazeley/dell 0.1.2. Any advice to sort this out? Thanks, Jonathan -- 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/54180673.5030003%40bristol.ac.uk. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] puppetlabs-apache n00b question - docroot value for fully proxied virtual host?
Unfortunately you can't. This is a restriction of Apache, which requires a docroot value for every vhost, and not of Puppet. -- 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/8c6a00ee-3cb6-4193-936a-6acc771142ba%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Announce: Puppet 3.7.1 Released!
Hello, when can I expect .deb to be available? W dniu wtorek, 16 września 2014 01:11:32 UTC+2 użytkownik Andy Parker napisał: Puppet 3.7.1 is a backward-compatible bugfix release in the Puppet 3 series. This release fixes several regressions and other issues. * PUP-3222: Windows service provider references a non-existent class * PUP-3190: each no longer supported in Puppet 3.7.0 * PUP-3191: Symlinks to missing targets cause a File Not Found error instead of a warning * PUP-3177: Resource titles ending with square brackets fail * Several fixes for directory environments Read the release notes here: https://docs.puppetlabs.com/puppet/3.7/reference/release_notes.html Installation instructions are here: https://docs.puppetlabs.com/guides/install_puppet/pre_install.html To track issues related to this release, you can follow the following JIRA queries: * List of all bugs fixed in 3.7.1: https://tickets.puppetlabs.com/secure/ReleaseNote.jspa?projectId=10102version=11854 * New issues introduced in 3.7.1: https://tickets.puppetlabs.com/issues/?filter=12673 If there are bugs that you're tracking, remember we now have nightly repositories available with packaged builds for our most-used operating systems. To use them, follow the install guide here: https://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#using-the-nightly-repos -- Andrew Parker a...@puppetlabs.com javascript: Freenode: zaphod42 Twitter: @aparker42 Software Developer *Join us at **PuppetConf 2014, **September 20-24 in San Francisco - * www.puppetconf.com -- 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/1c6b7331-ac0d-4083-a9dd-a2379a7f4053%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] hiera - default parameter values and design questions
On Monday, September 15, 2014 10:19:35 AM UTC-5, Mike Reed wrote:
@Xav, thanks for the information and pointers. I've added the 'default'
value into my arrays and things are running smoothly now. I'm still a bit
hazy on the resource ordering and how hiera by default, deals with applying
resources within (for example) a hiera.yaml file but for now, I have enough
into to get on with.
Hiera has no (direct) role in applying resources. It is strictly a data
service.
I think you may mean you're hazy about how Hiera handles interpolation of
Puppet variables (%{variable_name}). You are welcome to ask about that
here, but you probably should also consult the documentation
https://docs.puppetlabs.com/hiera/1/, and in particular the docs on
interpolation tokens
https://docs.puppetlabs.com/hiera/1/variables.html#interpolation-tokens,
to help fill in the picture.
Among the things it is important to understand is that each invocation of
Hiera, whether explicitly via one of the DSL functions or implicitly for
class parameter binding, is independent as far as Hiera itself is
concerned. That's part of why you can use Hiera to initialize variables
that Hiera will interpolate on subsequent invocations.
John
--
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/1b092b91-952e-413a-b63c-5f50bf936563%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Trouble with Facter
On Tuesday, September 16, 2014 4:44:32 AM UTC-5, Jonathan Gazeley wrote: Overnight my Facter seems to reporting new errors. As far as I can see, neither Puppet, Facter, MCollective or the facts in question were updated, so I'm struggling to find a cause. The problem as exacerbated because MCollective is emailing me with the same error every 15 minutes. This error is printed when I run facter: Error loading fact /var/lib/puppet/lib/facter/warranty.rb: no such file to load -- facter/util/warranty The fact is provided by this module (my module, but not my code) https://forge.puppetlabs.com/jgazeley/dell The file /var/lib/puppet/lib/facter/warranty.rb does exist on my system and is readable as is the referenced submodule in /var/lib/puppet/lib/facter/util/warranty.rb , so I am not sure what is causing the problem. My first guess would be a load path problem. If you're willing to limit your module to Ruby 1.9+, then you could try replacing the offending 'require' call with require_relative 'util/warranty' Even if you don't want that Ruby version constraint, it might be illuminating to see whether 'require_relative' in fact does solve the problem. For testing only, you could also consider printing the $LOAD_PATH just before executing the 'require'. And speaking of Ruby version, are you certain *that* didn't change on you? Clearly something did. John -- 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/69d6a1ec-29fd-4998-8f40-e96378798187%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Trouble with Facter
On Tuesday, September 16, 2014 4:44:32 AM UTC-5, Jonathan Gazeley wrote: Overnight my Facter seems to reporting new errors. As far as I can see, neither Puppet, Facter, MCollective or the facts in question were updated, so I'm struggling to find a cause. The problem as exacerbated because MCollective is emailing me with the same error every 15 minutes. This error is printed when I run facter: Error loading fact /var/lib/puppet/lib/facter/warranty.rb: no such file to load -- facter/util/warranty The fact is provided by this module (my module, but not my code) https://forge.puppetlabs.com/jgazeley/dell The file /var/lib/puppet/lib/facter/warranty.rb does exist on my system and is readable as is the referenced submodule in /var/lib/puppet/lib/facter/util/warranty.rb , so I am not sure what is causing the problem. Alternatively, you may want to check more thoroughly whether /var/lib/puppet/lib/facter/util/warranty.rb is in fact readable *to Puppet* in the relevant context. In addition to the ordinary permission bits, it is possible that POSIX ACLs or mandatory access controls (i.e. SELinux) might prevent access to the file from the Puppet agent. For SELinux, it could be that even though the relevant user (probably root) can read the file under other circumstances, the agent still cannot. And switching SELinux from permissive to enforcing mode is something that can be done quickly and easily without rebooting, perhaps even automatically, and not necessarily with full comprehension of its effects. John -- 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/8798dd99-2a32-4ce5-9b7f-cbc486322fd1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Trouble with Facter
On 16/09/14 14:30, jcbollinger wrote: On Tuesday, September 16, 2014 4:44:32 AM UTC-5, Jonathan Gazeley wrote: Overnight my Facter seems to reporting new errors. As far as I can see, neither Puppet, Facter, MCollective or the facts in question were updated, so I'm struggling to find a cause. The problem as exacerbated because MCollective is emailing me with the same error every 15 minutes. This error is printed when I run facter: Error loading fact /var/lib/puppet/lib/facter/warranty.rb: no such file to load -- facter/util/warranty The fact is provided by this module (my module, but not my code) https://forge.puppetlabs.com/jgazeley/dell https://forge.puppetlabs.com/jgazeley/dell The file /var/lib/puppet/lib/facter/warranty.rb does exist on my system and is readable as is the referenced submodule in /var/lib/puppet/lib/facter/util/warranty.rb , so I am not sure what is causing the problem. My first guess would be a load path problem. If you're willing to limit your module to Ruby 1.9+, then you could try replacing the offending 'require' call with require_relative 'util/warranty' Even if you don't want that Ruby version constraint, it might be illuminating to see whether 'require_relative' in fact does solve the problem. For testing only, you could also consider printing the $LOAD_PATH just before executing the 'require'. And speaking of Ruby version, are you certain /that/ didn't change on you? Clearly something did. John Thanks for your detailed response. We're running Ruby 1.8.7, the standard packaged with CentOS 6. We're unwilling/unable to switch to a newer Ruby from another source, especially as we're a university and the freshers are arriving this weekend! The penalty for breaking IT systems in the run-up to the start of term isn't worth thinking about ;) Permissions on the files in question and their parent directories shows that the files should be world-readable. We're not using POSIX ACLs. We are experienced users of SELinux and I can also confirm that the audit log shows nothing of relevance. Running in Permissive mode doesn't help. The facts that my module installs have the same SELinux contexts as other facts. I checked over the yum.log and nothing was updated at the time that these symptoms started happening on 3 servers at the same time. Nothing was changed in the puppet.log, and nobody updated any Forge modules etc. The 3 servers are all Dell of the same hardware generation. Other Dell servers in our estate were not affected. Attempting to use require_relative with Ruby 1.8.7 yields undefined method `require_relative' for main:Object Printing the $LOAD_PATH does not list /var/lib/puppet/lib/facter/ when executing facter or facter -p as my user. It does not print any paths when I execute facter as root. I don't really know my way around Facter and Ruby so I'm sort of shooting in the dark here trying to understand how it *should* work, and then working out why mine is different. Thanks, Jonathan -- 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/541843C8.7070503%40bristol.ac.uk. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] CA certificate and private key
Hello, I see that puppet generates a CA certificate for each machine in /var/lib/puppet/ssl/certs/ca.pem. Where is the private key for this certificate kept? Thank you, Cristian Falcas -- 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/CAMo7R_cbpKXmi3iBTS5UZ5-ZDXZvJ8oq6GcDx7rtKb9Dfkrjmw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Announce: Puppet 3.7.1 Released!
On Tue, Sep 16, 2014 at 4:22 AM, p.krysztof...@pixel.com.pl wrote: Hello, when can I expect .deb to be available? Hello! You can find packages for Debian and Ubuntu platforms at http://apt.puppetlabs.com/ For more information about how to use these repos, check out the documentation at https://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-debian-and-ubuntu W dniu wtorek, 16 września 2014 01:11:32 UTC+2 użytkownik Andy Parker napisał: Puppet 3.7.1 is a backward-compatible bugfix release in the Puppet 3 series. This release fixes several regressions and other issues. * PUP-3222: Windows service provider references a non-existent class * PUP-3190: each no longer supported in Puppet 3.7.0 * PUP-3191: Symlinks to missing targets cause a File Not Found error instead of a warning * PUP-3177: Resource titles ending with square brackets fail * Several fixes for directory environments Read the release notes here: https://docs.puppetlabs.com/ puppet/3.7/reference/release_notes.html Installation instructions are here: https://docs.puppetlabs.com/ guides/install_puppet/pre_install.html To track issues related to this release, you can follow the following JIRA queries: * List of all bugs fixed in 3.7.1: https://tickets.puppetlabs. com/secure/ReleaseNote.jspa?projectId=10102version=11854 * New issues introduced in 3.7.1: https://tickets.puppetlabs. com/issues/?filter=12673 If there are bugs that you're tracking, remember we now have nightly repositories available with packaged builds for our most-used operating systems. To use them, follow the install guide here: https://docs.puppetlabs.com/guides/puppetlabs_package_ repositories.html#using-the-nightly-repos -- Andrew Parker a...@puppetlabs.com Freenode: zaphod42 Twitter: @aparker42 Software Developer *Join us at **PuppetConf 2014, **September 20-24 in San Francisco - * www.puppetconf.com -- 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/1c6b7331-ac0d-4083-a9dd-a2379a7f4053%40googlegroups.com https://groups.google.com/d/msgid/puppet-users/1c6b7331-ac0d-4083-a9dd-a2379a7f4053%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Melissa Stone Release Engineer, Puppet Labs *Join us at **PuppetConf 2014, **September 20-24 in San Francisco - * www.puppetconf.com -- 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/CAHEe_kq7hvUhYRXaXdfOMAii%2BcroiodRC-1WB-L9KH2B438Qeg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] [Error after after upgrading to 3.7] Evaluation Error: Illegal Resource Type expression, expected result to be a type name, or untitled Resource, got Type[Class]
Hi guys,
From your comments I see that there are 2 issues here the parser and
the anchor. For clarity shake I have deleted the anchor resources and
Class defaults as I don't fully understand the purpose of if they have
meaning on my environment, even after reading the link you provided.
After this all the manifest seem to behave as before.
My puppet.conf working configuration with 3.6 was like this:
[...]
parser = future
evaluator = current
[...]
I needed the parser and the evaluator set like this to get some piece
of code from the [1] terrarum blog to work:
$trusted_networks = hiera_array('trusted_networks')
$trusted_networks.each |$network| {
firewall { 003 allow all traffic from ${network}:
proto = 'all',
source = $network,
action = 'accept',
}
}
On the other side I have comment out the parser and evaluator lines
because they are giving problems with other modules too:
Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: This Type-Name is not productive. A non productive construct
may only be placed last in a block/sequence at
/etc/puppet/environments/production/modules/postgresql/manifests/server/database.pp:73:3
on node server.example.com
So as far as I know my systems is as it was with 3.6 but the
trusted_networks are not being applied as they need the parser =
future.
Thank your for your time
Best regards
[1] http://terrarum.net/blog/puppet-infrastructure.html
--
Juan Sierra Pons j...@elsotanillo.net
Linux User Registered: #257202
Web: http://www.elsotanillo.net Git: http://www.github.com/juasiepo
GPG key = 0xA110F4FE
Key Fingerprint = DF53 7415 0936 244E 9B00 6E66 E934 3406 A110 F4FE
--
2014-09-15 17:32 GMT+02:00 jcbollinger john.bollin...@stjude.org:
On Monday, September 15, 2014 9:23:08 AM UTC-5, Henrik Lindberg wrote:
On 2014-12-09 14:57, Juan Sierra Pons wrote:
Hi,
I am using a mix of the following two blog post:
[1] A modern Puppet Master from scratch
[2] Puppet Infrastructure
After upgrading to 3.7 I am getting the following error message
Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: Evaluation Error: Illegal Resource Type expression, expected
result to be a type name, or untitled Resource, got Type[Class] at
/etc/puppet/environments/production/site/profiles/manifests/base.pp:5:3
on node server3.example.com
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
With 3.6 it worked like a charm.
In the sense that catalogs were compiled without error, perhaps. The
example does not perform proper containment, however: to do containment with
Anchor resources you need two per containing class, one to serve as a lower
bound and another to serve as an upper bound (see Henrik's link). The
example code and the terrarun tutorial on which it is based miss the latter,
leaving no containment whatever. You could just delete the anchor resources
and Class defaults without meaningfully changing the semantics of the
manifests.
Furthermore, using resource defaults for this purpose is tricky and prone to
failure because the default is ignored for any class that is declared with
its own specific require parameter.
From the error message, I think you are using the future parser.
Did you use the future parser on 3.6 as well?
The base.pp is like this:
class profiles::base {
anchor { 'profiles::base': }
Class { require = Anchor['profiles::base'] }
users { users: }
}
It looks like your intention is to set the default for every class in
the entire system to have a require of Anchor['profiles::base']. Is that
true, or are you trying to achieve something else?
Remember that resource defaults are dynamically scoped. The code is trying
to make every class declared by the given profile class have have the Anchor
as a require. The model on which it is based proposes that several of these
classes might be declared, all chained together. I think the idea is that
they could thereby get away with only one anchor apiece, but that doesn't
work. For example, Puppet could choose to apply all the (non-class)
resources declared directly by the profile classes first, including the
anchors, and then all the other classes in any order.
Read more about containment here:
https://docs.puppetlabs.com/puppet/latest/reference/lang_containment.html
+1
I observe also that Puppet has suffered for years from confusion among
users, among developers, in documentation, and even in code about whether
(or in what sense) classes are resources. Starting with the introduction of
parameterized classes, there was a push -- largely originating at PL, I
think -- to cast the class as just another resource
[Puppet Users] Sid and Unstable leaving apt.puppetlabs.com
Debian Unstable (also know by its codename Sid) is going to be removed from apt.puppetlabs.com on October 15th, 2014. This decision is because of the number of build failures we are seeing for this distribution due to the instability of the platform. Users should note that we will continue to build and ship packages for Debian Testing. -- Melissa Stone Release Engineer, Puppet Labs *Join us at **PuppetConf 2014, **September 20-24 in San Francisco - * www.puppetconf.com -- 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/CAHEe_krYMrfXXTcWVnLWDOv_fdVBV5E-vBnVV%2B38M9XaMpSCNQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Trouble with Facter
I had a problem similar to this when an error was introduced to my puppet master's served code base. To troubleshoot I did the following: 1) Restart the puppetmaster process (passenger, whatever you're using) 2) Remove everything under /var/lib/puppet/lib/facter/* on the clients that are having the issue. 3) Re-run the puppet agent on the affected node One of two things should happen, either your facts will be re-sync'd and everything will be fine or an error will be thrown noting that you have an error somewhere else. If this *doesn't* happen, check the server logs and see if there's something more insidious happening. Good luck, Trevor On Tue, Sep 16, 2014 at 5:44 AM, Jonathan Gazeley jonathan.gaze...@bristol.ac.uk wrote: Overnight my Facter seems to reporting new errors. As far as I can see, neither Puppet, Facter, MCollective or the facts in question were updated, so I'm struggling to find a cause. The problem as exacerbated because MCollective is emailing me with the same error every 15 minutes. This error is printed when I run facter: Error loading fact /var/lib/puppet/lib/facter/warranty.rb: no such file to load -- facter/util/warranty The fact is provided by this module (my module, but not my code) https://forge.puppetlabs.com/jgazeley/dell The file /var/lib/puppet/lib/facter/warranty.rb does exist on my system and is readable as is the referenced submodule in /var/lib/puppet/lib/facter/util/warranty.rb , so I am not sure what is causing the problem. I'm using Puppet 3.7.1, Facter 2.2.0, MCollective 2.6.0 and jgazeley/dell 0.1.2. Any advice to sort this out? Thanks, Jonathan -- 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/54180673.5030003%40bristol.ac.uk. For more options, visit https://groups.google.com/d/optout. -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 tvaug...@onyxpoint.com -- This account not approved for unencrypted proprietary information -- -- 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/CANs%2BFoX5iK9c-1L_SuOOmHCdQzbwYSkcb987QGDJq8%2BiMvRQ-w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Trouble with Facter
On 16/09/14 20:00, Trevor Vaughan wrote: I had a problem similar to this when an error was introduced to my puppet master's served code base. To troubleshoot I did the following: 1) Restart the puppetmaster process (passenger, whatever you're using) 2) Remove everything under /var/lib/puppet/lib/facter/* on the clients that are having the issue. 3) Re-run the puppet agent on the affected node One of two things should happen, either your facts will be re-sync'd and everything will be fine or an error will be thrown noting that you have an error somewhere else. If this *doesn't* happen, check the server logs and see if there's something more insidious happening. Good luck, Trevor Thanks for your advice. I'll try this when I'm back at work in the morning. For now, allow me to leave you with this video, which seems to summarise your advice ;) https://www.youtube.com/watch?v=kb2gzteVNa4 Cheers, Jonathan -- 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/541896E8.3090003%40bristol.ac.uk. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Trouble with Facter
*slow clap* Well played sir, well played. Trevor On Tue, Sep 16, 2014 at 4:00 PM, Jonathan Gazeley jonathan.gaze...@bristol.ac.uk wrote: On 16/09/14 20:00, Trevor Vaughan wrote: I had a problem similar to this when an error was introduced to my puppet master's served code base. To troubleshoot I did the following: 1) Restart the puppetmaster process (passenger, whatever you're using) 2) Remove everything under /var/lib/puppet/lib/facter/* on the clients that are having the issue. 3) Re-run the puppet agent on the affected node One of two things should happen, either your facts will be re-sync'd and everything will be fine or an error will be thrown noting that you have an error somewhere else. If this *doesn't* happen, check the server logs and see if there's something more insidious happening. Good luck, Trevor Thanks for your advice. I'll try this when I'm back at work in the morning. For now, allow me to leave you with this video, which seems to summarise your advice ;) https://www.youtube.com/watch?v=kb2gzteVNa4 Cheers, Jonathan -- 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/541896E8.3090003%40bristol.ac.uk. For more options, visit https://groups.google.com/d/optout. -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 tvaug...@onyxpoint.com -- This account not approved for unencrypted proprietary information -- -- 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/CANs%2BFoV_A5jYHN0hBuVwNZkN2x_rqDLbVBk3bxyOvgK5V%3DxyCg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] About the params pattern
Hi,
About the params pattern, I had read this article :
http://garylarizza.com/blog/2014/02/17/puppet-workflow-part-1/
Suppose I want to use the params pattern in my modulees (ok there
really is no *better* way but imagine I want to use this way). In
the article, the author explains that, for the top level class of
my module, I can use this way :
class my_module (
$var1 = $my_module::params::var1,
$var2 = $my_module::params::var2,
$var3 = $my_module::params::var3,
...
) inherits my_module::params {
# The body of the class
}
Ok, I understand that. But what about an internal class of my module?
If I want to define an internal class (my_module/internal.pp) which
will be declared in the my_module class, what is the best way?
In the internal class, I want probably to use some parameters of
the my_module class and some variables of the my_module::params
class. How can I do that? Like below? I have doubts because in this
cas I have lot of inheritance and I understand that it was not a
good thing.
# Definition of the my_module::internal class
# I need to the value of $var2 and $var3 of he top level class my_module
# and I need to parameters in my_module::params.
class my_module::internal (
$var2,
$var3,
) inherits my_module::params {
# The body of the class
}
# Declaration of my_module::internal class in the my_module class
class my_module (
$var1 = $my_module::params::var1,
$var2 = $my_module::params::var2,
$var3 = $my_module::params::var3,
...
) inherits my_module::params {
# The body of the class
class my_module::internal {
var2 = $var2,
var3 = $var3,
}
}
Thanks in advance for your help.
François Lafont
--
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/5418CF25.8070101%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] About the params pattern
As far as I know inner classes are an anti pattern(for the lack of a
better term)
Each class should live in its own file.
More than one class per file is discouraged
On Sep 16, 2014 7:00 PM, Francois Lafont francois.lafont.1...@gmail.com
wrote:
Hi,
About the params pattern, I had read this article :
http://garylarizza.com/blog/2014/02/17/puppet-workflow-part-1/
Suppose I want to use the params pattern in my modulees (ok there
really is no *better* way but imagine I want to use this way). In
the article, the author explains that, for the top level class of
my module, I can use this way :
class my_module (
$var1 = $my_module::params::var1,
$var2 = $my_module::params::var2,
$var3 = $my_module::params::var3,
...
) inherits my_module::params {
# The body of the class
}
Ok, I understand that. But what about an internal class of my module?
If I want to define an internal class (my_module/internal.pp) which
will be declared in the my_module class, what is the best way?
In the internal class, I want probably to use some parameters of
the my_module class and some variables of the my_module::params
class. How can I do that? Like below? I have doubts because in this
cas I have lot of inheritance and I understand that it was not a
good thing.
# Definition of the my_module::internal class
# I need to the value of $var2 and $var3 of he top level class
my_module
# and I need to parameters in my_module::params.
class my_module::internal (
$var2,
$var3,
) inherits my_module::params {
# The body of the class
}
# Declaration of my_module::internal class in the my_module class
class my_module (
$var1 = $my_module::params::var1,
$var2 = $my_module::params::var2,
$var3 = $my_module::params::var3,
...
) inherits my_module::params {
# The body of the class
class my_module::internal {
var2 = $var2,
var3 = $var3,
}
}
Thanks in advance for your help.
François Lafont
--
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/5418CF25.8070101%40gmail.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/CAApMPgy-7Ab%2Bsw5DZwNc3PQh2xtn%2BxiCC%3DEs5PB-XOpT06pY2g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
