Jira (PUP-1476) Puppet agent should supply an informative user agent
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-1476 Puppet agent should supply an informative user agent Change By: Geoff Nichols Sprint: AP Triage 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-3109) Puppetdb logs are managed by logrotate and logback.xml
Title: Message Title Erik Hansen moved an issue PuppetDB / PDB-3109 Puppetdb logs are managed by logrotate and logback.xml Change By: Erik Hansen Key: PE PDB - 18078 3109 Project: Puppet Enterprise [Internal] PuppetDB 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 (FACT-1428) FreeBSD facts are missing from Facter 3.X onwards
Title: Message Title Jason Slagle commented on FACT-1428 Re: FreeBSD facts are missing from Facter 3.X onwards FACT-1520. I got the networking ones - I'll do a diff tomorrow and figure out what's still missing. 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-3105) v2.1 Command Processing
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-3105 v2.1 Command Processing Change By: Karen Van der Veer Summary: Command Processing 2 v2 .1 Command Processing 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-3105) v2.1 Command Processing
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-3105 v2.1 Command Processing Change By: Karen Van der Veer Epic Name: Command Processing 2 v2 .1 Command Processing 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-3105) Command Processing 2.1
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-3105 Command Processing 2.1 Change By: Karen Van der Veer Epic Colour: ghx-label- 9 4 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 (FACT-1520) Newer Facter is missing facts on FreeBSD
Title: Message Title Jason Slagle created an issue Facter / FACT-1520 Newer Facter is missing facts on FreeBSD Issue Type: Bug Assignee: Unassigned Created: 2016/10/19 4:06 PM Priority: Normal Reporter: Jason Slagle FreeBSD has no networking facts on FreeBSD. This limits the utility of facter, because without things like fqdn, Puppet does not work properly. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (FACT-1428) FreeBSD facts are missing from Facter 3.X onwards
Title: Message Title Michael Smith commented on FACT-1428 Re: FreeBSD facts are missing from Facter 3.X onwards Please do, and identify which particular facts are still missing. 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 (FACT-1428) FreeBSD facts are missing from Facter 3.X onwards
Title: Message Title Jason Slagle commented on FACT-1428 Re: FreeBSD facts are missing from Facter 3.X onwards Ok - I suspect I need to open a NEW ticket for this then since this one is resolved? 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-6834) lookup explain shows found data incorrectly
Title: Message Title R.I.Pienaar created an issue Puppet / PUP-6834 lookup explain shows found data incorrectly Issue Type: Bug Affects Versions: PUP 4.7.0 Assignee: Unassigned Created: 2016/10/19 3:25 PM Priority: Normal Reporter: R.I.Pienaar # data/nodes/dev3.devco.net.yaml users::local: rip: email: "arri.pien...@example.net"
Jira (PUP-6827) Address puppet acceptance test failures on windows server 2016
Title: Message Title Moses Mendoza commented on PUP-6827 Re: Address puppet acceptance test failures on windows server 2016 pr up to address second failure 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 (PDOC-125) JSON: Splitting function signatures into two places is awkward
Title: Message Title Jesse Scott commented on PDOC-125 Re: JSON: Splitting function signatures into two places is awkward That sounds reasonable to me. Having one place to look for signatures (that is always a list, even if it only has one item) sounds a lot better than a conditional. 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-6765) Using produce/consume results in 'Attempt to redefine entity' errors
Title: Message Title Kevin Corcoran commented on PUP-6765 Re: Using produce/consume results in 'Attempt to redefine entity' errors What version(s) does this affect? I think it's 4.6 and 4.7, but would be nice to get that answered authoritatively. 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-3772) Provide a package provider to manage Puppet modules
Title: Message Title Nick Walker commented on PUP-3772 Re: Provide a package provider to manage Puppet modules Kenaz Kwa wouldn't puppet module install and puppet module update be something similar to a package manager? The best practice here would be to use a Puppetfile to deploy your modules with code manager / r10k. While you could certainly deploy puppet code with puppet, it seems like it'd be fraught with caveats. ( i.e. you need to deploy a new version of a module before you can use that code which you most likely can't do during the same puppet run ). A cool piece of functionality for finding out if your currently installed modules are out of date comes from Dylan Ratcliffe's onceover gem. You can get a listing of your current module versions compared to the latest. bundle exec onceover show puppetfile FULL NAME | CURRENT VERSION | LATEST VERSION | OUT OF DATE? ---|-||--- puppetlabs-inifile | 1.6.0 | 1.6.0 | No puppetlabs-stdlib | 4.12.0 | 4.13.1 | Minor puppetlabs-concat | 2.2.0 | 2.2.0 | No puppet-hiera | 2.1.2 | 2.2.0 | Minor
Jira (PDB-3104) Investigate and fix the extensions test-reports-summary-query cache invalidation failure
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3104 Investigate and fix the extensions test-reports-summary-query cache invalidation failure Change By: Rob Browning Sprint: Hopper SE 2016-11-02 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-3108) Enable certname "bash in place"
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-3108 Enable certname "bash in place" Issue Type: New Feature Assignee: Unassigned Created: 2016/10/19 2:20 PM Priority: Normal Reporter: Ryan Senior This has been implemented in master, but we found an issue that was going to be fixed in PDB-3087 . The issue was commands getting enqueued out of order chronologically. Although that can't happen in a 1 PDB node setup, it can happen in an HA scenario. Consider 3 catalogs for node 'foo.com'. Catalog 1 is collected at T1, catalog 2 at T2 and catalog 3 at T3. We have two PuppetDB instances, X and Y. PDB X gets and stores catalog 1. PDB X has catalog 3 enqueued (but not yet stored). PDB Y gets and stores catalog 2. PDB Y replicates with PDB X, causing catalog 2 to be enqueued in PDB X. With the logic we have today, catalog 2 would overwrite catalog 3, which is newer. The correct behavior here is to use the producer timestamp, rather than the time the message was received. This will involve adding producer timestamp to the message header (i.e. POST param) and using that to determine which catalog/factset is newer.
Jira (PDOC-129) 4.x function overload tags not parsed if the overload is missing a docstring
Title: Message Title William Hopper created an issue Puppet Strings / PDOC-129 4.x function overload tags not parsed if the overload is missing a docstring Issue Type: Bug Assignee: Unassigned Created: 2016/10/19 2:07 PM Priority: Normal Reporter: William Hopper In the following function overload, if you remove the "Subtracts two integers" line, strings will ignore the rest of the @param and @return tags, but only in the JSON output, it seems. Puppet::Functions.create_function(:subtract) do # Subtracts two integers. # @param x The first integer. # @param y The second integer.
Jira (FACT-1519) mountpoints fact does not show mounts on nfs
Title: Message Title
Andrey Khomyakov created an issue
Facter / FACT-1519
mountpoints fact does not show mounts on nfs
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/10/19 1:59 PM
Environment:
debian jessie and centos 72 show this behavior
Priority:
Normal
Reporter:
Andrey Khomyakov
I expect the mountpoints fact to return all mounts not just those mapped to physical devices. https://docs.puppet.com/facter/latest/core_facts.html#mountpoints
Set mount point using mount resource: mount { "userhome": name => "/home", device => "nfshost:/homedirs", fstype => "nfs", ensure => "mounted", options => "defaults", atboot => true, remounts => true, }
~# mount | grep home nfshost:/homedirs on /home type nfs (rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.10.10.10,mountvers=3,mountport=4046,mountproto=udp,local_lock=none,addr=10.10.10.10)
~# facter mountpoints | grep home
Add Comment
Jira (PDB-3107) new-command-schema validation prevents PDB/NewRelic integration
Title: Message Title
Wyatt Alt created an issue
PuppetDB / PDB-3107
new-command-schema validation prevents PDB/NewRelic integration
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/10/19 1:57 PM
Priority:
Normal
Reporter:
Wyatt Alt
This line: https://github.com/puppetlabs/puppetdb/blob/4.1.x/src/puppetlabs/puppetdb/command.clj#L169
results in this error:
``` 13:25 ```2016-10-13 23:05:30,557 ERROR [o.a.a.ActiveMQMessageConsumer] ID:ip-10-11-47-46.sj.b2c.nike.com-45556-1476399900148-6:1:1:1 Exception while processing messag 13:25 e: ID:ip-10-11-47-46.sj.b2c.nike.com-45556-1476399900148-8:1:1:1:4 13:25 clojure.lang.ExceptionInfo: Input to parse-new-command does not match schema: [(named {:headers {:NewRelicID disallowed-key, :NewRelicTransaction disallowed- 13:25 key, :JMSXDeliveryCount disallowed-key}} arg0)]``` ```
when PDB is run with the newrelic agent (supplied via java args). Instead of nailing down the exact schema we should just require the appropriate minimal set of keys/headers.
Add Comment
Jira (PUP-6474) Incorporate gettext_setup gem into puppet
Title: Message Title Branan Riley commented on PUP-6474 Re: Incorporate gettext_setup gem into puppet Update on the status of this: I've got it working on Linux via my PR branch and a small change to puppet-agent at https://github.com/branan/puppet-agent/tree/gettext I'm unsure of the best way to do this on Windows (maybe just a relative path from the Puppet executable directory to the locale data?). Whatever we figure out for Windows will also help distro packagers do it right. Also check out https://github.com/puppetlabs/puppet/pull/5329/commits/251faf0f4fc014536c0309037580c7f668d12260 for details on the server work that needs to happen. Chris Price has been in touch with me about that stuff, but if somebody else takes this over you'll want to make him aware you're the new Platform team contact for 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-6827) Address puppet acceptance test failures on windows server 2016
Title: Message Title Moses Mendoza commented on PUP-6827 Re: Address puppet acceptance test failures on windows server 2016 The first (errored) test passed on retry: ests/ticket_13948_lib_dir_hook_should_be_called_on_initialization.rb passed in 60.73 seconds Test Suite: tests @ 2016-10-19 13:35:37 -0700 - Host Configuration Summary - - Test Case Summary for suite 'tests' - Total Suite Time: 60.73 seconds Average Test Time: 60.73 seconds Attempted: 1
Jira (PUP-5000) acceptance: test agent_specified environment, ENC, and related facts
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-5000 acceptance: test agent_specified environment, ENC, and related facts Change By: Eric Thompson Assignee: qa Eric Thompson 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-5000) acceptance: test agent_specified environment, ENC, and related facts
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5000 acceptance: test agent_specified environment, ENC, and related facts Change By: Eric Thompson Sprint: Client 2015-12-02, Client 2016-05-18, Client 2016-06-01, Client 2016-06-15 , PDS 2016-11-02 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 (PDOC-125) JSON: Splitting function signatures into two places is awkward
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-125 JSON: Splitting function signatures into two places is awkward Change By: William Hopper Fix Version/s: PDOC 1.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 (PDB-3105) Command Processing 2.1
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-3105 Command Processing 2.1 Issue Type: Epic Assignee: Unassigned Created: 2016/10/19 1:27 PM Priority: Normal Reporter: Ryan Senior This epic is covering the improvements we want to make after the initial release of PuppetDB with Stockpile. The key focus of this Epic is to leverage the control and simplicity that Stockpile gives us to further improve performance of command processing. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (HI-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Craig Gomes updated an issue Hiera / HI-341 Hiera should support native HOCON to match Puppet Server Change By: Craig Gomes Sprint: PDS 2016-11- 02 16 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-6827) Address puppet acceptance test failures on windows server 2016
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6827 Address puppet acceptance test failures on windows server 2016 Change By: Moses Mendoza Fix Version/s: PUP 4.8.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-6827) test: ticket_6857_password-disclosure-when-changing-a-users-password.rb fails on windows server 2016
Title: Message Title
Moses Mendoza updated an issue
Puppet / PUP-6827
test: ticket_6857_password-disclosure-when-changing-a-users-password.rb fails on windows server 2016
Change By:
Moses Mendoza
When running the puppet aio test suite there were two failures during the run.The first is during tests/ticket_13948_lib_dir_hook_should_be_called_on_initialization.rb. It appears there was a connection failure during the test :{code} Test Case * verify that the application shows up in helppyjb322f9rtg4lp.delivery.puppetlabs.net (windows2016-64-1) 10:07:00$ cmd.exe /c puppet help --vardir="C:/cygwin64/tmp/ticket_13948_lib_dir_hook_should_be_called_on_initialization.SB3COc/agent_var"Warning: ssh channel on windows2016-64-1 received exception post command execution Errno::ETIMEDOUT - Operation timed out - recvfrom(2)Warning: Attemped ssh.close, (caught Net::SSH::Disconnect - connection closed by remote host).ssh connection to windows2016-64-1 has been terminatedpyjb322f9rtg4lp.delivery.puppetlabs.net (windows2016-64-1) executed in 318.63 seconds Beaker::Host::CommandFailure: Host 'pyjb322f9rtg4lp.delivery.puppetlabs.net' connection failure running: cmd.exe /c puppet help --vardir="C:/cygwin64/tmp/ticket_13948_lib_dir_hook_should_be_called_on_initialization.SB3COc/agent_var" Last 10 lines of output were: /Users/aileen/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/beaker-3.1.0/lib/beaker/host.rb:348 /Users/aileen/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/beaker-3.1.0/lib/beaker/dsl/helpers/host_helpers.rb:83 /Users/aileen/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/beaker-3.1.0/lib/beaker/shared/host_manager.rb:127 /Users/aileen/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/beaker-3.1.0/lib/beaker/dsl/patterns.rb:37 /Users/aileen/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/beaker-3.1.0/lib/beaker/dsl/helpers/host_helpers.rb:63 /Users/aileen/puppet/acceptance/ tests/ ticket_13948_lib_dir_hook_should_be_called_on_initialization.rb:137 /Users/aileen/puppet/acceptance/tests/ticket_13948_lib_dir_hook_should_be_called_on_initialization.rb:136 /Users/aileen/puppet/acceptance/tests/ticket_13948_lib_dir_hook_should_be_called_on_initialization.rb:136 /Users/aileen/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/beaker-3.1.0/lib/beaker/dsl/structure.rb:43 /Users/aileen/puppet/acceptance/tests/ticket_13948_lib_dir_hook_should_be_called_on_initialization.rb:135 /Users/aileen/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/beaker-3.1.0/lib/beaker/test_case.rb:133 /Users/aileen/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/beaker-3.1.0/lib/beaker/test_case.rb:133 /Users/aileen/.rbenv/versions/2.3.0/lib/ruby/2.3.0/benchmark.rb:308 /Users/aileen/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/beaker-3.1.0/lib/beaker/test_case.rb:130 /Users/aileen/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/beaker-3.1.0/lib/beaker/test_suite.rb:325 /Users/aileen/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/beaker-3.1.0/lib/beaker/test_suite.rb:322 /Users/aileen/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/beaker-3.1.0/lib/beaker/test_suite.rb:322 /Users/aileen/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/beaker-3.1.0/lib/beaker/test_suite.rb:371 /Users/aileen/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/beaker-3.1.0/li
Jira (PUP-6827) Address puppet acceptance test failures on windows server 2016
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6827 Address puppet acceptance test failures on windows server 2016 Change By: Moses Mendoza Summary: Address puppet acceptance test : ticket_6857_password-disclosure-when-changing-a-users-password.rb fails failures on windows server 2016 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-6821) binary_file() file not found: error message unclear
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6821 binary_file() file not found: error message unclear Change By: Craig Gomes Story Points: 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 (PUP-5908) Implement a PCore MsgPack Serializer
Title: Message Title Craig Gomes assigned an issue to Unassigned Puppet / PUP-5908 Implement a PCore MsgPack Serializer Change By: Craig Gomes Assignee: Kylo Ginsberg 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-4742) Bring semantic_puppet library into Puppet
Title: Message Title Craig Gomes assigned an issue to Unassigned Puppet / PUP-4742 Bring semantic_puppet library into Puppet Change By: Craig Gomes Assignee: Kylo Ginsberg 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-6780) modify the lookup helper implementation to support v5 features
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6780 modify the lookup helper implementation to support v5 features Change By: Craig Gomes Sprint: PDS 2016-10-19 , PDS 2016-11-02 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-6511) Add support for lookup.conf (version 5)
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6511 Add support for lookup.conf (version 5) Change By: Craig Gomes Sprint: PDS 2016-10-19 , PDS 2016-11-02 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-6775) acceptance: Newlines break Puppet tag validation
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6775 acceptance: Newlines break Puppet tag validation Change By: Craig Gomes Sprint: PDS 2016-10-05, PDS 2016-10-19 , PDS 2016-11-02 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-6799) PEZ 2016.5.x mono smoke integration fails with Unable to serialize non-Data type parameters unless a serializer is provided
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6799 PEZ 2016.5.x mono smoke integration fails with Unable to serialize non-Data type parameters unless a serializer is provided Change By: Eric Thompson QA Risk Assessment: Low 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-6799) PEZ 2016.5.x mono smoke integration fails with Unable to serialize non-Data type parameters unless a serializer is provided
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6799 PEZ 2016.5.x mono smoke integration fails with Unable to serialize non-Data type parameters unless a serializer is provided Change By: Eric Thompson 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-6778) acceptance: Binary Type
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6778 acceptance: Binary Type Change By: Craig Gomes Sprint: PDS 2016-10-19 , PDS 2016-11-02 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-6799) PEZ 2016.5.x mono smoke integration fails with Unable to serialize non-Data type parameters unless a serializer is provided
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6799 PEZ 2016.5.x mono smoke integration fails with Unable to serialize non-Data type parameters unless a serializer is provided Change By: Eric Thompson QA Status: Reviewed 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 (FACT-1356) External facts should be able to return structured data
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Facter / FACT-1356 External facts should be able to return structured data Change By: Maggie Dreyer Assignee: Maggie Dreyer 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-6827) test: ticket_6857_password-disclosure-when-changing-a-users-password.rb fails on windows server 2016
Title: Message Title Moses Mendoza assigned an issue to Moses Mendoza Puppet / PUP-6827 test: ticket_6857_password-disclosure-when-changing-a-users-password.rb fails on windows server 2016 Change By: Moses Mendoza Assignee: 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-6417) Regex of ssh_authorized_keys can't match lines with multi spaces as field separator
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6417 Regex of ssh_authorized_keys can't match lines with multi spaces as field separator Change By: Kylo Ginsberg Release Notes Summary: Previously, the ssh_authorized_key resource type would not match entries which had multiple spaces between fields - this is now fixed. 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-6417) Regex of ssh_authorized_keys can't match lines with multi spaces as field separator
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6417 Regex of ssh_authorized_keys can't match lines with multi spaces as field separator Change By: Kylo Ginsberg Release Notes: Bug Fix 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-3104) Investigate and fix the extensions test-reports-summary-query cache invalidation failure
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3104 Investigate and fix the extensions test-reports-summary-query cache invalidation failure Issue Type: Bug Assignee: Rob Browning Created: 2016/10/19 12:11 PM Labels: maintenance Priority: Normal Reporter: Rob Browning lein test :only puppetlabs.pe-puppetdb-extensions.sync.services-test/test-reports-summary-query FAIL in (test-reports-summary-query) (services_test.clj:93) caching expected: (= [[:open (to-date-time "2014-01-01T08:00:00.000Z")] [(to-date-time "2014-01-01T09:00:00.000Z") :open]] (clojure.core/deref queried-timespans)) actual: (not (= [[:open #object[org.joda.time.DateTime 0x5cde7cee "2014-01-01T08:00:00.000Z"]] [#object[org.joda.time.DateTime 0x7f53be27 "2014-01-01T09:00:00.000Z"] :open]] nil)) The [database] classname setting has been retired and will be ignored. The [database] subprotocol setting has been retired and will be ignored. Ran 1 tests containing 7 assertions. 1 failures, 0 errors. Tests failed. Add Comment
Jira (PUP-6789) Prefer but don't require capabilities matching the node environment
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6789 Prefer but don't require capabilities matching the node environment 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-6417) Regex of ssh_authorized_keys can't match lines with multi spaces as field separator
Title: Message Title Kenn Hussey commented on PUP-6417 Re: Regex of ssh_authorized_keys can't match lines with multi spaces as field separator Kylo Ginsberg is this still waiting for a green CI run or can it be resolved? 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-6585) Remove Puppet::Util.absolute_path?(path) / replace with Pathname.new(path)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6585 Remove Puppet::Util.absolute_path?(path) / replace with Pathname.new(path) Change By: Kenn Hussey Fix Version/s: PUP 4.8.0 Fix Version/s: PUP 4.9.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-6789) Prefer but don't require capabilities matching the node environment
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet / PUP-6789 Prefer but don't require capabilities matching the node environment Change By: Alex Dreyer Assignee: Alex Dreyer 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-6789) Prefer but don't require capabilities matching the node environment
Title: Message Title Alex Dreyer updated an issue Puppet / PUP-6789 Prefer but don't require capabilities matching the node environment Change By: Alex Dreyer Sprint: FF HA - 2016- 10 11 - 19 01 , FF 2016- 11 10 - 02 19 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-3065) Stop memoizing resource identity hashes
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-3065 Stop memoizing resource identity hashes Change By: Karen Van der Veer Sprint: SE 2016-10-19 , SE 2016-11-02 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-6761) [SPIKE] Find a workflow for POT file generation
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-6761 [SPIKE] Find a workflow for POT file generation Change By: Maggie Dreyer Sprint: AP 2016-11- 02 16 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-6803) puppet run status should be "failed" if there are failed generated resources
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6803 puppet run status should be "failed" if there are failed generated resources Change By: Geoff Nichols Fix Version/s: PUP 4.8.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-6423) The scheduled_task provider performs incorrect matching on file names
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6423 The scheduled_task provider performs incorrect matching on file names Change By: Geoff Nichols Fix Version/s: PUP 4.8.0 Fix Version/s: PUP 4.y 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-6432) Puppet::Util::Execution.execute cannot handle Unicode output on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6432 Puppet::Util::Execution.execute cannot handle Unicode output on Windows Change By: Geoff Nichols Fix Version/s: PUP 4.8.0 Fix Version/s: PUP 4.9.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-6432) Puppet::Util::Execution.execute cannot handle Unicode output on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6432 Puppet::Util::Execution.execute cannot handle Unicode output on Windows Change By: Geoff Nichols Sprint: AP 2016-11- 02 16 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-3098) Remove ActiveMQ/KahaDB related docs
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-3098 Remove ActiveMQ/KahaDB related docs Change By: Karen Van der Veer Sprint: SE 2016-10-19 , SE 2016-11-02 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-6827) test: ticket_6857_password-disclosure-when-changing-a-users-password.rb fails on windows server 2016
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6827 test: ticket_6857_password-disclosure-when-changing-a-users-password.rb fails on windows server 2016 Change By: Geoff Nichols Acceptance Criteria: Issue is fixed - tests pass on Windows Server 2016. 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-6827) test: ticket_6857_password-disclosure-when-changing-a-users-password.rb fails on windows server 2016
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6827 test: ticket_6857_password-disclosure-when-changing-a-users-password.rb fails on windows server 2016 Change By: Geoff Nichols Story Points: 3 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-6827) test: ticket_6857_password-disclosure-when-changing-a-users-password.rb fails on windows server 2016
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6827 test: ticket_6857_password-disclosure-when-changing-a-users-password.rb fails on windows server 2016 Change By: Geoff Nichols Sprint: AP Grooming Top 10 2016-11-02 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-6827) test: ticket_6857_password-disclosure-when-changing-a-users-password.rb fails on windows server 2016
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6827 test: ticket_6857_password-disclosure-when-changing-a-users-password.rb fails on windows server 2016 Change By: Geoff Nichols Acceptance Criteria: Issue is fixed 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-6827) test: ticket_6857_password-disclosure-when-changing-a-users-password.rb fails on windows server 2016
Title: Message Title
Geoff Nichols updated an issue
Puppet / PUP-6827
test: ticket_6857_password-disclosure-when-changing-a-users-password.rb fails on windows server 2016
Change By:
Geoff Nichols
When running the puppet aio test suite:{code}Test Case tests/ticket_6857_password-disclosure-when-changing-a-users-password.rb reported: # Test line: tests/ticket_6857_password-disclosure-when-changing-a-users-password.rb:45:in `block (2 levels) in run_test'Test Case tests/ticket_13948_lib_dir_hook_should_be_called_on_initialization.rb reported: # cmd.exe /c puppet help --vardir="C:/cygwin64/tmp/ticket_13948_lib_dir_hook_should_be_called_on_initialization.SB3COc/agent_var" Last 10 lines of output were: > Test line: tests/ticket_13948_lib_dir_hook_should_be_called_on_initialization.rb:137:in `block (3 levels) in run_test'{code} h2: In scope for Agent team* Reproduce issue* Solve the problem
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-2810) Update benchmark tool and samples
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-2810 Update benchmark tool and samples Change By: Karen Van der Veer Sprint: SE 2016-10-19 , SE 2016-11-02 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-3038) Merge mq_listener and command namespaces
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-3038 Merge mq_listener and command namespaces Change By: Karen Van der Veer Sprint: SE 2016-10-05, SE 2016-10-19 , SE 2016-11-02 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-3086) Implement new queue metrics from PDB-2931
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-3086 Implement new queue metrics from PDB-2931 Change By: Karen Van der Veer Sprint: SE 2016-10-19 , SE 2016-11-02 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-6825) Transient problem starting rabbitmq-server service on Ubuntu 10.04
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-6825 Transient problem starting rabbitmq-server service on Ubuntu 10.04 Change By: Maggie Dreyer Sprint: AP 2016-10-19 , AP 2016-11-02 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-6245) Acceptance: fix zpool create zone test
Title: Message Title Stan Duffy updated an issue Puppet / PUP-6245 Acceptance: fix zpool create zone test Change By: Stan Duffy Labels: maintenance 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 (FACT-1441) Add "virtualization" fact that identifies AWS, Azure, etc
Title: Message Title Patrick Carlisle updated an issue Facter / FACT-1441 Add "virtualization" fact that identifies AWS, Azure, etc Change By: Patrick Carlisle Sprint: Triage, Analytics 2016-10-19 , Analytics 2016-11-02 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-6188) Puppet::FileSystem.open / exclusive_open does not support passing an encoding like UTF-8
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6188 Puppet::FileSystem.open / exclusive_open does not support passing an encoding like UTF-8 Change By: Geoff Nichols Sprint: AP 2016-10-19 , AP 2016-11-02 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-6825) Transient problem starting rabbitmq-server service on Ubuntu 10.04
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6825 Transient problem starting rabbitmq-server service on Ubuntu 10.04 Change By: Geoff Nichols Sprint: AP 2016-10-19 , AP 2016-11-02 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-6825) Transient problem starting rabbitmq-server service on Ubuntu 10.04
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6825 Transient problem starting rabbitmq-server service on Ubuntu 10.04 Change By: Kenn Hussey Issue Type: CI Blocker Bug 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-6474) Incorporate gettext_setup gem into puppet
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6474 Incorporate gettext_setup gem into puppet Change By: Geoff Nichols Sprint: AP 2016-10-19 , AP 2016-11-02 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-6825) Transient problem starting rabbitmq-server service on Ubuntu 10.04
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6825 Transient problem starting rabbitmq-server service on Ubuntu 10.04 Change By: Geoff Nichols Priority: Blocker Normal 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 (FACT-1441) Add "virtualization" fact that identifies AWS, Azure, etc
Title: Message Title Patrick Carlisle updated an issue Facter / FACT-1441 Add "virtualization" fact that identifies AWS, Azure, etc Change By: Patrick Carlisle Sprint: Triage, Analytics 2016-10-19 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-6789) Prefer but don't require capabilities matching the node environment
Title: Message Title Alex Dreyer updated an issue Puppet / PUP-6789 Prefer but don't require capabilities matching the node environment Change By: Alex Dreyer Priority: Normal Critical 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-6789) Prefer but don't require capabilities matching the node environment
Title: Message Title Arafat Mohamed updated an issue Puppet / PUP-6789 Prefer but don't require capabilities matching the node environment Change By: Arafat Mohamed Labels: ha-dep 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-6789) Prefer but don't require capabilities matching the node environment
Title: Message Title Arafat Mohamed commented on PUP-6789 Re: Prefer but don't require capabilities matching the node environment Nick Lewis This is going to be a blocker for HA. Can we prioritize and get it merged soon please? /cc David Kramer 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-6789) Prefer but don't require capabilities matching the node environment
Title: Message Title Alex Dreyer updated an issue Puppet / PUP-6789 Prefer but don't require capabilities matching the node environment Change By: Alex Dreyer Fix Version/s: PUP 4.8.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 (PDB-3071) log a more helpful message when the old-style puppetdb.conf is used
Title: Message Title David Kramer updated an issue PuppetDB / PDB-3071 log a more helpful message when the old-style puppetdb.conf is used Change By: David Kramer Sprint: FF 2016-10-19 , FF 2016-11-02 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-3058) Report not being stored in PuppetDB due to Unicode Error
Title: Message Title David Kramer updated an issue PuppetDB / PDB-3058 Report not being stored in PuppetDB due to Unicode Error Change By: David Kramer Sprint: FF 2016-10-19 , FF 2016-11-02 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-6789) Prefer but don't require capabilities matching the node environment
Title: Message Title David Kramer updated an issue Puppet / PUP-6789 Prefer but don't require capabilities matching the node environment Change By: David Kramer Sprint: FF 2016-10-19 , FF 2016-11-02 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-3064) PuppetDB chokes on enqueued reports going from 3.2.x to 4.2
Title: Message Title David Kramer updated an issue PuppetDB / PDB-3064 PuppetDB chokes on enqueued reports going from 3.2.x to 4.2 Change By: David Kramer Sprint: FF 2016-10-19 , FF 2016-11-02 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-2987) i18n PuppetDB dependencies (stockpile and structured logging)
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2987 i18n PuppetDB dependencies (stockpile and structured logging) Change By: Ryan Senior Sprint: SE 2016-11-02 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-2908) Resolve conflict between i18n and structured-logging
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2908 Resolve conflict between i18n and structured-logging Change By: Ryan Senior Sprint: SE 2016-11-02 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-2986) i18n the rest of PuppetDB and PE PuppetDB Extensions
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2986 i18n the rest of PuppetDB and PE PuppetDB Extensions Change By: Ryan Senior Team: Systems Engineering 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-2986) i18n the rest of PuppetDB and PE PuppetDB Extensions
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2986 i18n the rest of PuppetDB and PE PuppetDB Extensions Change By: Ryan Senior Sprint: SE 2016-11-02 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-3101) Disable command "bashing in place" for the time being
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3101 Disable command "bashing in place" for the time being Change By: Ryan Senior Sprint: SE 2016-11-02 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-1476) Puppet agent should supply an informative user agent
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1476 Puppet agent should supply an informative user agent /cc Geoff Nichols Change By: Josh Cooper Team: Agent & Platform 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-6780) modify the lookup helper implementation to support v5 features
Title: Message Title Henrik Lindberg commented on PUP-6780 Re: modify the lookup helper implementation to support v5 features Use option #2 - that is better. Wer can work on the UX of the explain output later if it turns out to be too much data or hard to understand. 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-6760) Solaris pkg provider does not correctly handle expiring cert
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6760 Solaris pkg provider does not correctly handle expiring cert Change By: Moses Mendoza Sprint: AP Grooming Top 11-20 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-6614) Puppet 4.6.0 Error transactionstore is corrupt
Title: Message Title Moses Mendoza commented on PUP-6614 Re: Puppet 4.6.0 Error transactionstore is corrupt Hi Curtis Ruck, just following up to see if you'd been able to confirm puppet-agent 1.6.2 or later has resolved this issue for you? 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-6743) Classes should propagate schedule metaparameter to its contained resources
Title: Message Title cameris commented on PUP-6743 Re: Classes should propagate schedule metaparameter to its contained resources I did dig a little deeper and see the following problems when done while compilation: It seems that the function add_resource_metaparams ( https://github.com/puppetlabs/puppet/blob/5fb5e2deacb6043d2417e2d9acb4ebe78547f971/lib/puppet/parser/compiler.rb#L693-L716 ) is only called on define types and no other container (classes). The problem of the example in my previous comment. Currently the inner schedule takes precedence which is unintuitive. Overwriting the parameter from top down is also not possible, since the inner schedule should be honored when the outer allows it. Therefore we would have to intersect schedules. On the transaction (resource framework) side: The current state is that each resources schedule is checked ( https://github.com/puppetlabs/puppet/blob/5fb5e2deacb6043d2417e2d9acb4ebe78547f971/lib/puppet/transaction/resource_harness.rb#L48-L56 ) during evaluation of the transaction ( https://github.com/puppetlabs/puppet/blob/5fb5e2deacb6043d2417e2d9acb4ebe78547f971/lib/puppet/transaction.rb#L339-L340 ). In order to get all the schedules we would have to recursively ask the resources parent for their schedule parameters (and since the catalog is already in RAL while this is checked, its a bit hard to find the parent). This seems pretty inelegant. 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
Jira (PUP-6833) Windows is a first-class citizen
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6833 Windows is a first-class citizen Change By: Moses Mendoza This epic includes issues on Windows we should resolve / address that are basic platform parity This is effectively a holding bucket - it would be ideal to turn this into a fix-version targeted set of thematically related issues 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-6833) Windows is a first-class citizen
Title: Message Title Moses Mendoza created an issue Puppet / PUP-6833 Windows is a first-class citizen Issue Type: Epic Assignee: Unassigned Created: 2016/10/19 7:13 AM Priority: Major Reporter: Moses Mendoza This epic includes issues on Windows we should resolve / address that are basic platform parity Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6716) Error when purging local users on Windows
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6716 Error when purging local users on Windows Change By: Moses Mendoza Priority: Major Critical 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-5334) Puppet can't remove users from groups in OSX.
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-5334 Puppet can't remove users from groups in OSX. Change By: Moses Mendoza Priority: Major Critical 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-6762) [SPIKE] How and when do we get PO files from Transifex?
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6762 [SPIKE] How and when do we get PO files from Transifex? Change By: Moses Mendoza Sprint: AP 2016-11- 02 16 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 (FACT-1356) External facts should be able to return structured data
Title: Message Title Moses Mendoza assigned an issue to Unassigned Facter / FACT-1356 External facts should be able to return structured data Change By: Moses Mendoza Assignee: Branan Riley 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-6780) modify the lookup helper implementation to support v5 features
Title: Message Title Thomas Hallgren commented on PUP-6780 Re: modify the lookup helper implementation to support v5 features Question regarding explain and lookup options. When the lookup explanation was introduced, we decided to exempt the lookup of the lookup_options key from the explanation and instead provide a specific --explain-options option to the lookup command. This creates a problem. A data_hash function is called only once and will produce the full hash (it will include the lookup_options key if present). If the explanation support is disabled while the framework performs its initial assembly of the lookup_options hash, this means that whatever a data_hash sends to the explainer will be lost. This effectively renders the Context#explain() method useless for all data_hash methods since the initial call to produce the hash always origins from the lookup_options lookup. I see two possibilities for fixing this: 1. When explanation support is turned on, a data_hash function will always be called twice. Once for lookup_options with the explanation support disabled, and then once again, when the real lookup is made, with the explanation support enabled. 2. Always include the lookup_options in the explanation output and deprecate the --explain-options flag. I would prefer #2. My motivation is that a) it's inconsistent to use a different behavior when explanation is turned on, b) the explanation is also used for debugging, and c) although fairly verbose, it's actually nice to always see the lookup_options output. It sheds light on in what order things happen and that's the whole point with the explanation support. 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://g
Jira (PUP-6832) hash/resource expression confusion
Title: Message Title
Thomas Hallgren created an issue
Puppet / PUP-6832
hash/resource _expression_ confusion
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/10/19 2:12 AM
Priority:
Normal
Reporter:
Thomas Hallgren
The following code should return a Hash object but instead results in "_expression_ is not valid as a resource, resource-default, or resource-override":
function my_hash() {
notice('hello')
{ a => 'value a' }
}
Jira (PUP-6831) Change reverse.each
Title: Message Title Timur Sergeevich Tarasenko created an issue Puppet / PUP-6831 Change reverse.each Issue Type: CI Blocker Assignee: Unassigned Components: CLI Created: 2016/10/19 1:06 AM Priority: Normal Reporter: Timur Sergeevich Tarasenko Please check. This is a simple changes. Change on reverse_each because reverse_each loops in reverse order (no intermediate array created). https://github.com/puppetlabs/puppet/pull/5336 Add Comment
