Jira (PDB-889) PR (144): Update README.md - ghoneycutt
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-889 PR (144): Update README.md - ghoneycutt Change By: Kenneth Barber Sprint: PuppetDB 2014-10-08 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 (PDB-890) PR (145): Update jetty_ini.pp - ghoneycutt
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-890 PR (145): Update jetty_ini.pp - ghoneycutt Change By: Kenneth Barber Sprint: PuppetDB 2014-10-08 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 (PDB-889) PR (144): Update README.md - ghoneycutt
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-889 PR (144): Update README.md - ghoneycutt Change By: Kenneth Barber Affects Version/s: module-4.0.0 Story Points: 0 Fix Version/s: module-4.1.0 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 (PDB-889) PR (144): Update README.md - ghoneycutt
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-889 PR (144): Update README.md - ghoneycutt Change By: Kenneth Barber Component/s: DOCS 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 (PDB-890) PR (145): Update jetty_ini.pp - ghoneycutt
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-890 PR (145): Update jetty_ini.pp - ghoneycutt Change By: Kenneth Barber Component/s: DOCS Issue Type: Task Bug 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 (PDB-890) PR (145): Update jetty_ini.pp - ghoneycutt
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-890 PR (145): Update jetty_ini.pp - ghoneycutt Change By: Kenneth Barber Affects Version/s: module-4.0.0 Story Points: 0 Fix Version/s: module-4.1.0 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 (PDB-889) PR (144): Update README.md - ghoneycutt
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-889 PR (144): Update README.md - ghoneycutt Change By: Kenneth Barber Issue Type: Task Bug 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 (PDB-890) PR (145): Update jetty_ini.pp - ghoneycutt
Title: Message Title gepetto-bot commented on an issue Re: PR (145): Update jetty_ini.pp - ghoneycutt Pull request Update jetty_ini.pp has been closed. Add Comment PuppetDB / PDB-890 PR (145): Update jetty_ini.pp - ghoneycutt h2. Update jetty_ini.pp * Author: Garrett Honeycutt* Company: * Github ID: [ghoneycutt|https://github.com/ghoneycutt] * [Pull Request 145 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/145] * [Pull Request 145 File Diff|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/145/files] h2. Pull Requ... 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 (PDB-889) PR (144): Update README.md - ghoneycutt
Title: Message Title gepetto-bot commented on an issue Re: PR (144): Update README.md - ghoneycutt Pull request Update README.md has been closed. Add Comment PuppetDB / PDB-889 PR (144): Update README.md - ghoneycutt h2. Update README.md * Author: Garrett Honeycutt* Company: * Github ID: [ghoneycutt|https://github.com/ghoneycutt] * [Pull Request 144 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/144] * [Pull Request 144 File Diff|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/144/files] h2. Pull Request... 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 (PDB-121) Add Ruby 2.0.0 to spec test matrix for puppetdb
Title: Message Title Kenneth Barber commented on an issue Re: Add Ruby 2.0.0 to spec test matrix for puppetdb Roger Ignazio thanks mate . Add Comment PuppetDB / PDB-121 Add Ruby 2.0.0 to spec test matrix for puppetdb PuppetDB currently runs specs against 1.8.5, 1.8.7 and 1.9.3. Ruby 2.0 is now available in many distributions. We should be running specs against this version. 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-1054) Services should support 'reload' in addition to 'restart'
Title: Message Title xumingyue updated an issue Puppet / PUP-1054 Services should support 'reload' in addition to 'restart' Change By: xumingyue currently if a service needs kicking (e.g. a config file changed) you can notify the service, but this leads to a restart. It would be nice if a reload was done if the service was already running (although I suppose there are bound to be some services which require restarts for some files, reloads for others).A reload would be far faster (shorter service interruption) and potentially more robust. robus I'm looking at this since bind stop/start (I hadn't set "hasrestart") on Debian etch can fail - it looks like stop command doesn't wait for bind to exit (I'll raise a bug with Debian about that) 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-1054) Services should support 'reload' in addition to 'restart'
Title: Message Title Sam McLeod commented on an issue Re: Services should support 'reload' in addition to 'restart' Any update on this? It's a pretty critical feature that's missing... Add Comment Puppet / PUP-1054 Services should support 'reload' in addition to 'restart' currently if a service needs kicking (e.g. a config file changed) you can notify the service, but this leads to a restart. It would be nice if a reload was done if the service was already running (although I suppose there are bound to be some services which require restarts for some files, reloads for others). A reload would be far faster (shorter ser... 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-3342) Upgrading puppet client via puppet makes it stop working
Title: Message Title jon yeargers created an issue Puppet / PUP-3342 Upgrading puppet client via puppet makes it stop working Issue Type: Bug Affects Versions: 3.7.1 Assignee: Unassigned Created: 25/Sep/14 3:40 AM Environment: debian 6 Priority: Normal Reporter: jon yeargers Used the following module file to upgrade my 3.5.1 agents to 3.7.1: class plugpc::puppet_test { package { 'puppet' : ensure => '3.7.1-1puppetlabs1', require => Package[ 'dmidecode','puppet-common' ]; } package { 'puppet-common' : ensure => '3.7.1-1puppetlabs1', require => Package[ 'dmidecode' ]; } package { 'facter' : ensure => '2.2.0-1puppetlabs1', require => Package[ 'puppet-common' ] } package { 'dmidecode' : ensure => 'latest'; } file { '/etc/default/puppet' : ensure => 'file', source => 'puppet:///modules/plugpc/default/puppet' } file { '/etc/puppet/puppet.conf' : content => template("plugpc/puppet_conf.erb"); } service { 'puppet' : ensure => 'running', enable => true, } } After this is applied (successfully) the clients will report the following error m
Jira (PUP-1054) Services should support 'reload' in addition to 'restart'
Title: Message Title David Watzke commented on an issue Re: Services should support 'reload' in addition to 'restart' I also think it would be fine to have a possibility to notify services for reload, but I don't think it's very safe to use it in some cases. For example, if you reload an apache webserver after you changed something minor, such as a documentroot path, then it's (usually) fine, but when you mess with some LoadModule directives etc., then the reload won't be enough and may even fail (I don't know about this particular case but I do know that reload for some services sometimes doesn't end well). I'd be glad if puppet supported a pre-restart (and possibly pre-reload, if this feature gets implemented) command which you could specify to check if the restart or reload of a service is safe (e.g. that the service will start again after you stop it). But I guess that would deserve another ticket as it's an separate feature request. Add Comment Puppet / PUP-1054 Services should support 'reload' in addition to 'restart' currently if a service needs kicking (e.g. a config file changed) you can notify the service, but this leads to a restart. It would be nice if a reload was done if the service was already running (although I suppose there are bound to be some services which require restarts for some files, reloads for others). A reload would be far faster (shorter ser... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3342) Upgrading puppet client via puppet makes it stop working
Title: Message Title jon yeargers commented on an issue Re: Upgrading puppet client via puppet makes it stop working I changed the module file so it only updates facter to 2.2.0. Puppet and -common are left at 3.5.1. This results in a working system. Add Comment Puppet / PUP-3342 Upgrading puppet client via puppet makes it stop working Used the following module file to upgrade my 3.5.1 agents to 3.7.1: class plugpc::puppet_test { package { 'puppet' : ensure => '3.7.1-1puppetlabs1', require => Package[ 'dmidecode','puppet-common' ]; } package { 'puppet-common' : ... 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-3343) Exec resource environment does not allow double quoted string
Title: Message Title Julien Barbay created an issue Puppet / PUP-3343 Exec resource environment does not allow double quoted string Issue Type: Bug Affects Versions: 3.6.2 Assignee: Kylo Ginsberg Components: Client, Types and Providers Created: 25/Sep/14 5:09 AM Environment: Tested on Puppet Client 3.6.2 for OSX (10.9) Priority: Normal Reporter: Julien Barbay Related to this ticket When executing : testcase.pp
Jira (PUP-3343) Exec resource environment does not allow double quoted string
Title: Message Title Julien Barbay updated an issue Puppet / PUP-3343 Exec resource environment does not allow double quoted string Change By: Julien Barbay Related to [this ticket|https://projects.puppetlabs.com/issues/5224]+When executing :+{code:title=testcase.pp|borderStyle=solid}Exec { "test":environment => 'HOME="/Users/y_nk/"',command => 'puppet apply site.pp',}{code}+Error returned :+{code}Notice: /Stage[main]/Main/Exec[ repository-execute test ]/returns: Error: Could not initialize global default settings: non-absolute homeError: puppet apply "site.pp" returned 1 instead of one of [0]{code}When removing the double quotes in the {{environment}} attribute, everything seems fine. *The {{environment}} attribute's value should be escaped to allow double quotes in it*. 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-3342) Upgrading puppet client via puppet makes it stop working
Title: Message Title jon yeargers commented on an issue Re: Upgrading puppet client via puppet makes it stop working Updating puppet/-common to 3.7.1 while leaving facter at 1.7.5 is a working system Add Comment Puppet / PUP-3342 Upgrading puppet client via puppet makes it stop working Used the following module file to upgrade my 3.5.1 agents to 3.7.1: class plugpc::puppet_test { package { 'puppet' : ensure => '3.7.1-1puppetlabs1', require => Package[ 'dmidecode','puppet-common' ]; } package { 'puppet-common' : ... 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 (PDB-888) Replication: Spike Quartz for distributed job scheduling
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-888 Replication: Spike Quartz for distributed job scheduling Change By: Kenneth Barber Summary: Replication: Spike Quartz for distributed job scheduling 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 (PDB-489) Change response formats to include timestamp metadata in them
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-489 Change response formats to include timestamp metadata in them Change By: Wyatt Alt Sprint: PuppetDB 2014-10-08 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-3339) Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers.
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3339 Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers. Change By: Joshua Partlow Sprint: Platform 2014-10-01 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-3339) Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers.
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3339 Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers. Change By: Joshua Partlow Flagged: Impediment 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-3344) support "--index-url" and "--extra-index-url" for python pip
Title: Message Title redmine.exporter created an issue Puppet / PUP-3344 support "--index-url" and "--extra-index-url" for python pip Issue Type: New Feature Assignee: Unassigned Created: 25/Sep/14 8:49 AM Labels: redmine Priority: Normal Reporter: redmine.exporter This pull request: https://github.com/puppetlabs/puppet/pull/521 raised a few questions / issues about the best way to handle provider-specific parameters for package providers. We'd prefer not to be forced to stuff them into existing (somewhat unrelated) parameters and regex them out (though this does happen in certain providers), but we also want to be careful about adding too many provider-specific parameters to the main "package" resource type, which would clutter up the model and make it confusing. The pip case is particularly interesting, because the two parameters that we need to add support for touch on a few conceptual things that we don't yet have parameters for: 1) The ability to specify multiple source destinations (we currently only have the "source" parameter, and the docs for it definitely read as though it is a single file/URL). 2) The ability to disable the default (implicit) source of a given package provider (this is what the "--index-url" option for pip does). We should give some consideration to a long-term / general way to handle those two concepts; I'll create and link in a second ticket for that. However, in the short term, we do have an existing parameter
Jira (HI-293) merging not working
Title: Message Title Dmitry created an issue Hiera / HI-293 merging not working Issue Type: Bug Affects Versions: 1.3.4 Assignee: Unassigned Created: 25/Sep/14 8:50 AM Priority: Major Reporter: Dmitry I am trying to implement hiera merging. hier is my hiera.yaml — :hierarchy: fqdn/% {fqdn} roles/% {role} os/% {osfamily} common :backends: yaml options are native, deep, deeper :merge_behavior: deeper :yaml: :datadir: /etc/puppet/environments/% {environment} /data then I have: common.yaml — classes:
Jira (HI-293) merging not working
Title: Message Title Dmitry updated an issue Hiera / HI-293 merging not working Change By: Dmitry Assignee: Dmitry 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 (HI-293) merging not working
Title: Message Title Dmitry assigned an issue to Dmitry Hiera / HI-293 merging not working Change By: Dmitry Assignee: Dmitry 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-2940) Installing and using puppet with CentOS7 & RHEL7
Title: Message Title Charlie Sharpsteen commented on an issue Re: Installing and using puppet with CentOS7 & RHEL7 garrett honeycutt: Are you using puppetlabs-ruby as well? Add Comment Puppet / PUP-2940 Installing and using puppet with CentOS7 & RHEL7 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 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-2940) Installing and using puppet with CentOS7 & RHEL7
Title: Message Title garrett honeycutt commented on an issue Re: Installing and using puppet with CentOS7 & RHEL7 I did not get that far, since the puppet agent does not run. However, I do use that module and appreciate the work that Eric and yourself have been putting into it. Add Comment Puppet / PUP-2940 Installing and using puppet with CentOS7 & RHEL7 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 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.goog
Jira (PUP-3339) Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers.
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-3339 Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers. Change By: Hailee Kenney Assignee: Hailee Kenney 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-2940) Installing and using puppet with CentOS7 & RHEL7
Title: Message Title Charlie Sharpsteen commented on an issue Re: Installing and using puppet with CentOS7 & RHEL7 I still can't re-produce this on a RHEL 7 system: # yum install puppet ... Dependencies Resolved == Package Arch Version Repository Size == Installing:
Jira (PUP-3345) Puppet Master Memory Leak
Title: Message Title Jason Fonseca created an issue Puppet / PUP-3345 Puppet Master Memory Leak Issue Type: Bug Affects Versions: 3.7.1 Assignee: Andy Parker Components: Server Created: 25/Sep/14 11:08 AM Environment: Red Hat Enterprise Linux 6.5 Default Ruby and Apache PuppetDB connected to PostgreSQL Priority: Normal Reporter: Jason Fonseca Starting with 3.7, the Puppet master process will allocate more and more memory until it is killed by the OOM process. This occurs in about 24 hours in our environment. The behaviour occurs in both Rack and WEBRick configurations. In the Rack configuration the four Rack processes will grow until killed. In WEBRick configuration the one puppet master process will grow.
Jira (PDB-872) Change in namespace has made `lein run` show test namespaces also
Title: Message Title Ryan Senior commented on an issue Re: Change in namespace has made `lein run` show test namespaces also The right fix here I think is to create a new leiningen alias for run, that uses a different profile (maybe the "production" profile) that won't include the tests in the classpath. This is currently broken in lein, but should be fixed in the next release (2.5.1). It seems like that may drop next week. Setting this aside until it has been released as it's not a critical change that needs to happen right now. Add Comment PuppetDB / PDB-872 Change in namespace has made `lein run` show test namespaces also You can see this craziness by running `lein run`: {code} [ken@kb puppetdb]# lein run Available subcommands: anonymize Anonymize puppetdb dump files anonymize-test benchmark Development-only benchmarking tool export Export all PuppetDB catalog data to a backup file export-test import Import PuppetDB catalog data from a backup file imp... 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
Jira (PDB-872) Change in namespace has made `lein run` show test namespaces also
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-872 Change in namespace has made `lein run` show test namespaces also Change By: Ryan Senior Sprint: PuppetDB 2014-10-08 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 (PDB-854) PR (1072): (maint)(packaging) Updates to packaging for improved systemd support and PID dir handling - shrug
Title: Message Title gepetto-bot commented on an issue Re: PR (1072): (maint)(packaging) Updates to packaging for improved systemd support and PID dir handling - shrug shrug commented: I'm back on this @kbarber, minor updates incoming Add Comment PuppetDB / PDB-854 PR (1072): (maint)(packaging) Updates to packaging for improved systemd support and PID dir handling - shrug h2. (maint)(packaging) Updates to packaging for improved systemd support and PID dir handling * Author: <> * Company: * Github ID: [shrug|https://github.com/shrug] * [Pull Request 1072 Discussion|https://github.com/puppetlabs/puppetdb/pull/1072] * [Pull Request 1072 File Diff|https://github.com/puppetlabs/puppetdb/pull/1072/files] h2. Pull Reques... 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
Jira (PDB-854) PR (1072): (maint)(packaging) Updates to packaging for improved systemd support and PID dir handling - shrug
Title: Message Title gepetto-bot commented on an issue Re: PR (1072): (maint)(packaging) Updates to packaging for improved systemd support and PID dir handling - shrug mckern commented: :+1: Add Comment PuppetDB / PDB-854 PR (1072): (maint)(packaging) Updates to packaging for improved systemd support and PID dir handling - shrug h2. (maint)(packaging) Updates to packaging for improved systemd support and PID dir handling * Author: <> * Company: * Github ID: [shrug|https://github.com/shrug] * [Pull Request 1072 Discussion|https://github.com/puppetlabs/puppetdb/pull/1072] * [Pull Request 1072 File Diff|https://github.com/puppetlabs/puppetdb/pull/1072/files] h2. Pull Reques... 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
Jira (PDB-854) PR (1072): (maint)(packaging) Updates to packaging for improved systemd support and PID dir handling - shrug
Title: Message Title gepetto-bot commented on an issue Re: PR (1072): (maint)(packaging) Updates to packaging for improved systemd support and PID dir handling - shrug kbarber commented: @shrug no problem dude. you guys hit the button when you are ready. Add Comment PuppetDB / PDB-854 PR (1072): (maint)(packaging) Updates to packaging for improved systemd support and PID dir handling - shrug h2. (maint)(packaging) Updates to packaging for improved systemd support and PID dir handling * Author: <> * Company: * Github ID: [shrug|https://github.com/shrug] * [Pull Request 1072 Discussion|https://github.com/puppetlabs/puppetdb/pull/1072] * [Pull Request 1072 File Diff|https://github.com/puppetlabs/puppetdb/pull/1072/files] h2. Pull Reques... 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 (PDB-854) PR (1072): (maint)(packaging) Updates to packaging for improved systemd support and PID dir handling - shrug
Title: Message Title gepetto-bot commented on an issue Re: PR (1072): (maint)(packaging) Updates to packaging for improved systemd support and PID dir handling - shrug Pull request (maint)(packaging) Updates to packaging for improved systemd support and PID dir handling has been closed. Add Comment PuppetDB / PDB-854 PR (1072): (maint)(packaging) Updates to packaging for improved systemd support and PID dir handling - shrug h2. (maint)(packaging) Updates to packaging for improved systemd support and PID dir handling * Author: <> * Company: * Github ID: [shrug|https://github.com/shrug] * [Pull Request 1072 Discussion|https://github.com/puppetlabs/puppetdb/pull/1072] * [Pull Request 1072 File Diff|https://github.com/puppetlabs/puppetdb/pull/1072/files] h2. Pull Reques... 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.g
Jira (PUP-3339) Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers.
Title: Message Title Hailee Kenney commented on an issue Re: Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers. After going through this on Fedora 19 and Fedora 20, Fedora 19 seems to have an issue with changing ownership of the home directory while Fedora 20 does not. So on Fedora 20: [root@bd4849uiz04imoa ~]# usermod -u 1000 test [root@bd4849uiz04imoa ~]# cat /etc/passwd test:x:1000:1000::/home/test:/bin/bash [root@bd4849uiz04imoa ~]# ls -l /home/ drwxr-xr-x. 3 test test 4096 Sep 25 13:27 test [root@bd4849uiz04imoa ~]# ls -l /var/spool/mail/ -rw-rw. 1 test mail 0 Sep 25 13:20 test [root@bd4849uiz04imoa ~]# usermod -u 53 test [root@bd4849uiz04imoa ~]# ls -l /home/ drwxr-xr-x. 3 test test 4096 Sep 25 13:27 test
Jira (PUP-3342) Upgrading puppet client via puppet makes it stop working
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3342 Upgrading puppet client via puppet makes it stop working Change By: Charlie Sharpsteen Assignee: jon yeargers 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-3342) Upgrading puppet client via puppet makes it stop working
Title: Message Title Charlie Sharpsteen commented on an issue Re: Upgrading puppet client via puppet makes it stop working That error message means that an invalid option was passed to Facter.add when a fact was declared. In this case, the :type option was added in Facter 2.x to support aggregate resolutions. The error message suggests that the new version of Puppet is running against an old, or mixed version of Facter. puppet-common has dependency on Facter, so the Facter package should probably be synched before puppet-common. Does the upgrade work if you change the require statement to update Facter before updating Puppet? Add Comment Puppet / PUP-3342 Upgrading puppet client via puppet makes it stop working Used the following module file to upgrade my 3.5.1 agents to 3.7.1: class plugpc::puppet_test { package { 'puppet' : ensure => '3.7.1-1puppetlabs1', require => Package[ 'dmidecode','puppet-common' ]; } package { 'puppet-common' : ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2846) multiple providers are executed for the same resource
Title: Message Title Felix Frank commented on an issue Re: multiple providers are executed for the same resource I cannot reproduced with 3.6.1. Since I don't have aws installed, I replaced its command with /bin/echo in your provider. This is my output (running as non-root for simplicity). $ puppet apply ./pup-2846.pp Could not retrieve fact='virtual', resolution='': Permission denied @ rb_sysopen - /sys/firmware/dmi/entries/1-0/raw Notice: Compiled catalog for geras.fritz.box in environment production in 0.21 seconds Error: Execution of '/sbin/iptables -I POSTROUTING 1 -t nat -s 10.1.2.0/24 -o eth0 -p all -m comment --comment 100 snat for network foo2 -j MASQUERADE' returned 3: iptables v1.4.21: can't initialize iptables table `nat': Permission denied (you must be root) Perhaps iptables or your kernel needs to be upgraded. Error: /Stage[main]/Main/Firewall[100 snat for network foo2]/ensure: change from absent to present failed: Execution of '/sbin/iptables -I POSTROUTING 1 -t nat -s 10.1.2.0/24 -o eth0 -p all -m comment --comment 100 snat for network foo2 -j MASQUERADE' returned 3: iptables v1.4.21: can't initialize iptables table `nat': Permission denied (you must be root) Perhaps iptables or your kernel needs to be upgraded. [aws_securitygroup] Exists 000 accept all icmp requests
Jira (PUP-2846) multiple providers are executed for the same resource
Title: Message Title Felix Frank updated an issue Puppet / PUP-2846 multiple providers are executed for the same resource Change By: Felix Frank Assignee: Felix Frank cristi falcas 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-2718) Prefetching is prone to fail for eval_generated resources
Title: Message Title Felix Frank updated an issue Puppet / PUP-2718 Prefetching is prone to fail for eval_generated resources Change By: Felix Frank When the {{User}} type implemented purging of {{ssh_authorized_keys}} using the {{eval_generate}} hook, it became apparent that the following manifest{code}package { 'coreutils': before => User[root] } user { 'root': purge_ssh_keys => '/tmp/keyfile' }{code}would not purge any keys from {{/tmp/keyfile}}.The reason is that prefetching of the keys fails in the following fashion: # When {{Transaction#evaluate}} starts traversing the graph, no {{ssh_authorized_key}} resources are yet part of the graph # each resource has a {{pre_process}} hook that invokes {{#prefetch_if_necessary}} # this happens for the {{package}} resource first, and {{prefetch_if_necessary}} invokes {{resources_by_provider}}, which caches a hash of all resources in the graph # during its evaluation, the {{user}} resource generates {{ssh_authorized_key}} resources for purging # these keys also invoke {{prefetch_if_necesary}}, but the result from {{resources_by_provider}} is cached and lacks their references # no resources are passed to the provider's {{prefetch}} method, the provider considers the entities to be unmanaged and the resources are falsely determined to be already absentA workaround may comprise a way to invalidate the cache of the {{Transaction#resources_by_provider}} method upon {{eval_generate}}-ing resources.This needs a decision, though. 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 s
Jira (PUP-1366) yum provider doesn't respect items provided by a package, only the package name
Title: Message Title Felix Frank commented on an issue Re: yum provider doesn't respect items provided by a package, only the package name Hi Sam Kottler, any update on this? Add Comment Puppet / PUP-1366 yum provider doesn't respect items provided by a package, only the package name A simple use case: In EL5 and earlier, the curl development headers were included in a package called curl-devel. In EL6 and later that package was renamed to libcurl-devel. However, the libcurl-devel package still provides curl-devel. When using something like package { "curl-devel": ensure => installed } puppet looks for... 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-1222) If "ensure" changes, then no other changes are reported for that resource.
Title: Message Title Felix Frank commented on an issue Re: If "ensure" changes, then no other changes are reported for that resource. Hi Dan Bode, any update on this? Add Comment Puppet / PUP-1222 If "ensure" changes, then no other changes are reported for that resource. code: {code} service { 'httpd': ensure => running, enable => true, } {code} even though chkconfig is set to off in both cases, its only logged when the process isn't started. {code} # /sbin/service httpd stop Stopping httpd: [ OK ] [root@dannyboy manifests]# chkconfig httpd off [root@dannybo... 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-3337) Validation of shell in user resource breaks when using sudo
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3337 Validation of shell in user resource breaks when using sudo Change By: Charlie Sharpsteen Affects Version/s: 3.7.0 Affects Version/s: 3.5.0 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-3337) Validation of shell in user resource breaks when using sudo
Title: Message Title Charlie Sharpsteen commented on an issue Re: Validation of shell in user resource breaks when using sudo This issue is a result of changes made in Puppet 3.5.0 by PUP-1448 . In hindsight, the validation added there may be much too restrictive. Should we do any validation above and beyond what the underlying tool, such as chsh, requires? Add Comment Puppet / PUP-3337 Validation of shell in user resource breaks when using sudo We have an special user on our clients used to allow emergency logins if the user has lost his/hers smartcard. This user has a loginshell like this: "/usr/bin/sudo /usr/bin/emerg.sh" This worked fine before, but somewhere along the way a validation of the shell has been introduced which renders the error: "Shell /usr/bin/sudo /usr/bin/emerg.sh must 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 Groups "Puppet Bugs" group. To unsubscribe from thi
Jira (PUP-3345) Puppet Master Memory Leak
Title: Message Title Andy Parker commented on an issue Re: Puppet Master Memory Leak Jason Fonseca, can you provide any more information about this? Do you have any indication about what might be leaking? Are you using custom functions or using templates? I need some way to reproduce the problem in order to track this down. If you could come up with a way of reproducing the memory leak, maybe by simplifying your setup to something you can share but still shows the problem, that would help a lot. Add Comment Puppet / PUP-3345 Puppet Master Memory Leak Starting with 3.7, the Puppet master process will allocate more and more memory until it is killed by the OOM process. This occurs in about 24 hours in our environment. The behaviour occurs in both Rack and WEBRick configurations. In the Rack configuration the four Rack processes will grow until killed. In WEBRick configuration the one puppet maste... 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+unsubsc
Jira (PUP-3345) Puppet Master Memory Leak
Title: Message Title Andy Parker assigned an issue to Jason Fonseca Puppet / PUP-3345 Puppet Master Memory Leak Change By: Andy Parker Assignee: Andy Parker Jason Fonseca 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-1221) Mixed invocation of parameterized classes leads to order dependencies, should be disallowed
Title: Message Title Felix Frank commented on an issue Re: Mixed invocation of parameterized classes leads to order dependencies, should be disallowed So Henrik Lindberg, I assume this is not on the plate for 4.0, yes? Add Comment Puppet / PUP-1221 Mixed invocation of parameterized classes leads to order dependencies, should be disallowed When a parameterized class has default values for all of its parameters, it may be invoked using either "include" or class \{ ... \} notation. The "include" notation is idempotent; the class \{ ... \} notation isn't. As a result, there is an order dependency. This works: {code} class foo($param = defaultvalue) { notify { $param: } } class {... 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-1221) Mixed invocation of parameterized classes leads to order dependencies, should be disallowed
Title: Message Title Felix Frank updated an issue Puppet / PUP-1221 Mixed invocation of parameterized classes leads to order dependencies, should be disallowed Change By: Felix Frank Affects Version/s: 2.7.23 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 (PDB-888) Replication: Spike Quartz for distributed job scheduling
Title: Message Title Ryan Senior assigned an issue to Ryan Senior PuppetDB / PDB-888 Replication: Spike Quartz for distributed job scheduling Change By: Ryan Senior Assignee: Ryan Senior 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-3334) Changes to environment.conf are not being picked up, even when environment timeout is set to 0.
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3334 Changes to environment.conf are not being picked up, even when environment timeout is set to 0. Change By: Charlie Sharpsteen 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-1072) support HTTP(S) URL as the file 'source'
Title: Message Title Felix Frank updated an issue Puppet / PUP-1072 support HTTP(S) URL as the file 'source' Change By: Felix Frank Lots and lots of folks want to be able to do this: {code} file { "/tmp/example.txt": source => 'http://example.com/example.txt' } {code} This would be good to support; obviously the metadata for the HTTP URI is much less available than via puppet file serving, but this would make a lot of people very, very happy. 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-1072) support HTTP(S) URL as the file 'source'
Title: Message Title Felix Frank assigned an issue to Felix Frank Puppet / PUP-1072 support HTTP(S) URL as the file 'source' Change By: Felix Frank Assignee: Felix Frank 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-3327) puppet error in puppetmaster
Title: Message Title Charlie Sharpsteen commented on an issue Re: puppet error in puppetmaster Can this error be re-produced on Puppet 3.7.1? The 2.7.x series has passed end of life for bugfixes and security updates. Add Comment Puppet / PUP-3327 puppet error in puppetmaster {noformat} err: /File[/var/lib/puppet/lib]: Failed to generate additional resources using 'eval_generate: SSL_connect returned=1 errno=0 state=SSLv3 read finished A: tlsv1 alert decrypt error err: /File[/var/lib/puppet/lib]: Could not evaluate: SSL_connect returned=1 errno=0 state=SSLv3 read finished A: tlsv1 alert decrypt error Could not retrieve file ... 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-3327) puppet error in puppetmaster
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3327 puppet error in puppetmaster Change By: Charlie Sharpsteen Assignee: aswin venugopal 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-3339) Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers.
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3339 Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers. Change By: Joshua Partlow Assignee: Joshua Partlow 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-3339) Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers.
Title: Message Title Joshua Partlow assigned an issue to Hailee Kenney Puppet / PUP-3339 Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers. Change By: Joshua Partlow Assignee: Joshua Partlow Hailee Kenney 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-3286) Puppet module tool should have a download action
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3286 Puppet module tool should have a download action Change By: Charlie Sharpsteen Issue Type: Bug New Feature 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-3283) Resource type ssh_authorized key, 'name' attribute accepts a blank string
Title: Message Title Charlie Sharpsteen commented on an issue Re: Resource type ssh_authorized key, 'name' attribute accepts a blank string Well, an empty string can be unique if it is only used once. Can you create two authorized key resources with empty names? Add Comment Puppet / PUP-3283 Resource type ssh_authorized key, 'name' attribute accepts a blank string Specifying a blank string for the 'name' attribute should probably throw an error, because the [documentation|https://docs.puppetlabs.com/references/latest/type.html#ssh_authorized_key-attribute-name] says that the name has to be unique to the system. The manifest I used to test: {noformat} $username = 'testuser' $keyname = 'has_a_blank_name' u... 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://gr
Jira (PUP-3283) Resource type ssh_authorized key, 'name' attribute accepts a blank string
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3283 Resource type ssh_authorized key, 'name' attribute accepts a blank string Change By: Charlie Sharpsteen Assignee: Joe Pinsonault 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-3081) reported catalog run time is wildly inaccurate
Title: Message Title Adrien Thebo commented on an issue Re: reported catalog run time is wildly inaccurate The operation being benchmarked is just for catalog application and does not include catalog compilation and retrieval. I've submitted https://github.com/puppetlabs/puppet/pull/3121 to update that message. Add Comment Puppet / PUP-3081 reported catalog run time is wildly inaccurate The puppet client clearly does not actually use wallclock time to calculate how long a puppet run takes. Here are a few examples of puppet runs with the time command: # time puppet agent -t Notice: Finished catalog run in 131.19 seconds real 3m32.015s user 1m48.207s sys 0m18.101s# time puppet agent -t Notice: Fin... 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
Jira (PUP-3339) Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers.
Title: Message Title Joshua Partlow commented on an issue Re: Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers. Confined acceptance from running this test on fedora-19; merged to stable in 6d0d7f8 and to master in cc4e3c5 Add Comment Puppet / PUP-3339 Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers. This failure is showing up in the following acceptance test: acceptance/tests/config/puppet_manages_own_configuration_in_robust_manner.rb, but only on Fedora19. This test removes the puppet user/group and then confirms that the --mkusers flag allows the puppet master to recreate them. Before doing this, it records the current user/group state, and then ... 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://group
Jira (PUP-3339) Puppet user provider failing to reset puppet uid on Fedora19 due to usermod bug
Title: Message Title Hailee Kenney updated an issue Puppet / PUP-3339 Puppet user provider failing to reset puppet uid on Fedora19 due to usermod bug Change By: Hailee Kenney Summary: Puppet user provider failing usermod call to reset puppet uid on Fedora19 after a --mkusers. due to usermod bug 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-3339) Puppet user provider failing to reset puppet uid on Fedora19 due to usermod bug
Title: Message Title Hailee Kenney updated an issue Puppet / PUP-3339 Puppet user provider failing to reset puppet uid on Fedora19 due to usermod bug Change By: Hailee Kenney This failure is showing up in the following acceptance test: acceptance/tests/config/puppet_manages_own_configuration_in_robust_manner.rb, but only on Fedora19. This test removes the puppet user/group and then confirms that the --mkusers flag allows the puppet master to recreate them. Before doing this, it records the current user/group state, and then in the final teardown step, reapplies the origina user/group state.The failure began showing up after a fix to this test in [1d3fc272|https://github.com/puppetlabs/puppet/commit/1d3fc2724c65c6fce455bc35a87b24b6c361205a] began halting the test if the final puppet apply to reset the puppet user/group failed. It is likely that this was always failing, but we only began to see it with this change.https://jenkins.puppetlabs.com/job/Puppet-Package-Acceptance-stable/label=beaker,platform=fedora19/61/I've attached a detailed log of the point of failure, but don't know why it's failing.*UPDATE:* After further investigation, this issue was found to be caused by a bug in the {{usermod}} command on Fedora 19. The bug does not appear to be present on Fedora 20. Since Fedora 19 is approaching end of life, we've decided not to fix this issue and just confine the acceptance test not to run on Fedora 19. The following output illustrates the bug which is causing the issue: After going through this on Fedora 19 and Fedora 20 , Fedora 19 seems to have an issue with changing ownership of the home directory while Fedora 20 does not.So on Fedora 20 :{noformat}[root@bd4849uiz04imoa ~]# usermod -u 1000 test[root@bd4849uiz04imoa ~]# cat /etc/passwdtest:x:1000:1000::/home/test:/bin/bash[root@bd4849uiz04imoa ~]# ls -l /home/drwxr-xr-x. 3 test test 4096 Sep 25 13:27 test[root@bd4849uiz04imoa ~]# ls -l /var/spool/mail/-rw-rw. 1 test mail 0 Sep 25 13:20 test[root@bd4849uiz04imoa ~]# usermod -u 53 test[root@bd4849uiz04imoa ~]# ls -l /home/drwxr-xr-x. 3 test test 4096 Sep 25 13:27 test[root@bd4849uiz04imoa ~]# ls -l /var/spool/mail/-rw-rw. 1 test mail 0 Sep 25 13:20 test{noformat} But then on Fedora 19:{noformat}[root@nykbnzgen65yxtt ~]# usermod -u 1000 test[root@nykbnzgen65yxtt ~]# cat /etc/passwdtest:x:1000:1000::/home/test:/bin/bash[root@nykbnzgen65yxtt ~]# ls -l /home/drwxr-xr-x. 3 test test 4096 Sep 25 13:27 test[root@nykbnzgen65yxtt ~]# ls -l /var/spool/mail/-rw-rw. 1 test mail 0 Sep 25 13:20 test[root@nykbnzgen65yxtt ~]# usermod -u 53 testusermod: Failed to change ownership of the home directory[root@nykbnzgen65yxtt ~]# ls -l /var/spool/mail/-rw-rw. 1 test mail 0 Sep 25 13:20 test[root@nykbnzgen65yxtt ~]# ls -l /home/drwxr-xr-x. 3 1000 test 4096 Sep 25 13:27 test{noformat} So on Fedora 19, it will correctly change ownership of {{/var/spool/mail/}}, but it will fail to change {{/home/}} and will output this warning:{noformat}Failed to change ownership of the home directory{noformat}
Jira (PUP-3339) Puppet user provider failing to reset puppet uid on Fedora19 due to usermod bug
Title: Message Title Hailee Kenney updated an issue Puppet / PUP-3339 Puppet user provider failing to reset puppet uid on Fedora19 due to usermod bug Change By: Hailee Kenney This failure is showing up in the following acceptance test: acceptance/tests/config/puppet_manages_own_configuration_in_robust_manner.rb, but only on Fedora19. This test removes the puppet user/group and then confirms that the --mkusers flag allows the puppet master to recreate them. Before doing this, it records the current user/group state, and then in the final teardown step, reapplies the origina user/group state.The failure began showing up after a fix to this test in [1d3fc272|https://github.com/puppetlabs/puppet/commit/1d3fc2724c65c6fce455bc35a87b24b6c361205a] began halting the test if the final puppet apply to reset the puppet user/group failed. It is likely that this was always failing, but we only began to see it with this change.https://jenkins.puppetlabs.com/job/Puppet-Package-Acceptance-stable/label=beaker,platform=fedora19/61/I've attached a detailed log of the point of failure, but don't know why it's failing. *UPDATE:* After further investigation, this issue was found to be caused by a bug in the {{usermod}} command on Fedora 19. The bug does not appear to be present on Fedora 20. Since Fedora 19 is approaching end of life, we've decided not to fix this issue and just confine the acceptance test not to run on Fedora 19. The following output illustrates the bug which is causing the issue:After going through this on Fedora 19 and Fedora 20, Fedora 19 seems to have an issue with changing ownership of the home directory while Fedora 20 does not.So on Fedora 20:{noformat}[root@bd4849uiz04imoa ~]# usermod -u 1000 test[root@bd4849uiz04imoa ~]# cat /etc/passwdtest:x:1000:1000::/home/test:/bin/bash[root@bd4849uiz04imoa ~]# ls -l /home/drwxr-xr-x. 3 test test 4096 Sep 25 13:27 test[root@bd4849uiz04imoa ~]# ls -l /var/spool/mail/-rw-rw. 1 test mail 0 Sep 25 13:20 test[root@bd4849uiz04imoa ~]# usermod -u 53 test[root@bd4849uiz04imoa ~]# ls -l /home/drwxr-xr-x. 3 test test 4096 Sep 25 13:27 test[root@bd4849uiz04imoa ~]# ls -l /var/spool/mail/-rw-rw. 1 test mail 0 Sep 25 13:20 test{noformat}But then on Fedora 19:{noformat}[root@nykbnzgen65yxtt ~]# usermod -u 1000 test[root@nykbnzgen65yxtt ~]# cat /etc/passwdtest:x:1000:1000::/home/test:/bin/bash[root@nykbnzgen65yxtt ~]# ls -l /home/drwxr-xr-x. 3 test test 4096 Sep 25 13:27 test[root@nykbnzgen65yxtt ~]# ls -l /var/spool/mail/-rw-rw. 1 test mail 0 Sep 25 13:20 test[root@nykbnzgen65yxtt ~]# usermod -u 53 testusermod: Failed to change ownership of the home directory[root@nykbnzgen65yxtt ~]# ls -l /var/spool/mail/-rw-rw. 1 test mail 0 Sep 25 13:20 test[root@nykbnzgen65yxtt ~]# ls -l /home/drwxr-xr-x. 3 1000 test 4096 Sep 25 13:27 test{noformat}So on Fedora 19, it will correctly change ownership of {{/var/spool/mail/}}, but it will fail to change {{/home/}} and will output this warning:{noformat}Failed to change ownership of the home directory{noformat}
Jira (PUP-3336) Puppet defaults.rb doesn't split :libdir if multiple paths provided
Title: Message Title Andy Parker updated an issue Puppet / PUP-3336 Puppet defaults.rb doesn't split :libdir if multiple paths provided Change By: Andy Parker Fix Version/s: 4.0.0 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-3066) Services are started before flags are set
Title: Message Title Charlie Sharpsteen commented on an issue Re: Services are started before flags are set Jasper Lievisse Adriaanse: I see the original pull request was closed in favor of a re-write. Was this issue addressed by https://github.com/puppetlabs/puppet/pull/3017 ? Add Comment Puppet / PUP-3066 Services are started before flags are set The OpenBSD service provider is marked `flaggable` which means that `flags` may be passed which are written into `/etc/rc.conf.local`. These flags control the behaviour of the service when they're started. However it seems there's an issue in the ordering, the flags are written out to disk (flushed) _after_ the service is started. This means that the s... 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.co
Jira (PUP-3066) Services are started before flags are set
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3066 Services are started before flags are set Change By: Charlie Sharpsteen Assignee: Kylo Ginsberg Jasper Lievisse Adriaanse 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-3058) Broken images on vagrantcloud.com
Title: Message Title Charlie Sharpsteen commented on an issue Re: Broken images on vagrantcloud.com Just ran into the Debian 6 guest additions problem. Marking this as Accepted. Add Comment Puppet / PUP-3058 Broken images on vagrantcloud.com Hi. I use the http://vagrantcloud.com/puppetlabs images to test the community puppet modules I develop and I found 2 images with issues. * puppetlabs/centos-5.10-64-puppet the /etc/resolv.conf is hardcoded with puppet internal DNS * puppetlabs/debian-6.0.9-64-puppet The VirtualBox Guest additions was somehow installed that when I launch the vm ... 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 (PDB-813) Upgrade trapperkeeper & tk-jetty9 for JMX support and, fix certificate-whitelist
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-813 Upgrade trapperkeeper & tk-jetty9 for JMX support and, fix certificate-whitelist Change By: Kenneth Barber Summary: Upgrade trapperkeeper & tk-jetty9 for JMX support and , fix certificate-whitelist 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 (PDB-813) Upgrade trapperkeeper & tk-jetty9, fix certificate-whitelist
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-813 Upgrade trapperkeeper & tk-jetty9, fix certificate-whitelist Change By: Kenneth Barber Summary: Port certificate whitelist handling from PuppetDB into Upgrade trapperkeeper & tk - webserver- jetty9 , fix certificate-whitelist 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 (FACT-658) facter doesn't parse gnu uptime output
Title: Message Title Rahul Gopinath commented on an issue Re: facter doesn't parse gnu uptime output Merged in https://github.com/puppetlabs/facter/commit/797a07e6dcb4250c026b4879121d58f7ec859936 Add Comment Facter / FACT-658 facter doesn't parse gnu uptime output On Solaris if the user has changed there path to use the gnu utilities bin directory before /usr/bin facter will fail to output uptime information $ echo $PATH /usr/sbin:/usr/bin $ facter | grep uptime uptime => 1 day uptime_days => 1 uptime_hours => 46 uptime_seconds => 167460 $ PATH=/usr/gnu/bin:/usr/sbin:/usr/bin facter | grep uptime uptim... 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 (FACT-658) facter doesn't parse gnu uptime output
Title: Message Title Rahul Gopinath updated an issue Facter / FACT-658 facter doesn't parse gnu uptime output Change By: Rahul Gopinath Component/s: Community Fix Version/s: 3.0.0 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 (FACT-658) facter doesn't parse gnu uptime output
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-658 facter doesn't parse gnu uptime output Change By: Kylo Ginsberg Fix Version/s: 3.0.0 Fix Version/s: 2.3.0 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-3337) Validation of shell in user resource breaks when using sudo
Title: Message Title Kylo Ginsberg commented on an issue Re: Validation of shell in user resource breaks when using sudo Matching the underlying tool's behavior sounds good, although I don't know how to do that in abstract. Maybe a good-enough middle ground would be to tokenize the shell parameter and run the validation test against the first token? Add Comment Puppet / PUP-3337 Validation of shell in user resource breaks when using sudo We have an special user on our clients used to allow emergency logins if the user has lost his/hers smartcard. This user has a loginshell like this: "/usr/bin/sudo /usr/bin/emerg.sh" This worked fine before, but somewhere along the way a validation of the shell has been introduced which renders the error: "Shell /usr/bin/sudo /usr/bin/emerg.sh must 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 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 h
Jira (PUP-3075) Puppet client core dump when trying to configure more than 1005 vlans on Juniper device (Puppet client)
Title: Message Title Moses Mendoza commented on an issue Re: Puppet client core dump when trying to configure more than 1005 vlans on Juniper device (Puppet client) Kylo Ginsberg we do not currently support this commercially. We do not ship PE for Juniper. Add Comment Puppet / PUP-3075 Puppet client core dump when trying to configure more than 1005 vlans on Juniper device (Puppet client) Please refer log file for more details Puppet client getting configured when puppet is trying to configure vlans with vlan count greater than 1005 vlans. Pulling the config file from master which is having 1005 vlans to be configured on client. Notice: /Stage[main... 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 mor
Jira (PUP-3346) curl allows --insecure SSL connections
Title: Message Title Sean Knox created an issue Puppet / PUP-3346 curl allows --insecure SSL connections Issue Type: Bug Affects Versions: 3.7.1 Assignee: Kylo Ginsberg Components: Types and Providers Created: 25/Sep/14 6:26 PM Priority: Normal Reporter: Sean Knox The `appdmg` and `pkgdmg` providers were calling `curl` with `-k` which allows curl'ing over insecure HTTPS connections. I can't see why this would ever be desired, and many connections will often fail when attempting establish a connection. Add Comment
Jira (PDB-864) PR (138): Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini - robinbowes
Title: Message Title gepetto-bot commented on an issue Re: PR (138): Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini - robinbowes robinbowes commented: Damn, I thought I'd made the PE/parameterise changes. Will sort that and send updated PR. Add Comment PuppetDB / PDB-864 PR (138): Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini - robinbowes h2. Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini * Author: Robin Bowes* Company: YO61 Ltd * Github ID: [robinbowes|https://github.com/robinbowes] * [Pull Request 138 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/138] * [Pull Request 138 File Diff|https://github.com/puppetlab... 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
Jira (PUP-3346) curl allows --insecure SSL connections
Title: Message Title Sean Knox updated an issue Puppet / PUP-3346 curl allows --insecure SSL connections Change By: Sean Knox The `appdmg` and `pkgdmg` providers were calling `curl` with `-k` (alias for `--insecure`) which allows curl'ing over insecure HTTPS connections. I can't see why this would ever be desired, and many connections will often fail when attempting establish a connection. I have a PR removing the insecure option: https://github.com/puppetlabs/puppet/pull/3124 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-3075) Puppet client core dump when trying to configure more than 1005 vlans on Juniper device (Puppet client)
Title: Message Title Kylo Ginsberg commented on an issue Re: Puppet client core dump when trying to configure more than 1005 vlans on Juniper device (Puppet client) Hi Ganesh Nalawade, thanks for reporting this! We won't be able to act on this at Puppet Labs because this isn't a platform we test against or even have ready access to. That said, if you gather more information about this, please do report it here in case other users run into it. And of course, if you sort out a fix, we'd welcome a Pull Request with a solution. Thanks! Add Comment Puppet / PUP-3075 Puppet client core dump when trying to configure more than 1005 vlans on Juniper device (Puppet client) Please refer log file for more details Puppet client getting configured when puppet is trying to configure vlans with vlan count greater than 1005 vlans. Pulling the config file from master which is having 1005 vlans to be configured on client. Notice: /Stage[main... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3075) Puppet client core dump when trying to configure more than 1005 vlans on Juniper device (Puppet client)
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3075 Puppet client core dump when trying to configure more than 1005 vlans on Juniper device (Puppet client) Change By: Kylo Ginsberg Assignee: Kylo Ginsberg Ganesh Nalawade 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-3346) curl allows --insecure SSL connections
Title: Message Title Sean Knox updated an issue Puppet / PUP-3346 curl allows --insecure SSL connections Change By: Sean Knox Affects Version/s: 3.6.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-3346) curl allows --insecure SSL connections
Title: Message Title Sean Knox updated an issue Puppet / PUP-3346 curl allows --insecure SSL connections Change By: Sean Knox The `appdmg` and `pkgdmg` providers were calling ` {{ curl ` }} with `-k` (alias for `--insecure`) which allows curl'ing over insecure HTTPS connections. I can't see why this would ever be desired, and many connections will often fail when attempting establish a connection.I have a PR removing the insecure option: https://github.com/puppetlabs/puppet/pull/3124 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-3346) curl allows --insecure SSL connections
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3346 curl allows --insecure SSL connections Change By: Kylo Ginsberg Component/s: Community 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-3346) curl allows --insecure SSL connections
Title: Message Title Sean Knox updated an issue Puppet / PUP-3346 curl allows --insecure SSL connections Change By: Sean Knox The ` {{ appdmg ` }} and ` {{ pkgdmg ` }} providers were calling {{curl}} with ` {{ -k ` }} (alias for ` {{ --insecure ` }} ) which allows curl'ing over insecure HTTPS connections. I can't see why this would ever be desired, and many connections will often fail when attempting establish a connection.I have a PR removing the insecure option: https://github.com/puppetlabs/puppet/pull/3124 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-3346) curl allows --insecure SSL connections
Title: Message Title Sean Knox updated an issue Puppet / PUP-3346 curl allows --insecure SSL connections Change By: Sean Knox The {{appdmg}} and {{pkgdmg}} providers were calling {{curl}} with {{ \ -k}} (alias for {{--insecure}}) which allows curl'ing over insecure HTTPS connections. I can't see why this would ever be desired, and many connections will often fail when attempting establish a connection.I have a PR removing the insecure option: https://github.com/puppetlabs/puppet/pull/3124 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 (PDB-885) PR (1087): Add VPC support for acceptance test hosts for PuppetDB - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (1087): Add VPC support for acceptance test hosts for PuppetDB - kbarber pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/wyatt-ec2/1/ Add Comment PuppetDB / PDB-885 PR (1087): Add VPC support for acceptance test hosts for PuppetDB - kbarber h2. Add VPC support for acceptance test hosts for PuppetDB * Author: Ken Barber* Company: Puppet Labs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 1087 Discussion|https://github.com/puppetlabs/puppetdb/pull/1087] * [Pull Request 1087 File Diff|https://github.com/puppetlabs/puppetdb/pull/1087/files] h2. Pull 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
Jira (PDB-885) PR (1087): Add VPC support for acceptance test hosts for PuppetDB - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (1087): Add VPC support for acceptance test hosts for PuppetDB - kbarber wkalt commented: ^^ ignore that Add Comment PuppetDB / PDB-885 PR (1087): Add VPC support for acceptance test hosts for PuppetDB - kbarber h2. Add VPC support for acceptance test hosts for PuppetDB * Author: Ken Barber* Company: Puppet Labs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 1087 Discussion|https://github.com/puppetlabs/puppetdb/pull/1087] * [Pull Request 1087 File Diff|https://github.com/puppetlabs/puppetdb/pull/1087/files] h2. Pull 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://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2855) Puppet agent segfault on OSX Mavericks when puppet master is running under passenger
Title: Message Title Rudy McComb commented on an issue Re: Puppet agent segfault on OSX Mavericks when puppet master is running under passenger I can confirm that 10.9.5 upgrades Ruby to 2.0.0p481 from 2.0.0p451. This now allows many current versions of openssl to work with http.rb, and execute successful Puppet runs. This ticket can be closed. 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...@go
Jira (PUP-2771) service status field behaves exactly other way than documentation
Title: Message Title Stefan Schulte commented on an issue Re: service status field behaves exactly other way than documentation yes you are right. But if you just parse the process list you can actually just say service { 'my-service': ensure=> running, hasstatus => false, } And puppet will look for a process my-service (or use the pattern parameter if the process name differs from the service name). This should at least be easier to read. Do you think we can close the issue? Add Comment Puppet / PUP-2771 service status field behaves exactly other way than documentation
Jira (PUP-2940) Installing and using puppet with CentOS7 & RHEL7
Title: Message Title garrett honeycutt commented on an issue Re: Installing and using puppet with CentOS7 & RHEL7 Could not reproduce on CentOS 7. Will try RHEL7 tomorrow. Add Comment Puppet / PUP-2940 Installing and using puppet with CentOS7 & RHEL7 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 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.