Jira (PUP-2891) creating a resource override for a Class fails (future parser)
Title: Message Title Erik Daln commented on PUP-2891 Re: creating a resource override for a Class fails (future parser) arguably it should be allowed to add ordering dependencies this way though. Like require, before etc. As it doesn't change anything inside the class. But not terribly important to support as it works to add them using ordering arrows. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3753) Improve performance of zfs checks.
Title: Message Title Reinier Schoof created an issue Puppet / PUP-3753 Improve performance of zfs checks. Issue Type: Improvement Assignee: Unassigned Components: Puppet Server Created: 2014/12/09 1:14 AM Priority: Normal Reporter: Reinier Schoof We run machines on ZFS with relatively slow hard drives and relatively many filesystems (couple of hundred). When we want to manage ZFSes with Puppet, this is very slow. Investigation shows that for every Zfs resource the provider does a zfs list and then parses the output to see if a particular ZFS shows up. At least on our systems, this takes forever. I think I came up with a far more effective way of checking whether a ZFS exists or not. Tested by ensuring a ZFS, running puppet a couple of times seeing that it only creates it once, and when ensuring the resource to be absent, the ZFS was removed. before: Notice: Finished catalog run in 12946.60 seconds and after: Notice: Finished catalog run in 206.73 seconds Add Comment
Jira (PUP-1270) 'pkg' package provider does not understand IPS package versions properly
Title: Message Title
Lauri Tirkkonen commented on PUP-1270
Re: 'pkg' package provider does not understand IPS package versions properly
Josh, I think that's a separate bug in 'latest'. I am not seeing it on my test package, using puppet 87fad92f18966ea62544df16d251885794c5ec92 under OmniOS:
kekkonen ~/repos/puppet 141 % pkg list -vfa PUP-1270-test-package
FMRI IFO
pkg://niksula.hut.fi/PUP-1270-test-package@1.2,5.11-0.151006:20140930T124721Z i--
pkg://niksula.hut.fi/PUP-1270-test-package@1.2,5.11-0.151006:20140930T115744Z ---
pkg://niksula.hut.fi/PUP-1270-test-package@1.1,5.11:20140219T191731Z ---
pkg://niksula.hut.fi/PUP-1270-test-package@1.0,5.11-0.151006:20140220T084443Z ---
pkg://niksula.hut.fi/PUP-1270-test-package@1.0,5.11:20140219T191632Z ---
pkg://niksula.hut.fi/PUP-1270-test-package@1.0,5.11:20140219T191204Z ---
kekkonen ~/repos/puppet % RUBYLIB=`pwd`/lib pfexec ./bin/puppet apply --verbose -e 'package {PUP-1270-test-package: ensure = latest }'
Jira (PUP-3753) Improve performance of zfs checks.
Title: Message Title Reinier Schoof assigned an issue to Peter Huene Puppet / PUP-3753 Improve performance of zfs checks. Change By: Reinier Schoof Assignee: PeterHuene Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1059) PR (1172): (pdb-775) Retire old postgres versions - ajroetker
Title: Message Title gepetto-bot commented on PDB-1059 Re: PR (1172): (pdb-775) Retire old postgres versions - ajroetker kbarber commented: @ajroetker with your commit messages, make sure you use the capitalized form of the ticket number: (PDB-) foo. Otherwise, our automated PR-ticket software will create a new ticket: https://tickets.puppetlabs.com/browse/PDB-1059 ... that software is case sensitive it would seem. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1057) PR (156): (maint) Prune dead PE code - ajroetker
Title: Message Title gepetto-bot commented on PDB-1057 Re: PR (156): (maint) Prune dead PE code - ajroetker Pull request (maint) Prune dead PE code has been closed. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-158) Option to entirely disable update checking
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-158 Option to entirely disable update checking Change By: Kenneth Barber Fix Version/s: PDB3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-148) Support multiple backends of the same type
Title: Message Title
Martin Loy commented on HI-148
Re: Support multiple backends of the same type
+1 I have the same requirement of isolating data and to don't repeat it in every environment.
My current workaround at the moment, was to clone the yaml_backend.rb into yaml_defaults_backend.rb and define it with other datadir.
– :backends:
yaml
yaml_defaults
module_data :hierarchy:
% {clientcert}
% {environment} - common - defaults - credentials :yaml: :datadir: /etc/puppet/environments/%{environment}
/hiera
:yaml_defautls: :datadir: /etc/puppet/hiera
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
--
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-3127) LDAP - introduce LDAP-Certificat Directory
Title: Message Title Geoffrey Gardella commented on PUP-3127 Re: LDAP - introduce LDAP-Certificat Directory I managed to get a Solaris 10 system for testing. This does not appear to be under smf control in Solaris 10, but the directory was the same (/var/ldap). I don't see any documentation saying this is tunable. I suggest we set it to the default for Solaris 10. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 PDB-885 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/platform_puppetdb_intn-sys_pr/282/ Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 PDB-885 Re: PR (1087): Add VPC support for acceptance test hosts for PuppetDB - kbarber kbarber commented: Looks like beaker 2.0.0 has broken el7 for us: https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/282/ I'm seeing it in my own testing also for ezbake. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-715) LXC detection code raises errors on old OpenVZ
Title: Message Title Arnaud Gomes commented on FACT-715 Re: LXC detection code raises errors on old OpenVZ I filed pull request #825 on github. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3754) Better logging when fail to set ownership
Title: Message Title Neil Rickards created an issue Puppet / PUP-3754 Better logging when fail to set ownership Issue Type: Improvement Assignee: Unassigned Created: 2014/12/09 9:55 AM Priority: Minor Reporter: Neil Rickards If puppet fails to set the ownership of a logfile, the error message should include the file that failed Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (PDB-1060) Top-level extract requires fields with underscores instead of dashes
Title: Message Title Andrii Nikitiuk created an issue PuppetDB / PDB-1060 Top-level extract requires fields with underscores instead of dashes Issue Type: Bug Affects Versions: PDB 2.2.x Assignee: Unassigned Created: 2014/12/09 5:04 PM Priority: Normal Reporter: Andrii Nikitiuk Top-level extract fields are inconsistent with all other operators fields. They are inconsistent with responses too. Query example: curl -X GET http://localhost:8080/v4/reports --data-urlencode 'query=[extract,[transaction_uuid],[~,transaction-uuid,.*]]' Response:
Jira (PUP-3755) Catalogs are transformed to resources outside of node environments
Title: Message Title Charlie Sharpsteen created an issue Puppet / PUP-3755 Catalogs are transformed to resources outside of node environments Issue Type: Bug Affects Versions: PUP 3.7.0 Assignee: Henrik Lindberg Components: Server Created: 2014/12/09 6:56 PM Priority: Normal Reporter: Charlie Sharpsteen The master prepares a catalog for transmission to an agent by transforming it using the to_resource method. This call occurs outside of the context containing the agent's environment. This means that any resource operations involving the environment will use the master's 'default' environmant (almost always production unless set otherwise in puppet.conf). The resolution to PUP-1381 , released in 3.7.0, contains one such operation that involves the environment: a deprecation check. This check will force the default environment to load and can cause runs in other environments to fail if the default environment has any issues. Reproduction Case Setup
Jira (PUP-3755) Catalogs are transformed to resources outside of node environments
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3755 Catalogs are transformed to resources outside of node environments Change By: Charlie Sharpsteen Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3755) Catalogs are transformed to resources outside of node environments
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3755 Catalogs are transformed to resources outside of node environments Change By: Charlie Sharpsteen Labels: support Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3755) Catalogs are transformed to resources outside of node environments
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3755 Catalogs are transformed to resources outside of node environments Change By: Henrik Lindberg Fix Version/s: PUP3.7.4 Fix Version/s: PUP4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-2891) creating a resource override for a Class fails (future parser)
Title: Message Title Henrik Lindberg commented on PUP-2891 Re: creating a resource override for a Class fails (future parser) Erik Daln is this a regression? (Have not had time to check). While it can be argued that it should allow this, at this point we want the overrides to be backwards compatible. We are going to return to all catalog related expressions though. If it is a regression we should fix it to reduce breakage. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1805) Drop Ruby 1.8.7 support
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1805 Drop Ruby 1.8.7 support Change By: Kylo Ginsberg Epic Status: Done Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1625) Analyze unused modules
Title: Message Title Alex Harvey commented on PUP-1625 Re: Analyze unused modules Henrik Lindberg I need to develop a feature such as this for a project I'm working on, although enhancing Geppetto would take me too far afield. I'm intrigued by the idea of reusing the graphing subsystem though. If you or anyone else have any suggestions on how I could solve my problem and perhaps at the same time solve a portion of the enhancing Geppetto problem, I'd welcome the assistance and be more than happy to contribute the code. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1625) Analyze unused modules
Title: Message Title Alex Harvey commented on PUP-1625 Re: Analyze unused modules Henrik Lindberg I need to develop a feature such as this for a project I'm working on, although enhancing Geppetto would take me too far afield. I'm intrigued by the idea of reusing the graphing subsystem though. All I need is a tool that identifies classes that are defined but not declared anywhere, and I'm simply using site.pp for node classification. I then need to use that to identify data that exists in Hiera that isn't used by any class. If you or anyone else have any suggestions on how I could solve my problem and perhaps at the same time solve a portion of the enhancing Geppetto problem, I'd welcome the assistance and be more than happy to contribute the code. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3756) Don't try to chown log file destination when non-root
Title: Message Title
Josh Cooper created an issue
Puppet / PUP-3756
Don't try to chown log file destination when non-root
Issue Type:
Bug
Affects Versions:
PUP 3.7.3
Assignee:
Unassigned
Created:
2014/12/09 11:45 PM
Priority:
Normal
Reporter:
Josh Cooper
When puppet is using a log file destination, it will always try to chown owner and group to Puppet[:user] and Puppet[:group], which will fail when running as non-root:
$ bundle exec puppet apply --logdest /tmp/log -e notify { 'hello': }
$ less /tmp/log
2014-12-09 23:42:44 -0800 Puppet (err): Unable to set ownership of log file
Jira (PUP-3322) Add additional debugging to appdmg provider
Title: Message Title
Josh Cooper commented on PUP-3322
Re: Add additional debugging to appdmg provider
With manifest
package { 'Scratch':
ensure = installed,
source = 'http://download.scratch.mit.edu/MacScratch1.4.dmg',
provider = appdmg,
}
Puppet does warn when it downloads but does not install the package:
$ sudo bundle exec puppet apply scratch.pp --debug
...
Debug: Prefetching appdmg resources for package
Debug: Executing '/usr/bin/curl -o /tmp/d20141208-15694-is8sx/Scratch -C - -L -s --url http://download.scratch.mit.edu/MacScratch1.4.dmg'
