Jira (PUP-2643) Puppet Cron Resource Overwrites Crontab File Under Certain Situations
Title: Message Title Stefan Goethals updated an issue Puppet / PUP-2643 Puppet Cron Resource Overwrites Crontab File Under Certain Situations Change By: Stefan Goethals Affects Version/s: 3.6.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2908) service provider should default to upstart in RHEL6 and greater
Title: Message Title Kylo Ginsberg commented on an issue Re: service provider should default to upstart in RHEL6 and greater Jonathan Lynch FYI PUP-876 , which was fixed starting in 3.5.1, made upstart available on RHEL6, so you might want to try that out. However, that doesn't make upstart the default for RHEL6, though this should be straightforward. Adrien Thebo or William Hopper any thoughts on this one? (Btw, the 'and greater' in the description is probably incorrect - RHEL7 moved to systemd and puppet recently made it the default provider for RHEL7.) Add Comment Puppet / PUP-2908 service provider should default to upstart in RHEL6 and greater In RHEL6, init was replaced with upstart. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Technical_Notes/deployment.html In puppet, when osfamily = redhat,suse, the provider for the service type defaults to the redhat type, which uses chkconfig. http://docs.puppetlabs.com/references/latest/type.html#service-provider... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2940) Installing and using puppet with Centos7
Title: Message Title Mark Bell commented on an issue Re: Installing and using puppet with Centos7 Hi, I did not run any gem update commands or apply the puppetlabs/ruby module. Add Comment Puppet / PUP-2940 Installing and using puppet with Centos7 Hi, Has anyone successfully installed and used puppet on Centos7/RHEL7. I have added the EL7 Puppet labs repo and installed the RPM and its installing ruby from the CentOS base repo which is version 2.0, added the below dependancies that have been installed. However when trying to run commands I am getting the below. I had to install RVM with 1.9... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To 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-1244) Yum provider using version-release to validate installation.
Title: Message Title
Jason Antman commented on an issue
Re: Yum provider using version-release to validate installation.
Cool, thanks Andy Parker!
Add Comment
Puppet / PUP-1244
Yum provider using version-release to validate installation.
When using yum provider Puppet complains(error output) when using only the version(string) of the package to install or installed at the time of verification. {code} $snmp_version = 5.3.2.2 package { net-snmp: ensure = ${snmp_version}; } /pre Client output: pre debug: //Node[client.example.com]/snmp::base/Package[net-snmp]: Cha...
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-2905) When installing PIP packages from sources different than pypi, the install and any notifies are triggered during every run.
Title: Message Title
Alessio commented on an issue
Re: When installing PIP packages from sources different than pypi, the install and any notifies are triggered during every run.
I found that specifying the package name everything works properly again. e.g. package {editdist: ensure = present, provider = 'pip', source = https://py-editdist.googlecode.com/files/py-editdist-0.3.tar.gz, }
Can properly check with pip freeze that is installed.
This is a bit of workaround but we changed our configuration to something like this: package { HarvestingKit: ensure = present, provider = pip source = https://github.com/inspirehep/harvesting-kit/tarball/e163844543a6f3cf04369975645659334dac144c, }
And now the pip provider will work again because pip freeze will show the package name==version instead of the url
Add Comment
Puppet / PUP-2905
When installing PIP packages from sources different than pypi, the install and any notifies are triggered during every run.
I have a plugin for a Python application, Sentry, which I am installing via GitHub like so: package{ 'sentry-hipchat': ensure = 'cfac72b33dc8468745669ea65998a5b911e9aae0', provider = 'pip', source = 'git+git://github.com/invisiblehand/sentry-hipchat.git#39; } When running the Puppet agent with --debug --trace --test...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Markus Schuster commented on an issue Re: Not possible to manage SELinux file contexts via puppet in a sane way Might be a race condition but I don't think so. Usually our puppet agents run as daemon and all the file resources insist on changing SELinux file contexts back to the value they had at agents startup. So even the second and third (and so on...) run of the agent uses incorrect file contexts. You can even (manually or via pupet) run restorecon in between, puppet changes file contexts back. Our current workaround is to restart the puppet agent. Add Comment Puppet / PUP-2169 Not possible to manage SELinux file contexts via puppet in a sane way There's currently no sane way to manage SELinux file contexts using puppet. The only way is to call 'semanage' via a 'exec' resource. But then the next issue comes up: Puppet seems to keep some file context rule cache, built once at startup. I wasn't able to find a way to invalidate this cache without restarting the whole puppet agent. Even when calling '... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google
Jira (PUP-2945) Puppet Windows package provider warn when source =~ /\//
Title: Message Title Chris Spence created an issue Puppet / PUP-2945 Puppet Windows package provider warn when source =~ /\// Issue Type: Improvement Assignee: Unassigned Created: 17/Jul/14 5:43 AM Priority: Normal Reporter: Chris Spence Package installation/upgrade in Windows will probably fail if the source attribute path contains / Not sure of all the ins and outs here, but I think warning is sufficient - it the path ends up really not existing to msiexec etc then the resource will fail, and the warning will give a hint as to the cause. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-764) Malformed post-conditions in query.clj
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-764 Malformed post-conditions in query.clj Change By: Kenneth Barber Story Points: 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 (PDB-765) Puppetdb connexion to postgresql using client certificate
Title: Message Title Fabrice Bacchella created an issue PuppetDB / PDB-765 Puppetdb connexion to postgresql using client certificate Issue Type: Story Affects Versions: 2.1.0 Assignee: Unassigned Components: DOCS Created: 17/Jul/14 7:20 AM Priority: Minor Reporter: Fabrice Bacchella For people wanting to authenticate on a posgresql server, using a X509 client certificate, this procedure might help. This procedure does it in the java way, ie it take a jks store, not pem files. First create a jks with the private key for your account and put in it all the needed certificates in the chain (both server and user). The cn for user certificate should match the username used latter. Add to your JVM args : -Djavax.net.ssl.trustStore=.../puppetdb.jks -Djavax.net.ssl.trustStorePassword=JKS password -Djavax.net.ssl.keyStore=.../puppetdb.jks -Djavax.net.ssl.keyStorePassword=JKS password In case of problems, -Djavax.net.debug=ssl,defaultctx might help. My database.ini is : [database] classname = org.postgresql.Driver subprotocol = postgresql subname =
Jira (PDB-765) Puppetdb connexion to postgresql using client certificate
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-765 Puppetdb connexion to postgresql using client certificate Change By: Kenneth Barber Story Points: 1 Affects Version/s: 2.1.0 Issue Type: Story NewFeature 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-765) Puppetdb connexion to postgresql using client certificate
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-765 Puppetdb connexion to postgresql using client certificate Change By: Kenneth Barber Labels: trivial 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-764) Malformed post-conditions in query.clj
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-764 Malformed post-conditions in query.clj Change By: Kenneth Barber Labels: trivial 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-2946) FileUtils implementation broke compare_stream
Title: Message Title
Maksym Melnychok created an issue
Puppet / PUP-2946
FileUtils implementation broke compare_stream
Issue Type:
Bug
Affects Versions:
3.6.2
Assignee:
Kylo Ginsberg
Components:
Client
Created:
17/Jul/14 7:37 AM
Priority:
Normal
Reporter:
Maksym Melnychok
FileUtils#compare_stream implementation in ruby 1.9.3 was doing something along the lines of
a = b = nil while something a = as.read size b = bs.read size return false if a != b end
FileUtils#compare_stream in 2.0 instead does this:
a = b = while something as.read size, a bs.read size, b return false if a != b end
which is a problem since default encoding for strings is UTF-8 and when `File#read` reads into UTF-8 string it remains UTF-8 but when `StringIO#read` reads into UTF-8 string it becomes encoding of StringIO source string, which is ASCII for FileBucket::File contents.
This leads to problems with backing up files and under certain conditions gives errors like:
Error: Could not back up /bin/whatever.pyc: Got passed new contents for sum {md5}
ca60cf7b168557fb8c34be106b8c4ae8
Jira (PUP-2940) Installing and using puppet with Centos7
Title: Message Title Charlie Sharpsteen commented on an issue Re: Installing and using puppet with Centos7 Ruby is from CentOS Base, Puppet components are from yum.puppetlabs.com: Dependencies Resolved == Package ArchVersion RepositorySize == Installing: puppet noarch 3.6.2-1.el7 puppetlabs-products 1.2 M Installing for dependencies: augeas-libs x86_64 1.1.0-12.el7 base 327 k facter x86_64 1:2.1.0-1.el7 puppetlabs-products 89 k hiera noarch 1.3.4-1.el7 puppetlabs-products 23 k libselinux-ruby x86_64 2.2.2-6.el7 base 127 k pciutilsx86_64 3.2.1-4.el7 base 90 k rubyx86_64 2.0.0.353-20.el7 base 66 k ruby-augeas x86_64 0.4.1-3.el7 puppetlabs-deps 22 k ruby-irbnoarch 2.0.0.353-20.el7 base 87 k ruby-rgen noarch 0.6.5-2.el7 puppetlabs-deps 253 k ruby-shadow x86_64 1:2.2.0-2.el7 puppetlabs-deps 14 k rubygem-bigdecimal x86_64 1.2.0-20.el7 base 78 k rubygem-io-console x86_64 0.4.2-20.el7 base 49 k rubygem-jsonx86_64 1.7.7-20.el7 base 74 k rubygem-psych x86_64 2.0.0-20.el7 base 76 k rubygem-rdocnoarch 4.0.0-20.el7 base 317 k rubygemsnoarch 2.0.14-20.el7 base 211 k
Jira (PUP-2946) FileUtils implementation broke compare_stream
Title: Message Title Maksym Melnychok commented on an issue Re: FileUtils implementation broke compare_stream PR here: https://github.com/puppetlabs/puppet/pull/2881 Add Comment Puppet / PUP-2946 FileUtils implementation broke compare_stream FileUtils#compare_stream implementation in ruby 1.9.3 was doing something along the lines of a = b = nil while something a = as.read size b = bs.read size return false if a != b end FileUtils#compare_stream in 2.0 instead does this: a = b = while something as.read size, a bs.rea... 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-2946) FileUtils implementation broke compare_stream
Title: Message Title
Maksym Melnychok updated an issue
Puppet / PUP-2946
FileUtils implementation broke compare_stream
Change By:
Maksym Melnychok
{{ FileUtils # . compare_stream }} implementationinruby1.9.3wasdoingsomethingalongthelinesof {code:ruby} a=b=nilwhilesomethinga=as.readsizeb=bs.readsizereturnfalseifa!=bend {code} {{ FileUtils # . compare_stream }} in2.0insteaddoesthis: {code:ruby} a=b=whilesomethingas.readsize,abs.readsize,breturnfalseifa!=bend {code} whichisaproblemsincedefaultencodingforstringsisUTF-8andwhen ` {{ File#read ` }} readsintoUTF-8stringitremainsUTF-8butwhen ` {{ StringIO#read ` }} readsintoUTF-8stringitbecomesencodingofStringIOsourcestring,whichisASCIIfor {{ FileBucket::File }} contents.Thisleadstoproblemswithbackingupfilesandundercertainconditionsgiveserrorslike: {{ Error:Couldnotbackup/bin/whatever.pyc:Gotpassednewcontentsforsum{md5}ca60cf7b168557fb8c34be106b8c4ae8 }}
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-2946) FileUtils implementation broke compare_stream
Title: Message Title
Maksym Melnychok updated an issue
Puppet / PUP-2946
FileUtils implementation broke compare_stream
Change By:
Maksym Melnychok
{{FileUtils.compare_stream}}implementationinruby1.9.3wasdoingsomethingalongthelinesof{code:ruby}a=b=nilwhilesomethinga=as.readsizeb=bs.readsizereturnfalseifa!=bend{code}{{FileUtils.compare_stream}}in2.0insteaddoesthis:{code:ruby}a=b=whilesomethingas.readsize,abs.readsize,breturnfalseifa!=bend{code}whichisaproblemsincedefaultencodingforstringsisUTF-8andwhen{{File#read}}readsintoUTF-8stringitremainsUTF-8butwhen{{StringIO#read}}readsintoUTF-8stringitbecomesencodingofStringIOsourcestring,whichisASCIIfor{{FileBucket::File}}contents.Thisleadstoproblemswithbackingupfilesandundercertainconditionsgiveserrorslike:{{Error:Couldnotbackup/bin/whatever.pyc:Gotpassednewcontentsforsum \ {md5 \ }ca60cf7b168557fb8c34be106b8c4ae8}}
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-2882) PMT upgrade command returns an error when trying to upgrade a module with only one release
Title: Message Title
Ryan Coleman commented on an issue
Re: PMT upgrade command returns an error when trying to upgrade a module with only one release
Works for me, thank you. Adding as Should Have to https://confluence.puppetlabs.com/display/PROD/PMT+Improvements+for+PE+3.4?src="">.
Add Comment
Puppet / PUP-2882
PMT upgrade command returns an error when trying to upgrade a module with only one release
When you use the puppet module upgrade command to upgrade a module that has only one published release, it reports that there are no releases available for that module instead of telling you that you already have the latest version. {code} $ bin/puppet module install ghoneycutt/sysklogd Notice: Preparing to install into /Users/jesse/sandbox/puppet/...
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
Jira (PUP-2882) PMT upgrade command returns an error when trying to upgrade a module with only one release
Title: Message Title Ryan Coleman updated an issue Puppet / PUP-2882 PMT upgrade command returns an error when trying to upgrade a module with only one release Change By: Ryan Coleman Priority: Normal Minor 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-603) Facter acceptance should use our github mirror
Title: Message Title Josh Cooper commented on an issue Re: Facter acceptance should use our github mirror The following jobs are not using the mirror (due to reliance on EC2 coordinators), there may be others: https://jenkins.puppetlabs.com/view/Facter/view/Stable/job/Facter-Acceptance-Windows-stable/ https://jenkins.puppetlabs.com/view/Facter/view/Stable/job/Facter-Acceptance-Solaris-stable/ https://jenkins.puppetlabs.com/view/Facter/view/Stable/job/Facter-Specs-stable/ https://jenkins.puppetlabs.com/view/Facter/view/Master/job/Facter-Acceptance-Solaris-master/ https://jenkins.puppetlabs.com/view/Facter/view/Master/job/Facter-Acceptance-Windows-master/ Add Comment Facter / FACT-603 Facter acceptance should use our github mirror In the same way that we do puppet. This should be done after Facter 2.1 has been released in stable... sometime meaning perhaps a few weeks after it is released. 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
Jira (PUP-2882) PMT upgrade command returns an error when trying to upgrade a module with only one release
Title: Message Title Anderson Mills updated an issue Puppet / PUP-2882 PMT upgrade command returns an error when trying to upgrade a module with only one release Change By: Anderson Mills Story Points: 1 Fix Version/s: 3.7.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-2882) PMT upgrade command returns an error when trying to upgrade a module with only one release
Title: Message Title Anderson Mills updated an issue Puppet / PUP-2882 PMT upgrade command returns an error when trying to upgrade a module with only one release Change By: Anderson Mills Sprint: Week2014-7-9 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-1186) puppet module tool on windows will (sometimes) create a PaxHeader directory
Title: Message Title Brandon High commented on an issue Re: puppet module tool on windows will (sometimes) create a PaxHeader directory Merged to master, I've confirmed the fix on OSX by forcing it to use minitar but this still needs Windows confirmation. Add Comment Puppet / PUP-1186 puppet module tool on windows will (sometimes) create a PaxHeader directory In Puppet 3.2 the module tool started using minitar when the tar executable is not present. It turns out that minitar does not understand the [PAX](http://en.wikipedia.org/wiki/Pax_(Unix)) format. An example of a module that was created with this is [liamjbennet/win_facts v0.0.1](https://forge.puppetlabs.com/liamjbennett/win_facts/0.0.1). When that mod... 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-2752) Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format
Title: Message Title Brandon High commented on an issue Re: Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format Merged fix to master. New behavior is to warn about invalid semvers, default them to 0.0.0, and point maintainers at the semver docs. Here's example output after following the test case given in the description: Notice: Preparing to install into /Users/highb/.puppet/modules ... Warning: pound (/Users/highb/.puppet/modules/pound) has an invalid version number (0.1). The version has been set to 0.0.0. If you are the maintainer for this module, please update the metadata.json with a valid Semantic Version (http://semver.org). Notice: Downloading from https://forgeapi.puppetlabs.com ... Notice: Installing -- do not interrupt ... /Users/highb/.puppet/modules └── saz-rsyslog (v3.2.0) Add Comment Puppet / PUP-2752 Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format Since Puppet 3.6.0 the module tool is unable to install new modules if an already existing modules version does not conform to the MAJOR.MINOR.PATCH format. I believe this behaviour was introduced with the dependency resolver ( https://github.com/puppetlabs/puppet/commit/6fa68b54ac621d60dbf1b062f8dd66b186d1a87f ) How to reproduce problem: * Place a...
Jira (PUP-2882) PMT upgrade command returns an error when trying to upgrade a module with only one release
Title: Message Title Brandon High assigned an issue to Brandon High Puppet / PUP-2882 PMT upgrade command returns an error when trying to upgrade a module with only one release Change By: Brandon High Assignee: BrandonHigh 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-2947) Add a setting for second level environment (tier)
Title: Message Title Javier Palacios created an issue Puppet / PUP-2947 Add a setting for second level environment (tier) Issue Type: New Feature Assignee: Unassigned Created: 17/Jul/14 11:16 AM Priority: Normal Reporter: Javier Palacios In some environments it could be useful to have two simultaneous environment-alike variables to choose the manifests for a node. The use case is taken from the company I've just started to work for. We develop a complex application that is offered also by multiple partners (so, multiple simultaneous versions). That means that we have multiple qa/pre/prod sets, and as not every set run the same software version, thus potentially different module versions (mainly for our own apps), and we miss a finer grained grouping. Although we could use prod_partner as environment, it forces to get multiple copies of the same module+version, with overhead on puppet master management side. In this context I see really useful the tier setting, with a a module path like '$confdir/$environment/$tier/modules'. I've tried this with a simple approach with the new setting and basic tests(on https://github.com/javiplx/puppet/pull/3), although I have no real idea how could I extend the tests to parts like directory based environments nor how it could impact on other puppet areas. Add Comment
Jira (PUP-1186) puppet module tool on windows will (sometimes) create a PaxHeader directory
Title: Message Title John Duarte updated an issue Puppet / PUP-1186 puppet module tool on windows will (sometimes) create a PaxHeader directory Change By: John Duarte QA Contact: EricThompson JohnDuarte QA Status: Reviewed 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-2752) Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format
Title: Message Title John Duarte updated an issue Puppet / PUP-2752 Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format Change By: John Duarte QA Contact: EricThompson JohnDuarte QA Status: Reviewed 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-2745) Puppet 3.6.1 issue with Forge API v3
Title: Message Title John Duarte updated an issue Puppet / PUP-2745 Puppet 3.6.1 issue with Forge API v3 Change By: John Duarte QA Contact: EricThompson JohnDuarte QA Status: Reviewed 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-2078) Puppet module install --force does not re-install dependencies
Title: Message Title John Duarte updated an issue Puppet / PUP-2078 Puppet module install --force does not re-install dependencies Change By: John Duarte QA Contact: KurtWall JohnDuarte QA Status: Reviewed 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-2040) Allow excluding content from Puppet module tool built packages
Title: Message Title John Duarte updated an issue Puppet / PUP-2040 Allow excluding content from Puppet module tool built packages Change By: John Duarte QA Contact: EricThompson JohnDuarte QA Status: Reviewed 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-2079) puppet module generate can't copy template files without parsing/renaming them
Title: Message Title John Duarte updated an issue Puppet / PUP-2079 puppet module generate can't copy template files without parsing/renaming them Change By: John Duarte QA Contact: EricThompson JohnDuarte 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-2079) puppet module generate can't copy template files without parsing/renaming them
Title: Message Title John Duarte updated an issue Puppet / PUP-2079 puppet module generate can't copy template files without parsing/renaming them Change By: John Duarte QA Status: Reviewed 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-2882) PMT upgrade command returns an error when trying to upgrade a module with only one release
Title: Message Title John Duarte updated an issue Puppet / PUP-2882 PMT upgrade command returns an error when trying to upgrade a module with only one release Change By: John Duarte QA Contact: EricThompson JohnDuarte QA Status: Reviewed 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-777) Start deprecating 'versionRequirement' per code comment
Title: Message Title John Duarte updated an issue Puppet / PUP-777 Start deprecating 'versionRequirement' per code comment Change By: John Duarte QA Contact: KurtWall JohnDuarte QA Status: Reviewed 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-2935) Error deserializing JSON in CentOS
Title: Message Title
Andy Parker commented on an issue
Re: Error deserializing JSON in CentOS
Here is the stacktrace:
be puppet apply --catalog client1-catalog.json --trace
Error: Could not run: Could not deserialize catalog from pson: Could not intern from pson: Could not intern from data: Could not find relationship target Notify[{\type\=\A\}]
/Users/andy/work/puppet/lib/puppet/resource/catalog.rb:356:in `from_data_hash'
/Users/andy/work/puppet/lib/puppet/resource/catalog.rb:348:in `each'
/Users/andy/work/puppet/lib/puppet/resource/catalog.rb:348:in `from_data_hash'
/Users/andy/work/puppet/lib/puppet/util/pson.rb:11:in `pson_create'
/Users/andy/work/puppet/lib/puppet/external/pson/pure/parser.rb:305:in `parse_object'
/Users/andy/work/puppet/lib/puppet/external/pson/pure/parser.rb:98:in `parse'
/Users/andy/work/puppet/lib/puppet/external/pson/common.rb:133:in `parse'
/Users/andy/work/puppet/lib/puppet/network/formats.rb:143:in `intern'
/Users/andy/work/puppet/lib/puppet/network/format_support.rb:12:in `convert_from'
/Users/andy/work/puppet/lib/puppet/application/apply.rb:284:in `read_catalog'
/Users/andy/work/puppet/lib/puppet/application/apply.rb:162:in `apply'
/Users/andy/work/puppet/lib/puppet/application/apply.rb:150:in `run_command'
/Users/andy/work/puppet/lib/puppet/application.rb:384:in `run'
/Users/andy/work/puppet/lib/puppet/application.rb:510:in `plugin_hook'
/Users/andy/work/puppet/lib/puppet/application.rb:384:in `run'
/Users/andy/work/puppet/lib/puppet/util.rb:479:in `exit_on_fail'
/Users/andy/work/puppet/lib/puppet/application.rb:384:in `run'
/Users/andy/work/puppet/lib/puppet/util/command_line.rb:146:in `run'
/Users/andy/work/puppet/lib/puppet/util/command_line.rb:92:in `execute'
/Users/andy/work/puppet/bin/puppet:8
/Users/andy/work/puppet/.bundle/gems/ruby/1.8/bin/puppet:23:in `load'
/Users/andy/work/puppet/.bundle/gems/ruby/1.8/bin/puppet:23
Add Comment
Puppet / PUP-2935
Error deserializing JSON in CentOS
Jira (PUP-2691) Real-world module skeletons still use the 'description' metadata property
Title: Message Title John Duarte updated an issue Puppet / PUP-2691 Real-world module skeletons still use the 'description' metadata property Change By: John Duarte QA Contact: EricThompson JohnDuarte QA Status: Reviewed 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-2935) Error deserializing JSON in CentOS
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Error deserializing JSON in CentOS
So, what is happening here is that when a hash is used as a resource title, it is deserialized from the catalog as a string under Ruby 1.8.7:
Notify[typeA]
Under Ruby 1.9, the resource title is de-serialized as a hash:
Notify[{type=A}]
I think the core of the issue here is that the behavior of setting a resource title to a Hash instead of a String is not defined. The language docs say:
The title is an identifying string.
So, setting the title of a resource to a Hash could be resulting in undefined behavior.
adrian: Could you provide the Puppet manifest that produced this example catalog?
Add Comment
Puppet / PUP-2935
Error deserializing JSON in CentOS
With that environment, if I execute: {code} # puppet apply --catalog client1-catalog.json Error: Could not run: Could not deserialize catalog from pson: Could not intern from pson: Could not intern from data: Could not find relationship target Notify[{\type\=\A\}] {code} If I execute in Ubuntu 14.04 with Puppet 3.6.2 ruby-json 1.8.0-1build...
Jira (PUP-2935) Error deserializing JSON in CentOS
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2935 Error deserializing JSON in CentOS Change By: Charlie Sharpsteen Assignee: AndyParker adrian 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-2935) De-serializing resource title hashes from PSON raises an error under Ruby 1.8.7
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2935 De-serializing resource title hashes from PSON raises an error under Ruby 1.8.7 Change By: Charlie Sharpsteen Summary: ErrordeserializingJSONinCentOS De-serializingresourcetitlehashesfromPSONraisesanerrorunderRuby1.8.7 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2944) yum provider should use osfamily instead of operatingsystem fact
Title: Message Title garrett honeycutt commented on an issue Re: yum provider should use osfamily instead of operatingsystem fact PR - https://github.com/puppetlabs/puppet/pull/2882 Add Comment Puppet / PUP-2944 yum provider should use osfamily instead of operatingsystem fact The yum provider for the package type uses the operatingsystem fact to specify the defaultfor and should be using the osfamily fact so that we do not have to duplicate effort listing all the RedHat derivatives in both places. 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-2948) Enable rubocop for PRs in Github
Title: Message Title Rahul Gopinath created an issue Puppet / PUP-2948 Enable rubocop for PRs in Github Issue Type: Task Affects Versions: 4.x Assignee: Rahul Gopinath Components: Client Created: 17/Jul/14 1:29 PM Fix Versions: 4.0.0 Labels: github Priority: Normal Reporter: Rahul Gopinath Once PR-2909 is complete, we need to enable rubocop for PRs in Github. As of now, we should probably integrate rubocop verification into the TravisCI for Puppet.
Jira (PUP-2949) Enable rubocop verification in Jenkins
Title: Message Title Rahul Gopinath created an issue Puppet / PUP-2949 Enable rubocop verification in Jenkins Issue Type: Task Affects Versions: 4.x Assignee: Rahul Gopinath Components: Client Created: 17/Jul/14 1:31 PM Fix Versions: 4.0.0 Labels: github Priority: Normal Reporter: Rahul Gopinath Once PUP-2909 is complete, we should integrate rubocop task to Jenkins
Jira (PDB-711) Factset endpoint for simplifying structure fact export and full retrieval
Title: Message Title Kenneth Barber assigned an issue to Wyatt Alt PuppetDB / PDB-711 Factset endpoint for simplifying structure fact export and full retrieval Change By: Kenneth Barber Assignee: WyattAlt 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-2950) Enable rubocop:Style/AndOr
Title: Message Title Rahul Gopinath created an issue Puppet / PUP-2950 Enable rubocop:Style/AndOr Issue Type: Task Affects Versions: 4.x Assignee: Rahul Gopinath Components: Client Created: 17/Jul/14 1:33 PM Fix Versions: 4.0.0 Labels: github Priority: Normal Reporter: Rahul Gopinath Enable the Rubocop Style/AndOr cop which bans the use of keywords 'and' and 'or'
Jira (FACT-622) changes to ordering in custom facts breaks things
Title: Message Title Tim Hartmann commented on an issue Re: changes to ordering in custom facts breaks things Crap, and my super cool hacky fix of renaming the fact.rb file didn't seem to work after all.. (sadpanda) Add Comment Facter / FACT-622 changes to ordering in custom facts breaks things *edit* Looks like this also exists in 2.0.1 - so this may just mean that our custom facts aren't backwards compatible with the new loading logic. Is there a way to order facts if they are sourced from two different files, so that one depends correctly on the other, without filename precedence? *edit* We have a set of custom fact called node_type.rb whi... 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-622) changes to ordering in custom facts breaks things
Title: Message Title Eric Sorenson commented on an issue Re: changes to ordering in custom facts breaks things William Hopper or Adrien Thebo does this report make sense to your understanding of the Facter 2 changes? Is there an explicit way to do the ordering Tim is trying to achieve? Add Comment Facter / FACT-622 changes to ordering in custom facts breaks things *edit* Looks like this also exists in 2.0.1 - so this may just mean that our custom facts aren't backwards compatible with the new loading logic. Is there a way to order facts if they are sourced from two different files, so that one depends correctly on the other, without filename precedence? *edit* We have a set of custom fact called node_type.rb whi... 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-2947) Add a setting for second level environment (tier)
Title: Message Title Javier Palacios commented on an issue Re: Add a setting for second level environment (tier) You were right supposing that I pretended to sent tier from agent to master. Actually, I see that setting as only suitable for the [agent] section. I now that the prod_partner can solve my problem, but I would like not to get the overhead. More than 90% of the puppet modules/code is actually common to all prod or can be managed with hiera without big problems (that's even true for the qa/pre/prod sets). Add Comment Puppet / PUP-2947 Add a setting for second level environment (tier) In some environments it could be useful to have two simultaneous environment-alike variables to choose the manifests for a node. The use case is taken from the company I've just started to work for. We develop a complex application that is offered also by multiple partners (so, multiple simultaneous versions). That means that we have multiple qa/pre/pr... 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
Jira (PUP-2908) service provider should default to upstart in RHEL6 and greater
Title: Message Title
Jonathan Lynch commented on an issue
Re: service provider should default to upstart in RHEL6 and greater
The default is the real issue, because otherwise in a diverse environment I have to basically recreate puppet's logic, e.g.
if $osfamily == 'redhat' { if $operatingsystemmajrelease = 5 { $serviceprovider = 'redhat' }
else { $serviceprovider = 'upstart' }
} if $osfamily == 'ubuntu' { etc... }
service { 'vmware-tools': enable = true, ensure = running, provider = $serviceprovider, }
I can't just take the default because RHEL6 breaks, but if I'm going to make it a variable I have to recreate the entire logic. I suppose I could work around this by
service { 'vmware-tools': enable = true, ensure = running, }
if $osfamily == 'redhat' and $operatingsystemmajrelease == 6 { service { 'vmware-tools': enable = true, ensure = running, provider = upstart, }
}
Add Comment
Puppet / PUP-2908
service provider should default to upstart in RHEL6 and greater
In RHEL6, init was replaced with upstart. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Technical_Notes/deployment.html In puppet, when osfamily = redhat,suse, the provider for the service type defaults to the redhat type, which uses chkconfig. http://docs.puppetlabs.com/references/latest/type.html#service-provider...
Jira (FACT-623) add BSD interface alias support
Title: Message Title Adrien Thebo created an issue Facter / FACT-623 add BSD interface alias support Issue Type: Bug Assignee: Eric Sorenson Components: Community Created: 17/Jul/14 2:35 PM Labels: bsd network alias Priority: Normal Reporter: Adrien Thebo Output with patch: # facter | grep -E 'ip|alias' ipaddress = 174.36.235.173 ipaddress_em0 = 10.24.8.72 ipaddress_em1 = 174.36.235.173 ipaddress_em1_alias0 = 208.43.110.204 ipaddress_em1_alias1 = 208.43.110.205 ipaddress_em1_alias2 = 208.43.110.206 ipaddress_em1_alias3 = 208.43.110.207 ipaddress_lo0 = 127.0.0.1 netmask_em1_alias0 = 255.255.255.0 netmask_em1_alias1 = 255.255.255.0 netmask_em1_alias2 = 255.255.255.0 netmask_em1_alias3 = 255.255.255.0 Output currently (no patch): # facter | grep -E 'ip|alias' ipaddress = 174.36.235.173 ipaddress_em0 = 10.24.8.72 ipaddress_em1 = 174.36.235.173 ipaddress_lo0 = 127.0.0.1
Jira (FACT-623) add BSD interface alias support
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Facter / FACT-623 add BSD interface alias support Change By: Adrien Thebo Assignee: AdrienThebo 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-2944) yum provider should use osfamily instead of operatingsystem fact
Title: Message Title Charlie Sharpsteen commented on an issue Re: yum provider should use osfamily instead of operatingsystem fact Kylo Ginsberg: Any thoughts about getting this one into the backlog? This can result in some very surprising errors and would be nice to get into the next Puppet release. Garrett's patch should be backwards compatible, so I've opened PR 2883 targeted at stable. Add Comment Puppet / PUP-2944 yum provider should use osfamily instead of operatingsystem fact The yum provider for the package type uses the operatingsystem fact to specify the defaultfor and should be using the osfamily fact so that we do not have to duplicate effort listing all the RedHat derivatives in both places. 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-2944) yum provider should use osfamily instead of operatingsystem fact
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2944 yum provider should use osfamily instead of operatingsystem fact Change By: Charlie Sharpsteen Assignee: KyloGinsberg 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-2732) Validation of Exec-Attribute user limits usability with non-root user.
Title: Message Title
Andy Parker commented on an issue
Re: Validation of Exec-Attribute user limits usability with non-root user.
Merged fixes from PR 2884 into master in bdb0f4.
Add Comment
Puppet / PUP-2732
Validation of Exec-Attribute user limits usability with non-root user.
Our customer will only use Puppet if all necessary operations are possible running Puppet without root privileges. Actually Puppet agent validates the user attribute of exec ressource that way, that it's fully unsupported if running without root user. Doing so, the following error message is printed and execution aborted: {code} Error: Failed to apply c...
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-2951) Add static analysis of ruby code
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-2951 Add static analysis of ruby code Issue Type: Epic Assignee: Unassigned Created: 17/Jul/14 3:39 PM Priority: Normal Reporter: Kylo Ginsberg 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-2949) Enable rubocop verification in Jenkins
Title: Message Title Kylo Ginsberg commented on an issue Re: Enable rubocop verification in Jenkins Roger Ignazio can you work with Rahul Gopinath on this ticket? It will be a new job, only against puppet-4. Maybe in parallel with specs, or downstream from them - worth discussion on puppet-dev. Add Comment Puppet / PUP-2949 Enable rubocop verification in Jenkins Once PUP-2909 is complete, we should integrate rubocop task to Jenkins 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-2945) Puppet Windows package provider warn when source =~ /\//
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2945 Puppet Windows package provider warn when source =~ /\// Change By: Rob Reynolds Component/s: Community Component/s: Client 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-2945) Puppet Windows package provider warn when source =~ /\//
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2945 Puppet Windows package provider warn when source =~ /\// Change By: Rob Reynolds Labels: trivialwindows 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-2945) Puppet Windows package provider warn when source =~ /\//
Title: Message Title Rob Reynolds commented on an issue Re: Puppet Windows package provider warn when source =~ /\// It would be better to just go ahead and implement https://tickets.puppetlabs.com/browse/PUP-398 - then there is no warning at all. Add Comment Puppet / PUP-2945 Puppet Windows package provider warn when source =~ /\// Package installation/upgrade in Windows will probably fail if the source attribute path contains / Not sure of all the ins and outs here, but I think warning is sufficient - it the path ends up really not existing to msiexec etc then the resource will fail, and the warning will give a hint as to the cause. 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-2909) Incorporate linting and static verification with rubocop
Title: Message Title Kylo Ginsberg commented on an issue Re: Incorporate linting and static verification with rubocop Moved this to Ready for CI. But to be clear this is only needs to pass regular, existing CI. PUP-2949 is the follow-on ticket to add a CI Jenkins job. Add Comment Puppet / PUP-2909 Incorporate linting and static verification with rubocop Enable Rubocop static verification and linting in puppet 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-398) Backslashify windows paths when appropriate
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-398 Backslashify windows paths when appropriate Change By: Rob Reynolds Component/s: Client 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-398) Backslashify windows paths when appropriate
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-398 Backslashify windows paths when appropriate Change By: Rob Reynolds WheninstallinganMSI,thewindowspackageproviderpassesthepackagesourceparametertomsiexec.exe.Unfortunately,itbmust/busebackslashes,otherwise,msiexecthinksit'sacommandlineargumentandwillfailwithacrypticerror:preFailedtoinstall:FailonINT24./preThewindowspackageprovidershouldautomaticallyconvertthesourcetobackslashessothatitjustworks. 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-2918) puppet module build gives unhelpful error message
Title: Message Title Anderson Mills updated an issue Puppet / PUP-2918 puppet module build gives unhelpful error message Change By: Anderson Mills Sprint: Week2014-7-9 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-2935) De-serializing resource title hashes from PSON raises an error under Ruby 1.8.7
Title: Message Title
adrian commented on an issue
Re: De-serializing resource title hashes from PSON raises an error under Ruby 1.8.7
These are the three manifest involved. https://gist.github.com/b9605efeab711ea2e1bc
The idea is pass a json to monitorizacion::checks::collectd params parameter. This json contains one array (Threshold), where the user could define several different thresholds. In ruby or other programming language I will use a loop to go over the array and generate each of the thresholds. As this is difficult in puppet I use the idea seen here: https://tobrunet.ch/2013/01/iterate-over-datastructures-in-puppet-manifests/ When a array is passed to a defined type, it is executed once per element.
Inside each threshold object there is another array, and the same strategy is used, sending to a defined type to go over all elements of the array.
Also I have to insert and id element to avoid duplicated resources (for example if two different thresholds have the same type with same parameters).
P.D.: any constructive criticism is welcome
Add Comment
Puppet / PUP-2935
De-serializing resource title hashes from PSON raises an error under Ruby 1.8.7
With that environment, if I execute: {code} # puppet apply --catalog client1-catalog.json Error: Could not run: Could not deserialize catalog from pson: Could not intern from pson: Could not intern from data: Could not find relationship target Notify[{\type\=\A\}] {code} If I execute in Ubuntu 14.04 with Puppet 3.6.2 ruby-json 1.8.0-1build...
Jira (PUP-2952) Puppet should only log facts in debug mode
Title: Message Title William Van Hevelingen created an issue Puppet / PUP-2952 Puppet should only log facts in debug mode Issue Type: Bug Assignee: Unassigned Created: 17/Jul/14 4:22 PM Priority: Normal Reporter: William Van Hevelingen 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-2952) Puppet should only log facts in debug mode
Title: Message Title
William Van Hevelingen updated an issue
Puppet / PUP-2952
Puppet should only log facts in debug mode
Change By:
William Van Hevelingen
Inenvironmentswithlotsoffactspuppetagentcanfillthescreenandlogfileswithloadingfactmessages.Thisisonlyusefulwhendebuggingandshouldthusbeonlyenabledwhenindebugmode.{code}rickon:~#puppetagent--testInfo:RetrievingpluginInfo:Loadingfactsin/var/lib/puppet/lib/facter/facter_dot_d.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/thunderbird_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/rabbitmq_erlang_cookie.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/is_lxc.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/collectd_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/puppet_vardir.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/staging_windir.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/root_home.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/sunray.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/concat_basedir.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/dns_ip_4.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/iptables_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/raidtype.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/staging_http_get.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/kernel_type.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/iptables_persistent_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/dns_ip_6.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/hardware_platform.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/pe_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/ganeti_cluster.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/dept.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/nvidia_graphics_device.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/os_maj_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/ip6tables_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/raid_devices.rbInfo:Cachingcatalogforrickon.cat.pdx.edu{code}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-605) facter incorrectly filters localhost and link-local IPv6 addresses when creating interface-specific ipaddress6 facts
Title: Message Title Matthew Pounsett updated an issue Facter / FACT-605 facter incorrectly filters localhost and link-local IPv6 addresses when creating interface-specific ipaddress6 facts Change By: Matthew Pounsett Summary: facter ignoresRFC4193ULAs incorrectlyfilterslocalhostandlink-localIPv6addresses whencreatinginterface-specificipaddress6facts 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-2953) masterlog setting is dead code
Title: Message Title Nicholas Fagerlund created an issue Puppet / PUP-2953 masterlog setting is dead code Issue Type: Bug Assignee: Unassigned Created: 17/Jul/14 5:20 PM Priority: Normal Reporter: Nicholas Fagerlund http://docs.puppetlabs.com/references/latest/configuration.html#masterlog Where puppet master logs. This is generally not used, since syslog is the default log destination. If you ack the Puppet source, you'll see that this setting is never referenced by any other area of code. It's dead, Jim. (The similar puppetdlog setting – http://docs.puppetlabs.com/references/latest/configuration.html#puppetdlog – is apparently only used on systems that are neither POSIX nor Windows.) Add Comment This
Jira (PUP-2952) Puppet should only log facts in debug mode
Title: Message Title
William Van Hevelingen updated an issue
Puppet / PUP-2952
Puppet should only log facts in debug mode
Change By:
William Van Hevelingen
Inenvironmentswithlotsoffactspuppetagentcanfillthescreenandlogfileswithloadingfactmessages.Thisisonlyusefulwhendebuggingandshouldthusbeonlyenabledwhenindebugmode.{code}rickon:~#puppetagent--testInfo:RetrievingpluginInfo:Loadingfactsin/var/lib/puppet/lib/facter/facter_dot_d.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/thunderbird_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/rabbitmq_erlang_cookie.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/is_lxc.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/collectd_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/puppet_vardir.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/staging_windir.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/root_home.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/sunray.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/concat_basedir.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/dns_ip_4.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/iptables_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/raidtype.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/staging_http_get.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/kernel_type.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/iptables_persistent_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/dns_ip_6.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/hardware_platform.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/pe_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/ganeti_cluster.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/dept.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/nvidia_graphics_device.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/os_maj_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/ip6tables_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/raid_devices.rbInfo:Cachingcatalogforrickon.cat.pdx.edu Info:Applyingconfigurationversion'1405637813'Notice:Finishedcatalogrunin14.01seconds {code}Withthepatchapplied{code} yoruichi rickon :~#puppetagent-tInfo:RetrievingpluginInfo:Cachingcatalogfor yoruichi rickon .cat.pdx.eduInfo:Applyingconfigurationversion'1405637813'Notice:Finishedcatalogrunin14.01seconds{code}
Add Comment
Jira (PUP-2881) Upgrade win32-taskscheduler (or replace)
Title: Message Title Ethan Brown updated an issue Puppet / PUP-2881 Upgrade win32-taskscheduler (or replace) Change By: Ethan Brown 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 (FACT-614) Create structured operating system fact
Title: Message Title
William Hopper commented on an issue
Re: Create structured operating system fact
Pull request is live at https://github.com/puppetlabs/facter/pull/732 !
Add Comment
Facter / FACT-614
Create structured operating system fact
Currently, there are several facts related to operating system based data, including: {noformat} operatingsystem operatingsystemmajrelease operatingsystemrelease osfamily {noformat} Also, there are a handful of lsb* facts for Linux systems, including: {noformat} lsbdistcodename lsbdistdescription lsbdistid lsbdistrelease lsbmajdistrele...
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-2908) service provider should default to upstart in RHEL6 and greater
Title: Message Title Kylo Ginsberg commented on an issue Re: service provider should default to upstart in RHEL6 and greater Jonathan Lynch that makes total sense. Offhand, I would think we could do something that pretty much looks like what we did to make systemd the default service provider for RHEL7 in commit 0b5cbc. William Hopper this is the commit I mentioned in passing earlier today. Add Comment Puppet / PUP-2908 service provider should default to upstart in RHEL6 and greater In RHEL6, init was replaced with upstart. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Technical_Notes/deployment.html In puppet, when osfamily = redhat,suse, the provider for the service type defaults to the redhat type, which uses chkconfig. http://docs.puppetlabs.com/references/latest/type.html#service-provider... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To
Jira (PUP-2908) service provider should default to upstart in RHEL6 and greater
Title: Message Title William Hopper commented on an issue Re: service provider should default to upstart in RHEL6 and greater Thanks, Kylo Ginsberg! I'll take the deep dive into puppet tomorrow morning and see if I can get a PR up for this! Add Comment Puppet / PUP-2908 service provider should default to upstart in RHEL6 and greater In RHEL6, init was replaced with upstart. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Technical_Notes/deployment.html In puppet, when osfamily = redhat,suse, the provider for the service type defaults to the redhat type, which uses chkconfig. http://docs.puppetlabs.com/references/latest/type.html#service-provider... 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-2944) yum provider should use osfamily instead of operatingsystem fact
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2944 yum provider should use osfamily instead of operatingsystem fact Change By: Kylo Ginsberg Fix Version/s: 3.7.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-2924) Puppet searches disk for whit classes
Title: Message Title Peter Bakkum commented on an issue Re: Puppet searches disk for whit classes Tried this out by running time puppet apply --verbose --debug oursite.pp before and after applying the patch. I ran 5 times and averaged the output, here is the improvement we see. real 19.9044 - 18.5814 6.6% user 10.3344 - 9.7594 5.9% sys3.999 - 3.440816.2% So system time went from 4s to 3.44s for a 16% improvement. Not a massive win but definitely in the right direction. What IS nice is the number of stat calls for our instance went from 49,936 before to 39,100 after, so big improvement there. That probably explains why there's so much less system time. This seems like an easy win, hope you guys can release it soon. Thanks for digging in. Add Comment Puppet / PUP-2924 Puppet searches disk for whit classes Our Puppet instance has been pretty slow lately so we traced a puppet agent run to see what it was doing. In the trace we see a bunch of lines like this: stat(/opt/local/lib/ruby/site_ruby/2.0.0/puppet/vendor/semantic/lib/puppet/type/completed_stage.rb, 0xFD7FFFDFE4A0) Err#2 ENOENT stat(/etc/puppet/modules/admin/lib/puppet/type/completed_stage
Jira (PUP-1916) puppet cert clean cannot remove signing requests
Title: Message Title Stefan Lasiewski updated an issue Puppet / PUP-1916 puppet cert clean cannot remove signing requests Change By: Stefan Lasiewski Affects Version/s: 3.6.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2944) yum provider should use osfamily instead of operatingsystem fact
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2944 yum provider should use osfamily instead of operatingsystem fact Change By: Kylo Ginsberg Story Points: 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-2944) yum provider should use osfamily instead of operatingsystem fact
Title: Message Title Kylo Ginsberg commented on an issue Re: yum provider should use osfamily instead of operatingsystem fact I'm +1 on this. Looks like completely the right thing to do. Marked for 3.7. Add Comment Puppet / PUP-2944 yum provider should use osfamily instead of operatingsystem fact The yum provider for the package type uses the operatingsystem fact to specify the defaultfor and should be using the osfamily fact so that we do not have to duplicate effort listing all the RedHat derivatives in both places. 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.
