Jira (PUP-10096) Parameters of resources are base64 encoded in puppetdb if created as raw byte strings by ruby functions
Title: Message Title
Josh Cooper commented on PUP-10096
Re: Parameters of resources are base64 encoded in puppetdb if created as raw byte strings by ruby functions
The problem stems from ruby's Resolv.getname function which returns a ruby ASCII-8BIT string:
irb(main):001:0> require 'resolv'
=> true
irb(main):002:0> name = Resolv.getname("172.217.14.196")
=> "sea30s01-in-f4.1e100.net"
irb(main):003:0> name.encoding
=> #
Note it's the same as a ruby binary string:
irb(main):008:0> Encoding::ASCII_8BIT == Encoding::BINARY
=> true
Puppet preserves the binary-ness of the string throughout the catalog compilation process, and converts it to base64 when storing in puppetdb. IIRC postgres can't store null bytes specifically. Nick Lewis pointed out:
Internally, programs that manipulate domain names should represent them as sequences of labels, where each label is a length octet followed by an octet string.
By convention, domain names can be stored with arbitrary case, but domain name comparisons for all present domain functions are don
Jira (PUP-10096) Parameters of resources are base64 encoded in puppetdb if created as raw byte strings by ruby functions
Title: Message Title Henrik Lindberg commented on PUP-10096 Re: Parameters of resources are base64 encoded in puppetdb if created as raw byte strings by ruby functions Thanks Reinhard Vicinus - if you are absolutely sure there is no Binary in the catalog sent to the agent it must be a matter of the ASCII-8BIT getting converted en route to PDB in a different way. That is a problem to look into - it should be done the same way for sure. (Maybe Puppet is already doing what was suggested in terms of auto-conversion on one of the paths; when the catalog is being serialized, but not on the other). In any case if the function rdnslookup() was changed to return UTF-8 it would prevent the problem. (I think the function should be fixed as that is the prudent thing to do for any function returning what is known to be "text". Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.328499.1570559378000.135239.1570572840460%40Atlassian.JIRA.
Jira (PUP-10096) Parameters of resources are base64 encoded in puppetdb if created as raw byte strings by ruby functions
Title: Message Title
Reinhard Vicinus commented on PUP-10096
Re: Parameters of resources are base64 encoded in puppetdb if created as raw byte strings by ruby functions
I don't know if the return value should be auto converted. But in my opinion whatever is done should be done consistently and at the moment, the parameter value gets base64 encoded but the title does not even if it is the same value. Also I would expect that there is no difference between the catalog submitted to the puppetdb and the catalog stored under /opt/puppetlabs/puppet/cache/client_data/catalog/${fqdn}.json but at the moment there are no base64 encoded values in the node catalog, only in the puppetdb catalog.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.328499.1570559378000.135178.1570571940153%40Atlassian.JIRA.
Jira (PUP-5915) exec resources fail unless cwd is readable
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5915 exec resources fail unless cwd is readable Change By: Josh Cooper Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.117135.1455734657000.135167.1570571820265%40Atlassian.JIRA.
Jira (PUP-5915) exec resources fail unless cwd is readable
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5915 exec resources fail unless cwd is readable Change By: Josh Cooper Fix Version/s: PUP 5.5.7 Fix Version/s: PUP 6.11.0 Fix Version/s: PUP 6.4.5 Fix Version/s: PUP 5.5.18 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.
Jira (PUP-5915) exec resources fail unless cwd is readable
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-5915 exec resources fail unless cwd is readable Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.117135.1455734657000.135158.1570571761201%40Atlassian.JIRA.
Jira (PUP-10080) Exec resources fail if the working directory is inaccessible
Title: Message Title Josh Cooper commented on PUP-10080 Re: Exec resources fail if the working directory is inaccessible I agree. Let's close this as a dup of PUP-9997, update PR https://github.com/puppetlabs/puppet/pull/7775 to reference PUP-5915, and track the general issue of Dir.chdir in PUP-9997. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327890.1570115712000.135141.1570571580355%40Atlassian.JIRA.
Jira (PUP-10080) Exec resources fail if the working directory is inaccessible
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10080 Exec resources fail if the working directory is inaccessible Change By: Josh Cooper Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327890.1570115712000.135098.1570570680268%40Atlassian.JIRA.
Jira (PUP-10080) Exec resources fail if the working directory is inaccessible
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-10080 Exec resources fail if the working directory is inaccessible Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327890.1570115712000.135101.1570570680280%40Atlassian.JIRA.
Jira (PUP-10080) Exec resources fail if the working directory is inaccessible
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10080 Exec resources fail if the working directory is inaccessible Change By: Josh Cooper Fix Version/s: PUP 6.4.5 Fix Version/s: PUP 5.5.18 Fix Version/s: PUP 6.11.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327890.1570115712000.135093.1570570620360%40Atlassian.JIRA.
Jira (PUP-10096) Parameters of resources are base64 encoded in puppetdb if created as raw byte strings by ruby functions
Title: Message Title Henrik Lindberg commented on PUP-10096 Re: Parameters of resources are base64 encoded in puppetdb if created as raw byte strings by ruby functions Since the function is clearly meant to return "text" it should encode the return string as an UTF-8 string instead of ASCII-8BIT. Then it is totally clear what it is returning. It could be argued that if ASCII-8BIT encoded text can be changed to UTF-8 without errors then it should be automatically treated as "text" (like in Puppet before version 6 - where we also had difficulty with non compliant UTF-8 strings being used). The issue is that there is a fairly large risk that binary content could represent "garbage text" and be displayed as such. Auto conversion is generally evil and is usually the cause of unforeseen problems - remember all the funny stuff that happened with automatic string to number conversions? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.328499.1570559378000.135043.1570569660182%40Atlassian.JIRA.
Jira (FACT-2055) Facter fails if its working directory does not exist
Title: Message Title James Ralston commented on FACT-2055 Re: Facter fails if its working directory does not exist The problem is that although facter does not call boost::filesystem::current_path directly (at least as far as I can tell), something else it calls does (most likely, another boost library call), and getcwd() fails with ENOENT if the cwd has been unlinked. I'll play devil's advocate here: is this a bug with Puppet, or a feature of Unix? Puppet is not the only program that will fail if its cwd is unlinked. A great many number of standard Unix utilities will throw errors (and potentially die / fail to function) if the cwd does not exist. If facter died or produced errors if the cwd were inaccessible, I would assert that is a bug with facter. (See PUP-9997 for the rationale there.) But facter bombing out if its cwd is unlinked? I'd argue the most reasonable response to that might simply be the punchline to the old "doctor, it hurts when I move my arm this way" joke: then don't do that. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327976.1570129217000.134972.1570568160103%40Atlassian.JIRA.
Jira (PDB-4509) Fresh install of puppetdb will not start ERROR: invalid byte sequence for encoding "UTF8"
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4509 Fresh install of puppetdb will not start ERROR: invalid byte sequence for encoding "UTF8" Change By: Austin Blatt Release Notes Summary: PuppetDB migrations require the postgres database the setting `standard_conforming_strings` to be `true`. Before a Postgres exception would terminate startup, now we will verify that setting before checking if any migrations are necessary. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.325166.1568831083000.134945.1570567680682%40Atlassian.JIRA.
Jira (PDB-4509) Fresh install of puppetdb will not start ERROR: invalid byte sequence for encoding "UTF8"
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4509 Fresh install of puppetdb will not start ERROR: invalid byte sequence for encoding "UTF8" Change By: Austin Blatt Release Notes Summary: PuppetDB migrations require the postgres database the setting `standard_conforming_strings` to be `true`. Before a Postgres exception would terminate startup, now we will verify that setting before checking if migrations are necessary. Release Notes: Not Needed Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.325166.1568831083000.134941.1570567620232%40Atlassian.JIRA.
Jira (PDB-4509) Fresh install of puppetdb will not start ERROR: invalid byte sequence for encoding "UTF8"
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4509 Fresh install of puppetdb will not start ERROR: invalid byte sequence for encoding "UTF8" Change By: Austin Blatt Release Notes: Bug Fix Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.325166.1568831083000.134931.1570567500260%40Atlassian.JIRA.
Jira (PUP-10080) Exec resources fail if the working directory is inaccessible
Title: Message Title James Ralston commented on PUP-10080 Re: Exec resources fail if the working directory is inaccessible John Bollinger, I propose that there are two separate issues here: Puppet misbehaves / fails if the cwd is inaccessible. Puppet misbehaves / fails if the cwd does not exist. I reopend my ticket PUP-9997, which is solely about issue #1. Would you be willing to confine issue #1 to PUP-9997, and keep issue #2 confined to this ticket? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327890.1570115712000.134915.1570567080145%40Atlassian.JIRA.
Jira (PUP-5915) exec resources fail unless cwd is readable
Title: Message Title
James Ralston commented on PUP-5915
Re: exec resources fail unless cwd is readable
I was incorrect. This is not actually fixed. The problem is that the exec resource itself implicitly defaults the cwd parameter to the cwd if the cwd parameter was not provided for the exec resource in question. In the case where Puppet's cwd is inaccessible, this will cause all Puppet exec() resources to fail. I assert that defaulting the cwd parameter to the cwd of the Puppet process is wrong. If the user does not supply a cwd parameter to the exec resource in question, Puppet must assume that the user does not want Puppet to attempt to chdir() to any directory. Assuming that the user wants Puppet to chdir() to the cwd is an erroneous assumption, as 1) this is not what the user specified, and 2) it's nonsensical, as even if the chdir() call succeeds, Puppet has not actually changed the cwd. To fully fix this bug, I agree with John Bollinger in PUP-10080: the "implicitly default the cwd parameter to Puppet's cwd if it was not specified" behavior is wrong and should be removed. I think the only thing required is removing this line from lib/puppet/provider/exec.rb:
cwd ||= Dir.pwd
This is because, from my read, Puppet::Util::Execution.execute() will do the correct thing if the cwd parameter is unspecified:
cwd = options[:cwd]
if cwd && ! Puppet::FileSystem.directory?(cwd)
raise ArgumentError, _("Working directory %{cwd} does not exist!") % { cwd: cwd }
end
And:
cwd = options[:c
Jira (PUP-10080) Exec resources fail if the working directory is inaccessible
Title: Message Title John Bollinger commented on PUP-10080 Re: Exec resources fail if the working directory is inaccessible James Ralston, I came to the same conclusion about the code change to be made, +/- explanatory code comments. That seems to be what Josh Cooper was looking at, too. I guess I can go ahead and submit the PR, and Puppet can kick it back to me if they don't want it. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327890.1570115712000.134737.1570563660128%40Atlassian.JIRA.
Jira (PUP-10096) Parameters of resources are base64 encoded in puppetdb if created as raw byte strings by ruby functions
Title: Message Title Reinhard Vicinus created an issue Puppet / PUP-10096 Parameters of resources are base64 encoded in puppetdb if created as raw byte strings by ruby functions Issue Type: Bug Affects Versions: PUP 6.9.0 Assignee: Unassigned Created: 2019/10/08 11:29 AM Priority: Normal Reporter: Reinhard Vicinus Puppet Version: 6.10.0 Puppet Server Version: 6.7.0 PuppetDB Version: 6.7.0 OS Name/Version: Ubuntu 18.04. If a ruby function returns a raw byte string, the puppet server handles it without problems, but if the returned value is used as the value of a parameter of a resource the parameter is stored base64 encoded in the puppetdb even if it only contains utf-8 conform characters. This issue only appears with puppet 6, puppet 5 is not affected. To reproduce this issue you need a puppetserver with a puppetdb. Then you need to place the ruby function were the puppetserver can find it: require 'resolv' module Puppet::Parser::Functions newfunction(:rdnslookup, :type => :rvalue) do |args|
Jira (PUP-10080) Exec resources fail if the working directory is inaccessible
Title: Message Title James Ralston commented on PUP-10080 Re: Exec resources fail if the working directory is inaccessible John Bollinger, I'll defer to Puppet folks who want to chime in, but as the reporter of PUP-9997, I would just submit a PR with the code fixes and no tests. From looking at the code for the Exec provider, I think the only thing that is required is removing the cwd ||= Dir.pwd line, as Puppet::Util::Execution.execute() only calls Dir.chdir if the cwd parameter was set. Did you come to a different conclusion? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327890.1570115712000.134538.1570559100152%40Atlassian.JIRA.
Jira (PUP-9570) Catalog failure on first run due to pluginsync and environment switch
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-9570 Catalog failure on first run due to pluginsync and environment switch Change By: Josh Cooper Assignee: Jorie Tappa Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300842.1553021716000.133901.1570551003172%40Atlassian.JIRA.
Jira (PUP-9990) no_proxy config setting is overridden by http_proxy environment variable
Title: Message Title Ob Rzwo commented on PUP-9990 Re: no_proxy config setting is overridden by http_proxy environment variable Ha, the no_proxy variable in /etc/environment is the solution. It works with version 6.8, 6.9 and 6.10. Sorry I made the horses a bit shy, but you have to add the puppet master to the no_proxy variable now!!! sudo vi /etc/environment PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games" http_proxy="http://corporateproxy:8123" https_proxy="http://corporateproxy:8123" ftp_proxy="http://corporateproxy:8123" # Attention: Problem: Only 1024 characters possible: no_proxy="localhost,127.0.0.1,localaddress,.local,puppet" HTTP_PROXY="http://corporateproxy:8123" HTTPS_PROXY="http://corporateproxy:8123" FTP_PROXY="http://corporateproxy:8123"
Jira (FACT-2059) premature loading of module-provided facts under `-p`
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2059 premature loading of module-provided facts under `-p` Change By: Mihai Buzgau Sprint: PR - Triage Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.328315.1570469412000.133607.1570539240228%40Atlassian.JIRA.
Jira (FACT-2059) premature loading of module-provided facts under `-p`
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2059 premature loading of module-provided facts under `-p` Change By: Mihai Buzgau Team: Night's Watch Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.328315.1570469412000.133604.1570539180215%40Atlassian.JIRA.
Jira (FACT-2054) Facter::Core::Execution.execute incorrectly expands shell builtins
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2054 Facter::Core::Execution.execute incorrectly expands shell builtins Change By: Mihai Buzgau Sprint: PR - Triage Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327886.1570111406000.133598.1570538940215%40Atlassian.JIRA.
Jira (PUP-10059) Puppet won't install (some) packages with ensure => held
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10059 Puppet won't install (some) packages with ensure => held Change By: Mihai Buzgau Sprint: PR - Triage Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327639.157002023.133595.1570538880237%40Atlassian.JIRA.
Jira (PUP-1537) Dpkg package provider misbehaving for held package with specific version
Title: Message Title Ciprian Badescu assigned an issue to Ciprian Badescu Puppet / PUP-1537 Dpkg package provider misbehaving for held package with specific version Change By: Ciprian Badescu Assignee: Jesse Hathaway Ciprian Badescu Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.24894.1391021944000.133439.1570523760716%40Atlassian.JIRA.
