Jira (PUP-2940) Installing and using puppet with Centos7
Title: Message Title Eric Shamow commented on an issue Re: Installing and using puppet with Centos7 Seeing the same today with CentOS 7, 64-bit. RPM version 3.7.1-1. No gem updates. Puppet appears to work for a single run for meI get one puppet agent run and then the same json/pure error garrett honeycutt reported. -Eric Add Comment Puppet / PUP-2940 Installing and using puppet with Centos7 Hi, Has anyone successfully installed and used puppet on Centos7/RHEL7. I have added the EL7 Puppet labs repo and installed the RPM and its installing ruby from the CentOS base repo which is version 2.0, added the below dependancies that have been installed. However when trying to run commands I am getting the below. I had to install RVM with 1.9... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To
Jira (PUP-3248) Update PMT tests for directory environment support
Title: Message Title Joshua Partlow commented on an issue Re: Update PMT tests for directory environment support But I've hit some conflicts merging down to pe-puppet 3.4.x. I'm away this weekend, will need to look into it Monday morning. Add Comment Puppet / PUP-3248 Update PMT tests for directory environment support Most of the PMT acceptance tests use the `host['distmoduledir']` variable which is not meaningful if the install is using directory environments. The acceptance suite needs to be updated to introspect the module path rather than use `host['distmoduledir']`. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3321) config set adds a preceding newline to value if previous value was empty
Title: Message Title John Duarte created an issue Puppet / PUP-3321 config set adds a preceding newline to value if previous value was empty Issue Type: Bug Affects Versions: 3.7.1 Assignee: Unassigned Created: 19/Sep/14 4:32 PM Priority: Normal Reporter: John Duarte Using `puppet config set` to set a value if the value was previously present, puts the value on a separate line and makes the config file unparsable. Steps to reproduce 1. Either add a config entry by hand or with config set with no value 2. Use `puppet config set` to set the entry with a value Result: The value is placed on a separate line. Example session showing the error: [root@centos6-64-ma environmentpath.6nQgZ4]# cat my.conf [main] foo = bar bar = baz [root@centos6-64-ma environmentpath.6nQgZ4]# puppet config set foo '' --section main --config my.conf [root@centos6-64-ma environmentpath.6nQgZ4]# cat my.conf [main] foo = bar = baz [root@centos6-64-ma environmentpath.6nQgZ4]# puppet config set foo 'bar' --section main --config my.conf [root@centos6-64-ma environmentpath.6nQgZ4]# cat my.conf [main] foo = bar bar = baz [root@centos6-64-ma environmentpath.6nQgZ4]# puppet config set foo 'foo' --section main --config my.conf Error: Could not parse /tmp/environmentpath.6nQgZ4/my.conf: Could not match line bar at /tmp/environmentpath.6nQgZ4/my.conf:3
Jira (PUP-3248) Update PMT tests for directory environment support
Title: Message Title Joshua Partlow commented on an issue Re: Update PMT tests for directory environment support Merged to stable in 9e5b0f4 Add Comment Puppet / PUP-3248 Update PMT tests for directory environment support Most of the PMT acceptance tests use the `host['distmoduledir']` variable which is not meaningful if the install is using directory environments. The acceptance suite needs to be updated to introspect the module path rather than use `host['distmoduledir']`. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3248) Update PMT tests for directory environment support
Title: Message Title John Duarte commented on an issue Re: Update PMT tests for directory environment support Joshua Partlow PR 3099 has been closed. These changes need to be merged into stable. A new PR against stable has been created at PR 3109 Add Comment Puppet / PUP-3248 Update PMT tests for directory environment support Most of the PMT acceptance tests use the `host['distmoduledir']` variable which is not meaningful if the install is using directory environments. The acceptance suite needs to be updated to introspect the module path rather than use `host['distmoduledir']`. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3226) Non-existent directory environments should raise a helpful error
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3226 Non-existent directory environments should raise a helpful error Change By: Andy Parker Assignee: Andy Parker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3239) Add a validate method to Puppet::Node::Environment so the Compiler can easily halt for environments with bad configuration.
Title: Message Title Andy Parker assigned an issue to Unassigned Puppet / PUP-3239 Add a validate method to Puppet::Node::Environment so the Compiler can easily halt for environments with bad configuration. Change By: Andy Parker Assignee: Andy Parker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3320) Could not find declared class
Title: Message Title Paul Gibson commented on an issue Re: Could not find declared class Copying Ben Ford as per IRC. Also set environment_timeout = 0 in master config and no change in behaviour. Add Comment Puppet / PUP-3320 Could not find declared class When running puppet agent -t from agents (or from master it self) getting consistent but intermittent errors that the defined class can not be found. The class name varies, and is not consistent. Using PE, this issue is resolvable on an adhoc basis by simply navigating to the "Classes" page on the PE console and then running puppet agent -t again. Th... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3320) Could not find declared class
Title: Message Title Paul Gibson created an issue Puppet / PUP-3320 Could not find declared class Issue Type: Bug Affects Versions: 3.6.2 Assignee: Unassigned Components: PE Created: 19/Sep/14 12:44 PM Environment: RHEL6.5/7 AWS/EC2 Fix Versions: 3.3.0 Labels: support Priority: Normal Reporter: Paul Gibson When running puppet agent -t from agents (or from master it self) getting consistent but intermittent errors that the defined class can not be found. The cla
Jira (PUP-2940) Installing and using puppet with Centos7
Title: Message Title garrett honeycutt commented on an issue Re: Installing and using puppet with Centos7 Attempting to install Puppet on RHEL7 Workstation. Facter works, though Puppet does not. subscription-manager repos --enable rhel-7-workstation-optional-rpms yum install puppet == Package Arch VersionRepository Size == Installing: puppetnoarch3.7.1-1.el7puppetlabs-products 1.5 M Installing for dependencies: facterx86_641:2.2.0-1.el7 puppetlabs-products 95 k hiera noarch1.3.4-1.el7puppetlabs-products 23 k libselinux-ruby x86_642.2.2-6.el7rhel-7-workstation-optional-rpms127 k ruby x86_642.0.0.353-20.el7 rhel-7-workstation-rpms 66 k ruby-augeas x86_640.4.1-3.el7puppetlabs-deps 22 k ruby-irb noarch2.0.0.353-20.el7 rhel-7-workstation-rpms 87 k ruby-libs x86_642.0.0.353-20.el7 rhel-7-workstation-rpms 2.8 M ruby-shadow x86_641:2.2.0-2.el7 puppetlabs-deps 14 k rubygem-bigdecimalx86_641.2.0-20.el7 rhel-7-workstation-rpms 78 k rubygem-io-consolex86_640.4.2-20.el7 rhel-7-workstation-rpms 49 k rubygem-json x86_641.7.7-20.el7 rhel-7-workstation-rpms 74 k rubygem-psych x86_642.0.0-20.el7 rhel-7-workstation-rpms 76 k rubygem-rdoc noarch4.0.0-20.el7 rhel-7-workstation-rpms 317 k rubygems noarch2.0.14-20.el7
Jira (PUP-2940) Installing and using puppet with Centos7
Title: Message Title garrett honeycutt updated an issue Puppet / PUP-2940 Installing and using puppet with Centos7 Change By: garrett honeycutt Affects Version/s: 3.7.1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3319) client should retry if connection to master fails
Title: Message Title redmine.exporter created an issue Puppet / PUP-3319 client should retry if connection to master fails Issue Type: New Feature Assignee: Unassigned Created: 19/Sep/14 12:20 PM Labels: redmine Priority: Normal Reporter: redmine.exporter It would be nice if the client retried several times over say a 30-second period when it can't connect to the master. Use case 1: Restart the puppetmaster while a client is busy processing a catalog. At present, the client will fail to fetch any files with puppet:/// source URLs, leading to many error messages on the client. Use case 2: Run puppetmasterd and a puppetd client on the same host. Have a manifest with "notify => Service[puppetmasterd]" after upgrading the package that contains puppet itself, or upgrading ruby, or some other dependency. The client will upgrade the puppet package, and restart puppetmasterd. Then the client will try to send a report to the master, and fail, like this: notice: Package[puppet]/ensure: ensure changed '0.25.5,REV=2010.06.17.13.13' to '0.25.5,REV=2010.08.03.09.06' info: Package[puppet]: Scheduling refresh of Service[puppetmasterd] notice: Service[puppetmasterd]: Triggering 'refresh' from 1 dependencies err: Reporting failed: Connection refused - connect(2) notice: Finished catalog run in 202.94 seconds
Jira (PUP-3092) Json lib issue when installing Puppet on RHEL 7
Title: Message Title garrett honeycutt updated an issue Puppet / PUP-3092 Json lib issue when installing Puppet on RHEL 7 Change By: garrett honeycutt Environment: AWS , RHEL 7 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3092) Json lib issue when installing Puppet on RHEL 7
Title: Message Title garrett honeycutt updated an issue Puppet / PUP-3092 Json lib issue when installing Puppet on RHEL 7 Change By: garrett honeycutt Affects Version/s: 3.7.1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3318) Puppet prints warning when "environment" is set using classifier rather than local puppet.conf
Title: Message Title
Marc Seeger updated an issue
Puppet / PUP-3318
Puppet prints warning when "environment" is set using classifier rather than local puppet.conf
Change By:
Marc Seeger
We set the environment in the external node classifier and don't have one set locally.Puppet seems to default to the 'production' environment in case you don't have one set and it turns into:{noformat}Warning: Local environment: "production" doesn't match server specified node environment "devel", switching agent to "devel".{noformat}"devel" is the environment currently set for this node.We didn't specify "production" anywhere manually.I think that when a user DOESN'T specify any environment in the puppet.conf file but sets it in the classifier, this warning seems superfluous. This is the local puppet.conf:{noformat}[main]logdir=/var/log/puppetvardir=/var/lib/puppetssldir=/var/lib/puppet/sslrundir=/var/run/puppet# This is required for Ruby 2.1.1, due to a bug in Puppet. In reality, we# always compressed the response data with mod_deflate for certain file types.# Now, Ruby will add it's own Accept-Encoding header, and decode the response# for you. Unfortunately, Puppet will also try to decode that response.# See: https://tickets.puppetlabs.com/browse/PUP-1680http_compression = true[agent] server = master.e.some.thing.com certname = srv-13.some.thing.com{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email
Jira (PUP-3318) Puppet prints warning when "environment" is set using classifier rather than local puppet.conf
Title: Message Title
Marc Seeger updated an issue
Puppet / PUP-3318
Puppet prints warning when "environment" is set using classifier rather than local puppet.conf
Change By:
Marc Seeger
We set the environment in the external node classifier and don't have one set locally.Puppet seems to default to the 'production' environment in case you don't have one set and it turns into:{noformat}Warning: Local environment: "production" doesn't match server specified node environment "devel", switching agent to "devel".{noformat}"devel" is the environment currently set for this node.We didn't specify "production" anywhere manually.I think that when a user DOESN'T specify any environment in the puppet.conf file but sets it in the classifier, this warning seems superfluous.This is the local puppet.conf:{noformat}[main]logdir=/var/log/puppetvardir=/var/lib/puppetssldir=/var/lib/puppet/sslrundir=/var/run/puppet # This is required for Ruby 2.1.1, due to a bug in Puppet. In reality, we# always compressed the response data with mod_deflate for certain file types.# Now, Ruby will add it's own Accept-Encoding header, and decode the response# for you. Unfortunately, Puppet will also try to decode that response.# See: https://tickets.puppetlabs.com/browse/PUP-1680 http_compression = true[agent] server = master.e.some.thing.com certname = srv-13.some.thing.com{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email
Jira (PUP-3318) Puppet prints warning when local environment isn't set
Title: Message Title Marc Seeger created an issue Puppet / PUP-3318 Puppet prints warning when local environment isn't set Issue Type: Bug Affects Versions: 3.x Assignee: Unassigned Created: 19/Sep/14 11:24 AM Environment: puppet 3.5.1 Priority: Normal Reporter: Marc Seeger We set the environment in the external node classifier and don't have one set locally. Puppet seems to default to the 'production' environment in case you don't have one set and it turns into: Warning: Local environment: "production" doesn't match server specified node environment "devel", switching agent to "devel". "devel" is the environment currently set for this node. We didn't specify "production" anywhere manually. I think that when a user DOESN'T specify any environment in the puppet.conf file but sets it in the classifier, this warning seems superfluous.
Jira (PUP-3318) Puppet prints warning when "environment" is set using classifier rather than local puppet.conf
Title: Message Title Marc Seeger updated an issue Puppet / PUP-3318 Puppet prints warning when "environment" is set using classifier rather than local puppet.conf Change By: Marc Seeger Summary: Puppet prints warning when local " environment isn't " is set using classifier rather than local puppet.conf Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2304) Implement "requirements" support for the PMT
Title: Message Title Anderson Mills commented on an issue Re: Implement "requirements" support for the PMT Andy Parker As the assignee, my understanding is that this is not the direction we want to go with the PMT, but Ryan Coleman is the product owner, so has the final call. We currently do not have any requirements functionality in PE-Puppet. It was removed. Add Comment Puppet / PUP-2304 Implement "requirements" support for the PMT We should implement support for validated (at install time) requirements for modules, particularly for Puppet and Facter. As an example, if a release of module is published with a 'puppet' requirement and the current Puppet version does not fall in that range PMT should refuse to install that release. This behaviour can be bypassed with the --ignore-r... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http:/
Jira (PUP-3185) A puppet-passenger master fails with cryptic message for default directory environment setup with non-existent production directory.
Title: Message Title Joshua Partlow commented on an issue Re: A puppet-passenger master fails with cryptic message for default directory environment setup with non-existent production directory. Hi François Chenais, the puppet master needs some initial environment to bootstrap from. By default this is production. For a passenger setup, you can edit your config.ru to add the debugging flag (this file should be one up from your Apache Passenger virtualhost's documentroot) Add Comment Puppet / PUP-3185 A puppet-passenger master fails with cryptic message for default directory environment setup with non-existent production directory. PUP-2519 changed the settings catalog to create the default directory environment. [~fpletz] noticed that for a puppet master running under passenger, this can cause problems (and does with the default puppetmaster-passenger package on Debian) if the user the rack process is running as does not have permission to create the production directory. You e... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Gr
Jira (PUP-3317) Extend Package Source to include HTTP Urls (Windows)
Title: Message Title
Josh Cooper commented on an issue
Re: Extend Package Source to include HTTP Urls (Windows)
Louis Mayorga I agree this would be useful and eliminate the need to have a second copy of the installer. There is a related ticket PUP-3189 for supporting this for file resource sources.
Since msiexec already supports URLs, I was thinking would should just pass the URL to it for (MSI packages). For exe-based packages, I think we'd need to download the package to a secure temp location, and execute from there, but only download if we actually need to install or update.
Thoughts?
Add Comment
Puppet / PUP-3317
Extend Package Source to include HTTP Urls (Windows)
Currently, The *package* resource type for windows does not include the http url as a valid value. {code} windows Windows package management. This provider supports either MSI or self-extracting executable installers. This provider requires a source attribute when installing the package. It accepts paths to local files, mapped drives, or U...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3317) Extend Package Source to include HTTP Urls (Windows)
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3317 Extend Package Source to include HTTP Urls (Windows) Change By: Josh Cooper Labels: windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3317) Extend Package Source to include HTTP Urls (Windows)
Title: Message Title Andy Parker assigned an issue to Josh Cooper Puppet / PUP-3317 Extend Package Source to include HTTP Urls (Windows) Change By: Andy Parker Assignee: Andy Parker Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3317) Extend Package Source to include HTTP Urls (Windows)
Title: Message Title Andy Parker updated an issue Puppet / PUP-3317 Extend Package Source to include HTTP Urls (Windows) Change By: Andy Parker Component/s: Modules Component/s: Types and Providers Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3301) concat type/provider broken since 3.7.1
Title: Message Title Andreas Roth commented on an issue Re: concat type/provider broken since 3.7.1 Thank you for pointing out my error. I already modified by concat* type to use the proper autorequire and if you like you could check out the git repo again (just if you're interested ). Add Comment Puppet / PUP-3301 concat type/provider broken since 3.7.1 I set up a GIT repository at https://github.com/aroth-arsoft/puppet-type-concat with my concat type+provider. When i'm running the run_concat_test script using puppet version 3.7.0 (or before) the script creates two files: /tmp/concat_test2 which contains concat1 concat2 concat3 and /tmp/concat_test_redir concat1 concat2 concat2_1 concat2_1... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs.
Jira (PUP-2855) Puppet agent segfault on OSX Mavericks when puppet master is running under passenger
Title: Message Title Christian Caterham commented on an issue Re: Puppet agent segfault on OSX Mavericks when puppet master is running under passenger Mac OS X 10.9.5 seems to fix the issue. Puppet installs and runs as it did in Mac OS X 10.9.2. Add Comment Puppet / PUP-2855 Puppet agent segfault on OSX Mavericks when puppet master is running under passenger When running under the default WEBrick server puppet master and agents function as expected. When running under passenger agents on OSX Mavericks segfault (sorry, I don't have access to other versions of OSX currently). Agents running under CentOS 6.5 continue to function normally under passenger. Dump file attached. Here is the output: bash-3.2#... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.goo
Jira (FACT-712) Add is_ec2 and is_euca facts
Title: Message Title redmine.exporter created an issue Facter / FACT-712 Add is_ec2 and is_euca facts Issue Type: New Feature Assignee: Eric Sorenson Created: 19/Sep/14 7:53 AM Labels: redmine Priority: Normal Reporter: redmine.exporter Sometimes you just want to know if a host is EC2 or Eucalyptus. This adds two facts in a similar vein to "is_virtual". Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3317) Extend Package Source to include HTTP Urls (Windows)
Title: Message Title
Louis Mayorga created an issue
Puppet / PUP-3317
Extend Package Source to include HTTP Urls (Windows)
Issue Type:
Improvement
Affects Versions:
3.7.1
Assignee:
Andy Parker
Components:
Modules
Created:
19/Sep/14 7:36 AM
Environment:
Windows 7, Windows 2008R2
Priority:
Normal
Reporter:
Louis Mayorga
Currently,
The package resource type for windows does not include the http url as a valid value.
windows
Windows package management.
This provider supports either MSI or self-extracting executable installers.
This provider requires a source attribute when installing the package. It accepts paths to local files, mapped drives, or UNC paths.
This provider supports the install_options and uninstall_options attributes, which allow command-line flags to be passed to the installer. These options should be specified as a string (e.g. ‘–flag’), a hash (e.g. {‘–flag’ => ‘value’}), or an array where each element is either a string or a hash.
If the ex
Jira (PUP-3316) When loading dynamic environments, ignore directories on EACCESS (with a logged warning) rather than bomb out
Title: Message Title Jon McKenzie updated an issue Puppet / PUP-3316 When loading dynamic environments, ignore directories on EACCESS (with a logged warning) rather than bomb out Change By: Jon McKenzie Affects Version/s: 3.6.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3316) When loading dynamic environments, ignore directories on EACCESS (with a logged warning) rather than bomb out
Title: Message Title Jon McKenzie created an issue Puppet / PUP-3316 When loading dynamic environments, ignore directories on EACCESS (with a logged warning) rather than bomb out Issue Type: Improvement Assignee: Unassigned Created: 19/Sep/14 7:07 AM Priority: Normal Reporter: Jon McKenzie Currently, if an environment directory exists which the Puppet server process(es) cannot access, an Errno::EACCESS is raised, but not caught by anything. This causes all requests to the Puppet server to fail spectacularly (even if no clients are actually using the faulty environment). Instead, this error should be caught and logged, and processing should continue as normal. An environment which is misconfigured in this way should not be considered a valid environment, so that only clients which are trying to use this environment error (rather than all clients). Add Comment
Jira (PDB-884) Consider revising the queue order for commands
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-884 Consider revising the queue order for commands Issue Type: Improvement Assignee: Unassigned Created: 19/Sep/14 6:48 AM Priority: Normal Reporter: Kenneth Barber Currently the queue order is FIFO. Which means that things get more or less processed in chronological order as they are inserted. The problems with this methodology arise when there are many generations of data that have queued up. In the case of catalogs & facts, only the most latest information for example is useful. It would be nice to create a scenario, where we could process this later information first - currently our logic for facts & catalogs is to just drop any information that is older so this would speed up queue processing for this case. For reports, the same is kind of true, the latest information usually matters the most - although old data will always need to be stored. So one proposal is just to simply reverse the queueing using Camel & Resequencing or something similar. The concern I have is that slow producers in a loaded scenario might never get their items processed, but this only occurs under larger load anyway. When we start to do historical analysis this might play havoc with our solutions, so we'd need to be wary of that. For example catalog diffs between current and last, might be thrown off if the "last" hasn't actually entered the system yet. A more intelligent way to queue would be some sort of context-aware queueing, but this might require some custom development to achieve this, like a special ordering or comparator in Camel perhaps.
Jira (PUP-1253) systemd service provider should support masking
Title: Message Title Netbulae commented on an issue Re: systemd service provider should support masking We are currently having the requirement to mask services with puppet, so this feature would be very appreciated. Anything we can do to help? (not a developer) Add Comment Puppet / PUP-1253 systemd service provider should support masking systemd knows three states for a service: enabled, disabled and masked. So far, the latter state doesn't seem to be supported by puppet's systemd service provider. The difference of disabling and masking a service is as follows: a disabled service can be started as a dependency of another service or be started manually by a user. A masked service can n... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more opti
Jira (PUP-3185) A puppet-passenger master fails with cryptic message for default directory environment setup with non-existent production directory.
Title: Message Title fc commented on an issue Re: A puppet-passenger master fails with cryptic message for default directory environment setup with non-existent production directory. I use a puppet server as test server before pushing on production server. On this test server, each developer has is own environment, test on client with --environment and --server parameters so I don't need any "production" environment and creating the directory has no sense. => The server should stop or show a clear error message saying that the default environment can't be access ... PS: with apache/passenger, the error message saies to look on webserver logs. What's the way to activate a clear log level for debugging ? Add Comment Puppet / PUP-3185 A puppet-passenger master fails with cryptic message for default directory environment setup with non-existent production directory. PUP-2519 changed the settings catalog to create the default directory environment. [~fpletz] noticed that for a puppet master running under passenger, this can cause problems (and does with the default puppetmaster-passenger package on Debian) if the user the rack process is running as does not have permission to create the production directory. You e... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
