Jira (PUP-7613) DNF should be default package provider for Fedora
Title: Message Title Josh Cooper commented on PUP-7613 Re: DNF should be default package provider for Fedora Martin Jackson Thanks for filing this issue and the related PR. I've marked this as a dup, as discussion/effort is continuing on the other ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7638) `puppet config print certname` only reads from [main], defaults to FQDN if no value is in [main]
Title: Message Title Josh Cooper assigned an issue to Paul Showalter Puppet / PUP-7638 `puppet config print certname` only reads from [main], defaults to FQDN if no value is in [main] Change By: Josh Cooper Assignee: Paul Showalter Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7635) Custom service provider is always selected as default
Title: Message Title Josh Cooper commented on PUP-7635 Re: Custom service provider is always selected as default Hi Daniel, I'm guessing your provider is chosen because neither debian nor systemd service providers are selected as the default. Note the debian provider is not the default on Debian 8, due to systemd. And the systemd provider may not be suitable if /run/systemd/system doesn't exist. What fact values do you get for operatingsystem and operatingsystemmajrelease? Does /run/systemd/system exist? Is systemctl available in your PATH and executable? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6739) Error running puppet with non-existent and non-default environment
Title: Message Title Dylan Ratcliffe commented on PUP-6739 Re: Error running puppet with non-existent and non-default environment It's worth noting here that this will also break puppetserver if you try to start puppetserver on a machine that doesn't have it's environment on disk. A good example of this is if you try to promote a non-production agent to a compile master, puppetserver fails to start because of this bug. Which is extra annoying because you need puppetserver running to get code manager/file-sync to actually create the directory and fix the issue. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7628) Cannot run puppet commands or startup master when environment directory missing
Title: Message Title Dylan Ratcliffe commented on PUP-7628 Re: Cannot run puppet commands or startup master when environment directory missing Thanks Josh Cooper I knew someone would be able to find it Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6739) Error running puppet with non-existent and non-default environment
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6739 Error running puppet with non-existent and non-default environment Change By: Josh Cooper Fix Version/s: PUP 5.y Fix Version/s: PUP 5.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7628) Cannot run puppet commands or startup master when environment directory missing
Title: Message Title Josh Cooper commented on PUP-7628 Re: Cannot run puppet commands or startup master when environment directory missing Thanks Dylan Ratcliffe and Jeremy Barlow, this is a dup of PUP-6739, which has links to many other similarly reported issues where puppet can't run if it's configured to use something other than production and the directory doesn't exist. Closing this as a dup. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7632) FreeBSD package providers are outdated
Title: Message Title Josh Cooper commented on PUP-7632 Re: FreeBSD package providers are outdated Hi Helmut, puppet has a pkgng package provider for FreeBSD, but we do not have systems to test against in-house, so it may need some attention and updating. Could you take a look and either close this ticket or update it with information about what isn't working? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7632) FreeBSD package providers are outdated
Title: Message Title Josh Cooper assigned an issue to Helmut Ritter Puppet / PUP-7632 FreeBSD package providers are outdated Change By: Josh Cooper Assignee: Helmut Ritter Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7638) `puppet config print certname` only reads from [main], defaults to FQDN if no value is in [main]
Title: Message Title R.I.Pienaar commented on PUP-7638 Re: `puppet config print certname` only reads from [main], defaults to FQDN if no value is in [main] Isn't this expected behaviour? Config print runs with the same config as apply would - so it does not consult agent. You can set which run mode you want on the CLI Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7555) Update default fileserver.conf that allow/deny are no longer allowed
Title: Message Title Geoff Nichols commented on PUP-7555 Re: Update default fileserver.conf that allow/deny are no longer allowed PR #5948 merged to puppet#master at https://github.com/puppetlabs/puppet/commit/17c651b4075df86de4ed1820ec994ce6b3116c24. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6395) file type documentation does not have quotes around modes in doc comments
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6395 file type documentation does not have quotes around modes in doc comments Change By: Josh Cooper Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6395) file type documentation does not have quotes around modes in doc comments
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6395 file type documentation does not have quotes around modes in doc comments Change By: Josh Cooper Sprint: Agent 2017-06-14 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6395) file type documentation does not have quotes around modes in doc comments
Title: Message Title Josh Cooper commented on PUP-6395 Re: file type documentation does not have quotes around modes in doc comments Merged to master in https://github.com/puppetlabs/puppet/commit/930a119de5e330151a57111e74a3b1acaa54f671 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6395) file type documentation does not have quotes around modes in doc comments
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6395 file type documentation does not have quotes around modes in doc comments Change By: Josh Cooper Fix Version/s: PUP 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7639) Measure performance delta - Server 2.7+PA 1.10 vs Platform 5
Title: Message Title Moses Mendoza commented on PUP-7639 Re: Measure performance delta - Server 2.7+PA 1.10 vs Platform 5 ping Geoff Nichols for queuing up for tech debt sprints Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7639) Measure performance delta - Server 2.7+PA 1.10 vs Platform 5
Title: Message Title Moses Mendoza commented on PUP-7639 Re: Measure performance delta - Server 2.7+PA 1.10 vs Platform 5 cc Joe Pinsonault Jeremy Barlow Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7639) Measure performance delta - Server 2.7+PA 1.10 vs Platform 5
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7639 Measure performance delta - Server 2.7+PA 1.10 vs Platform 5 Change By: Moses Mendoza Fix Version/s: PUP 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7639) Measure performance delta - Server 2.7+PA 1.10 vs Platform 5
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7639 Measure performance delta - Server 2.7+PA 1.10 vs Platform 5 Change By: Moses Mendoza Sprint: Agent Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7639) Measure performance delta - Server 2.7+PA 1.10 vs Platform 5
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7639 Measure performance delta - Server 2.7+PA 1.10 vs Platform 5 Change By: Moses Mendoza Summary: Measure performance delta - server Server 2.7 / + PA 1.10 vs Platform 5 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7639) Measure performance delta - Server 2.7+PA 1.10 vs Platform 5
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7639 Measure performance delta - Server 2.7+PA 1.10 vs Platform 5 Change By: Moses Mendoza Acceptance Criteria: Perf data is gathered and distributed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7639) Measure performance delta - server 2.7/PA 1.10 vs Platform 5
Title: Message Title Moses Mendoza created an issue Puppet / PUP-7639 Measure performance delta - server 2.7/PA 1.10 vs Platform 5 Issue Type: Improvement Assignee: Unassigned Created: 2017/06/08 7:54 PM Priority: Normal Reporter: Moses Mendoza There are change sets targeted for Puppet 5 that may substantially impact^^improve performance: changing to JSON as the default serialization format (PUP-3852) because we are now using native JSON parsing vs pure ruby PSON threading facts through a request vs (re-)querying them ( PUP-3438 ) because we are avoiding superfluous network traffic, PDB ops and disk IO turning off node caching by default ( PUP-6060 ) because we are avoiding superfluous disk IO in the best case and network traffic in the worst (ie node cache terminus configured to be PDB) With SERVER-1831/https://github.com/puppetlabs/gatling-puppet-load-test/pull/128, we will be able to specify the Puppet Agent
Jira (PUP-3486) Update jetty_external_root_ca acceptance test to use disabled CA service
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3486 Update jetty_external_root_ca acceptance test to use disabled CA service Change By: Jeremy Barlow Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3042) If a catalog has a dependency cycle, it does not count as failed
Title: Message Title
Josh Cooper commented on PUP-3042
Re: If a catalog has a dependency cycle, it does not count as failed
Verified using:
$ cat cycle.rb
notify { foo: require => Notify[bar] }
notify { bar: require => Notify[foo] }
$ bx puppet apply cycle.rb
Notice: Compiled catalog for XXX in environment production in 0.05 seconds
Error: Found 1 dependency cycle:
(Notify[bar] => Notify[foo] => Notify[bar])
Try the '--graph' option and opening the resulting '.dot' file in OmniGraffle or GraphViz
Error: Failed to apply catalog: One or more resource dependency cycles detected in graph
The overall report status is failed:
Jira (PUP-3042) If a catalog has a dependency cycle, it does not count as failed
Title: Message Title Josh Cooper assigned an issue to Unassigned Puppet / PUP-3042 If a catalog has a dependency cycle, it does not count as failed Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7638) `puppet config print certname` only reads from [main], defaults to FQDN if no value is in [main]
Title: Message Title Paul Schaffer created an issue Puppet / PUP-7638 `puppet config print certname` only reads from [main], defaults to FQDN if no value is in [main] Issue Type: Bug Affects Versions: PUP 4.10.1 Assignee: Unassigned Created: 2017/06/08 3:55 PM Priority: Normal Reporter: Paul Schaffer `puppet config print certname` appears to read from the [main] section of puppet.conf only, and if certname is not set in that section it defaults to the FQDN of the system. To test: 1. Spin up a blank box. 2. Create puppet.conf and set the certname to something other than the FQDN. 3. Install the agent, confirming that the certname has been set to something other than the FQDN. 4. Run `puppet config print certname` and compare to expected output. Additionally: 1. Open puppet.conf, and if certname is set in [main] comment it out. 2. Add a unique certname value to the [agent] section and save and close the file. 3. Run 'puppet config print certname' and compare to expected output. 4. Run 'puppet config print --section=agent` and compare. 5. Repeat for any other sections, such as [master].
Jira (PUP-7616) Fix broken implementation of Property#change_to_s method
Title: Message Title Josh Cooper assigned an issue to Unassigned Puppet / PUP-7616 Fix broken implementation of Property#change_to_s method Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7616) Fix broken implementation of Property#change_to_s method
Title: Message Title Josh Cooper commented on PUP-7616 Re: Fix broken implementation of Property#change_to_s method Follow up merged to master in https://github.com/puppetlabs/puppet/commit/a80e24dd49d0bfa9143d882fdd2bc07d9935add6 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6405) Pip package provider runs every time when updating setuptools
Title: Message Title Ben Hines updated an issue Puppet / PUP-6405 Pip package provider runs every time when updating setuptools Change By: Ben Hines Affects Version/s: PUP 4.10.1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3549) Have acceptance tests use puppet5-nightly
Title: Message Title John Duarte updated an issue PuppetDB / PDB-3549 Have acceptance tests use puppet5-nightly Change By: John Duarte QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3549) Have acceptance tests use puppet5-nightly
Title: Message Title John Duarte assigned an issue to Russell Mull PuppetDB / PDB-3549 Have acceptance tests use puppet5-nightly Change By: John Duarte Assignee: John Duarte Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3549) Have acceptance tests use puppet5-nightly
Title: Message Title
John Duarte updated an issue
PuppetDB / PDB-3549
Have acceptance tests use puppet5-nightly
Change By:
John Duarte
Acceptance Criteria:
h3. Case 1: Specified PuppetDB build*Given* that I have specified a value for {{PUPPETDB_PACKAGE_BUILD_VERSION}}*And* I have specified {{NIGHTLY=true}}*When* I run the {{./ext/jenkins/beaker-tests.sh}} script from the {{puppetdb/acceptance}} directory*Then* the specified {{PUPPETDB_PACKAGE_BUILD_VERSION}} of {{puppetdb}} should be installed*And* the published {{puppet5-nightly}} package for {{puppet-agent}} should be installed*And* the published {{puppet5-nightly}} package for {{puppetserver}} should be installedh3. Case 2: No specified PuppetDB build*Given* I have specified {{NIGHTLY=true}}*When* I run the {{./ext/jenkins/beaker-tests.sh}} script from the {{puppetdb/acceptance}} directory*Then*the published {{puppet5-nightly}} package for {{puppetdb}} should be installed*And* the published {{puppet5-nightly}} package for {{puppet-agent}} should be installed*And* the published {{puppet5-nightly}} package for {{puppetserver}} should be installed
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3549) Have acceptance tests use puppet5-nightly
Title: Message Title John Duarte created an issue PuppetDB / PDB-3549 Have acceptance tests use puppet5-nightly Issue Type: Task Assignee: John Duarte Created: 2017/06/08 1:29 PM Priority: Normal Reporter: John Duarte When using installing component dependencies (e.g. puppet-agent, puppetserver) from nighties for acceptance testing, these should be installed from puppet5-nightly repositories. These are located at the following URLs: http://yum.puppetlabs.com/puppet5-nightly http://apt.puppetlabs.com If a test build version for PuppetDB is not specified, then PuppetDB should also be installed using the puppet5-nightly repo version. Add Comment This message was sent by Atlassian
Jira (PUP-7612) It is impossible to navigate an integer keyed Hiera hash using dotted keys
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7612 It is impossible to navigate an integer keyed Hiera hash using dotted keys Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7637) Switch to using ci:test:git for puppet component integration tests
Title: Message Title Maggie Dreyer created an issue Puppet / PUP-7637 Switch to using ci:test:git for puppet component integration tests Issue Type: Task Assignee: Unassigned Created: 2017/06/08 11:03 AM Priority: Normal Reporter: Maggie Dreyer In order to avoid having to build a puppet-agent package in the puppet component pipeline, we would like to switch to using ci:test:git in the integration step of the pipeline. This will clone puppet and run the tests on the test target standalone. We should still be able to run the same test subsets we usually run. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7634) Puppet device - make it threadable
Title: Message Title Thomas Honey assigned an issue to Thomas Honey Puppet / PUP-7634 Puppet device - make it threadable Change By: Thomas Honey Assignee: Henrik Lindberg Thomas Honey Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7636) Determine list of platforms for puppet component smoke testing with ci:test:git
Title: Message Title Maggie Dreyer created an issue Puppet / PUP-7636 Determine list of platforms for puppet component smoke testing with ci:test:git Issue Type: Task Assignee: Unassigned Created: 2017/06/08 10:58 AM Priority: Normal Reporter: Maggie Dreyer Switching to using ci:test:git to run some acceptance tests in the Puppet component pipeline entails that we will also be testing in an environment that is highly dependent on the OS under test, because ci:test:git does not install and run against an Agent package. We need to determine which OSes it makes the most sense to run these smoke tests on, taking into account the state of the existing pooler images (e.g. what Ruby version do they have?) and what that means in terms of the feedback it gives us. We then need to weigh how much work it would be to get ci:test:git working reliably on the platforms we currently use (for example, I believe it's fairly broken on redhat6 right now, which is one of the platforms we currently test in the puppet component pipeline) against what we might lose (or gain) by switching to an alternative OS that could give us the same kind of feedback. Add Comment
Jira (PUP-7611) Can't turn off deprecation warnings
Title: Message Title Josh Cooper commented on PUP-7611 Re: Can't turn off deprecation warnings Merged to master in https://github.com/puppetlabs/puppet/commit/d453ad688f54b5d14cf7783b40f5f1415739866c Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7612) It is impossible to navigate an integer keyed Hiera hash using dotted keys
Title: Message Title John Duarte assigned an issue to Unassigned Puppet / PUP-7612 It is impossible to navigate an integer keyed Hiera hash using dotted keys Change By: John Duarte Assignee: John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7612) It is impossible to navigate an integer keyed Hiera hash using dotted keys
Title: Message Title John Duarte commented on PUP-7612 Re: It is impossible to navigate an integer keyed Hiera hash using dotted keys Given the clarification in Thomas Hallgren's comment above about accessing the segments, currently this functions as expected. The case of using a quoted integer in your hieradata introduces a usability edge-case, but has a reasonable behavior as seen below. [root@cxt941rwcarxu6n ~]# puppet lookup ports --- 80: test: eight-zero 443: test: four-four-three '8080': test: eight-zero-eight-zero [root@cxt941rwcarxu6n ~]# puppet lookup ports.80 ---
Jira (PUP-7612) It is impossible to navigate an integer keyed Hiera hash using dotted keys
Title: Message Title Geoff Nichols assigned an issue to John Duarte Puppet / PUP-7612 It is impossible to navigate an integer keyed Hiera hash using dotted keys Change By: Geoff Nichols Assignee: John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3042) If a catalog has a dependency cycle, it does not count as failed
Title: Message Title Moses Mendoza assigned an issue to Josh Cooper Puppet / PUP-3042 If a catalog has a dependency cycle, it does not count as failed Change By: Moses Mendoza Assignee: Moses Mendoza Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7635) Custom service provider is always selected as default
Title: Message Title Daniel Urist created an issue Puppet / PUP-7635 Custom service provider is always selected as default Issue Type: Bug Affects Versions: PUP 4.10.1 Assignee: Unassigned Components: Types and Providers Created: 2017/06/08 9:59 AM Environment: Server environment: Debian 8 (jessie) puppetserver package v.2.7.2-1puppetlabs1 Client environment: Debian 8 (jessie) puppet package v.4.8.2-5~bpo8+1 (from debian backports) Priority: Normal Reporter: Daniel Urist I'm trying to create a custom service provider to be distributed with a module. I don't want it to ever be selected as the default service provider, but it's always selected as the default over the debian provider. Here is a trivial test case for the service provider:
Jira (PUP-7616) Fix broken implementation of Property#change_to_s method
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-7616 Fix broken implementation of Property#change_to_s method Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3042) If a catalog has a dependency cycle, it does not count as failed
Title: Message Title Moses Mendoza assigned an issue to Moses Mendoza Puppet / PUP-3042 If a catalog has a dependency cycle, it does not count as failed Change By: Moses Mendoza Assignee: Josh Cooper Moses Mendoza Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6123) remove ruby code that backs resource_type endpoint
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-6123 remove ruby code that backs resource_type endpoint Change By: Jeremy Barlow Release Notes Summary: The HTTP resource_type and resource_types endpoints and the resource_type puppet command line face have been removed. The environment_classes HTTP endpoint in Puppet Server replaces a subset of the resource_type functionality, including name and parameter metadata for classes. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3546) Add docs for node-purge-gc-batch-limit, etc.
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3546 Add docs for node-purge-gc-batch-limit, etc. Change By: Rob Browning Release Notes Summary: PuppetDB no longer purges all eligible nodes during its periodic garbage collections. Now it only purges up to 25 each time, but this value can be adjusted by the `node-purge-gc-batch-limit` configuration setting. It is now also possible to specify a purge_nodes batch_limit for admin/cmd endpoint clean commands. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3497) Document dropped support for JDK7
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3497 Document dropped support for JDK7 Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6123) remove ruby code that backs resource_type endpoint
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-6123 remove ruby code that backs resource_type endpoint Change By: Jeremy Barlow Release Notes Summary: The HTTP resource_type and resource_types endpoints and the resource_type puppet command line face have been removed. Release Notes: Deprecation Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7632) FreeBSD package providers are outdated
Title: Message Title
Helmut Ritter updated an issue
Puppet / PUP-7632
FreeBSD package providers are outdated
Change By:
Helmut Ritter
Hi,the FreeBSD package providers "ports" and "portupgrade" are outdated as they use "pkg_info" instead of "pkg info":https://wiki.freebsd.org/pkgngI would like to offer my support here but due to the lack of ruby knowledge I cannot do this myself.My current workaround is to create /usr/sbin/pkg_info with the following content: {code:shell} #!/bin/shCMD="$(echo ${@} | sed -e 's#Q#q#g' -e 's#O#o#g')"/usr/sbin/pkg info ${CMD} {code} Helmut
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7632) FreeBSD package providers are outdated
Title: Message Title
Helmut Ritter updated an issue
Puppet / PUP-7632
FreeBSD package providers are outdated
Change By:
Helmut Ritter
Hi,the FreeBSD package providers "ports" and "portupgrade" are outdated as they use "pkg_info" instead of "pkg info":https://wiki.freebsd.org/pkgngI would like to offer my support here but due to the lack of ruby knowledge I cannot do this myself. My current workaround is to create /usr/sbin/pkg_info with the following content:#!/bin/shCMD="$(echo ${@} | sed -e 's#Q#q#g' -e 's#O#o#g')"/usr/sbin/pkg info ${CMD} Helmut
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7634) Puppet device - make it threadable
Title: Message Title Thomas Honey created an issue Puppet / PUP-7634 Puppet device - make it threadable Issue Type: Improvement Assignee: Henrik Lindberg Components: Applications Created: 2017/06/08 7:42 AM Priority: Normal Reporter: Thomas Honey This will mean: adding config print to puppet device. enabling the last_run_report for puppet device. Add Comment
Jira (PUP-7633) need to show that module config cannot be overridden
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-7633 need to show that module config cannot be overridden Issue Type: Story Assignee: Unassigned Created: 2017/06/08 7:41 AM Priority: Normal Reporter: Henrik Lindberg In an organization that has security compliance issues there is the need to show that parameters set in a module are final. This means that regular use of hiera data in a sensitive module can not be used because all of the parameters defined that way can be overridden in the environment and global layers. The author of a module would however like to use hierarchical data and integration with hiera backends and construct the logic with APL. Since this is not possible, the current work around is to write custom functions that read data files in yaml, and/or call custom functions to get data from external sources. These do not work with APL. Alternatively the user is stuck with params.pp and defining the values in code. The features we have proposed for partial ordering of layers etc. do not help as they all allow for overrides to be made outside of the control of the module. We have a similar use case in MEEP where a completely private hierarchy is needed. I can imagine that part of the solution is to support private defines and classes and to specify that those may not have their parameters bound in higher layers (i.e their bindings in hiera are private and final in the module). To make them configurable they would need to have public wrappers that define the API for the public (and variable) subset the module supports. Such a solution seems more appealing than trying to come up with a mechanism for a private layer or by trying to work in specification of "final" declarations in keys in the
Jira (PUP-7616) Fix broken implementation of Property#change_to_s method
Title: Message Title Thomas Hallgren commented on PUP-7616 Re: Fix broken implementation of Property#change_to_s method I created PR-5960 to address the problems found in the acceptance tests. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7616) Fix broken implementation of Property#change_to_s method
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7616 Fix broken implementation of Property#change_to_s method Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6359) Completely remove allow/deny rules from fileserver.conf syntax
Title: Message Title Jeremy Barlow commented on PUP-6359 Re: Completely remove allow/deny rules from fileserver.conf syntax Passed through latest puppet master component pipeline run here. puppet-agent master suite with code from this PR is still pending. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7612) It is impossible to navigate an integer keyed Hiera hash using dotted keys
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7612 It is impossible to navigate an integer keyed Hiera hash using dotted keys Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7612) It is impossible to navigate an integer keyed Hiera hash using dotted keys
Title: Message Title Kenn Hussey commented on PUP-7612 Re: It is impossible to navigate an integer keyed Hiera hash using dotted keys What do we need in order to make a decision here? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7612) It is impossible to navigate an integer keyed Hiera hash using dotted keys
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7612 It is impossible to navigate an integer keyed Hiera hash using dotted keys Change By: Kenn Hussey Fix Version/s: PUP 4.10.z Fix Version/s: PUP 4.10.2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7612) It is impossible to navigate an integer keyed Hiera hash using dotted keys
Title: Message Title Kenn Hussey commented on PUP-7612 Re: It is impossible to navigate an integer keyed Hiera hash using dotted keys Thomas Hallgren I bumped it because the cut-off for changes intended for Puppet 4.10.2 was yesterday. I missed the fact that the changes have already landed. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7612) It is impossible to navigate an integer keyed Hiera hash using dotted keys
Title: Message Title Thomas Hallgren commented on PUP-7612 Re: It is impossible to navigate an integer keyed Hiera hash using dotted keys This ticket fixes a problem introduced in PUP-7594 . If this one doesn't make it to 4.10.2, then we need to remove PUP-7594 too, or we will introduce breaking changes. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7612) It is impossible to navigate an integer keyed Hiera hash using dotted keys
Title: Message Title Thomas Hallgren commented on PUP-7612 Re: It is impossible to navigate an integer keyed Hiera hash using dotted keys @kenn, not sure why this was removed from 4.10.2. It was implemented as designed and we haven't made any decisions yet to change that. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7612) It is impossible to navigate an integer keyed Hiera hash using dotted keys
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7612 It is impossible to navigate an integer keyed Hiera hash using dotted keys Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7487) Default to JSON when sending facts and reports
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7487 Default to JSON when sending facts and reports Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7627) CreateSymbolicLinkW returns the wrong data type
Title: Message Title Kenn Hussey commented on PUP-7627 Re: CreateSymbolicLinkW returns the wrong data type Moses Mendoza please provide release notes for this issue, if applicable. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1890) URI.unescape mangles UTF-8 paths producing invalid ASCII strings
Title: Message Title Kenn Hussey commented on PUP-1890 Re: URI.unescape mangles UTF-8 paths producing invalid ASCII strings Moses Mendoza please provide release notes for this issue, if applicable. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7612) It is impossible to navigate an integer keyed Hiera hash using dotted keys
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7612 It is impossible to navigate an integer keyed Hiera hash using dotted keys Change By: Kenn Hussey Fix Version/s: PUP 4.10.2 Fix Version/s: PUP 4.10.z Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1890) URI.unescape mangles UTF-8 paths producing invalid ASCII strings
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-1890 URI.unescape mangles UTF-8 paths producing invalid ASCII strings Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7632) FreeBSD package providers are outdated
Title: Message Title Helmut Ritter created an issue Puppet / PUP-7632 FreeBSD package providers are outdated Issue Type: Improvement Affects Versions: PUP 4.10.1 Assignee: Unassigned Components: Platform Created: 2017/06/08 4:13 AM Environment: FreeBSD BSDHelmut.charlieroot.de 10.3-RELEASE-p17 FreeBSD 10.3-RELEASE-p17 #3 r315512: Sat Mar 18 23:07:14 CET 2017 r...@bsdhelmut.charlieroot.de:/usr/obj/usr/src/sys/GENERIC-PF-ALTQ amd64 Priority: Normal Reporter: Helmut Ritter Hi, the FreeBSD package providers "ports" and "portupgrade" are outdated as they use "pkg_info" instead of "pkg info": https://wiki.freebsd.org/pkgng I would like to offer my support here but due to the lack of ruby knowledge I cannot do this myself. Helmut
Jira (PUP-355) how to run rspec-puppet with lookup a.k.a data in environment/modules
Title: Message Title Henrik Lindberg commented on PUP-355 Re: how to run rspec-puppet with lookup a.k.a data in environment/modules A subject that keeps popping up is how to create a LookupContext that can be used to unit test lookup functions. Right now you can create an instance of a LookupContext even from puppet language, but it has to be done in the context of a lookup() call in progress or there will be gremlins. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7612) It is impossible to navigate an integer keyed Hiera hash using dotted keys
Title: Message Title Thomas Hallgren commented on PUP-7612 Re: It is impossible to navigate an integer keyed Hiera hash using dotted keys I'm in favor of "a segment is Numeric when applied to an array". This is already the case. I would like to turn the statement "a segment is String when applied to a hash, if there is no such string key, it is used as a numeric key" around though, since the most common data format is YAML and since YAML will automatically create numeric keys unless quoted, it's probably better to assume that and then fallback to using a string if there is no match. I'm opposed to using # and #() since they a) will force a replacement of the current parser (essentially a regexp split) for something slower and more complex, and b) will make '#' a special character which means that it is a breaking change. The gain would be to cater for corner cases that I think there's a good chance that no one will ever encounter. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7611) Can't turn off deprecation warnings
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-7611
Can't turn off deprecation warnings
Change By:
Henrik Lindberg
Sub-team:
Language
Release Notes Summary:
Some deprecation warnings were issued even when using {{\--disable_warnings deprecations}}.
Sprint:
Agent 2017-06-14
Release Notes:
Bug Fix
Fix Version/s:
PUP 5.y
Fix Version/s:
PUP 5.0.0
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7611) Can't turn off deprecation warnings
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-7611 Can't turn off deprecation warnings Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7611) Can't turn off deprecation warnings
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-7611 Can't turn off deprecation warnings Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7597) Add hiera5 default config file to puppet
Title: Message Title John O'Connor commented on PUP-7597 Re: Add hiera5 default config file to puppet Geoff Nichols This ticket/PR doesn't actually become active until the corresponding changes in PA-1139 are made in puppet-agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7612) It is impossible to navigate an integer keyed Hiera hash using dotted keys
Title: Message Title Henrik Lindberg commented on PUP-7612 Re: It is impossible to navigate an integer keyed Hiera hash using dotted keys Not sure how this snowballed into this state First - the axioms: Arrays are always indexed with integer key Hashes have keys that can be strings, integers, or floats (actually Any data type, but that is besides the use case as the type of the key is restricted) A Hash can contain string keys '10', '012', '0xa', and an integer key 10 - all at the same time Then an assumption: We don't want automatic type conversion turning a numeric 10 segment into the string '10' key lookup in case it was used as a key in a hash, and there was no numeric 10 entry. If we change that assumption, then the problem of quoting goes away, but we get the then unsolvable problem of not being able to lookup a string key '10' in a hash if there is also a numeric key 10. Maybe this problem is preferable? (Or the reversed problem obtained by first trying the numeric key as a decimal string key. The rationale being that string keys is the most common form of keys in a hash.) It does not help if we use brackets around the index/key, there is still a difference between [10] and ['10'], unless we take the brackets to mean "this is a string" (which would be very surprising to me, as that is not how it works in the puppet language). So which problem do we want? A quoting problem, or a corner case problem finding a value in a hash? The solution is simple for not supporting 'string and numeric key of same "value"', but more difficult for quoting as there are obvious shell escaping problems (different shells - different rules - horrible to document - even professionals get it wrong all the time (see scrollback in this ticket)). So, I propose that instead of solving the problem of 'quoting string' that we make the 'numeric key in hash' the special case as that is the least commonly used. a segment is Numeric when applied to an array a segment is String when applied to a hash, if there is no such string key, it is used as a numeric key the prefix # forces a segment to be numeric the notation #() allows the numeric to be a float
Jira (PUP-7629) Hieradata should be loaded and cached in accordance with the environment_timeout
Title: Message Title Henrik Lindberg commented on PUP-7629 Re: Hieradata should be loaded and cached in accordance with the environment_timeout Nick Walker and other watchers - how important is it to fix this? Should we try to get this into Puppet 5.0.0 ? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7629) Hieradata should be loaded and cached in accordance with the environment_timeout
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7629 Hieradata should be loaded and cached in accordance with the environment_timeout Change By: Henrik Lindberg Sub-team: Language Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
