Jira (PUP-1318) Provide a logoutput for service like exec
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1318
Provide a logoutput for service like exec
Issue Type:
New Feature
Assignee:
Unassigned
Created:
31/Dec/13 12:19 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
If I have a service defined that fails, and the service does not log anywhere, it becomes near impossible to troubleshoot the issue. I have this case for memcached, which at least on Centos does not have a way of logging. Even for those services that do have logging, this would be extremely helpful.
Example of current output:
Sep 6 15:38:18 domU-12-31-39-0B-C4-71 puppet-agent[1109]: (/Stage[main]/Elmer::Virtualenvtest/Service[memcached]/ensure) change from stopped to running failed: Could not start Service[memcached]: Execution of '/sbin/service memcached start' returned 1: at /etc/puppet/modules/elmer/manifests/virtualenvtest.pp:37
OK I know it failed but I have no idea why. Without knowing the stderr, one has to attempt to reproduce the exact situation in a shell, which would be difficult.
If we could just be able to use the same feature currently available for exec like below, my life would be a lot easier:
service {memcached: ensure = running, logoutput = on failure, }
Jira (PUP-1255) Default file mode is now 0600 instead of 0644
Title: Message Title
Dominic Cleal commented on an issue
Re: Default file mode is now 0600 instead of 0644
Merged into 2.7.x in 6a11ab
Add Comment
Puppet / PUP-1255
Default file mode is now 0600 instead of 0644
As of Puppet 3.4.1 and 2.7.24, the default file mode when no mode is explicitly specified on a file resource has changed from 0644 to 0600. It appears from the commits (https://github.com/puppetlabs/puppet/commit/65909fbe and 691fbbeaa) that this was not the intention. {noformat} # rpm -q puppet puppet-3.4.0-1.el6.noarch # puppet apply -e 'file { ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1319) Ability to run --onetime in the background while a daemon is idle
Title: Message Title redmine.exporter created an issue Puppet / PUP-1319 Ability to run --onetime in the background while a daemon is idle Issue Type: Bug Assignee: Unassigned Created: 31/Dec/13 3:56 AM Labels: redmine Priority: Normal Reporter: redmine.exporter When the puppetd daemon is running it has the pid file preventing other background daemons. When running --onetime --no-daemonize - a foreground run - this is fine, pid file doesnt prevent the --onetime run but if you wanted to do a backgrounded --onetime run the pid file will prevent that run from happening. We should arrange so that a backgrounded --onetime is allowed if the other daemon isnt actively also doing a run. Additionally if you do --onetime --splay 30 the new daemon should background and only bail out the run when it starts at the end of the splay period if the background daemon is then doing a run. The context of that from mcollective I'd like to schedule --onetime runs - with optional splay. In that case I start the puppetd in the background and report back if that was successful or not leaving the actual running up to the puppetd that will then have disowned itself from the mcollectived so it can run at its own schedule using splay or whatever is configured. This is possibly closely related to #3757
Jira (PUP-1320) service puppet ensure stopped kills off cron-run puppet with Caught TERM; calling stop
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1320
service puppet ensure stopped kills off cron-run puppet with Caught TERM; calling stop
Issue Type:
Bug
Assignee:
Unassigned
Created:
31/Dec/13 5:07 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
We have recently switched from puppet agent in daemon mode (for kick) to cron-run puppet with mcollective agent. However, I started noticing that puppet policies were being inconsistently applied across the hosts. It turns out that this policy is the problem:
pre service { 'puppet': ensure = stopped, enable = false, require = File['/etc/cron.d/puppet','/etc/puppet/puppet.conf'], }
/pre
I have checked and confirmed that the puppet init script returns the correct response even when puppet is running. If I run puppet agent --test in one window and while it is running I run this in the other window, it shows clear:
pre root@sj2-noc01 ~$ service puppet status ; echo $? puppet is stopped 3 /pre
However, if I run puppet in a silent mode with --onetime and --no-daemon then the init script returns this value
pre root@sj2-noc01 ~$ service puppet status ; echo $? puppet (pid 30406) is running... 0 /pre
This causes it to kill itself off, and not finish the run. Due to the semi-random nature of ordering, this happens near the end or near the beginning of the puppet run on different hosts. (there are few dependancies on the puppet module, so its order in the manifest is
Jira (PUP-1321) ruby_manifest_spec does not test everything properly
Title: Message Title Filip Hrbek created an issue Puppet / PUP-1321 ruby_manifest_spec does not test everything properly Issue Type: Bug Affects Versions: 3.x Assignee: Unassigned Components: DSL Created: 31/Dec/13 5:22 AM Priority: Normal Reporter: Filip Hrbek Steps to reproduce: 1. Modify spec/integration/parser/ruby_manifest_spec.rb, test should be properly reloaded when stale, so that Puppet[:filetimeout] would be set to a high value (e.g. 1000) instead of current -1. 2. Run spec tests 3. Check the result Expected result: The test fails as the file should be cached and obsolete notice should be present in the output. Actual result: The test succeeds. It means that the test as it stands today is useless, not actually checking the expected functionality.
Jira (PUP-1322) Puppet REST API always fails if there's at least one broken manifest
Title: Message Title Filip Hrbek created an issue Puppet / PUP-1322 Puppet REST API always fails if there's at least one broken manifest Issue Type: Bug Affects Versions: 3.x Assignee: Unassigned Components: DSL Created: 31/Dec/13 5:30 AM Priority: Major Reporter: Filip Hrbek Steps to reproduce: 1. Install several puppet modules 2. Make a syntax error in one or more installed manifests 3. Query host/production/resource_types/*?kind=class 4. Query the same url again Expected result: Step #3 and #4 returns the same result, containing parseable all classes *) Actual result: Step #3 fails with an error reporting the first problem it encounters, step #4 fails with Import loop detected *) The question is how errors should be reported - this is a matter of design/discussion. Perhaps it would be good if a list of errors would be exposed in the json structure along with the successfully parsed classes.
Jira (PUP-1322) Puppet REST API always fails if there's at least one broken manifest
Title: Message Title Filip Hrbek commented on an issue Re: Puppet REST API always fails if there's at least one broken manifest A pull request is available for review. There's still an open question of reporting problems with unparseable classes. I'm open to any proposals from the puppet core developers how to handle this. Add Comment Puppet / PUP-1322 Puppet REST API always fails if there's at least one broken manifest Steps to reproduce: 1. Install several puppet modules 2. Make a syntax error in one or more installed manifests 3. Query host/production/resource_types/*?kind=class 4. Query the same url again Expected result: Step #3 and #4 returns the same result, containing parseable all classes *) Actual result: Step #3 fails with an error reporting the ... 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-1274) PR (2201): PE-2123 Do not fail hard on unparseable files - fhrbek
Title: Message Title gepetto-bot commented on an issue Re: PR (2201): PE-2123 Do not fail hard on unparseable files - fhrbek fhrbek commented: Travis is now OK, the PUP ticket is https://tickets.puppetlabs.com/browse/PUP-1322. Add Comment Puppet / PUP-1274 PR (2201): PE-2123 Do not fail hard on unparseable files - fhrbek h2. PE-2123 Do not fail hard on unparseable files * Author: Filip Hrbek filip.hr...@gmail.com * Company: * Github ID: [fhrbek|https://github.com/fhrbek] * [Pull Request 2201 Discussion|https://github.com/puppetlabs/puppet/pull/2201] * [Pull Request 2201 File Diff|https://github.com/puppetlabs/puppet/pull/2201/files] h2. Pull Request Description ... 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-1321) ruby_manifest_spec does not test everything properly
Title: Message Title Filip Hrbek assigned an issue to Filip Hrbek Puppet / PUP-1321 ruby_manifest_spec does not test everything properly Change By: Filip Hrbek Assignee: FilipHrbek 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/groups/opt_out.
Jira (PUP-1322) Puppet REST API always fails if there's at least one broken manifest
Title: Message Title Filip Hrbek assigned an issue to Filip Hrbek Puppet / PUP-1322 Puppet REST API always fails if there's at least one broken manifest Change By: Filip Hrbek Assignee: FilipHrbek 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/groups/opt_out.
Jira (PUP-1321) ruby_manifest_spec does not test everything properly
Title: Message Title Filip Hrbek commented on an issue Re: ruby_manifest_spec does not test everything properly Changes made: 1. The compile method can operate in two modes: a) With contents specified - this resets the puppet code together with the cached environments b) Without contents specified - this recompiles the recent contents without clearing the cache 2. The improved compilation method is used in the should be properly cached for multiple compiles test (making the code equivalent but simpler and easier to read) 3. The test should be properly reloaded when stale was fixed to that it would test what it was supposed to test: the sleep 1 was removed since it's not needed when all files are considered as stale (thanks to file timeout set to -1) the second compilation is called without resetting Puppet[:code] since otherwise it cleared the cache and the test passed with any setting of the puppet file timeout, even when it was longer that the sleep With the changes from this PR applied all tests pass the test should be properly cached for multiple compiles is simpler and cleaner the test should be properly reloaded when stale passes in its current form or if the file timeout is set to a smaller value than an eventual sleep, and fails if Add Comment Puppet / PUP-1321
Jira (PUP-1323) 'Push' functionality in puppetmaster to clients
Title: Message Title redmine.exporter created an issue Puppet / PUP-1323 'Push' functionality in puppetmaster to clients Issue Type: New Feature Assignee: Unassigned Created: 31/Dec/13 6:52 AM Labels: redmine Priority: Normal Reporter: redmine.exporter In addition to the client puppetd connecting to the puppetmaster and pulling configuration from it, the puppetmaster should also be able to configure clients in 'push' mode where it initiates the connection to the remote client. This feature solves the problem where the puppetmaster, on the inside of a restrictive firewall, is managing clients that are in the DMZ of or outside the firewall. In this configuration, the remote puppet client is not able to start a connection to the puppetmaster, but the puppetmaster is capable of starting a connection to the client. It is preferable in most situations to keep the firewall as closed as possible, and in some network configurations there may be multiple firewalls, load balancers and other devices not in the puppet sysadmin's control that make it difficult to start a connection from the external machine in to the puppetmaster. Add
Jira (PUP-1324) Module path specification with wildcards
Title: Message Title redmine.exporter created an issue Puppet / PUP-1324 Module path specification with wildcards Issue Type: New Feature Assignee: Unassigned Created: 31/Dec/13 6:52 AM Labels: redmine Priority: Normal Reporter: redmine.exporter Modulepath configuration directive should support path globbing. It should use Dir.glob ruby feature. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1325) Extend Pacman provider for Archlinux to use Yaourt when needed.
Title: Message Title redmine.exporter created an issue Puppet / PUP-1325 Extend Pacman provider for Archlinux to use Yaourt when needed. Issue Type: New Feature Assignee: Unassigned Created: 31/Dec/13 7:22 AM Labels: redmine Priority: Normal Reporter: redmine.exporter On Archlinux, the Puppet and Facter packages are presently in the Arch User Repository, which the standard package manager, Pacman, doesn't support. This makes keeping Puppet itself up to date more difficult than it really needs to be. This patch extends the Pacman package provider to use the ubiquitous AUR wrapper, Yaourt, when referencing the AUR. This has been written as an extension to the Pacman provider rather than a separate provider mainly because I have no idea how to make two different providers co-exist nicely. Tips much appreciated. This patch aims to keep the status quo if Yaourt is not installed - packages should fail or succeed exactly as before. If Yaourt is installed, AUR packages should be able to be installed/queried/updated. I was going to extend the test for Pacman to show I've not broken anything, but there doesn't appear to be one. I'm unsire how to start a brand new test from scratch - again, tips welcome. I've issued a pull request for the current version of the provider, at https://github.com/puppetlabs/puppet/pull/241 Regards, Greg Sutcliffe
Jira (PUP-1326) Apply for registered port number with IANA
Title: Message Title redmine.exporter created an issue Puppet / PUP-1326 Apply for registered port number with IANA Issue Type: New Feature Assignee: Unassigned Created: 31/Dec/13 7:51 AM Labels: redmine Priority: Normal Reporter: redmine.exporter re #3669, we should register our services with IANA http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xml http://www.iana.org/cgi-bin/usr-port-number.pl Add Comment
Jira (FACT-182) Facter Does not run on OS X 10.9 Mavericks
Title: Message Title Nate Walck created an issue Facter / FACT-182 Facter Does not run on OS X 10.9 Mavericks Issue Type: Bug Affects Versions: 1.7.4 Assignee: Eric Sorenson Created: 31/Dec/13 8:47 AM Priority: Major Reporter: Nate Walck If you install Facter 1.7.4 and earlier on OS X 10.9 Mavericks and try to run it, you get the following error: sh-3.2# facter /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in `require': cannot load such file facter/application (LoadError) from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in `require' from /usr/bin/facter:14:in `main' This is the same issue we were running into with Puppet itself prior to version 3.4.x. The issue is that facter is still being installed into /usr/lib/ruby/site_ruby/1.8 and it should be installed into /Library/Ruby/Site instead. The reason this is necessary is because OS X 10.9 now uses Ruby 2.0 as its default. Until this is fixed, facter is broken on OS X 10.9 and won't function unless you cherry pick fixes to facter and roll your own installer.
Jira (PUP-1327) owner of files created by nagios resource types
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1327
owner of files created by nagios resource types
Issue Type:
Bug
Assignee:
Unassigned
Created:
31/Dec/13 8:50 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
Currently the files are created with the permission 600 and are owned by root
it will be nice to have the possibility to change the owner and/or the permissions of those resources
example : pre nagios_host { korin: ensure = present, use = linux-server, alias = korin, address = 192.168.109.84, hostgroups = linux-servers, target = /etc/nagios/host_korin.cfg, **owner = nagios**; }
/pre
Add Comment
Jira (PUP-1321) ruby_manifest_spec does not test everything properly
Title: Message Title Michelle Johansen commented on an issue Re: ruby_manifest_spec does not test everything properly Kurt Wall Can you take a look at this please? Add Comment Puppet / PUP-1321 ruby_manifest_spec does not test everything properly Steps to reproduce: 1. Modify spec/integration/parser/ruby_manifest_spec.rb, test should be properly reloaded when stale, so that Puppet[:filetimeout] would be set to a high value (e.g. 1000) instead of current -1. 2. Run spec tests 3. Check the result Expected result: The test fails as the file should be cached and obsolete notice should be pre... 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/groups/opt_out.
Jira (PUP-1321) ruby_manifest_spec does not test everything properly
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-1321 ruby_manifest_spec does not test everything properly Change By: Michelle Johansen Assignee: KurtWall 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/groups/opt_out.
Jira (PUP-1322) Puppet REST API always fails if there's at least one broken manifest
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-1322 Puppet REST API always fails if there's at least one broken manifest Change By: Michelle Johansen Fix Version/s: 3.5.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1322) Puppet REST API always fails if there's at least one broken manifest
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-1322 Puppet REST API always fails if there's at least one broken manifest Change By: Michelle Johansen Story Points: 3 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/groups/opt_out.
Jira (PUP-1322) Puppet REST API always fails if there's at least one broken manifest
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-1322 Puppet REST API always fails if there's at least one broken manifest Change By: Michelle Johansen Component/s: PE 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/groups/opt_out.
Jira (PUP-1322) Puppet REST API always fails if there's at least one broken manifest
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-1322 Puppet REST API always fails if there's at least one broken manifest Change By: Michelle Johansen Sprint: Week2014-1-8to2014-1-15 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/groups/opt_out.
Jira (FACT-82) Pull Request (513): (#22107) Force ASCII-8BIT encoding on raw data in property lists
Title: Message Title Michelle Johansen commented on an issue Re: Pull Request (513): (#22107) Force ASCII-8BIT encoding on raw data in property lists Kylo Ginsberg Can we get a story point estimate on this one? Add Comment Facter / FACT-82 Pull Request (513): (#22107) Force ASCII-8BIT encoding on raw data in property lists h2. (#22107) Force ASCII-8BIT encoding on raw data in property lists * Author: Dustin J. Mitchell dus...@v.igoro.us * Company: Mozilla, Inc. * Github ID: [djmitche|https://github.com/djmitche] * [Pull Request 513 Discussion|https://github.com/puppetlabs/facter/pull/513] * [Pull Request 513 File Diff|https://github.com/puppetlabs/facter/pull/513/fi... 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/groups/opt_out.
Jira (FACT-82) Pull Request (513): (#22107) Force ASCII-8BIT encoding on raw data in property lists
Title: Message Title Michelle Johansen commented on an issue Re: Pull Request (513): (#22107) Force ASCII-8BIT encoding on raw data in property lists Kylo Ginsberg Can we get a story point estimate on this one? Add Comment Facter / FACT-82 Pull Request (513): (#22107) Force ASCII-8BIT encoding on raw data in property lists h2. (#22107) Force ASCII-8BIT encoding on raw data in property lists * Author: Dustin J. Mitchell dus...@v.igoro.us * Company: Mozilla, Inc. * Github ID: [djmitche|https://github.com/djmitche] * [Pull Request 513 Discussion|https://github.com/puppetlabs/facter/pull/513] * [Pull Request 513 File Diff|https://github.com/puppetlabs/facter/pull/513/fi... 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/groups/opt_out.
Jira (PUP-1255) Default file mode is now 0600 instead of 0644
Title: Message Title Joshua Cooper assigned an issue to Joshua Cooper Failing on windows 2012, investigating Puppet / PUP-1255 Default file mode is now 0600 instead of 0644 Change By: Joshua Cooper Assignee: JoshuaCooper 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/groups/opt_out.
Jira (FACT-183) PR (590): Extract Facter execution methods to mixin - adrienthebo
Title: Message Title gepetto-bot created an issue Facter / FACT-183 PR (590): Extract Facter execution methods to mixin - adrienthebo Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 31/Dec/13 9:45 AM Labels: github Priority: Normal Reporter: gepetto-bot Extract Facter execution methods to mixin Author: Adrien Thebo git+git...@somethingsinistral.net Company: Puppet Labs Github ID: adrienthebo Pull Request 590 Discussion Pull Request 590 File Diff Pull Request Description The command
Jira (PUP-1328) gem package provider should reset permissions
Title: Message Title redmine.exporter created an issue Puppet / PUP-1328 gem package provider should reset permissions Issue Type: Bug Assignee: Unassigned Created: 31/Dec/13 10:01 AM Labels: redmine Priority: Normal Reporter: redmine.exporter If the user running `puppet apply` uses a restrictive umask (e.g. 0077), gems installed using the gem package provider will be unreadable for all users except root. rubygems author has [ruled this behaviour as a feature](https://github.com/rubygems/rubygems/issues/272), but in Puppet context I fail to see a reason why the gem package provider should behave differently than, for example, apt. Add Comment
Jira (FACT-183) PR (590): Extract Facter execution methods to mixin - adrienthebo
Title: Message Title
gepetto-bot commented on an issue
Re: PR (590): Extract Facter execution methods to mixin - adrienthebo
jhoblitt commented:
Are there any external users of `Facter::Util::Resolution` as a instance? I'm wondering if it wouldn't be easier to leave the execution class methods under the current namespace, since these are likely used by a majority of facts, and move away the resolution instance methods to a new namespace like `Facter::Core:: {Resolution,Verdict, etc.}
`.
Add Comment
Facter / FACT-183
PR (590): Extract Facter execution methods to mixin - adrienthebo
h2. Extract Facter execution methods to mixin * Author: Adrien Thebo git+git...@somethingsinistral.net * Company: Puppet Labs * Github ID: [adrienthebo|https://github.com/adrienthebo] * [Pull Request 590 Discussion|https://github.com/puppetlabs/facter/pull/590] * [Pull Request 590 File Diff|https://github.com/puppetlabs/facter/pull/590/files] h2
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
Jira (PUP-1255) Default file mode is now 0600 instead of 0644
Title: Message Title
Andrew Parker commented on an issue
Re: Default file mode is now 0600 instead of 0644
The Win2012 failure is
expected: NT AUTHORITY\SYSTEM:(I) 0x1f01ff
BUILTIN\Administrators:(I)0x1f01ff
BURI\Administrator:(I)0x1f01ff
got: NT AUTHORITY\SYSTEM: 0x1f01ff
BUILTIN\Administrators: 0x1f01ff
BURI\Administrator: 0x1f01ff
NT AUTHORITY\SYSTEM:(I) 0x1f01ff
BUILTIN\Administrators:(I)0x1f01ff
BURI\Administrator:(I)0x1f01ff
(using ==)
Diff:
@@ -1,3 +1,6 @@
+ NT AUTHORITY\SYSTEM: 0x1f01ff
+ BUILTIN\Administrators: 0x1f01ff
+ BURI\Administrator: 0x1f01ff
NT AUTHORITY\SYSTEM:(I) 0x1f01ff
BUILTIN\Administrators:(I)0x1f01ff
BURI\Administrator:(I)0x1f01ff
./spec/integration/util_spec.rb:73:in `block (3 levels) in top (required)'
Add Comment
Puppet / PUP-1255
Default file mode is now 0600 instead of 0644
As of Puppet 3.4.1 and 2.7.24, the default file mode when no mode is explicitly specified on a file resource has changed from 0644 to 0600. It appears from the commits (https://github.com/puppetlabs/puppet/commit/65909fbe and 691fbbeaa) that this was not the intention. {noformat} # rpm -q puppet puppet-3.4.0-1.el6.noarch # puppet apply -e 'file { ...
Jira (PUP-1314) Updates the downloads page
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1314 Updates the downloads page Change By: Andrew Parker Fix Version/s: 3.4.0 Fix Version/s: 3.4.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/groups/opt_out.
Jira (PUP-1303) Is there a commit for every bug targeted at the release
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1303 Is there a commit for every bug targeted at the release Change By: Andrew Parker Fix Version/s: 3.4.0 Fix Version/s: 3.4.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/groups/opt_out.
Jira (PUP-1313) Merge 3.4.0 into pe-puppet
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1313 Merge 3.4.0 into pe-puppet Change By: Andrew Parker Fix Version/s: 3.4.0 Fix Version/s: 3.4.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/groups/opt_out.
Jira (PUP-1305) Prepare puppet-announcement
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1305 Prepare puppet-announcement Change By: Andrew Parker Fix Version/s: 3.4.0 Fix Version/s: 3.4.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/groups/opt_out.
Jira (PUP-1310) Go/no-go meeting
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1310 Go/no-go meeting Change By: Andrew Parker Fix Version/s: 3.4.0 Fix Version/s: 3.4.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/groups/opt_out.
Jira (PUP-1308) Create packages
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1308 Create packages Change By: Andrew Parker Fix Version/s: 3.4.0 Fix Version/s: 3.4.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/groups/opt_out.
Jira (PUP-1315) Close merged pending release tickets in redmine and Resolved ticket jira
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1315 Close merged pending release tickets in redmine and Resolved ticket jira Change By: Andrew Parker Fix Version/s: 3.4.0 Fix Version/s: 3.4.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/groups/opt_out.
Jira (PUP-1301) Are tests passing (spec, acceptance, all platforms)
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1301 Are tests passing (spec, acceptance, all platforms) Change By: Andrew Parker Fix Version/s: 3.4.0 Fix Version/s: 3.4.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/groups/opt_out.
Jira (PUP-1302) Is there a bug targeting at the release for every commit
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1302 Is there a bug targeting at the release for every commit Change By: Andrew Parker Fix Version/s: 3.4.0 Fix Version/s: 3.4.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/groups/opt_out.
Jira (PUP-1311) Docs pushed
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1311 Docs pushed Change By: Andrew Parker Fix Version/s: 3.4.0 Fix Version/s: 3.4.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/groups/opt_out.
Jira (PUP-1304) Is a redmine affected version created for the new version
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1304 Is a redmine affected version created for the new version Change By: Andrew Parker Fix Version/s: 3.4.0 Fix Version/s: 3.4.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/groups/opt_out.
Jira (PUP-1306) Tag the release
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1306 Tag the release Change By: Andrew Parker Fix Version/s: 3.4.0 Fix Version/s: 3.4.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/groups/opt_out.
Jira (PUP-1309) Smoke test packages
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1309 Smoke test packages Change By: Andrew Parker Fix Version/s: 3.4.0 Fix Version/s: 3.4.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/groups/opt_out.
Jira (PUP-1312) Packages pushed
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1312 Packages pushed Change By: Andrew Parker Fix Version/s: 3.4.0 Fix Version/s: 3.4.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/groups/opt_out.
Jira (FACT-82) Pull Request (513): (#22107) Force ASCII-8BIT encoding on raw data in property lists
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-82 Pull Request (513): (#22107) Force ASCII-8BIT encoding on raw data in property lists 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/groups/opt_out.
Jira (FACT-183) PR (590): Extract Facter execution methods to mixin - adrienthebo
Title: Message Title gepetto-bot commented on an issue Re: PR (590): Extract Facter execution methods to mixin - adrienthebo adrienthebo commented: `Facter::Util::Resolution` extends `Facter::Util::Execution`, so all existing invocations of `Facter::Util::Resolution.exec` and related still work. It's a pure refactor and shouldn't break any existing behavior. Add Comment Facter / FACT-183 PR (590): Extract Facter execution methods to mixin - adrienthebo h2. Extract Facter execution methods to mixin * Author: Adrien Thebo git+git...@somethingsinistral.net * Company: Puppet Labs * Github ID: [adrienthebo|https://github.com/adrienthebo] * [Pull Request 590 Discussion|https://github.com/puppetlabs/facter/pull/590] * [Pull Request 590 File Diff|https://github.com/puppetlabs/facter/pull/590/files] h2 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
Jira (PDB-112) Provide means to request events from latest report in timeframe
Title: Message Title
Joseph Wagner commented on an issue
Re: Provide means to request events from latest report in timeframe
Michelle Johansen I'd like to get this prioritized so we can take care of for PE 3.3. What is the process for doing so? I consider this a high priority for PE 3.3 as it will enable a change (in 1906) that will make Event Inspector a much more effective reporting tool.
Add Comment
PuppetDB / PDB-112
Provide means to request events from latest report in timeframe
h2. Summary Implement something like a {{latest-report-before}} query for the Events endpoint. This is necessary in order to enable the user experience / feature request described in [PE-1906|https://jira.puppetlabs.com/browse/PE-1906?focusedCommentId=20630page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-20630]. h2. Des...
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
Jira (PDB-112) Provide means to request events from latest report in timeframe
Title: Message Title Joseph Wagner updated an issue PuppetDB / PDB-112 Provide means to request events from latest report in timeframe Change By: Joseph Wagner UX Priority: Major 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/groups/opt_out.
Jira (FACT-183) PR (590): Extract Facter execution methods to mixin - adrienthebo
Title: Message Title gepetto-bot commented on an issue Re: PR (590): Extract Facter execution methods to mixin - adrienthebo puppetcla commented: CLA signed by all contributors. Add Comment Facter / FACT-183 PR (590): Extract Facter execution methods to mixin - adrienthebo h2. Extract Facter execution methods to mixin * Author: Adrien Thebo git+git...@somethingsinistral.net * Company: Puppet Labs * Github ID: [adrienthebo|https://github.com/adrienthebo] * [Pull Request 590 Discussion|https://github.com/puppetlabs/facter/pull/590] * [Pull Request 590 File Diff|https://github.com/puppetlabs/facter/pull/590/files] h2 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/groups/opt_out.
Jira (PDB-112) Provide means to request events from latest report in timeframe
Title: Message Title Michelle Johansen updated an issue PuppetDB / PDB-112 Provide means to request events from latest report in timeframe Change By: Michelle Johansen Component/s: PE 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/groups/opt_out.
Jira (PDB-112) Provide means to request events from latest report in timeframe
Title: Message Title Michelle Johansen updated an issue PuppetDB / PDB-112 Provide means to request events from latest report in timeframe Change By: Michelle Johansen Fix Version/s: 2.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/groups/opt_out.
Jira (PDB-112) Provide means to request events from latest report in timeframe
Title: Message Title Michelle Johansen updated an issue PuppetDB / PDB-112 Provide means to request events from latest report in timeframe Change By: Michelle Johansen Assignee: DeepakGiridharagopal 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/groups/opt_out.
Jira (PDB-112) Provide means to request events from latest report in timeframe
Title: Message Title Michelle Johansen updated an issue PuppetDB / PDB-112 Provide means to request events from latest report in timeframe Change By: Michelle Johansen Priority: Normal Major 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/groups/opt_out.
Jira (PDB-112) Provide means to request events from latest report in timeframe
Title: Message Title
Michelle Johansen commented on an issue
Re: Provide means to request events from latest report in timeframe
Deepak Giridharagopal Can this be added to the 2.0 scope?
Add Comment
PuppetDB / PDB-112
Provide means to request events from latest report in timeframe
h2. Summary Implement something like a {{latest-report-before}} query for the Events endpoint. This is necessary in order to enable the user experience / feature request described in [PE-1906|https://jira.puppetlabs.com/browse/PE-1906?focusedCommentId=20630page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-20630]. h2. Des...
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/groups/opt_out.
Jira (PDB-248) PR (781): Update changelog for 1.6.0 - grimradical
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-248 PR (781): Update changelog for 1.6.0 - grimradical Issue Type: Task Assignee: Unassigned Created: 31/Dec/13 11:43 AM Labels: github Priority: Normal Reporter: gepetto-bot Update changelog for 1.6.0 Author: Deepak Giridharagopal Company: Github ID: grimradical Pull Request 781 Discussion Pull Request 781 File Diff Pull Request Description (webhooks-id: dc1db3cc23d8fb6474551cdc72285c83)
Jira (PDB-248) PR (781): Update changelog for 1.6.0 - grimradical
Title: Message Title gepetto-bot commented on an issue Re: PR (781): Update changelog for 1.6.0 - grimradical Pull request Update changelog for 1.6.0 has been closed. Add Comment PuppetDB / PDB-248 PR (781): Update changelog for 1.6.0 - grimradical h2. Update changelog for 1.6.0 * Author: Deepak Giridharagopal * Company: * Github ID: [grimradical|https://github.com/grimradical] * [Pull Request 781 Discussion|https://github.com/puppetlabs/puppetdb/pull/781] * [Pull Request 781 File Diff|https://github.com/puppetlabs/puppetdb/pull/781/files] h2. Pull Request Description (webhoo... 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/groups/opt_out.
Jira (PDB-248) PR (781): Update changelog for 1.6.0 - grimradical
Title: Message Title gepetto-bot commented on an issue Re: PR (781): Update changelog for 1.6.0 - grimradical puppetlabs-jenkins commented: :green_heart: Test passed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/116/ Add Comment PuppetDB / PDB-248 PR (781): Update changelog for 1.6.0 - grimradical h2. Update changelog for 1.6.0 * Author: Deepak Giridharagopal * Company: * Github ID: [grimradical|https://github.com/grimradical] * [Pull Request 781 Discussion|https://github.com/puppetlabs/puppetdb/pull/781] * [Pull Request 781 File Diff|https://github.com/puppetlabs/puppetdb/pull/781/files] h2. Pull Request Description (webhoo... 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 (PDB-248) PR (781): Update changelog for 1.6.0 - grimradical
Title: Message Title gepetto-bot commented on an issue Re: PR (781): Update changelog for 1.6.0 - grimradical puppetlabs-jenkins commented: :red_circle: Test failed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/117/ Add Comment PuppetDB / PDB-248 PR (781): Update changelog for 1.6.0 - grimradical h2. Update changelog for 1.6.0 * Author: Deepak Giridharagopal * Company: * Github ID: [grimradical|https://github.com/grimradical] * [Pull Request 781 Discussion|https://github.com/puppetlabs/puppetdb/pull/781] * [Pull Request 781 File Diff|https://github.com/puppetlabs/puppetdb/pull/781/files] h2. Pull Request Description (webhoo... 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-536) Create endpoint for enumerating environments
Title: Message Title Eric Sorenson commented on an issue Re: Create endpoint for enumerating environments One additional requirement that needs consideration: We need to support multi-element modulepaths with this scheme, for users who currently use this pattern: # search environment-specific modules first, then a common modulepath modulepath = /etc/puppet/environments/$environment/modules:/etc/puppet/environments/common/modules Some refinements/complexities on this pattern (not all of which need to port over directly but we need to understand their use cases) are https://projects.puppetlabs.com/issues/11900 (another layer of interpolation in the modulepath elements) PUP-1324 directory globbing in the final modulepath element librarian-puppet / r10k workflows (have not explored this personally but Adrien Thebo says modules are always installed into the modules/ directory, and modules in the git repo itself are in a separate directory Add Comment Puppet / PUP-536 Create endpoint for enumerating environments Much of the Node
Jira (PDB-112) Provide means to request events from latest report in timeframe
Title: Message Title
Michelle Johansen commented on an issue
Re: Provide means to request events from latest report in timeframe
Aaron Armstrong and Kenn Hussey Unfortunately the PuppetDB team does not have the capacity to support this request for the PE 3.3 timeline. Hopefully the PE team can pick up this issue to support the needed functionality.
Add Comment
PuppetDB / PDB-112
Provide means to request events from latest report in timeframe
h2. Summary Implement something like a {{latest-report-before}} query for the Events endpoint. This is necessary in order to enable the user experience / feature request described in [PE-1906|https://jira.puppetlabs.com/browse/PE-1906?focusedCommentId=20630page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-20630]. h2. Des...
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-1329) composite namevars should be more robust
Title: Message Title redmine.exporter created an issue Puppet / PUP-1329 composite namevars should be more robust Issue Type: Bug Assignee: Unassigned Created: 31/Dec/13 1:52 PM Labels: redmine Priority: Normal Reporter: redmine.exporter when trying to implement composite namevars with parsedfile, I ran into a few issues. This ticket is meant to address those issues: This ticket is related to several other tickets: #1621 - the initial ticket for composite namevars: #5605 - pre-fetching does not work #7625 - should fail explicitly if no title_pattern is matched. It also addresses some additional issues: composite namevars should not require that a parameters :name be added parsedfile should support composite namevars
Jira (PDB-112) Provide means to request events from latest report in timeframe
Title: Message Title
Deepak Giridharagopal commented on an issue
Re: Provide means to request events from latest report in timeframe
Looking at the feature request, I don't think this one is that large for someone on the PE side to take up. This should be a matter of defining the new operator and generating an IN clause with a subselect to retrieve just the reports that match.
I know that at least with PostgreSQL, you could accomplish the latest report for a system from before a given time through the use of DISTINCT ON; not sure about HSQLDB. But I'd be fine with us just not supporting that operator when using the embedded database.
Add Comment
PuppetDB / PDB-112
Provide means to request events from latest report in timeframe
h2. Summary Implement something like a {{latest-report-before}} query for the Events endpoint. This is necessary in order to enable the user experience / feature request described in [PE-1906|https://jira.puppetlabs.com/browse/PE-1906?focusedCommentId=20630page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-20630]. h2. Des...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1330) PR (2207): (maint) Simply confine test to any platform with Ruby shadow - jpartlow
Title: Message Title gepetto-bot created an issue Puppet / PUP-1330 PR (2207): (maint) Simply confine test to any platform with Ruby shadow - jpartlow Issue Type: Task Assignee: Unassigned Components: Community Created: 31/Dec/13 3:39 PM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Simply confine test to any platform with Ruby shadow Author: Josh Partlow Company: Github ID: jpartlow Pull Request 2207 Discussion Pull Request 2207 File Diff Pull Request Description
Jira (PUP-1330) PR (2207): (maint) Simply confine test to any platform with Ruby shadow - jpartlow
Title: Message Title gepetto-bot commented on an issue Re: PR (2207): (maint) Simply confine test to any platform with Ruby shadow - jpartlow jpartlow commented: This fixes the last issue blocking future parser acceptance runs. I'm going to merge it in and will check to see that the adjusted test still gets run from package installs and on solaris and windows source checkouts. Add Comment Puppet / PUP-1330 PR (2207): (maint) Simply confine test to any platform with Ruby shadow - jpartlow h2. (maint) Simply confine test to any platform with Ruby shadow * Author: Josh Partlow * Company: * Github ID: [jpartlow|https://github.com/jpartlow] * [Pull Request 2207 Discussion|https://github.com/puppetlabs/puppet/pull/2207] * [Pull Request 2207 File Diff|https://github.com/puppetlabs/puppet/pull/2207/files] h2. Pull Request Description -... 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-1330) PR (2207): (maint) Simply confine test to any platform with Ruby shadow - jpartlow
Title: Message Title gepetto-bot commented on an issue Re: PR (2207): (maint) Simply confine test to any platform with Ruby shadow - jpartlow Pull request (maint) Simply confine test to any platform with Ruby shadow has been closed. Add Comment Puppet / PUP-1330 PR (2207): (maint) Simply confine test to any platform with Ruby shadow - jpartlow h2. (maint) Simply confine test to any platform with Ruby shadow * Author: Josh Partlow * Company: * Github ID: [jpartlow|https://github.com/jpartlow] * [Pull Request 2207 Discussion|https://github.com/puppetlabs/puppet/pull/2207] * [Pull Request 2207 File Diff|https://github.com/puppetlabs/puppet/pull/2207/files] h2. Pull Request Description -... 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-984) Review the acceptance failures with --parser=future.
Title: Message Title Joshua Partlow commented on an issue Re: Review the acceptance failures with --parser=future. Just waiting on a final run (hopefully green) Add Comment Puppet / PUP-984 Review the acceptance failures with --parser=future. And fix up if straight forward. 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/groups/opt_out.
Jira (PUP-984) Review the acceptance failures with --parser=future.
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-984 Review the acceptance failures with --parser=future. Change By: Joshua Partlow Assignee: HenrikLindberg JoshuaPartlow 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/groups/opt_out.
Jira (PUP-1176) Add feature switch for evaluator
Title: Message Title Joshua Partlow commented on an issue Re: Add feature switch for evaluator Henrik Lindberg I can't find the PR for this (no link, and I'm not seeing it immediately when I look through the open prs?) Add Comment Puppet / PUP-1176 Add feature switch for evaluator Add a feature switch --evaluator that can be set to future or current. This should toggle the use of the future evaluator. We can later decide if it should be current or future by default. 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/groups/opt_out.
Jira (PUP-671) PR (2034): (#23084) Package options property for package - ptomulik
Title: Message Title gepetto-bot commented on an issue Re: PR (2034): (#23084) Package options property for package - ptomulik adrienthebo commented: I thought that I posted a comment on it earlier, but it looks like it has vanished into the ether. The problem with `enablerepo/disablerepo` is that those options need to be available when the package is installed, updated, and queried, so we can't neatly shoehorn those into the existing `install_options` and `uninstall_options`. In general there are a number of cases across other providers where other information is needed that we can't put inside of `install_options` or `uninstall_options` and doesn't slot neatly into the `build_options` parameter. Does this make sense? Add Comment Puppet / PUP-671 PR (2034): (#23084) Package options property for package - ptomulik h2. (#23084) Package options property for package * Author: Paweł Tomulik ptomu...@meil.pw.edu.pl * Company: Warsaw University of Technology * Github ID: [ptomulik|https://github.com/ptomulik] * [Pull Request 2034 Discussion|https://github.com/puppetlabs/puppet/pull/2034] * [Pull Request 2034 File Diff|https://github.com/puppetlabs/puppet/pull/203... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1330) PR (2207): (maint) Simply confine test to any platform with Ruby shadow - jpartlow
Title: Message Title Kurt Wall commented on an issue Re: PR (2207): (maint) Simply confine test to any platform with Ruby shadow - jpartlow I believe this PR caused https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Master/job/Puppet-Package-Acceptance-Per-Commit-master/98/ to fail. >From the log: Gems in the group development were not installed. It was installed into ./.bundle/gems + [[ rhel6 =~ solaris ]] + cat + [[ -z failure ]] + [[ failure = \s\u\c\c\e\s\s ]] + exit 1 Build step 'Execute shell' marked build as failure Recording test results Finished: FAILURE Add Comment Puppet / PUP-1330 PR (2207): (maint) Simply confine test to any platform with Ruby shadow - jpartlow h2. (maint) Simply confine test to any platform with Ruby shadow * Author: Josh Partlow * Company: * Github ID: [jpartlow|https://github.com/jpartlow] * [Pull Request 2207 Discussion|https://github.com/puppetlabs/puppet/pull/2207] * [Pull Request 2207 File Diff|https://github.com/puppetlabs/puppet/pull/2207/files] h2. Pull Request Description -... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
