Jira (PUP-797) PR (2094): (#23219) - Fix support of extra arguments in windows service - luisfdez
Title: Message Title gepetto-bot commented on an issue Re: PR (2094): (#23219) - Fix support of extra arguments in windows service - luisfdez luisfdez commented: @ferventcoder thanks for the polishing and pulling this in :+1: Add Comment Puppet / PUP-797 PR (2094): (#23219) - Fix support of extra arguments in windows service - luisfdez h2. (#23219) - Fix support of extra arguments in windows service * Author: Luis Fernndez lvarez * Company: CERN * Github ID: [luisfdez|https://github.com/luisfdez] * [Pull Request 2094 Discussion|https://github.com/puppetlabs/puppet/pull/2094] * [Pull Request 2094 File Diff|https://github.com/puppetlabs/puppet/pull/2094/files] h2. Pull Request... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (MCO-141) PR (137): [PE-2344] Make audit plugin log output match standard format - ericalthatcher
Title: Message Title gepetto-bot commented on an issue Re: PR (137): [PE-2344] Make audit plugin log output match standard format - ericalthatcher Pull request [PE-2344] Make audit plugin log output match standard format has been closed. Add Comment MCollective / MCO-141 PR (137): [PE-2344] Make audit plugin log output match standard format - ericalthatcher h2. [PE-2344] Make audit plugin log output match standard format * Author: * Company: Puppet Labs * Github ID: [ericalthatcher|https://github.com/ericalthatcher] * [Pull Request 137 Discussion|https://github.com/puppetlabs/marionette-collective/pull/137] * [Pull Request 137 File Diff|https://github.com/puppetlabs/marionette-collective/pull/137/f... 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-1180) Use inotify to trigger checks
Title: Message Title redmine.exporter created an issue Puppet / PUP-1180 Use inotify to trigger checks Issue Type: New Feature Assignee: Unassigned Created: 19/Dec/13 2:41 AM Labels: redmine Priority: Normal Reporter: redmine.exporter Using inotify (on Linux - not sure of other OS options) would allow Puppet to trigger checks on a more immediate basis. Currently Puppet checks on a fixed schedule with a bit of jitter thrown in for good measure. This means there is a window of opportunity (albeit a small one) for files to drift. The rationale behind this request is from looking at estates deployed in virtualized or cloud environments. In these kind of deployments, CPU usage can be a premium (either on a monetary cost basis or a CPU load basis). Estates that are configured to run full Puppet checks on a frequent basis pay the price of increased host usage. Whilst careful writing of manifests etc can mitigate this and keep running time to a minimum, the opportunity exists to remove this periodic load and rely on the system itself to alert Puppet to any changes to files of interest. It may also be possible after incorporating this to then allow Puppet to run selective checks to target only the files that have been changed. Providing the lowest system loading option to users will be of great interest to those who are charged based on CPU cycles and those who want their systems to be as 'quiet' as possible other than for designated system loads.
Jira (MCO-142) MCollective logger plugin should display updated log format
Title: Message Title Pieter Loubser created an issue MCollective / MCO-142 MCollective logger plugin should display updated log format Issue Type: Bug Assignee: Unassigned Created: 19/Dec/13 2:47 AM Fix Versions: 2.4.0 Priority: Normal Reporter: Pieter Loubser 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
Jira (MCO-142) MCollective logger plugin should display updated log format
Title: Message Title Pieter Loubser assigned an issue to Pieter Loubser MCollective / MCO-142 MCollective logger plugin should display updated log format Change By: Pieter Loubser Assignee: PieterLoubser 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-638) PR (198): Modify pick() to always return a value. - DavidS
Title: Message Title gepetto-bot commented on an issue Re: PR (198): Modify pick() to always return a value. - DavidS example42 commented: +1 for an alternative function if it's not possible to operate on the current one. Add Comment Puppet / PUP-638 PR (198): Modify pick() to always return a value. - DavidS h2. Modify pick() to always return a value. * Author: David Schmitt da...@dasz.at * Company: dasz.at OG * Github ID: [DavidS|https://github.com/DavidS] * [Pull Request 198 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/198] * [Pull Request 198 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/198/files] h2. Pull Requ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-1181) Modulefile dependency should support git repo as source
Title: Message Title redmine.exporter created an issue Puppet / PUP-1181 Modulefile dependency should support git repo as source Issue Type: New Feature Assignee: Unassigned Created: 19/Dec/13 4:36 AM Labels: redmine Priority: Normal Reporter: redmine.exporter According to the documentation here: http://docs.puppetlabs.com/puppet/3/reference/modules_publishing.html#write-a-modulefile you can optionally specify a third argument in dependencies, a repository. Reading through that document, I assumed that repository meant SCM repo, such as git. Unfortunately, it appears to mean another Forge. Please modify lib/puppet/module_tool/dependency.rb to support pulling a dependency from another Git repo. Add Comment
Jira (PUP-1182) Sun package provider should have remove_options to support -O nozones
Title: Message Title Christian Pearce created an issue Puppet / PUP-1182 Sun package provider should have remove_options to support -O nozones Issue Type: Bug Assignee: Unassigned Created: 19/Dec/13 4:37 AM Priority: Normal Reporter: Christian Pearce Similar to http://projects.puppetlabs.com/issues/8288 as an issue. We should have the ability to specify -O nozones on a package remove. Global zones will do interesting tasks like try to boot zones that are not running to see if it should remove a package or not. This could be a big problem if you didn't intend for it. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-240) anonymize used read-string
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-240 anonymize used read-string Issue Type: Bug Assignee: Unassigned Created: 19/Dec/13 4:37 AM Priority: Normal Reporter: Ryan Senior It should instead use clojure.edn/read-string as we're really want to just read in Clojure data structures. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed
Jira (PDB-241) Parameterize exit for the cli functions
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-241 Parameterize exit for the cli functions Issue Type: Bug Assignee: Unassigned Created: 19/Dec/13 4:42 AM Priority: Normal Reporter: Ryan Senior Trapper Keeper throws an exception when command line arguments don't validate. There's code in several of the commands to catch that exception and exit. The code that has these exits can't be tested. We could parameterize these command functions to take a function for exit (something similar is done in core.clj). Another option would be to use the exception (and it's message) as something top level and exit from there.. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1183) Allow provider-specific options as a first class part of the RAL model.
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1183
Allow provider-specific options as a first class part of the RAL model.
Issue Type:
New Feature
Assignee:
Unassigned
Created:
19/Dec/13 4:41 AM
Labels:
redmine customer
Priority:
Normal
Reporter:
redmine.exporter
http://groups.google.com/group/puppet-users/browse_thread/thread/2ef615fc42225d99?pli=1
Our requirement is more or less the same as in the linked thread, we need to use a proxy to install gems but for a variety of reasons can't set a global proxy on the machines. Thus some way of passing options to gem is necessary.
(Nigel) - We should do this consistently across providers, perhaps combining with the preseed functionality of apt/dpkg.
Rather than doing this as a generic pass unstructured data hack, we should resolve this by allowing provider-specific parameters to be first class elements in declarations:
pre package { example: provider = something, something_specific_parameter = value }
/pre
That should cover more than just packages - extending to all types. Requiring the provider to be explicitly specified is preferable to allowing it to be inferred when non-type parameters or properties are present.
It is unclear if both properties and parameters should be supported, or if only parameters should be allowed.
Jira (PUP-1184) puppet agent --genconfig also create settings for puppet master
Title: Message Title redmine.exporter created an issue Puppet / PUP-1184 puppet agent --genconfig also create settings for puppet master Issue Type: Bug Assignee: Unassigned Created: 19/Dec/13 6:50 AM Labels: redmine Priority: Normal Reporter: redmine.exporter When I run puppet agent --genconfig /tmp/puppet.conf, I did get the template for puppet. I not familiar what settings got generated are really needed. Can you confirm settings in puppet.conf are validd for puppet agent ? To me following two settings obviously below to puppet master not puppet agent. cert_inventory = /etc/opt/puppetclient268/ssl/ca/inventory.txt ca_name = Puppet CA: puppetagent1.test.com Please see attached puppet.conf file for details. Add Comment
Jira (FACT-170) PR (582): (maint) restrict redcarpet gem to = 2.3.0 - jhoblitt
Title: Message Title gepetto-bot commented on an issue Re: PR (582): (maint) restrict redcarpet gem to = 2.3.0 - jhoblitt jhoblitt commented: This should be merged into both the stable and facter-2 branches. Add Comment Facter / FACT-170 PR (582): (maint) restrict redcarpet gem to = 2.3.0 - jhoblitt h2. (maint) restrict redcarpet gem to = 2.3.0 * Author: Joshua Hoblitt jhobl...@cpan.org * Company: * Github ID: [jhoblitt|https://github.com/jhoblitt] * [Pull Request 582 Discussion|https://github.com/puppetlabs/facter/pull/582] * [Pull Request 582 File Diff|https://github.com/puppetlabs/facter/pull/582/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 (FACT-170) PR (582): (maint) restrict redcarpet gem to = 2.3.0 - jhoblitt
Title: Message Title gepetto-bot created an issue Facter / FACT-170 PR (582): (maint) restrict redcarpet gem to = 2.3.0 - jhoblitt Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 19/Dec/13 7:20 AM Labels: github Priority: Normal Reporter: gepetto-bot (maint) restrict redcarpet gem to = 2.3.0 Author: Joshua Hoblitt jhobl...@cpan.org Company: Github ID: jhoblitt Pull Request 582 Discussion Pull Request 582 File Diff Pull Request Description Per the tag annotation from the redcarpet 3.0.0
Jira (PUP-1185) The 'puppet node find' command does not report all node information
Title: Message Title Jon McKenzie created an issue Puppet / PUP-1185 The 'puppet node find' command does not report all node information Issue Type: Bug Affects Versions: 3.x Assignee: Unassigned Created: 19/Dec/13 7:29 AM Priority: Normal Reporter: Jon McKenzie Running the following... puppet node find $(puppet config print certname) --render-as yaml ... does not produce all of the node data. In particular, it's missing any ENC-set parameters (among other things, see this discussion on the mail group: https://groups.google.com/forum/#!msg/puppet-users/AciTXjtzwtg/GGueZ9qagl8J) This is in comparison to the /node REST endpoint on the Puppetmaster which does report the correct information (e.g. if I send a GET to https://puppet:8140/production/node/foo.bar.com). (The puppet fact find command also does not seem to report this information.)
Jira (PUP-1187) tagmail report sends email when nothing happens
Title: Message Title redmine.exporter created an issue Puppet / PUP-1187 tagmail report sends email when nothing happens Issue Type: Bug Assignee: Unassigned Created: 19/Dec/13 7:33 AM Labels: redmine customer Priority: Normal Reporter: redmine.exporter Since upgrading to the 2.7 series (2.6.8 - 2.7.3), the tagmail report will send an email with 1 line, shown below, after every run. Before the upgrade, it would only send emails when something occurred during the puppet run. Steps to reproduce: Enable tagmail report Execute a puppet run that produces no updates Expected result: No email sent Actual result: Email sent with line below Email body: Tue Aug 23 13:11:59 -0400 2011 Puppet (notice): Finished catalog run in 16.60 seconds tagmail.conf: all: x...@.com Add Comment
Jira (PUP-1186) puppet module tool on windows will (sometimes) create a PaxHeader directory
Title: Message Title redmine.exporter created an issue Puppet / PUP-1186 puppet module tool on windows will (sometimes) create a PaxHeader directory Issue Type: Bug Assignee: Unassigned Created: 19/Dec/13 7:33 AM Labels: redmine Priority: Normal Reporter: redmine.exporter 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 module is installed the problem appears as follows. pre C:\Program Files (x86)\Puppet Labs\Puppet\binpuppet module install liamjbennett -win_facts Notice: Preparing to install into C:/ProgramData/PuppetLabs/puppet/etc/modules . .. Notice: Downloading from https://forge.puppetlabs.com ... Notice: Installing – do not interrupt ... C:/ProgramData/PuppetLabs/puppet/etc/modules └── liamjbennett-win_facts (v0.0.1) C:\Program Files (x86)\Puppet Labs\Puppet\binpuppet apply -e 'notice hello' Error loading fact C:/ProgramData/PuppetLabs/puppet/etc/modules/win_facts/lib/fa cter/PaxHeader/operatingsystemversion.rb C:/ProgramData/PuppetLabs/puppet/etc/mo dules/win_facts/lib/facter/PaxHeader/operatingsystemversion.rb:1: syntax error, unexpected tIDENTIFIER, expecting $end 17 gid=790807719 ^ Error loading fact C:/ProgramData/PuppetLabs/puppet/etc/modules/win_facts/lib/fa cter/PaxHeader/windows_productkey.rb C:/ProgramData/PuppetLabs/puppet/etc/module s/win_facts/lib/facter/PaxHeader/windows_productkey.rb:1: syntax
Jira (FACT-79) Facter built-in legacy facts are inconsistent in type - convert to string and add simple schema
Title: Message Title Joshua Hoblitt commented on an issue Re: Facter built-in legacy facts are inconsistent in type - convert to string and add simple schema I'll admit that I was a bit skeptical of the json schema approach when I first heard about it but after looking at PR 581 I'm pretty enthusiastic about this approach since it's done as a regression test rather than at runtime. My vote would be for a strong policy of maintaining the return types of stable/1.7 facts as they are now essentially forever (or at least through ~ 2) and only fixing the cases where a different type could be returned essentially making the return type invariant for all existing types. Add Comment Facter / FACT-79 Facter built-in legacy facts are inconsistent in type - convert to string and add simple schema I just saw a ticket go past from the PuppetDB team about stringification to work around a test failure due to data type changes, and I think they hit the same issue we did: Facter is actually pretty bad at imposing the ABI that Puppet strongly suggests it has. We hit this in the Microkernel for Razor in about the same way: we get facts from Facter... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1188) Extract Modulefile parsing in a separate gem
Title: Message Title Ringo De Smet created an issue Puppet / PUP-1188 Extract Modulefile parsing in a separate gem Issue Type: Improvement Affects Versions: 3.3.0 Assignee: Unassigned Components: Packaging Created: 19/Dec/13 7:56 AM Priority: Normal Reporter: Ringo De Smet We all love librarian-puppet. While that gem states it does not depend on the Puppet gem, it's internals do use Puppet Ruby code directly: to extract some metadata from the Modulefile for modules retrieved via Git: https://github.com/rodjek/librarian-puppet/blob/master/lib/librarian/puppet/source/git.rb#L86 There are a few issues and pull requests (some mine) in the librarian-puppet project discussing whether or not to remove the Puppet gem dependency: https://github.com/rodjek/librarian-puppet/issues/38 https://github.com/rodjek/librarian-puppet/pull/62 https://github.com/rodjek/librarian-puppet/pull/134 https://github.com/rodjek/librarian-puppet/pull/105 To get this working without relying on all of Puppet, it would be handy if Puppetlabs could ship the part of the code handling the Modulefile as as separate gem. To conclude: relying on the puppet gem currently does not work for Windows as the gem dependencies are not correct there.
Jira (FACT-167) PR (581): Issue/fact 79/stable/add facter schema - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (581): Issue/fact 79/stable/add facter schema - kylog jhoblitt commented: How difficult would it be to scan the collection for facts that don't have a schema defined? This is trivial but it would be nice if there was a flag to get stdout status output from validate.rb. As is, I had to check $? to make sure something had happened. Would it make sense for this to done as an rspec test that is skipped if the json-schema gem isn't available? I think there would be a lot of value of this code getting run via travis for PRs. /CC @adrienthebo Add Comment Facter / FACT-167 PR (581): Issue/fact 79/stable/add facter schema - kylog h2. Issue/fact 79/stable/add facter schema * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 581 Discussion|https://github.com/puppetlabs/facter/pull/581] * [Pull Request 581 File Diff|https://github.com/puppetlabs/facter/pull/581/files] h2. Pull Request Description (webhooks-id: be8b3... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-167) PR (581): Issue/fact 79/stable/add facter schema - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (581): Issue/fact 79/stable/add facter schema - kylog adrienthebo commented: As @jhoblitt said it could provide value to add testing for this into rspec for travis. However it's very easy to stub out method calls and return data that could never actually be generated in normal operation, so we will need to have acceptance test coverage as well. Add Comment Facter / FACT-167 PR (581): Issue/fact 79/stable/add facter schema - kylog h2. Issue/fact 79/stable/add facter schema * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 581 Discussion|https://github.com/puppetlabs/facter/pull/581] * [Pull Request 581 File Diff|https://github.com/puppetlabs/facter/pull/581/files] h2. Pull Request Description (webhooks-id: be8b3... 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.
Jira (PUP-665) Select a section
Title: Message Title Andrew Parker commented on an issue Re: Select a section The initial changes for this have caused some fallout. It regressed handling of templatedir = $confdir/templates because of the way in which hooks and application defaults are handled. It also broke rspec-puppet (and probably others) because of changed handling of nil in settings. Add Comment Puppet / PUP-665 Select a section puppet config set setting=value --section agent sets setting=value in the [agent] section of the puppet.conf file. --section should default to main. puppet config print setting --section agent reads the agent section's value for the setting. 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-224) PR (773): FOR REVIEW: Port PuppetDB to use trapperkeeper - nwolfe
Title: Message Title gepetto-bot commented on an issue Re: PR (773): FOR REVIEW: Port PuppetDB to use trapperkeeper - nwolfe cprice404 commented: Thanks, @senior . So, here's my laundry list: Rebase Add comments to bootstrap.cfg file Add namespaces to cli slingshot exceptions Remove Jetty config code Change SNAPSHOT dependency versions to point to our release versions Does that sound accurate? Add Comment PuppetDB / PDB-224 PR (773): FOR REVIEW: Port PuppetDB to use trapperkeeper - nwolfe h2. FOR REVIEW: Port PuppetDB to use trapperkeeper * Author: Nate Wolfe * Company: Puppet Labs * Github ID: [nwolfe|https://github.com/nwolfe] * [Pull Request 773 Discussion|https://github.com/puppetlabs/puppetdb/pull/773] * [Pull Request 773 File Diff|https://github.com/puppetlabs/puppetdb/pull/773/files] h2. Pull Request Description This...
Jira (FACT-170) PR (582): (maint) restrict redcarpet gem to = 2.3.0 - jhoblitt
Title: Message Title gepetto-bot commented on an issue Re: PR (582): (maint) restrict redcarpet gem to = 2.3.0 - jhoblitt puppetcla commented: CLA signed by all contributors. Add Comment Facter / FACT-170 PR (582): (maint) restrict redcarpet gem to = 2.3.0 - jhoblitt h2. (maint) restrict redcarpet gem to = 2.3.0 * Author: Joshua Hoblitt jhobl...@cpan.org * Company: * Github ID: [jhoblitt|https://github.com/jhoblitt] * [Pull Request 582 Discussion|https://github.com/puppetlabs/facter/pull/582] * [Pull Request 582 File Diff|https://github.com/puppetlabs/facter/pull/582/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 https://groups.google.com/groups/opt_out.
Jira (PUP-1189) Custom reports not working (Class is already defined in Puppet::Reports)
Title: Message Title redmine.exporter created an issue Puppet / PUP-1189 Custom reports not working (Class is already defined in Puppet::Reports) Issue Type: Bug Assignee: Unassigned Created: 19/Dec/13 9:22 AM Labels: redmine Priority: Normal Reporter: redmine.exporter I've got a client experiencing this with the boundary report from https://github.com/puppetlabs/puppetlabs-boundary Also someone in #puppet said they get it with the datadog report in Puppet 3.0. Here's the full message we get at the end of the run: err: Could not send report: Error 400 on SERVER: Could not autoload boundary: Class Boundary is already defined in Puppet::Reports Add Comment
Jira (PUP-1190) Problem parsing options in ssh_authorized_key
Title: Message Title redmine.exporter created an issue Puppet / PUP-1190 Problem parsing options in ssh_authorized_key Issue Type: Bug Assignee: Unassigned Created: 19/Dec/13 9:34 AM Labels: redmine Priority: Normal Reporter: redmine.exporter The following options line in a ssh_authorized_key resource isn't working as expected: pre options = [ command=\if [ -n $THING\\\ ];then echo;fi\, ], /pre When it is applied it writes the correct string out but repeated runs don't seem to parse in the rule correctly (it is truncated by the \\\) and always trigger a change pre Notice: /Stage[main]//Ssh_authorized_key[test]/options: options changed 'command=if [ -n \' to 'command=if [ -n \$THING\ ];then echo;fi' /pre [ We're doing rather more work in the option, the above is enough to display the behaviour ] Add Comment
Jira (PUP-1023) PR (2155): (maint) Use internal rubygems mirror during CI bootstrap - branan
Title: Message Title gepetto-bot commented on an issue Re: PR (2155): (maint) Use internal rubygems mirror during CI bootstrap - branan kylog commented: Also, maybe we should point this at stable and merge up? Add Comment Puppet / PUP-1023 PR (2155): (maint) Use internal rubygems mirror during CI bootstrap - branan h2. (maint) Use internal rubygems mirror during CI bootstrap * Author: Branan Purvine-Riley bra...@puppetlabs.com * Company: Puppet Labs * Github ID: [branan|https://github.com/branan] * [Pull Request 2155 Discussion|https://github.com/puppetlabs/puppet/pull/2155] * [Pull Request 2155 File Diff|https://github.com/puppetlabs/puppet/pull/2155/files]... 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 (FACT-167) PR (581): Issue/fact 79/stable/add facter schema - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (581): Issue/fact 79/stable/add facter schema - kylog jhoblitt commented: @adrienthebo I was thinking something simple, more or less what the acceptance test is doing by shelling out but then parsing the the output as rspec examples. That way stubbing wouldn't be an issue but facts that don't run in the travis env wouldn't be covered either. Add Comment Facter / FACT-167 PR (581): Issue/fact 79/stable/add facter schema - kylog h2. Issue/fact 79/stable/add facter schema * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 581 Discussion|https://github.com/puppetlabs/facter/pull/581] * [Pull Request 581 File Diff|https://github.com/puppetlabs/facter/pull/581/files] h2. Pull Request Description (webhooks-id: be8b3... 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 (FACT-167) PR (581): Issue/fact 79/stable/add facter schema - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (581): Issue/fact 79/stable/add facter schema - kylog kylog commented: Re scanning the output for facts that don't have a schema defined, that would be great and will ensure the schema gets updated as facts get added. I thought about two ways to do that but both have some difficulties: 1) have per-kernel list of required facts and set additionalProperties = false in the schema. However I think we'd need support in the json schema for conditional schema dependencies, which isn't there currently. (Maybe in schema 5??) 2) just thought of this on my ride in, but maybe we could have a default pattern that matches anything not matched elsewhere? If so, we could set that to some bogus type and that would always fail allowing us to catch new facts. I'll play with this a little bit. Add Comment Facter / FACT-167 PR (581): Issue/fact 79/stable/add facter schema - kylog h2. Issue/fact 79/stable/add facter schema * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 581 Discussion|https://github.com/puppetlabs/facter/pull/581] * [Pull Request 581 File Diff|https://github.com/puppetlabs/facter/pull/581/files] h2. Pull Request Description (webhooks-id: be8b3... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-167) PR (581): Issue/fact 79/stable/add facter schema - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (581): Issue/fact 79/stable/add facter schema - kylog kylog commented: The tweak to validate.rb is a good idea. I'll add a succeeded or failed validation output. Add Comment Facter / FACT-167 PR (581): Issue/fact 79/stable/add facter schema - kylog h2. Issue/fact 79/stable/add facter schema * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 581 Discussion|https://github.com/puppetlabs/facter/pull/581] * [Pull Request 581 File Diff|https://github.com/puppetlabs/facter/pull/581/files] h2. Pull Request Description (webhooks-id: be8b3... 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 (FACT-167) PR (581): Issue/fact 79/stable/add facter schema - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (581): Issue/fact 79/stable/add facter schema - kylog kylog commented: Travis coverage would be nice but it doesn't run on many platforms, so is limited in coverage. I started with acceptance tests because that gives us an opportunity to test against a number of real platforms. Add Comment Facter / FACT-167 PR (581): Issue/fact 79/stable/add facter schema - kylog h2. Issue/fact 79/stable/add facter schema * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 581 Discussion|https://github.com/puppetlabs/facter/pull/581] * [Pull Request 581 File Diff|https://github.com/puppetlabs/facter/pull/581/files] h2. Pull Request Description (webhooks-id: be8b3... 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.
Jira (FACT-171) PR (583): (fact-163) Remove relative path for FACTERLIB paths (which was unintenti... - kylog
Title: Message Title gepetto-bot created an issue Facter / FACT-171 PR (583): (fact-163) Remove relative path for FACTERLIB paths (which was unintenti... - kylog Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 19/Dec/13 10:00 AM Labels: github Priority: Normal Reporter: gepetto-bot (fact-163) Remove relative path for FACTERLIB paths (which was unintenti... Author: Kylo Ginsberg Company: Github ID: kylog Pull Request 583 Discussion Pull Request 583 File Diff Pull Request Description
Jira (PUP-1191) Puppet should not reset locale
Title: Message Title redmine.exporter created an issue Puppet / PUP-1191 Puppet should not reset locale Issue Type: Bug Assignee: Unassigned Created: 19/Dec/13 10:03 AM Labels: redmine Priority: Normal Reporter: redmine.exporter Puppet resets various locale related ENV variables to the posix default of 'C' immediately before invoked Kernel.exec to launch an executable (occurs when running a Single_exec in a recipe) http://github.com/reductivelabs/puppet/blob/master/lib/puppet/util.rb#L295 The problem is, the python interpreter will attempt to parse these variables to determine the default locale, and if it is set to 'C' (or not set at all as it will default to 'C'), 'None' will be returned, ignoring the true default locale. Thus any python script launched via Single_exec from a puppet recipe will not be able to get the default locale by invoking locale.getdefaultlocale(). This functionality is part of the standard python library and is relied upon by many various Python scripts. Add Comment
Jira (FACT-171) PR (583): (fact-163) Remove relative path for FACTERLIB paths (which was unintenti... - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (583): (fact-163) Remove relative path for FACTERLIB paths (which was unintenti... - kylog puppetcla commented: CLA signed by all contributors. Add Comment Facter / FACT-171 PR (583): (fact-163) Remove relative path for FACTERLIB paths (which was unintenti... - kylog h2. (fact-163) Remove relative path for FACTERLIB paths (which was unintenti... * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 583 Discussion|https://github.com/puppetlabs/facter/pull/583] * [Pull Request 583 File Diff|https://github.com/puppetlabs/facter/pull/583/files] h2. Pull Request Descrip... 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-1006) CLONE - Create packages
Title: Message Title Melissa Stone commented on an issue Re: CLONE - Create packages Packages staged at http://builds.puppetlabs.lan/puppet/3.4.0 Waiting on jenkins legacy for the windows package Add Comment Puppet / PUP-1006 CLONE - Create packages 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-171) PR (583): (fact-163) Remove relative path for FACTERLIB paths (which was unintenti... - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (583): (fact-163) Remove relative path for FACTERLIB paths (which was unintenti... - kylog jhoblitt commented: :+1: This was not an intention change in semantics. I think it makes more sense to try to covert a relative path to an absolute one rather than silently ignoring it but we should keep the previous behavior. Add Comment Facter / FACT-171 PR (583): (fact-163) Remove relative path for FACTERLIB paths (which was unintenti... - kylog h2. (fact-163) Remove relative path for FACTERLIB paths (which was unintenti... * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 583 Discussion|https://github.com/puppetlabs/facter/pull/583] * [Pull Request 583 File Diff|https://github.com/puppetlabs/facter/pull/583/files] h2. Pull Request Descrip... 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
Jira (PUP-1192) PR (2176): (maint) Windows file provider :links = :follow - Iristyle
Title: Message Title gepetto-bot created an issue Puppet / PUP-1192 PR (2176): (maint) Windows file provider :links = :follow - Iristyle Issue Type: Task Assignee: Unassigned Components: Community Created: 19/Dec/13 11:32 AM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Windows file provider :links = :follow Author: Ethan J. Brown Company: Github ID: Iristyle Pull Request 2176 Discussion Pull Request 2176 File Diff Pull Request Description
Jira (PUP-998) Start 3.4.0 Final - Dec 19, 2013
Title: Message Title Melissa Stone updated an issue Puppet / PUP-998 Start 3.4.0 Final - Dec 19, 2013 Change By: Melissa Stone Summary: Start3.4.0Final -Dec19,2013 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-1192) PR (2176): (maint) Windows file provider :links = :follow - Iristyle
Title: Message Title gepetto-bot commented on an issue Re: PR (2176): (maint) Windows file provider :links = :follow - Iristyle puppetcla commented: CLA signed by all contributors. Add Comment Puppet / PUP-1192 PR (2176): (maint) Windows file provider :links = :follow - Iristyle h2. (maint) Windows file provider :links = :follow * Author: Ethan J. Brown * Company: * Github ID: [Iristyle|https://github.com/Iristyle] * [Pull Request 2176 Discussion|https://github.com/puppetlabs/puppet/pull/2176] * [Pull Request 2176 File Diff|https://github.com/puppetlabs/puppet/pull/2176/files] h2. Pull Request Description - Prev... 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-1003) CLONE - Prepare puppet-announcement
Title: Message Title Melissa Stone assigned an issue to Ryan McKern Puppet / PUP-1003 CLONE - Prepare puppet-announcement Change By: Melissa Stone Assignee: MelissaStone RyanMcKern 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-171) PR (583): (fact-163) Remove relative path for FACTERLIB paths (which was unintenti... - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (583): (fact-163) Remove relative path for FACTERLIB paths (which was unintenti... - kylog Pull request (fact-163) Remove relative path for FACTERLIB paths (which was unintenti... has been closed. Add Comment Facter / FACT-171 PR (583): (fact-163) Remove relative path for FACTERLIB paths (which was unintenti... - kylog h2. (fact-163) Remove relative path for FACTERLIB paths (which was unintenti... * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 583 Discussion|https://github.com/puppetlabs/facter/pull/583] * [Pull Request 583 File Diff|https://github.com/puppetlabs/facter/pull/583/files] h2. Pull Request Descrip... 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-1194) PR (2177): Add guide to running local acceptance tests. - aperiodic
Title: Message Title gepetto-bot created an issue Puppet / PUP-1194 PR (2177): Add guide to running local acceptance tests. - aperiodic Issue Type: Task Assignee: Unassigned Components: Community Created: 19/Dec/13 2:37 PM Labels: github Priority: Normal Reporter: gepetto-bot Add guide to running local acceptance tests. Author: Dan Lidral-Porter Company: Github ID: aperiodic Pull Request 2177 Discussion Pull Request 2177 File Diff Pull Request Description Point to it
Jira (PUP-1120) Change default private key permissions to permit group read
Title: Message Title Joshua Cooper assigned an issue to Joshua Cooper Puppet / PUP-1120 Change default private key permissions to permit group read 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 (PUP-1194) PR (2177): Add guide to running local acceptance tests. - aperiodic
Title: Message Title gepetto-bot commented on an issue Re: PR (2177): Add guide to running local acceptance tests. - aperiodic zaphod42 commented: @aperiodic I think that you should just incorporate it into `acceptance/README.md`. We should try to make that the one source of how to run them rather than having all sorts of different docs scattered around. Might even consider consolidating the acceptance readme and the `README_DEVELOPER` Add Comment Puppet / PUP-1194 PR (2177): Add guide to running local acceptance tests. - aperiodic h2. Add guide to running local acceptance tests. * Author: Dan Lidral-Porter * Company: * Github ID: [aperiodic|https://github.com/aperiodic] * [Pull Request 2177 Discussion|https://github.com/puppetlabs/puppet/pull/2177] * [Pull Request 2177 File Diff|https://github.com/puppetlabs/puppet/pull/2177/files] h2. Pull Request Description Poin... 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
Jira (PUP-1023) PR (2155): (maint) Use internal rubygems mirror during CI bootstrap - branan
Title: Message Title gepetto-bot commented on an issue Re: PR (2155): (maint) Use internal rubygems mirror during CI bootstrap - branan Pull request (maint) Use internal rubygems mirror during CI bootstrap has been closed. Add Comment Puppet / PUP-1023 PR (2155): (maint) Use internal rubygems mirror during CI bootstrap - branan h2. (maint) Use internal rubygems mirror during CI bootstrap * Author: Branan Purvine-Riley bra...@puppetlabs.com * Company: Puppet Labs * Github ID: [branan|https://github.com/branan] * [Pull Request 2155 Discussion|https://github.com/puppetlabs/puppet/pull/2155] * [Pull Request 2155 File Diff|https://github.com/puppetlabs/puppet/pull/2155/files]... 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-1023) PR (2155): (maint) Use internal rubygems mirror during CI bootstrap - branan
Title: Message Title gepetto-bot commented on an issue Re: PR (2155): (maint) Use internal rubygems mirror during CI bootstrap - branan kylog commented: Merged in 485f7f14cf2897ba8adeb22c7c9b75d0e53d1aec Add Comment Puppet / PUP-1023 PR (2155): (maint) Use internal rubygems mirror during CI bootstrap - branan h2. (maint) Use internal rubygems mirror during CI bootstrap * Author: Branan Purvine-Riley bra...@puppetlabs.com * Company: Puppet Labs * Github ID: [branan|https://github.com/branan] * [Pull Request 2155 Discussion|https://github.com/puppetlabs/puppet/pull/2155] * [Pull Request 2155 File Diff|https://github.com/puppetlabs/puppet/pull/2155/files]... 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-1195) PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar
Title: Message Title gepetto-bot created an issue Puppet / PUP-1195 PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar Issue Type: Task Assignee: Unassigned Components: Community Created: 19/Dec/13 3:17 PM Labels: github Priority: Normal Reporter: gepetto-bot fix is_numeric/is_integer when checking non-string parameters Author: Simon Effenberg Company: Github ID: Savar Pull Request 213 Discussion Pull Request 213 File Diff Pull Request Description
Jira (HI-119) PR (168): (maint) Adding beaker gem required items - ferventcoder
Title: Message Title gepetto-bot created an issue Hiera / HI-119 PR (168): (maint) Adding beaker gem required items - ferventcoder Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 19/Dec/13 3:35 PM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Adding beaker gem required items Author: Rob Reynolds Company: Github ID: ferventcoder Pull Request 168 Discussion Pull Request 168 File Diff Pull Request Description This will allow us to use the beaker gem instead of cloning it
Jira (PUP-1012) CLONE - Updates the downloads page
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-1012 CLONE - Updates the downloads page Change By: Melissa Stone Assignee: EricSorenson MelissaStone 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-1015) Error: Could not intialize global default settings: undefined method `mode=' for #Puppet::Settings::AutosignSetting:0x7ff361614368
Title: Message Title Melissa Stone updated an issue Puppet / PUP-1015 Error: Could not intialize global default settings: undefined method `mode=' for #Puppet::Settings::AutosignSetting:0x7ff361614368 Change By: Melissa Stone Fix Version/s: 3.4.0 Fix Version/s: 3.4.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 (HI-119) PR (168): (maint) Adding beaker gem required items - ferventcoder
Title: Message Title gepetto-bot commented on an issue Re: PR (168): (maint) Adding beaker gem required items - ferventcoder ferventcoder commented: @jpartlow can you review and pull this in? Add Comment Hiera / HI-119 PR (168): (maint) Adding beaker gem required items - ferventcoder h2. (maint) Adding beaker gem required items * Author: Rob Reynolds * Company: * Github ID: [ferventcoder|https://github.com/ferventcoder] * [Pull Request 168 Discussion|https://github.com/puppetlabs/hiera/pull/168] * [Pull Request 168 File Diff|https://github.com/puppetlabs/hiera/pull/168/files] h2. Pull Request Description This will all... 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 (MCO-143) Windows agents stop working when the mcollective service cannot be restarted
Title: Message Title Nick Walker created an issue MCollective / MCO-143 Windows agents stop working when the mcollective service cannot be restarted Issue Type: Bug Assignee: Pieter Loubser Created: 19/Dec/13 4:24 PM Environment: Windows Priority: Normal Reporter: Nick Walker 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
Jira (PUP-1196) Add resources based on a Hash
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1196
Add resources based on a Hash
Issue Type:
New Feature
Assignee:
Unassigned
Created:
19/Dec/13 4:46 PM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
Create resources from a Hash, in fact the syntax for a resource looks like a Ruby Hash already. The idea is to use it in conjuntion with external_nodes or with functions which return hashes.
I'll explain it with an en example.
With this external_nodes yaml pre parameters: symlinks: /tmp/one: ensure: target1 /tmp/two: ensure: target2 classes:
foo_class /pre
and a this manifest: pre file {$symlinks:} /pre
Puppet should create two file resources /tmp/one and /tmp/two.
This feature allows the creation of simple resources, like a list of users or cron jobs, outside puppet.
Jira (PUP-647) PR (2022): (#7244) Add autosign command - adrienthebo
Title: Message Title Ryan McKern updated an issue Puppet / PUP-647 PR (2022): (#7244) Add autosign command - adrienthebo Change By: Ryan McKern Summary: PR(2022):(# 2744 7244 )Addautosigncommand-adrienthebo h2.(# 2744 7244 )Addautosigncommand *Author:AdrienThebogit+git...@somethingsinistral.net *Company:PuppetLabs *GithubID:[adrienthebo|https://github.com/adrienthebo] *[PullRequest2022Discussion|https://github.com/puppetlabs/puppet/pull/2022] *[PullRequest2022FileDiff|https://github.com/puppetlabs/puppet/pull/2022/files] h2.PullRequestDescription Thispullrequestaddssupportforusinganexternalcommandtoautosigncertificates.Ifthe`autosign_command`settingisspecified,incomingCSRswillberunwiththatcommand.ThespecifiedcommandwillbegiventheCSRnameasthefirstargument,andthebodyoftheCSRwillbeencodedinPEMformatandpassedtothecommandonstdin.ThisimplementspartofGH-1522. (webhooks-id:10bfd42b22d39c1fa54a97f32011b17e) 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
Jira (PUP-309) Merge packaging test harness changes/pe test updates puppet/jpartlow:integration/acceptance into stable/master
Title: Message Title Melissa Stone commented on an issue Re: Merge packaging test harness changes/pe test updates puppet/jpartlow:integration/acceptance into stable/master This was released in Puppet 3.3.2, correct? Should this then not be targeted at 3.4.0? Add Comment Puppet / PUP-309 Merge packaging test harness changes/pe test updates puppet/jpartlow:integration/acceptance into stable/master 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-1013) CLONE - Close merged pending release tickets in redmine and Resolved ticket jira
Title: Message Title Melissa Stone updated an issue Puppet / PUP-1013 CLONE - Close merged pending release tickets in redmine and Resolved ticket jira Change By: Melissa Stone Summary: CLONE-Closemergedpendingrelease bugs tickets inredmine / andResolvedticket jira 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-1197) Add downgrade flag to package provider base class (boolean)
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1197
Add downgrade flag to package provider base class (boolean)
Issue Type:
New Feature
Assignee:
Unassigned
Created:
19/Dec/13 5:19 PM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
Some package providers can downgrade (yum, for example). However it's not always safe to downgrade every package, so it would be nice to be able to say, per package, whether downgrading is enabled or not. So if I could do something like this:
package { foo: provider = yum, ensure = 1.2.3, downgrade = false }
package { bar: provider = yum, ensure = 4.5.6, downgrade = true }
... then when foo was at version 1.3.2, it would be left alone; but when bar was at version 5.3.2, it would be reverted to 4.5.6.
It seems like this is something that almost any versionable package provider could implement.
I can submit a patch for this on github, I'm just gauging interest before I send the patch in blindly. Thanks.
Jira (HI-119) PR (168): (maint) Adding beaker gem required items - ferventcoder
Title: Message Title gepetto-bot commented on an issue Re: PR (168): (maint) Adding beaker gem required items - ferventcoder puppetcla commented: CLA signed by all contributors. Add Comment Hiera / HI-119 PR (168): (maint) Adding beaker gem required items - ferventcoder h2. (maint) Adding beaker gem required items * Author: Rob Reynolds * Company: * Github ID: [ferventcoder|https://github.com/ferventcoder] * [Pull Request 168 Discussion|https://github.com/puppetlabs/hiera/pull/168] * [Pull Request 168 File Diff|https://github.com/puppetlabs/hiera/pull/168/files] h2. Pull Request Description This will all... 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.
