Jira (FACT-1492) FACT [OS][RELEASE][MAJOR] returns FULL version instead of MAJOR version on WIndows Server 2016
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1492 FACT [OS][RELEASE][MAJOR] returns FULL version instead of MAJOR version on WIndows Server 2016 Change By: Geoff Nichols Sprint: APS 2016-09-21 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-1492) FACT [OS][RELEASE][MAJOR] returns FULL version instead of MAJOR version on WIndows Server 2016
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1492 FACT [OS][RELEASE][MAJOR] returns FULL version instead of MAJOR version on WIndows Server 2016 Change By: Geoff Nichols Sprint: APS 2016-09-21 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-348) Facter should provide a convenient way to cache values
Title: Message Title Geoff Nichols updated an issue Facter / FACT-348 Facter should provide a convenient way to cache values Change By: Geoff Nichols Sprint: Client APS 2016-09-21 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-1446) Improve the windows user check in facter/acceptance/test/facts/window.rb
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1446 Improve the windows user check in facter/acceptance/test/facts/window.rb Change By: Geoff Nichols Sprint: Windows APS 2016-09-21 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-1492) FACT [OS][RELEASE][MAJOR] returns FULL version instead of MAJOR version on WIndows Server 2016
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1492 FACT [OS][RELEASE][MAJOR] returns FULL version instead of MAJOR version on WIndows Server 2016 Change By: Geoff Nichols Team: Agent & Platform 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://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1461) Reload facter.conf when puppet reloads its configuration
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1461 Reload facter.conf when puppet reloads its configuration Change By: Geoff Nichols Team: Agent & Platform 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://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6684) Puppet agent run errors with `Could not run stack level too deep`
Title: Message Title Daniel Lynch created an issue Puppet / PUP-6684 Puppet agent run errors with `Could not run stack level too deep` Issue Type: Bug Assignee: Unassigned Components: Puppet Server Created: 2016/09/06 5:56 PM Priority: Normal Reporter: Daniel Lynch I have configured Puppet Server to use an external CA, and generated the necessary keys. My puppet.conf looks like the following: [master] vardir = /opt/puppetlabs/server/data/puppetserver logdir = /var/log/puppetlabs/puppetserver rundir = /var/run/puppetlabs/puppetserver pidfile = /var/run/puppetlabs/puppetserver/puppetserver.pid codedir = /etc/puppetlabs/code ca = false cacert = /etc/puppet/ssl/certs/bubbleshadow-ca-cert.pem hostcert = /etc/puppet/ssl/certs/bubbleshadow-server-cert.pem hostprivkey = /etc/puppet/ssl/private_keys/bubbleshadow-server-key.pem ssl_client_ca_auth = /etc/puppet/ssl/certs/bubbleshadow-ca-cert.pem [agent] server = puppet.bubbleshadow.net hostcert = /etc/puppet/ssl/certs/bubbleshadow-agent-cert.pem hostprivkey = /etc/puppet/ssl/private_keys/bubbleshadow-agent-key.pem localcacert = /etc/puppet/ssl/certs/bubbleshadow-ca-cert.pem certificate_revocation = false However, when I try to run `puppet agent --test --debug` I get the following output: Debug: Using cached certificate for ca Debug: Dynamically-bound server lookup failed, falling back to ca_server setting Debug: Dynamically-bound port lookup failed; falling back to ca_port setting
Jira (FACT-348) Facter should provide a convenient way to cache values
Title: Message Title Geoff Nichols updated an issue Facter / FACT-348 Facter should provide a convenient way to cache values Change By: Geoff Nichols Team: Agent & Platform 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://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-718) Allow for disabling certain facts within Facter
Title: Message Title Geoff Nichols updated an issue Facter / FACT-718 Allow for disabling certain facts within Facter Change By: Geoff Nichols Team: Agent & Platform 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://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1502) acceptance: mount a tmpfs directory and check the fact
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1502 acceptance: mount a tmpfs directory and check the fact Change By: Geoff Nichols Sprint: Client APS 2016-09-21 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-6683) Puppet agent 1.6.2 breaks defined()
Title: Message Title Nick Le Mouton commented on PUP-6683 Re: Puppet agent 1.6.2 breaks defined() Thanks, it looks like a restart fixes the problem after upgrading to puppet agent 1.6.2. I guess I just need to restart puppetserver when puppet agent gets updated. 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-6675) Puppet::Util::Execution.execute 'hostname' returns nothing as daemon
Title: Message Title
Michael Smith updated an issue
Puppet / PUP-6675
Puppet::Util::Execution.execute 'hostname' returns nothing as daemon
Change By:
Michael Smith
When {{Puppet::Util::Execution.execute 'hostname'}} is invoked by Puppet running as a daemon, no output is written. This seems to be exclusive to {{hostname}}, and may be restricted to certain Linux versions. I've tried it on RedHat 7 (64-bit).This can happen in a provider when using {{commands :hostname => 'hostname'}}, and then invoking {{hostname}}. The root appears to be how {{/usr/bin/hostname}} handles file handles. It can be simplified to{code}exec { '/bin/hostname': logoutput => true }{code} This is getting into some core Ruby weirdness:{code}ruby -e "Kernel.fork { \$stdout.reopen('/tmp/foo', 'w+'); Kernel.exec 'hostname' }"{code}prints hostname to {{/tmp/foo}} when run from the command-line. When run as a systemd script:{code:title=/usr/lib/systemd/system/print-hostname.service}[Unit]Description=Print the hostname using RubyWants=basic.targetAfter=basic.target network.target[Service]ExecStart=/usr/bin/ruby -e "Kernel.fork { $stdout.reopen('/tmp/foo', 'w'); Kernel.exec 'hostname' }"KillMode=process[Install]WantedBy=multi-user.target{code}symlinked to {{/etc/systemd/system/multi-user.target.wants/print-hostname.service}} it creates an empty file.Changing the ruby script to{code}foo = open('/tmp/foo', 'w'); pid = Kernel.fork { $stdout.reopen(foo); Kernel.exec 'hostname' }; Process.wait pid; foo.close{code}to ensure the file is closed doesn't seem to change the behavior.Also, behavior is consistent with both system Ruby on Redhat 7 (2.0.0) and Ruby with a puppet-agent 1.6.2 build candidate.If I use a simple fork/exec without trying to redirect stdout, it prints correctly as a service and from the command-line. It's only once I redirect stdout that things get weird. The above is essentially what Puppet::Util::Execution.execute does, which is what the type is calling to. Interestingly, Facter::Core::Execution.execute (with Facter 3) works fine.With {{strace}}, I note that {{hostname}} calls {{write(1, ...)}} then immediately exits. Other examples will close fids 1 and 2 before exiting.
Add Comment
Jira (PDB-3042) upgrade hikari CP
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3042 upgrade hikari CP Issue Type: Task Assignee: Unassigned Created: 2016/09/06 4:29 PM Priority: Normal Reporter: Wyatt Alt We're a few releases behind, and a number of bug fixes have occurred since our version. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-5717) Ruby crash when using Unicode codepage on windows when writing to STDOUT on a console
Title: Message Title Ethan Brown commented on PUP-5717 Re: Ruby crash when using Unicode codepage on windows when writing to STDOUT on a console Similarly, http://stackoverflow.com/a/38694885 talks about command prompt tweaks. 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-1444) Enable run-time configuration of facter
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1444 Enable run-time configuration of facter Change By: Geoff Nichols Team/s: Agent & Platform 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://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1462) Allow disabling subsections of structured facts
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1462 Allow disabling subsections of structured facts Change By: Geoff Nichols Team: Agent & Platform 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://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6655) acceptance: tidy resources should be non-isomorphic
Title: Message Title Phong Ly updated an issue Puppet / PUP-6655 acceptance: tidy resources should be non-isomorphic Change By: Phong Ly Team: Agent & Platform Support Sprint: Client 2016-09-07 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-3041) Implement a priority queue with a deadline for command processing
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-3041 Implement a priority queue with a deadline for command processing Issue Type: Task Assignee: Unassigned Created: 2016/09/06 1:51 PM Priority: Normal Reporter: Ryan Senior Some of our commands are more important to have timely processing on than others. We'd like to have catalogs processed as soon as possible as it could impact puppet runs. Reports are probably the next highest priority as orchestrator is using their results, but they're not as important as catalogs (and take significantly longer to store). Factsets are lower priority because although they change on every run, the changes aren't typically what people code against, it's more likely that they're writing code against things that change very infrequently (i.e. operating system). Add Comment
Jira (PDB-3040) Implement bypassing the queue perf optimization
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-3040 Implement bypassing the queue perf optimization Issue Type: Task Assignee: Unassigned Created: 2016/09/06 1:47 PM Priority: Normal Reporter: Ryan Senior The simplest example of this is when the queue is empty, why spend time writing the command to disk, just to read it out an process it. We need to flesh out exactly what that looks like. Is it only when the queue is empty? Do we only bypass the queue for catalogs? We can definitely process a catalog faster than we can write the catalog to disk, but that might not be as big of a difference after we are compressing the commands (PDB-2640). Factset and report processing time is closer to the time it takes to persist the commands to disk. Add Comment
Jira (PDB-3036) Make metrics endpoint available over SSL so it can be queried from a seperate host
Title: Message Title Andrew Roetker commented on PDB-3036 Re: Make metrics endpoint available over SSL so it can be queried from a seperate host Nick Walker I can't reproduce this problem. The metrics service runs on the same Jetty server as PuppetDB so if PuppetDB is hosted over SSL the metrics service will be as well. 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-3039) Stockpile metadata string length enforcement
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-3039 Stockpile metadata string length enforcement Issue Type: Task Assignee: Unassigned Created: 2016/09/06 1:11 PM Priority: Normal Reporter: Ryan Senior Most filesystems we run on require filenames to be less than 255 bytes. We should take some precautionary actions based on that assumption. First, we should validate incoming certnames, to ensure they are ASCII, (assuming certnames that don't fit are punycode encoded). Second, we should put precautionary code in place to trim certnames in a way that preserves their uniqueness, but shortens it. One option Rob Browning and I were talking about was checking if certnames are over X length, if so, taking the first 160 chars of the certname, hashing the certname, and appending the hash as the suffix. This hash would probably need to be a separate metadata field in the stockpile metadata string to avoid collisions with auto-generated certnames (and REALLY REALLY bad luck). Add Comment
Jira (PDB-3038) Merge mq_listener and command namespaces
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-3038 Merge mq_listener and command namespaces Issue Type: Task Assignee: Unassigned Created: 2016/09/06 12:57 PM Priority: Normal Reporter: Ryan Senior There is currently a very complicated relationship between the puppetlabs.puppetdb.mq-listener ns and the puppetlabs.puppetdb.command ns. These should be merged together. This complexity as caused a lot of wrapping and indirection between the two namespaces. The success criteria of this ticket is to merge the two namespaces and do some basic refactoring (time boxed) to improve the code after the merge. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3037) Find/remove ActiveMQ code no longer being used
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-3037 Find/remove ActiveMQ code no longer being used Issue Type: Task Assignee: Unassigned Created: 2016/09/06 12:53 PM Priority: Normal Reporter: Ryan Senior A decent chunk of the AMQ code has been removed, but some is still left over. This ticket is for making another pass through the codebase and removing anything left behind that is no longer being used. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-4643) Add return/next/break for iteration control
Title: Message Title John Duarte commented on PUP-4643 Re: Add return/next/break for iteration control This passes manual validation on Debian 8 amd64 and Windows 2012r2 using a pre-release build of puppet-agent at SHA 753e7e0 containing puppet at SHA 1d2adb7. A PR for acceptance tests has been submitted to test across all supported platforms. 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-3036) Make metrics endpoint available over SSL so it can be queried from a seperate host
Title: Message Title Nick Walker created an issue PuppetDB / PDB-3036 Make metrics endpoint available over SSL so it can be queried from a seperate host Issue Type: New Feature Assignee: Unassigned Created: 2016/09/06 11:57 AM Labels: tcse Priority: Normal Reporter: Nick Walker The Problem I'd like to query PuppetDB metrics from a host other than the PuppetDB host. The Solution Make the metrics endpoint available over SSL. Add Comment
Jira (PUP-6014) Default resource parameters are not stored in PuppetDB - not usable in collector
Title: Message Title David Kramer assigned an issue to Henrik Lindberg Puppet / PUP-6014 Default resource parameters are not stored in PuppetDB - not usable in collector Change By: David Kramer Assignee: David Kramer 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-6014) Default resource parameters are not stored in PuppetDB - not usable in collector
Title: Message Title Eric Sorenson commented on PUP-6014 Re: Default resource parameters are not stored in PuppetDB - not usable in collector My vote would be to leave it as is, since it has always behaved this way and it's a valid (i.e. not obviously wrong) thing to do. 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-1482) mountpoints fact does not show mounts on tmpfs
Title: Message Title Phong Ly commented on FACT-1482 Re: mountpoints fact does not show mounts on tmpfs create FACT-1502 for the acceptance test for this. 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-6647) Function dispatch taking zero arguments is incorrectly chosen
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6647 Function dispatch taking zero arguments is incorrectly chosen 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 (PUP-6675) Puppet::Util::Execution.execute 'hostname' returns nothing as daemon
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-6675 Puppet::Util::Execution.execute 'hostname' returns nothing as daemon Change By: Maggie Dreyer 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-6675) Puppet::Util::Execution.execute 'hostname' returns nothing as daemon
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-6675 Puppet::Util::Execution.execute 'hostname' returns nothing as daemon Change By: Maggie Dreyer Sprint: Client 2016-09-21 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-6647) Function dispatch taking zero arguments is incorrectly chosen
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6647 Function dispatch taking zero arguments is incorrectly chosen Change By: Eric Thompson QA Highest Test Level: Unit 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-1502) acceptance: mount a tmpfs directory and check the fact
Title: Message Title Phong Ly created an issue Facter / FACT-1502 acceptance: mount a tmpfs directory and check the fact Issue Type: Task Assignee: Unassigned Created: 2016/09/06 10:29 AM Priority: Normal Reporter: Phong Ly Verify that mount resource can mount a tmpfs directory and 'facter mountpoints' show the mount Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (FACT-1502) acceptance: mount a tmpfs directory and check the fact
Title: Message Title Phong Ly assigned an issue to Phong Ly Facter / FACT-1502 acceptance: mount a tmpfs directory and check the fact Change By: Phong Ly Assignee: Phong Ly 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-4643) Add return/next/break for iteration control
Title: Message Title John Duarte updated an issue Puppet / PUP-4643 Add return/next/break for iteration control Change By: John Duarte Summary: Add continue return /next/break for iteration control 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-4643) Add continue/next/break for iteration control
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-4643 Add continue/next/break for iteration control Change By: John Duarte Assignee: qa 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 (FACT-1482) mountpoints fact does not show mounts on tmpfs
Title: Message Title Phong Ly assigned an issue to Phong Ly Facter / FACT-1482 mountpoints fact does not show mounts on tmpfs Change By: Phong Ly Assignee: qa Phong Ly 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-6683) Puppet agent 1.6.2 breaks defined()
Title: Message Title R.I.Pienaar commented on PUP-6683 Re: Puppet agent 1.6.2 breaks defined() yes exactly the same 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-6683) Puppet agent 1.6.2 breaks defined()
Title: Message Title Henrik Lindberg commented on PUP-6683 Re: Puppet agent 1.6.2 breaks defined() R.I.Pienaar did you have exactly the same problem "redfined resource" ? I have seen other errors caused by not restarting the server. 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-6683) Puppet agent 1.6.2 breaks defined()
Title: Message Title R.I.Pienaar commented on PUP-6683 Re: Puppet agent 1.6.2 breaks defined() I had the same problem, restart fixed it. puppet-agent package should detect puppetserver and restart it or signal it somehow to kill its ruby workers and restart them I think 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-6683) Puppet agent 1.6.2 breaks defined()
Title: Message Title
Henrik Lindberg commented on PUP-6683
Re: Puppet agent 1.6.2 breaks defined()
Tweaking the above example to:
notify { $a_title: message => the_message }
if defined(Notify[$a_title]) == false {
notify { $a_title: message => the_message }
}
Does not trigger the problem (that is, the defined function does indeed find the resource). And if it is change to this:
notify { $a_title: message => the_message }
if defined(Notify[$a_title]) != false {
notify { $a_title: message => the_message }
}
It, as expected, errors with a duplicate resource.
Jira (PUP-6683) Puppet agent 1.6.2 breaks defined()
Title: Message Title Henrik Lindberg moved an issue Puppet / PUP-6683 Puppet agent 1.6.2 breaks defined() Change By: Henrik Lindberg Affects Version/s: puppet-agent 1.6.2 Affects Version/s: PUP 4.6.2 Workflow: Release Engineering Scrum Teams Workflow Key: PA PUP - 517 6683 Project: 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 gr
Jira (PUP-6669) Puppet should return better errors for Enum mismatches
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-6669 Puppet should return better errors for Enum mismatches Change By: John Duarte Status: Ready for CI Test Assignee: qa 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-6670) Newlines break Puppet tag validation
Title: Message Title Henrik Lindberg commented on PUP-6670 Re: Newlines break Puppet tag validation cherry picked commit to stable and merged stable to master 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-4643) Add continue/next/break for iteration control
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-4643 Add continue/next/break for iteration control Change By: John Duarte Status: Ready for CI Test Assignee: qa 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-6670) Newlines break Puppet tag validation
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6670 Newlines break Puppet tag validation Change By: Henrik Lindberg Fix Version/s: PUP 4.6.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-6670) Newlines break Puppet tag validation
Title: Message Title Henrik Lindberg commented on PUP-6670 Re: Newlines break Puppet tag validation ok, Charlie Sharpsteen I can merge it to stable for 4.6.3 / 4.7.z whatever comes first. 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-6670) Newlines break Puppet tag validation
Title: Message Title Charlie Sharpsteen commented on PUP-6670 Re: Newlines break Puppet tag validation Dang it, I meant to target this at the stable branch instead of master. Since this causes PuppetDB to fairly silently reject catalogs, it would be great to get it into a 4.7.z release. 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-6682) $settings leaks symbols into manifests
Title: Message Title R.I.Pienaar commented on PUP-6682 Re: $settings leaks symbols into manifests Yes, I wouldn't suggest keeping it called $settings, some thing else that clearly indicate that it's the master settings etc, perhaps somewhere below trusted leaving the option open to deprecate $settings as horrible. 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-6682) $settings leaks symbols into manifests
Title: Message Title Henrik Lindberg commented on PUP-6682 Re: $settings leaks symbols into manifests They can safely be bound to $settings::settings_hash though, since that cannot clash with anything that already exists. 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-6682) $settings leaks symbols into manifests
Title: Message Title Henrik Lindberg commented on PUP-6682 Re: $settings leaks symbols into manifests Actually, it is the other way around - $settings does not currently exist (as it is a namespace/scope). Thus if adding that top scope variable it may clash with users potential assignment to $settings. 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-6682) $settings leaks symbols into manifests
Title: Message Title Henrik Lindberg commented on PUP-6682 Re: $settings leaks symbols into manifests The "do not leak symbols" part is easily fixed - turning it into a hash is more complicated (need to investigate if $settings on its own is bound to something (if not, then that should also be easily 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-6682) $settings leaks symbols into manifests
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6682 $settings leaks symbols into manifests Change By: Henrik Lindberg 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-6682) $settings leaks symbols into manifests
Title: Message Title
R.I.Pienaar created an issue
Puppet / PUP-6682
$settings leaks symbols into manifests
Issue Type:
Bug
Affects Versions:
PUP 4.6.1
Assignee:
Unassigned
Created:
2016/09/06 6:49 AM
Priority:
Normal
Reporter:
R.I.Pienaar
% puppet apply -e '$be = $settings::storeconfigs_backend notice(inline_template("<%= @be.class %>"))'
Notice: Scope(Class[main]): Symbol
and therefore
Jira (PUP-6670) Newlines break Puppet tag validation
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6670 Newlines break Puppet tag validation Change By: Henrik Lindberg Acceptance Criteria: That a tag containing a new-line results in an error. 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-6670) Newlines break Puppet tag validation
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6670 Newlines break Puppet tag validation Change By: Henrik Lindberg Component/s: DOCS 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-6670) Newlines break Puppet tag validation
Title: Message Title Henrik Lindberg commented on PUP-6670 Re: Newlines break Puppet tag validation merged to master at: 5bf4d5d 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-6670) Newlines break Puppet tag validation
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6670 Newlines break Puppet tag validation Change By: Henrik Lindberg 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-6681) Add documentation for Timespan.new and Timestamp.new
Title: Message Title Henrik Lindberg commented on PUP-6681 Re: Add documentation for Timespan.new and Timestamp.new merged to master: a0bf79a Pulled straight through to done as this is only a documentation change. 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-6681) Add documentation for Timespan.new and Timestamp.new
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-6681 Add documentation for Timespan.new and Timestamp.new Change By: Henrik Lindberg 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-6680) Descendant providers do not inherit features from ancestors
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6680 Descendant providers do not inherit features from ancestors Change By: Henrik Lindberg Scrum Team: Client 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-6681) Add documentation for Timespan.new and Timestamp.new
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-6681 Add documentation for Timespan.new and Timestamp.new Change By: Thomas Hallgren Summary: Add documentation of for Timespan.new and Timestamp.new 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-6681) Add documentation of Timespan.new and Timestamp.new
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-6681 Add documentation of Timespan.new and Timestamp.new Issue Type: Improvement Assignee: Thomas Hallgren Created: 2016/09/06 2:05 AM Fix Versions: PUP 4.8.0 Priority: Normal Reporter: Thomas Hallgren Documentation for "Conversion to Timespan" and "Conversion to Timestamp" should be added to the documentation for the puppet function #new. It must be added to the 3.x stub. Add Comment
