Jira (PUP-3653) Unable to create/force empty Windows groups
Title: Message Title Jo Rhett commented on PUP-3653 Re: Unable to create/force empty Windows groups This is very much not clear from the documentation description. Can we get a documentation update? auth_membership whether the provider is authoritative for group membership. Valid values are true, false, yes, no. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4644) puppet tells you to read man pages that aren't installed
Title: Message Title Jo Rhett created an issue Puppet / PUP-4644 puppet tells you to read man pages that aren't installed Issue Type: Bug Affects Versions: PUP 4.1.0 Assignee: Unassigned Created: 2015/05/22 12:24 AM Environment: [vagrant@client ~]$ uname -a Linux client.example.com 3.10.0-123.20.1.el7.x86_64 #1 SMP Thu Jan 29 18:05:33 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux [vagrant@client ~]$ cat /etc/redhat-release CentOS Linux release 7.0.1406 (Core) Priority: Normal Reporter: Jo Rhett Puppet instructs the user to read man pages which are not installed in Manpath from the puppet-agent rpm. >From your own Vagrant image: [vagrant@client ~]$ puppet --help (snip)
Jira (PUP-4645) render-as string products an object
Title: Message Title Jo Rhett created an issue Puppet / PUP-4645 render-as string products an object Issue Type: Bug Affects Versions: PUP 4.1.0 Assignee: Unassigned Created: 2015/05/22 12:27 AM Priority: Normal Reporter: Jo Rhett The man page for Puppet tells the user they can output facts in string format: $ puppet man facts ...(snip)... * --render-as FORMAT: The format in which to render o
Jira (PUP-4645) render-as string produces an object
Title: Message Title Jo Rhett updated an issue Puppet / PUP-4645 render-as string produces an object Change By: Jo Rhett Summary: render-as string products produces an object Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4642) Allow $environment to be used in external_nodes
Title: Message Title
Colin Deisenroth commented on PUP-4642
Re: Allow $environment to be used in external_nodes
I believe this is a unique issue worth considering. The other 2 issues you linked involve passing the agent's environment variable to the ENC (which is a worthwhile task).
This involves allowing me to have a unique ENC for each environment. This goes along with the "git branch per environment" model. Here's an example: If my ENC is a script that does regex statements to assign a $role variable to nodes, I would not want to make changes to the version of the script "production" is using. I would want to "git clone" the environment branch, and make any changes, test those changes directly on a few machines using puppet agent --test --environment=my_new_test --noop. Once I am happy with my changes and my new ENC settings, I can merge them into the production environment branch during an approved maintenance window.
I feel the more we can have cloned in environment branches (hieradata, ENC, modules, manifests) the easier it is to have multiple people branch off master and test changes, then review/merge those changes to master when they're ready. Having everyone work directly on the single ENC that all environments use hinders testing, release cycles, auditing, and code review of changes before they can affect production.
Hiera lets us have :datadir: /etc/puppet/environments/%{::environment}/hieradata so please let me do the same branching of my ENC script in environments directories as I can with hieradata and modules by properly supporting the $environment variable in external_nodes = $confdir/environments/$environment/enc.rb
Thank you for your time and consideration
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
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
Jira (PUP-4646) puppet functions with optional lambas cannot be called without lambda
Title: Message Title
Jo Rhett created an issue
Puppet / PUP-4646
puppet functions with optional lambas cannot be called without lambda
Issue Type:
Bug
Affects Versions:
PUP 4.1.0
Assignee:
Unassigned
Created:
2015/05/22 2:23 AM
Priority:
Normal
Reporter:
Jo Rhett
You cannot call a function with an optional lambda without supplying one.
function myfunc( $value, Callable $lambda = nil ) {
notice($value)
}
Jira (PUP-4646) puppet functions with optional lambas cannot be called without lambda
Title: Message Title
Jo Rhett updated an issue
Puppet / PUP-4646
puppet functions with optional lambas cannot be called without lambda
Change By:
Jo Rhett
You cannot call a function with an optional lambda without supplying one. {code}function myfunc( $value, Callable $lambda = nil ) { notice($value)}myfunc( 3 ){code}Puppet complains of a non-existent String being added.{noformat}Error: Evaluation Error: Error while evaluating a Function Call, myfunc called with mis-matched argumentsexpected: myfunc(Any value, Callable lambda?) - arg count {1,2}actual: myfunc(Integer, String) - arg count {2} at /vagrant/mytest.pp:4:1 on node client.example.com{noformat} Likewise, actually supplying the lambda doesn't work either, even though it admits the input matches what was provided:{noformat}Error: Evaluation Error: Error while evaluating a Function Call, function 'myfunc' called with mis-matched argumentsexpected: myfunc(Any value, Callable lambda?) - arg count {1,2}actual: myfunc(Integer, Callable[Any]) - arg count {2} at /vagrant/mytest.pp:8:1 on node client.example.com{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4642) Allow $environment to be used in external_nodes
Title: Message Title Colin Deisenroth commented on PUP-4642 Re: Allow $environment to be used in external_nodes I still would want this bug fixed, but on further consideration if either of the other 2 issues you mentioned were resolved so $environment variable is passed to the ENC script, then the main ENC script could just be a wrapper that calls $confdir/environments/$environment/enc.rb which would be a workaround to give the same functionality. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4333) Puppet package provider on windows fails if non-UTF8 characters are in Uninstall products name value
Title: Message Title Simon Wydooghe commented on PUP-4333 Re: Puppet package provider on windows fails if non-UTF8 characters are in Uninstall products name value I can confirm this issue. A quick peek through the list of applications shows Skype with the special trademark symbol next to it, this might be the culprit. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4642) Allow $environment to be used in external_nodes
Title: Message Title Henrik Lindberg commented on PUP-4642 Re: Allow $environment to be used in external_nodes Exactly. I don't see that as a workaround - in fact, that is the only way I can see this working. There must be an authoritative service that acts on a request from a node (this is currently the ENC). If we have another service - a proposed ENC-classifier, then we must call it with the same information that we provide to the ENC, then that service would do what? Return the name of the environment that is then given to the ENC? (That does not make sense). To achieve what you want, the agent specified environment must be passed in the call to the ENC. That is what PUP-4522 and PUP-4521 are about. With that implemented, you can do what you want in your ENC. Closing this as a duplicate; if not identical in idea, the work that needs to be done in Puppet is the same. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4646) puppet functions with optional lambas cannot be called without lambda
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4646 puppet functions with optional lambas cannot be called without lambda Change By: Henrik Lindberg Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4647) Yum provider uses rpm -e to uninstall packages
Title: Message Title
Kike Escorihuela Navarro created an issue
Puppet / PUP-4647
Yum provider uses rpm -e to uninstall packages
Issue Type:
Bug
Assignee:
Unassigned
Created:
2015/05/22 3:24 AM
Priority:
Normal
Reporter:
Kike Escorihuela Navarro
class gvpbi::install ($ensure) {
package {'pdi-gvp-bi-core': require => Class['gvpbibase'], provider => 'yum', install_options => [ '-d5', '-e5' ], ensure => $ensure, }
package {'pdi-python2.7-numpy': require => Class['gvpbibase'], provider => 'yum', install_options => [ '-d5', '-e5' ], ensure => absent, before => Package['pdi-gvp-bi-core'], }
}
but:
Error: Execution of '/bin/rpm -e pdi-python2.7-numpy-1.8.1-1.x86_64' returned 1: error: Failed dependencies: pdi-python2.7-numpy is needed by (installed) pdi-gvp-bi-core-3.1.0-175.ga7bcd2c.noarch Error: /Stage[main]/Gvpbi::Install/Package[pdi-python2.7-numpy]/ensure: change from 1.8.1-1 to absent failed: Execution of '/bin/rpm -e pdi-python2.7-numpy-1.8.1-1.x86_64' returned 1: error: Failed dependencies: pdi-python2.7-numpy is needed by (installed) pdi-gvp-bi-core-3.1.0-175.ga7bcd2c.noarch
but if I remove the package using yum the dependecies are automatically resolved and unistall the pdi-gvp-bi-core package.
Jira (PUP-4646) puppet functions with optional lambas cannot be called without lambda
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4646 puppet functions with optional lambas cannot be called without lambda Change By: Henrik Lindberg Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4646) puppet functions with optional lambas cannot be called without lambda
Title: Message Title Henrik Lindberg commented on PUP-4646 Re: puppet functions with optional lambas cannot be called without lambda This is a feature known to be missing; functions written in the Puppet Language cannot support lambdas. - the language specification actually has a note about this problem. The problem is really an internal problem with the implementation of Scope since a scope cannot in general be reliably used as the closure of a lambda as it will end up referring to the wrong set of values if a lambda is ever invoked after the function that received it has returned. Creating a new sane implementation of Scope is in our backlog and has been on the wish list for quite some time - it is not a big implementation per se, but the API consequences are quite big since there are a myeriad of constructs that hinge upon Scope being central (all functions are methods on scope as an example). It is acceptable to expect that those that implement functinos in Ruby abide by the rule "do not return a lambda", but we felt that having just a "do not walk on the grass" sign as the only safety mechanism in the puppet language was not acceptable. The error messages are not ideal. I think we should fix this by giving an explicit error; "passing a lambda/callable to a puppet function is not supported in this version" (or somesuch). (ping Thomas Hallgren for PUP-2315 consideration). So - there is the need to have several tickets: Functions written in Puppet should be able to accept a lambda (optional or required) - we probably need syntax for this as the idea to just stick the lambda as the last argument proved to be difficult in practice, we need to have a distinct way to handle this. Calling a function written in Puppet with a lambda should produce a meaningful error message (until they are supported) There should be a mechanism to call a Callable given to a puppet function - probably via the call operator - i.e. $lambda() Lambdas should be fist class values Not sure which one of these cases this ticket should represent. Add Comment
Jira (PUP-4646) puppet functions with optional lambas cannot be called without lambda
Title: Message Title Henrik Lindberg commented on PUP-4646 Re: puppet functions with optional lambas cannot be called without lambda Added PUP-1832 as a blocking issue since that is the umbrella ticket under which the new scope work exists. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4576) Prepare long form release notes and short form release story
Title: Message Title Henrik Lindberg commented on PUP-4576 Re: Prepare long form release notes and short form release story May want to tweak the last sentence so that users understand that "align" does not mean that 4.1.0 and 3.8.1 have the same set of features (since there are additional features in 4.1) - i.e. "align" should be read as: those that exist in 3.8.1 works the same way as in 4.1.0. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider
Title: Message Title
C Lang commented on PUP-1165
Re: Spurious 'trigger changed' messages generated by scheduled task provider
In 3.7.5, on a weekly task that was doing this to me, I found I could fix it simply by changing 'day_of_week' to 'on' - despite what the documentation says.
Before that I was getting:
trigger changed
'[ {'enabled' => 'true', 'every' => '1', 'index' => '0', 'on' => ['mon'], 'schedule' => 'weekly', 'start_date' => '2015-5-22', 'start_time' => '03:00'}
]'
to
'[ {'day_of_week' => 'mon', 'every' => '1', 'schedule' => 'weekly', 'start_date' => '2015-5-22', 'start_time' => '3:00'}
]'
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3653) Unable to create/force empty Windows groups
Title: Message Title Ryan Gard updated an issue Puppet / PUP-3653 Unable to create/force empty Windows groups Change By: Ryan Gard QA Contact: Eric Thompson Ryan Gard Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3653) Unable to create/force empty Windows groups
Title: Message Title Ryan Gard assigned an issue to Ethan Brown Puppet / PUP-3653 Unable to create/force empty Windows groups Change By: Ryan Gard Assignee: Ethan Brown Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3653) Unable to create/force empty Windows groups
Title: Message Title Ryan Gard commented on PUP-3653 Re: Unable to create/force empty Windows groups Hey Ethan Brown, per Jo Rhett's comment can we get a documentation update for this? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3653) Unable to create/force empty Windows groups
Title: Message Title Ryan Gard updated an issue Puppet / PUP-3653 Unable to create/force empty Windows groups Change By: Ryan Gard Priority: Blocker Normal Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3653) Unable to create/force empty Windows groups
Title: Message Title Ryan Gard commented on PUP-3653 Re: Unable to create/force empty Windows groups Jo Rhett the documentation is being updated to address your concerns. The linked ticket DOC-1651 is private, but I promise it resolves your issue. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-713) `facter -p` should be the default behavior
Title: Message Title Josh Cooper commented on FACT-713 Re: `facter -p` should be the default behavior Now that `facter --puppet` is deprecated, we don't want to make that the default behavior. Closing this as won't fix. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-26) Create acceptance test to compare a set of facts to expected values.
Title: Message Title Josh Cooper commented on FACT-26 Re: Create acceptance test to compare a set of facts to expected values. We added acceptance tests covering facts based on platform in FACT-958 . It covers the core facts for each supported platform, e.g. os, etc. We also have tests that the facter output comforms to the schema, e.g. for dynamic facts. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1482) PR (1378): (maint) allow ordering on non-extracted fields - wkalt
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1482 PR (1378): (maint) allow ordering on non-extracted fields - wkalt Change By: Kenneth Barber Fix Version/s: PDB 3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1534) Split query/command APIs
Title: Message Title AJ Roetker assigned an issue to AJ Roetker PuppetDB / PDB-1534 Split query/command APIs Change By: AJ Roetker Assignee: AJ Roetker Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-804) cfpropertylist is a missing dependency
Title: Message Title Josh Cooper commented on FACT-804 Re: cfpropertylist is a missing dependency It looks like your gem install is not selecting the universal-darwin version of the facter gem that expresses the dependency on CFPropertyList. I'm guessing it's related to rvm due to the .rvm in the error message. When using gem directly (no rvm, rbenv or bundler) it works as expected: svg7yqfin8g74rk:~ root# uname -rs Darwin 14.1.0 svg7yqfin8g74rk:~ root# ruby --version ruby 2.0.0p481 (2014-05-08 revision 45883) [universal.x86_64-darwin14] svg7yqfin8g74rk:~ root# gem list *** LOCAL GEMS *** bigdecimal (1.2.0) builder (3.2.2)
Jira (FACT-1015) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title Josh Cooper commented on FACT-1015 Re: deprecation of 'facter --puppet' removes critically necessary functionality I could have sworn we already had a ticket on this, but I can't find it. Yep, the functionality is important, and something we plan on addressing before removing the --puppet option. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider
Title: Message Title Rob Reynolds commented on PUP-1165 Re: Spurious 'trigger changed' messages generated by scheduled task provider Perhaps we need to update the documentation - it may already be updated. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3653) Unable to create/force empty Windows groups
Title: Message Title Rob Reynolds assigned an issue to Unassigned Puppet / PUP-3653 Unable to create/force empty Windows groups Change By: Rob Reynolds Assignee: Ethan Brown Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3653) Unable to create/force empty Windows groups
Title: Message Title Rob Reynolds commented on PUP-3653 Re: Unable to create/force empty Windows groups Jo Rhett When you state documentation update, do you mean in code or on docs.puppetlabs.com? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3653) Unable to create/force empty Windows groups
Title: Message Title
Rob Reynolds updated an issue
Puppet / PUP-3653
Unable to create/force empty Windows groups
Change By:
Rob Reynolds
In Windows, many groups are built-in and cannot be removed, therefore ' {{ ensure => absent ' }} is useless. Another approach would be to define the group as present with no members. For example:{noformat}group { 'Guests': ensure => 'present', members => [],}{noformat}Unfortunately, this will not remove any members of the built-in Guests group, but instead leave any members existing.The underlying goal is to ensure that all unnecessary groups are empty.h3. Update for Puppet 4In PUP 4.x+, because groups are not authoritative by default, you need the add {{auth_membership => true}} to the mix to force an existing group to empty.{noformat}group { 'Guests': ensure => 'present', members => [], auth_membership => true,}{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4532) Remove passenger testing in AIO pipelines
Title: Message Title Justin Stoller commented on PUP-4532 Re: Remove passenger testing in AIO pipelines Deleted Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4576) Prepare long form release notes and short form release story
Title: Message Title Nicholas Fagerlund commented on PUP-4576 Re: Prepare long form release notes and short form release story Ah, you're right. I hadn't noticed the deal with multi-var assignments et al when I wrote that. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-374) configure hiera to work out of the box
Title: Message Title
Eric Sorenson commented on HI-374
Re: configure hiera to work out of the box
I think if "work out of the box" means "make the default settings invisible because there's no config file", that is actually a worse user experience because there's no discoverability; it errs on the side of implicit magic.
The default config ought to be more realistic and in line with best-practices, which (based on other discussion) looks like it should be:
---
:backends:
- yaml
:hierarchy:
- "certname/%{clientcert}"
- common
:yaml:
:datadir: "/etc/puppetlabs/code/environments/%{environment}/hieradata"
I don't understand the confusion around the h
Jira (PUP-4567) Fix acceptance infrastructure
Title: Message Title Michael Smith commented on PUP-4567 Re: Fix acceptance infrastructure Actually, it appears to be running Ruby 1.9.3. I'm not clear on the failure, but it could be something in the acceptance test itself. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4532) Remove passenger testing in AIO pipelines
Title: Message Title Kylo Ginsberg commented on PUP-4532 Re: Remove passenger testing in AIO pipelines Justin Stoller: a nit, but can we rename the last step in https://jenkins.puppetlabs.com/view/All%20in%20One%20Agent/view/Stable/view/Puppet%20Agent%20Nightly/ from "Step 8" to "Step 7" now? Thanks! Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4532) Remove passenger testing in AIO pipelines
Title: Message Title Justin Stoller commented on PUP-4532 Re: Remove passenger testing in AIO pipelines Kylo Ginsberg, not nitpicky at all. My apologies about that. Updated. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-374) configure hiera to work out of the box
Title: Message Title Owen Rodabaugh commented on HI-374 Re: configure hiera to work out of the box Eric Sorenson I was not aware noreplace was an option based on the ticket description, agreed that explicitly dropping a config file on initial install and then not clobbering it on upgrade would be the best option. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-374) configure hiera to work out of the box
Title: Message Title Mark Butcher commented on HI-374 Re: configure hiera to work out of the box Just reopened hiera PR 268 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-96) Deprecate 'facter --puppet'
Title: Message Title
Kylo Ginsberg commented on FACT-96
Re: Deprecate 'facter --puppet'
Jo Rhett I didn't connect your comment to your example. Specifically, system_uptime is a built-in fact, not a plugin-synced fact. Are you asking about the ability to get an individual element of a structured fact (like system_uptime) from the command-line?
If so, with facter 3, you can use a dotted syntax on the command line, e.g.
$ ./bin/facter system_uptime
{
days => 27,
hours => 669,
seconds => 2410743,
uptime => "27 days"
}
$ ./bin/facter system_uptime.days
27
Jira (PDB-1469) puppetdb-terminus-2.3.3-1.el6 cannot find rubygems-json package
Title: Message Title John Duarte commented on PDB-1469 Re: puppetdb-terminus-2.3.3-1.el6 cannot find rubygems-json package FYI: This is still broken. It is blocking testing of PDB 2.3.3 on el6 with Puppet 4.x. Kenneth Barber, do you know if it would be safe for Matthaus Owens to remove the rubygem-json dependency in PDB 2.3.x? cc Ryan Senior Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1545) PR (1413): (maint) Pass test_url to install_puppetdb helper function - ajroetker
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1545 PR (1413): (maint) Pass test_url to install_puppetdb helper function - ajroetker Issue Type: Task Assignee: Unassigned Created: 2015/05/22 1:38 PM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Pass test_url to install_puppetdb helper function Author: Andrew Roetker <> Company: Puppet Labs Github ID: ajroetker Pull Request 1413 Discussion Pull Request 1413 File Diff Pull Request Description (webhooks-id: bceb816eb03ff9a718cd263c5ebdde6d)
Jira (PDB-1545) PR (1413): (maint) Pass test_url to install_puppetdb helper function - ajroetker
Title: Message Title gepetto-bot commented on PDB-1545 Re: PR (1413): (maint) Pass test_url to install_puppetdb helper function - ajroetker pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1288/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1545) PR (1413): (maint) Pass test_url to install_puppetdb helper function - ajroetker
Title: Message Title gepetto-bot commented on PDB-1545 Re: PR (1413): (maint) Pass test_url to install_puppetdb helper function - ajroetker pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1290/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1545) PR (1413): (maint) Pass test_url to install_puppetdb helper function - ajroetker
Title: Message Title gepetto-bot commented on PDB-1545 Re: PR (1413): (maint) Pass test_url to install_puppetdb helper function - ajroetker Pull request (maint) Pass test_url to install_puppetdb helper function has been closed. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-918) Virtualization facts are incorrect in SPARC Solaris LDoms
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-918 Virtualization facts are incorrect in SPARC Solaris LDoms Change By: Kylo Ginsberg Sprint: Client 2015-06- 10 24 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-912) FQDN reported as just hostname in SPARC
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-912 FQDN reported as just hostname in SPARC Change By: Kylo Ginsberg Sprint: Client 2015-06- 10 24 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-910) Solaris is missing the LDom facts
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-910 Solaris is missing the LDom facts Change By: Kylo Ginsberg Sprint: Client 2015-06- 10 24 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-961) Windows binary sizes are huge
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-961 Windows binary sizes are huge Change By: Kylo Ginsberg Sprint: Client 2015-06- 10 24 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-915) Serialnumber fact doesn't resolve in SPARC Solaris
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-915 Serialnumber fact doesn't resolve in SPARC Solaris Change By: Kylo Ginsberg Sprint: Client 2015-06- 10 24 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-911) manufacturer and productname facts are missing in SPARC Solaris
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-911 manufacturer and productname facts are missing in SPARC Solaris Change By: Kylo Ginsberg Sprint: Client 2015-06- 10 24 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-964) Unable to find Ruby library on Debian 8 "Jessie"
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-964 Unable to find Ruby library on Debian 8 "Jessie" Change By: Kylo Ginsberg Sprint: Client 2015-06- 10 24 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-909) Processor facts are incorrect in SPARC Solaris
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-909 Processor facts are incorrect in SPARC Solaris Change By: Kylo Ginsberg Sprint: Client 2015-06- 10 24 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4482) Add support for PE platforms/repos/paths
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4482 Add support for PE platforms/repos/paths Change By: Kylo Ginsberg Sprint: Client 2015-06- 10 24 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-974) Compare facter 3 AIX output with facter 2 AIX output on AIX 5.3
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-974 Compare facter 3 AIX output with facter 2 AIX output on AIX 5.3 Change By: Kylo Ginsberg Sprint: Client 2015-06-10 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-974) Compare facter 3 AIX output with facter 2 AIX output on AIX 5.3
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-974 Compare facter 3 AIX output with facter 2 AIX output on AIX 5.3 Change By: Kylo Ginsberg Fix Version/s: FACT 3.1.0 Fix Version/s: FACT 3.x Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-974) Compare facter 3 AIX output with facter 2 AIX output on AIX 5.3
Title: Message Title Kylo Ginsberg commented on FACT-974 Re: Compare facter 3 AIX output with facter 2 AIX output on AIX 5.3 AFAIK we do not have an AIX 5.3 toolchain yet, so I'm dropping this from Facter 3.1.0 and tagging it for 3.x. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-973) Compare facter 3 AIX output with facter 2 AIX output on AIX 7.1
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-973 Compare facter 3 AIX output with facter 2 AIX output on AIX 7.1 Change By: Kylo Ginsberg Sprint: Client 2015-06- 10 24 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1006) Add Cisco NXOS support
Title: Message Title Kylo Ginsberg commented on FACT-1006 Re: Add Cisco NXOS support FACT-976 is the ticket for adding this to facter 3. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1006) Add Cisco NXOS support
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1006 Add Cisco NXOS support Change By: Kylo Ginsberg Fix Version/s: FACT 3.1.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1006) Add Cisco NXOS support
Title: Message Title Kylo Ginsberg commented on FACT-1006 Re: Add Cisco NXOS support We can leave this ticket open in case we decide we want to add this to Ruby facter. But for now I've dropped the fix version. The ticket of interest is FACT-976. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3930) Applying catalogs spends an inordinate amount of time checking for failed dependencies.
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3930 Applying catalogs spends an inordinate amount of time checking for failed dependencies. Change By: Kylo Ginsberg Sprint: Client 2015-06- 24 10 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4452) Support passenger packages
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4452 Support passenger packages Change By: Kylo Ginsberg Epic Status: To Do Done Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1314) Add a sync event log file
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1314 Add a sync event log file Change By: Ryan Senior Fix Version/s: PDB 3.0.0 Fix Version/s: PDB 3.1.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2386) Puppet Package Acceptance provides the equivalent of a manual smoke test.
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2386 Puppet Package Acceptance provides the equivalent of a manual smoke test. Change By: Kylo Ginsberg Epic Status: To Do Done Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2386) Puppet Package Acceptance provides the equivalent of a manual smoke test.
Title: Message Title Kylo Ginsberg commented on PUP-2386 Re: Puppet Package Acceptance provides the equivalent of a manual smoke test. This epic has no tickets. All the linked tickets are closed except for one ticket which is itself in another epic. This isn't serving much purpose anymore so closing. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-550) Work to enhance Puppet Performance
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-550 Work to enhance Puppet Performance Change By: Kylo Ginsberg Epic Status: To Do Done Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-550) Work to enhance Puppet Performance
Title: Message Title Kylo Ginsberg commented on PUP-550 Re: Work to enhance Puppet Performance All the tickets in this epic are resolved, so resolving this. Jira cleanup! Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4543) Document best practices for acceptance tests with puppet 4
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4543 Document best practices for acceptance tests with puppet 4 Change By: Kylo Ginsberg Sprint: Client 2015-06-24 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4567) Fix acceptance infrastructure
Title: Message Title Josh Cooper commented on PUP-4567 Re: Fix acceptance infrastructure So it looks like the test installs puppet-server, but is actually running with webrick. xqsxndjjt326ypw.delivery.puppetlabs.net (master) 14:25:15$ yum -y install puppet-server Later in with_puppet_running_on, we start the puppetmaster service which is webrick. It should be starting puppetserver: xqsxndjjt326ypw.delivery.puppetlabs.net (master) 14:26:24$ puppet resource service puppetmaster ensure=running Debug: new listener called performance Debug: registering instrumentation listener performance Debug: new listener called log Debug: registering instrumentation listener log Debug: Runtime environment: puppet_version=3.8.0, ruby_version=1.8.7, run_mode=user Note the ruby_version=1.8.7 is coming from the puppet resource application being used to start the puppetmaster (as opposed t
Jira (FACT-950) Switch to a tagged version of Leatherman
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-950 Switch to a tagged version of Leatherman Change By: Kylo Ginsberg Sprint: Client 2015-06- 10 24 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3653) Unable to create/force empty Windows groups
Title: Message Title Rob Reynolds commented on PUP-3653 Re: Unable to create/force empty Windows groups I did just create https://github.com/puppetlabs/puppet/pull/3963 as a possible followup to the actual code documentation. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1016) Repeated resolution of a facter fact causes never GC'd object references
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1016 Repeated resolution of a facter fact causes never GC'd object references Change By: Kylo Ginsberg Scrum Team: Puppet Server Client Platform Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1016) Repeated resolution of a facter fact causes never GC'd object references
Title: Message Title Kylo Ginsberg moved an issue Facter / FACT-1016 Repeated resolution of a facter fact causes never GC'd object references Change By: Kylo Ginsberg Component/s: Puppet Server Key: PE FACT - 9848 1016 Project: Puppet Enterprise [Internal] Facter Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1016) Repeated resolution of a facter fact causes never GC'd object references
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1016 Repeated resolution of a facter fact causes never GC'd object references Change By: Kylo Ginsberg Comment: [~kylo] please feel free to move it, I was just creating subtasks here as placeholders while I fleshed out the details. Have been expecting that they would get moved around once they were ready. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1016) Repeated resolution of a facter fact causes never GC'd object references
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1016 Repeated resolution of a facter fact causes never GC'd object references Change By: Kylo Ginsberg Comment: [~chris] any objections to my moving this ticket to FACT and changing the summary from a (rhetorical?) question to a statement? Alternately, If you'd rather preserve this as a subtask here (which makes some sense too), I can create a new FACT ticket and link it. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1016) Repeated resolution of a facter fact causes never GC'd object references
Title: Message Title Kylo Ginsberg commented on FACT-1016 Re: Repeated resolution of a facter fact causes never GC'd object references We should start by characterizing what a fix for this would entail in both ruby and native facter. I haven't studied it enough to know at this point. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1016) Repeated resolution of a facter fact causes never GC'd object references
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1016 Repeated resolution of a facter fact causes never GC'd object references Change By: Kylo Ginsberg Sub-team: jade Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1011) Docs prep for facter 3
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1011 Docs prep for facter 3 Change By: Kylo Ginsberg Sprint: Client 2015-06-10 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1016) Repeated resolution of a facter fact causes never GC'd object references
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1016 Repeated resolution of a facter fact causes never GC'd object references Change By: Kylo Ginsberg Sprint: Client 2015-07-08 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4603) Enable acceptance testing in CI Pipeline
Title: Message Title Michael Smith updated an issue Puppet / PUP-4603 Enable acceptance testing in CI Pipeline Change By: Michael Smith Acceptance testing in CI is blocked on several package releases. Once those are released, enable the pipeline and ensure it passes. This task should include updating testing to use Puppet Server 2.1, and re-enabling EL6 testing. The CI pipeline is setup at https://jenkins-modules.delivery.puppetlabs.net/view/4.%20cross%20platform/view/agent_upgrade/view/master/. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2628) Ability to add a member to a group, instead of specifying the complete list
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2628 Ability to add a member to a group, instead of specifying the complete list Change By: Rob Reynolds Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4522) Provide Facts for a classifier to select whether to enable overriding the environment
Title: Message Title Michael Smith commented on PUP-4522 Re: Provide Facts for a classifier to select whether to enable overriding the environment Sending `agent_specified_environment` as a fact means the normal classifier workflow should match it and pick the correct classification on the first try. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2628) Ability to add a member to a group, instead of specifying the complete list
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2628 Ability to add a member to a group, instead of specifying the complete list Change By: Rob Reynolds Fix Version/s: PUP 3.8.0 Fix Version/s: PUP 4.1.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-892) load_average resolver is not really posix
Title: Message Title Michael Smith assigned an issue to QA Facter / FACT-892 load_average resolver is not really posix Change By: Michael Smith Status: Ready for Merge Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4567) Fix acceptance infrastructure
Title: Message Title Josh Cooper commented on PUP-4567 Re: Fix acceptance infrastructure So the problem is ruby 1.8.7 and future parser on the master. The work for switching to puppetserver is in PUP-4603. I've removed redhat-6 from the CI pipeline, and it is passing on redhat-7: https://jenkins-modules.puppetlabs.com/view/4.%20cross%20platform/view/agent_upgrade/view/master/job/modules_puppetlabs-agent_upgrade_intn-sys_core-master-foss-stable/9/ Marking this as passed CI. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1015) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title
Kylo Ginsberg commented on FACT-1015
Re: deprecation of 'facter --puppet' removes critically necessary functionality
Ah I saw the comment on
FACT-96
but missed this ticket initially. So I'll ask here
Jo Rhett I didn't connect your comment to your example. Specifically, system_uptime is a built-in fact, not a plugin-synced fact. Are you asking about the ability to get an individual element of a structured fact (like system_uptime) from the command-line?
If so, with facter 3, you can use a dotted syntax on the command line, e.g.
$ ./bin/facter system_uptime
{
days => 27,
hours => 669,
seconds => 2410743,
uptime => "27 days"
}
$ ./bin/facter system_uptime.days
27
Jira (PUP-4603) Enable acceptance testing in CI Pipeline
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-4603 Enable acceptance testing in CI Pipeline Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4603) Enable acceptance testing in CI Pipeline
Title: Message Title Michael Smith updated an issue Puppet / PUP-4603 Enable acceptance testing in CI Pipeline Change By: Michael Smith Sprint: Client 2015-06-10 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4603) Enable acceptance testing againt Puppet Server in CI Pipeline
Title: Message Title Michael Smith updated an issue Puppet / PUP-4603 Enable acceptance testing againt Puppet Server in CI Pipeline Change By: Michael Smith Summary: Enable acceptance testing againt Puppet Server in CI Pipeline Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4648) Problem of identation with epp()
Title: Message Title
Francois Lafont created an issue
Puppet / PUP-4648
Problem of identation with epp()
Issue Type:
Bug
Affects Versions:
PUP 4.1.0
Assignee:
Unassigned
Components:
Language
Created:
2015/05/22 4:08 PM
Environment:
I'm on Ubuntu Trusty (updated). I have followed the documentation for the installation of Puppet 4 server.
Priority:
Normal
Reporter:
Francois Lafont
Hi,
I have just tried the epp() function in a basic module with this code:
class test {
Jira (PUP-2400) Add acceptance tests for mount type
Title: Message Title John Duarte assigned an issue to Kurt Wall Puppet / PUP-2400 Add acceptance tests for mount type Change By: John Duarte Assignee: John Duarte Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2400) Add acceptance tests for mount type
Title: Message Title John Duarte commented on PUP-2400 Re: Add acceptance tests for mount type Kurt Wall I have amended the PR to correct the teardown failures that you uncovered. Please see if it behaves better in review. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4576) Prepare long form release notes and short form release story
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4576 Prepare long form release notes and short form release story Yes, much better henrik Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4492) Investigate: plan for module testing with puppet-agent
Title: Message Title Kylo Ginsberg commented on PUP-4492 Re: Investigate: plan for module testing with puppet-agent Marking this as resolved. The modules team has a plan for testing with puppet-agent. There is also a longer term discussion / planning effort around testing in general (SDK etc) but that's definitely outside the scope of this ticket Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4342) add acceptance to call all parser functions
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-4342 add acceptance to call all parser functions Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
