Jira (PUP-5637) systemd unit puppet.service is missing ExecReload=
Title: Message Title John Duarte updated an issue Puppet / PUP-5637 systemd unit puppet.service is missing ExecReload= Change By: John Duarte Release Notes Summary: Puppet systemd packages now include an ExecReload command in the puppet.service files in order to facilitate graceful restart on systemd systems. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5637) systemd unit puppet.service is missing ExecReload=
Title: Message Title John Duarte updated an issue Puppet / PUP-5637 systemd unit puppet.service is missing ExecReload= Change By: John Duarte Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5637) systemd unit puppet.service is missing ExecReload=
Title: Message Title John Duarte commented on PUP-5637 Re: systemd unit puppet.service is missing ExecReload= Verified that the puppet.service files installed by the el7 rpm include the expected ExecReload command [root@vep8km4xgj6h5h1 ~]# grep -r ExecReload /usr/share/puppet/* /usr/share/puppet/ext/systemd/puppet.service:ExecReload=/bin/kill -HUP $MAINPID [root@vep8km4xgj6h5h1 ~]# grep -r ExecReload /usr/lib/systemd/system/puppet* /usr/lib/systemd/system/puppetagent.service:ExecReload=/bin/kill -HUP $MAINPID /usr/lib/systemd/system/puppet.service:ExecReload=/bin/kill -HUP $MAINPID [root@vep8km4xgj6h5h1 ~]# ls puppet-3.8.6.20-1.el7.noarch.rpm
Jira (PUP-5637) systemd unit puppet.service is missing ExecReload=
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-5637 systemd unit puppet.service is missing ExecReload= Change By: John Duarte Assignee: qa John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1024) Facter can't handle non-ascii ec2_userdata
Title: Message Title John Duarte updated an issue Facter / FACT-1024 Facter can't handle non-ascii ec2_userdata Change By: John Duarte QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1024) Facter can't handle non-ascii ec2_userdata
Title: Message Title John Duarte updated an issue Facter / FACT-1024 Facter can't handle non-ascii ec2_userdata Change By: John Duarte QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6031) static catalogs do not copy source host and port to content_uri
Title: Message Title John Duarte updated an issue Puppet / PUP-6031 static catalogs do not copy source host and port to content_uri Change By: John Duarte QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6031) static catalogs do not copy source host and port to content_uri
Title: Message Title John Duarte updated an issue Puppet / PUP-6031 static catalogs do not copy source host and port to content_uri Change By: John Duarte QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1282) networking.ip should fall back to default route 'src' if networking.primary has no IP address
Title: Message Title John Duarte updated an issue Facter / FACT-1282 networking.ip should fall back to default route 'src' if networking.primary has no IP address Change By: John Duarte QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1282) networking.ip should fall back to default route 'src' if networking.primary has no IP address
Title: Message Title John Duarte updated an issue Facter / FACT-1282 networking.ip should fall back to default route 'src' if networking.primary has no IP address Change By: John Duarte QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6033) Recursive file resource in static catalog creates empty directory when source has trailing "/"
Title: Message Title John Duarte updated an issue Puppet / PUP-6033 Recursive file resource in static catalog creates empty directory when source has trailing "/" Change By: John Duarte QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6033) Recursive file resource in static catalog creates empty directory when source has trailing "/"
Title: Message Title John Duarte updated an issue Puppet / PUP-6033 Recursive file resource in static catalog creates empty directory when source has trailing "/" Change By: John Duarte QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6024) Restrict which files are inlined within the per-environment directory
Title: Message Title John Duarte updated an issue Puppet / PUP-6024 Restrict which files are inlined within the per-environment directory Change By: John Duarte QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6024) Restrict which files are inlined within the per-environment directory
Title: Message Title John Duarte updated an issue Puppet / PUP-6024 Restrict which files are inlined within the per-environment directory Change By: John Duarte QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6036) static catalogs cannot inline metadata for files requiring percent encoding
Title: Message Title John Duarte updated an issue Puppet / PUP-6036 static catalogs cannot inline metadata for files requiring percent encoding Change By: John Duarte QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6036) static catalogs cannot inline metadata for files requiring percent encoding
Title: Message Title John Duarte updated an issue Puppet / PUP-6036 static catalogs cannot inline metadata for files requiring percent encoding Change By: John Duarte QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6044) Puppet agent 4 failing to retrieve catalog due to missing gem dependency for unused provider
Title: Message Title Ryan Whitehurst created an issue Puppet / PUP-6044 Puppet agent 4 failing to retrieve catalog due to missing gem dependency for unused provider Issue Type: Bug Assignee: Unassigned Created: 2016/03/10 6:07 PM Priority: Normal Reporter: Ryan Whitehurst We were running the PE 3.8.1 agent. We upgraded the agent to AIO 1.2.7/Puppet 4.2.3, and the agent failed with the following error: Error: Could not autoload puppet/provider/dns_record/route53: cannot load such file -- nokogiri Error: Could not autoload puppet/type/dns_record: Could not autoload puppet/provider/dns_record/route53: cannot load such file -- nokogiri Error: Could not retrieve catalog from remote server: Could not intern from text/pson: Could not autoload puppet/type/dns_record: Could not autoload puppet/provider/dns_record/route53: cannot load such file -- nokogiri
Jira (PDOC-23) Add the ability to output JSON
Title: Message Title Hailee Kenney commented on PDOC-23 Re: Add the ability to output JSON Hailee Kenney Interesting. I wish I had time to address those tickets, but I'm really busy right now. Thanks for finally getting this reviewed! Don't worry about it at all! Just want to get them recored for prosperity in case this project gets picked up again. The JSON stuff we have right now is real cool so I'd like to get it into the hands of users and see what they do with it. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-23) Add the ability to output JSON
Title: Message Title Ian Kronquist commented on PDOC-23 Re: Add the ability to output JSON Hailee Kenney Interesting. I wish I had time to address those tickets, but I'm really busy right now. Thanks for finally getting this reviewed! Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6024) Restrict which files are inlined within the per-environment directory
Title: Message Title
William Hopper commented on PUP-6024
Re: Restrict which files are inlined within the per-environment directory
FR: verified that a file in /etc/puppetlabs/code/environments/production/site/site_module/files/ has its metadata inlined. The following can be found in the cached catalog"
"metadata":{"/tmp/foo":{"path":"/etc/puppetlabs/code/environments/production/site/site_module/files/site_file_test","relative_path":null,"links":"manage","owner":998,"group":997,"mode":420,"checksum":{"type":"md5","value":"{md5}09f7e02f1290be211da707a266f153b3"},"type":"file","destination":null,"content_uri":"puppet:///site/site_module/files/site_file_test","source":"puppet:///modules/site_module/site_file_test"}}
Then verified that a file in /etc/puppetlabs/code/environments/production/site/dist/site_dist_module/site_dist_file does not have its metadata inlined (there is no metadata in the cached catalog). This format falls under the /etc/puppetlabs/code/environments/production///module/files format, which shouldn't have metadata inlined.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this
Jira (FACT-1282) networking.ip should fall back to default route 'src' if networking.primary has no IP address
Title: Message Title Branan Riley updated an issue Facter / FACT-1282 networking.ip should fall back to default route 'src' if networking.primary has no IP address Change By: Branan Riley Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1282) networking.ip should fall back to default route 'src' if networking.primary has no IP address
Title: Message Title Branan Riley updated an issue Facter / FACT-1282 networking.ip should fall back to default route 'src' if networking.primary has no IP address Change By: Branan Riley Release Notes Summary: Facter will now consider the 'source' attribute of routing table entries associated with an interface to be an additional address tied to that interface. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5637) systemd unit puppet.service is missing ExecReload=
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5637 systemd unit puppet.service is missing ExecReload= Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5637) systemd unit puppet.service is missing ExecReload=
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5637 systemd unit puppet.service is missing ExecReload= Change By: Eric Thompson QA Highest Test Level: Acceptance QA Risk Assessment: Medium QA Risk Probability: Low QA Risk Severity: Medium QA Highest Test Level Reason: needs a full stack test. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To
Jira (PUP-5637) systemd unit puppet.service is missing ExecReload=
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5637 systemd unit puppet.service is missing ExecReload= Change By: Eric Thompson The systemd unit file shipped with puppet 3.8.4 (and lower 3.x versions) does not define an ExecReload command. As es a result , systemd does a reload , sending the agent a SIGTERM and possibly killing off any currently running puppet run.The agent supports to restart itself on receiving a SIGHUP. Systemd should send this signal to restart the puppet agent.This is fixed in puppet 4.3, see https://github.com/puppetlabs/puppet/blob/4.3.0/ext/systemd/puppet.service Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (NPUP-29) Parser does not parse resource override expressions for collectors correctly
Title: Message Title Eric Thompson updated an issue Native Puppet / NPUP-29 Parser does not parse resource override expressions for collectors correctly Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (NPUP-29) Parser does not parse resource override expressions for collectors correctly
Title: Message Title Eric Thompson updated an issue Native Puppet / NPUP-29 Parser does not parse resource override expressions for collectors correctly Change By: Eric Thompson QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6020) Puppet types sometimes fail to compare for equality
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6020 Puppet types sometimes fail to compare for equality Change By: Eric Thompson QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6020) Puppet types sometimes fail to compare for equality
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6020 Puppet types sometimes fail to compare for equality Change By: Eric Thompson QA Highest Test Level: Unit Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6020) Puppet types sometimes fail to compare for equality
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6020 Puppet types sometimes fail to compare for equality Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1282) networking.ip should fall back to default route 'src' if networking.primary has no IP address
Title: Message Title Michael Smith commented on FACT-1282 Re: networking.ip should fall back to default route 'src' if networking.primary has no IP address Looks like it could use some release notes. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6020) Puppet types sometimes fail to compare for equality
Title: Message Title
Eric Thompson commented on PUP-6020
Re: Puppet types sometimes fail to compare for equality
validated on ubuntu1404 at stable puppet-agent SHA: 2472bc6b2524fa178ad68d409104b7d2729f71e6
root@r794dzncqml7hgf:/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/functions# puppet apply -e "notice({ Variant[Enum[a,b,c]] => 'first', Variant[Pattern[a,b,c]] => 'second'})"
Notice: Scope(Class[main]): {Variant[Enum['a', 'b', 'c']] => first, Variant[Pattern[/a/, /b/, /c/]] => second}
Notice: Compiled catalog for r794dzncqml7hgf.delivery.puppetlabs.net in environment production in 0.04 seconds
Notice: Applied catalog in 0.01 seconds
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-6033) Recursive file resource in static catalog creates empty directory when source has trailing "/"
Title: Message Title William Hopper commented on PUP-6033 Re: Recursive file resource in static catalog creates empty directory when source has trailing "/" FR: Verified on puppet#stable: On the master, we have: [root@nweot3buh2vwtko tmp]# ls -l /etc/puppetlabs/code/environments/production/modules/example_mod/files/example_dir/ total 4 drwxr-xr-x. 2 root root 27 Mar 10 16:04 sub_dir -rw-r--r--. 1 root root 3 Mar 10 16:04 top_level_file [root@nweot3buh2vwtko tmp]# ls -l /etc/puppetlabs/code/environments/production/modules/example_mod/files/example_dir/sub_dir/ total 4 -rw-r--r--. 1 root root 9 Mar 10 16:04 sub_level_file With a manifest,
Jira (PUP-5964) Improve how type mismatches are asserted and reported
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5964 Improve how type mismatches are asserted and reported Change By: Eric Thompson QA Highest Test Level: Unit QA Risk Assessment: Low QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5964) Improve how type mismatches are asserted and reported
Title: Message Title Eric Thompson commented on PUP-5964 Re: Improve how type mismatches are asserted and reported this was largely validated in the other type mismatch reporter tickets. the only user functionality here is consistent error reporting in assert_type(): and this is relatively low priority root@r794dzncqml7hgf:~# puppet apply -e 'assert_type(10, 10)' Error: Evaluation Error: Error while evaluating a Function Call, 'assert_type' expects one of: (Type type, Any value, Callable[Type, Type] block?) rejected: parameter 'type' expects a Type value, got Integer (String type_string, Any value, Callable[Type, Type] block?) rejected: parameter 'type_string' expects a String value, got Integer at line 1:1 on node r794dzncqml7hgf.delivery.puppetlabs.net root@r794dzncqml7hgf:~# puppet apply -e 'assert_type(type(Integer), "yes. hello")' Error: Evaluation Error: Error while evaluating a Function Call, assert_type(): expected a Type value, got String at line 1:1 on node
Jira (PUP-3018) Puppet doesn't like to evaluate 'require => [ [], [] ],'
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-3018 Puppet doesn't like to evaluate 'require => [ [], [] ],' Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6043) puppet apply -e states "syntax error at end of file" when there is no file
Title: Message Title Eric Thompson created an issue Puppet / PUP-6043 puppet apply -e states "syntax error at end of file" when there is no file Issue Type: Bug Assignee: Unassigned Created: 2016/03/10 4:34 PM Priority: Minor Reporter: Eric Thompson $> puppet apply -e 'assert_type(type(Integer, "yes. hello")' Error: Could not parse for environment production: Syntax error at end of file on node r794dzncqml7hgf.delivery.puppetlabs.net i believe this is a regression, or duplicate ticket, but i could not find the older ticket (if it exists)
Jira (PUP-5855) Deprecate inexact resource reference matches
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5855
Deprecate inexact resource reference matches
Change By:
Henrik Lindberg
As described in PUP-5659 it is currently allowed to make references to resources that are inexact because they are not validated, and at runtime on the agent they may be references to the same resource . e.g. File[/tmp/foo/] and File[/tmp/foo] is considered to be the same resource.This is impossible to know on the Catalog Compilation side. Therefore this should not be allowed as it creates a far worse problem of not being able to validate that resources do exists in the catalog at compile time.This can be implemented as a warning in 4.x after having performed the validation that will be standard in 5.0.0. UPDATEThis was implemented as a catalog validation after all defaults, collectors etc. have run. A warning of error is issued if {{\--strict}} is set to {{warning}} or {{error}}. When {{strict}} is set to {{off}}, the behavior is as before this was added. When strict is set to {{warning}}, it is possible to suppress warnings by adding {{undefined_resources}} to the setting {{disable_warnings}}. When warning, the warning will only be made once per missing resource (irrespective of the same resource being referenced from multiple locations, and in different meta parameters).
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an
Jira (PDOC-23) Add the ability to output JSON
Title: Message Title Hailee Kenney commented on PDOC-23 Re: Add the ability to output JSON This appears to work as described! A few improvements we may want to file tickets for (but that needn't hold up this ticket): Add some spec test that make sure we get the expected json for a given file Add the ability to run against and entire module. Right now this can only be run on a file by file basis but the way the schema is formatted it could pretty easily support and entire module (there is a section for classes, defines, functions, etc) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-23) Add the ability to output JSON
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-23 Add the ability to output JSON Change By: Hailee Kenney Issue Type: Task New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-23) Add the ability to output JSON
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-23 Add the ability to output JSON Change By: Hailee Kenney Fix Version/s: PDOC 0.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-28) Make puppet strings available as a gem
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-28 Make puppet strings available as a gem Change By: Hailee Kenney Fix Version/s: PDOC 0.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6033) Recursive file resource in static catalog creates empty directory when source has trailing "/"
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6033 Recursive file resource in static catalog creates empty directory when source has trailing "/" Change By: Josh Cooper Release Notes Summary: Ensuring unreleased static catalogs behave the same as non-static catalogs when sources have trailing slashes. Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2526) Query pdb metrics / replication status from the cli
Title: Message Title Russell Mull created an issue PuppetDB / PDB-2526 Query pdb metrics / replication status from the cli Issue Type: New Feature Assignee: Unassigned Created: 2016/03/10 4:04 PM Priority: Normal Reporter: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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
Jira (PUP-5901) Type mismatch describer should merge Enum expectations
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5901 Type mismatch describer should merge Enum expectations Change By: Henrik Lindberg Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6033) Recursive file resource in static catalog creates empty directory when source has trailing "/"
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-6033 Recursive file resource in static catalog creates empty directory when source has trailing "/" Change By: William Hopper Assignee: qa William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2525) (maint) Handle terminus to termini package upgrades
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2525 (maint) Handle terminus to termini package upgrades Issue Type: Bug Assignee: Unassigned Created: 2016/03/10 3:41 PM Priority: Normal Reporter: gepetto-bot This commit adds an exec to allow users to upgrade to termini-3.x via the module with no extra manual steps. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PDB-2525) (maint) Handle terminus to termini package upgrades
Title: Message Title gepetto-bot updated an issue PuppetDB / PDB-2525 (maint) Handle terminus to termini package upgrades Change By: gepetto-bot Sprint: PuppetDB 2016-03-23 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5901) Type mismatch describer should merge Enum expectations
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5901 Type mismatch describer should merge Enum expectations Change By: Eric Thompson Release Notes Summary: Type mismatches where the type is an Enum or multiple Enums are now merged to make it easier to figure out what is wrong. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5901) Type mismatch describer should merge Enum expectations
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5901 Type mismatch describer should merge Enum expectations Change By: Eric Thompson QA Highest Test Level: Unit QA Risk Assessment: Medium QA Status: Reviewed Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5901) Type mismatch describer should merge Enum expectations
Title: Message Title
Eric Thompson commented on PUP-5901
Re: Type mismatch describer should merge Enum expectations
validated on ubuntu1404 at stable puppet-agent SHA: 2472bc6b2524fa178ad68d409104b7d2729f71e6
root@r794dzncqml7hgf:~# puppet apply -e 'notify { type([2, 4.14], gobbledygooked): }'
Error: Evaluation Error: Error while evaluating a Function Call, 'type' parameter 'inference_method' expects a match for Enum['detailed', 'generalized', 'reduced'], got 'gobbledygooked' at line 1:10 on node r794dzncqml7hgf.delivery.puppetlabs.net
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-2524) Display replication status in the built-in dashboard
Title: Message Title Russell Mull created an issue PuppetDB / PDB-2524 Display replication status in the built-in dashboard Issue Type: New Feature Assignee: Unassigned Created: 2016/03/10 3:24 PM Priority: Normal Reporter: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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
Jira (PUP-5902) Type mismatch describer should expand aliases
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5902 Type mismatch describer should expand aliases Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5902) Type mismatch describer should expand aliases
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5902 Type mismatch describer should expand aliases Change By: Eric Thompson QA Highest Test Level: Unit QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5902) Type mismatch describer should expand aliases
Title: Message Title
Eric Thompson commented on PUP-5902
Re: Type mismatch describer should expand aliases
validated on ubuntu1404 at stable puppet-agent SHA: 2472bc6b2524fa178ad68d409104b7d2729f71e6
root@r794dzncqml7hgf:~# puppet apply alias.pp
Error: Evaluation Error: Error while evaluating a Function Call, 'pull_sled' parameter 'a_deer' expects a match for OhDeer = Enum['blixem', 'comet', 'cupid', 'dancer', 'dasher', 'dunder', 'prancer', 'rudolph', 'vixen'], got 'blixen' at /root/alias.pp:3:1 on node r794dzncqml7hgf.delivery.puppetlabs.net
root@r794dzncqml7hgf:~# cat alias.pp
type OhDeer = Enum[rudolph, dasher, dancer, prancer, vixen, comet, cupid, dunder, blixem,]
function pull_sled(OhDeer $a_deer) { }
pull_sled('blixen')
Add Comment
Jira (PUP-5902) Type mismatch describer should expand aliases
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-5902 Type mismatch describer should expand aliases Change By: Eric Thompson Assignee: qa Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6042) `puppet agent --test` does not override cached catalog behavior
Title: Message Title Ryan Coleman created an issue Puppet / PUP-6042 `puppet agent --test` does not override cached catalog behavior Issue Type: Improvement Assignee: Unassigned Created: 2016/03/10 3:05 PM Priority: Normal Reporter: Ryan Coleman * --test: Enable the most common options used for testing. These are 'onetime', 'verbose', 'ignorecache', 'no-daemonize', 'no-usecacheonfailure', 'detailed-exitcodes', 'no-splay', and 'show_diff'.
Jira (PUP-6036) static catalogs cannot inline metadata for files requiring percent encoding
Title: Message Title Michael Smith updated an issue Puppet / PUP-6036 static catalogs cannot inline metadata for files requiring percent encoding Change By: Michael Smith Release Notes Summary: Bug on unreleased feature. Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6041) puppet inspect fails to report changes to resources on the agent
Title: Message Title William Hopper commented on PUP-6041 Re: puppet inspect fails to report changes to resources on the agent Hah! No problem, Jo Rhett, you're the reporter now! We're looking into the old compliance console in PE 2.7, though we haven't had a ton of luck yet Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6041) puppet inspect fails to report changes to resources on the agent
Title: Message Title Jo Rhett commented on PUP-6041 Re: puppet inspect fails to report changes to resources on the agent I'm also confused as to why the sync status of the resource is roughly half of the output, but I'm being told that sync status was not checked? (perhaps this was half implemented?) It may end up that this should be a feature request more than bug, I'm still trying to dig up history on previous output. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6041) puppet inspect fails to report changes to resources on the agent
Title: Message Title William Hopper updated an issue Puppet / PUP-6041 puppet inspect fails to report changes to resources on the agent Change By: William Hopper Reporter: William Hopper Jo Rhett Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6041) puppet inspect fails to report changes to resources on the agent
Title: Message Title Jo Rhett commented on PUP-6041 Re: puppet inspect fails to report changes to resources on the agent I'm trying to track down older reports I used to pull using inspect to figure out what's missing. Is it possible that inspect used to provide verbose output when doing the comparison which it no longer does? I'm seeing evidence that collecting the e-mail output of inspect was done, as well as the report files. FWIW may I be the reporter of this issue? Then the blame goes to me Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6034) Bundler Fails when Running Under a Unicode Windows User
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6034 Bundler Fails when Running Under a Unicode Windows User Change By: Ethan Brown Labels: i18n windows Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6034) Bundler Fails when Running Under a Unicode Windows User
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6034 Bundler Fails when Running Under a Unicode Windows User Change By: Ethan Brown Fix Version/s: PUP 4.4.1 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6035) Puppet Throws Exception when Running Under Unicode Windows User
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6035 Puppet Throws Exception when Running Under Unicode Windows User Change By: Ethan Brown Labels: i18n windows Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6036) static catalogs cannot inline metadata for files requiring percent encoding
Title: Message Title Michael Smith commented on PUP-6036 Re: static catalogs cannot inline metadata for files requiring percent encoding Verified with bar is a file and puppet://myfileserver:/modules/foo/ %:@!$&'()*+,;=. Note this is really hard to test (I used Ruby to generate the file using double quoting and had to use single quotes in Puppet and escape the single quote). Found that some characters are still not escaped and cause issues. The content_uri string looks correct puppet://myfileserver:/site/foo/files/ %:@Unable to render embedded object: File (@) not found.$&'()*+,;=?environment=production_id=1 and everything starting with the comma is not passed on to code-content. The same content request without static catalogs appears to succeed: GET /puppet/v3/file_content/modules/foo/%20%25:@!$&'()*+,;=?environment=production&. There appears to be a bug in the puppetserver handling of that request (compared to puppet). Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6035) Puppet Throws Exception when Running Under Unicode Windows User
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6035 Puppet Throws Exception when Running Under Unicode Windows User Change By: Ethan Brown Fix Version/s: PUP 4.4.1 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6036) static catalogs cannot inline metadata for files requiring percent encoding
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-6036 static catalogs cannot inline metadata for files requiring percent encoding Change By: Michael Smith Assignee: qa Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6031) static catalogs do not copy source host and port to content_uri
Title: Message Title Michael Smith updated an issue Puppet / PUP-6031 static catalogs do not copy source host and port to content_uri Change By: Michael Smith Release Notes Summary: Bug fix for unreleased feature. Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6041) puppet inspect fails to report changes to resources on the agent
Title: Message Title Branan Riley commented on PUP-6041 Re: puppet inspect fails to report changes to resources on the agent My understanding is that this is not at all how Inspect was intended to work, and that it has never done this. inspect just sends reports to the master detailing what the status of audited resource paramters is. It's up to you to do something with that information (including tracking detlas, if you so desire). PE used to have a GUI (compliance) for these resports, which did provide information on drift, but all the logic for doing that work lived in the Puppet Enterprise console, not in Puppet itself. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6024) Restrict which files are inlined within the per-environment directory
Title: Message Title Michael Smith commented on PUP-6024 Re: Restrict which files are inlined within the per-environment directory With this fix, the puppet agent constructs a content_uri that the results in puppetserver passing production 1 site/foo/files/bar to a code-content end-point. That seems correct. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6031) static catalogs do not copy source host and port to content_uri
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-6031
static catalogs do not copy source host and port to content_uri
Change By:
Josh Cooper
If you define a file resource with a source parameter:{code:puppet}file { '/tmp/file': ensure => file, source => 'puppet:// / host:/modules/foo/bar',}{code}Then the {{content_uri}} omits the host and port:{code:json} "content_uri": "puppet:///modules/foo/bar"{code}which can cause the agent to retrieve the file from a different host/port than was originally specified.We should preserve the host and port. The reason we don't is because we call {{CGI.escape}} which corrupts the URI.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-5233) puppet inspect is using wrong path for catalog data
Title: Message Title William Hopper commented on PUP-5233 Re: puppet inspect is using wrong path for catalog data Jo Rhett makes sense. I've created https://tickets.puppetlabs.com/browse/PUP-6041 to track the sad state of inspect, and like you say we'll probably call this ticket resolved when we verify it can at least find the catalog again. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6041) puppet inspect fails to report changes to resources on the agent
Title: Message Title William Hopper created an issue Puppet / PUP-6041 puppet inspect fails to report changes to resources on the agent Issue Type: Bug Affects Versions: PUP 4.3.2, PUP 3.5.1 Assignee: Unassigned Created: 2016/03/10 1:45 PM Priority: Normal Reporter: William Hopper When auditing resources in a manifest, one would expect the puppet inspect tool to send reports which detail local changes to said resources outside of puppet runs. While inspect does properly identify resources which have the audit bit set, changes are never picked up and thus audit reports contain false negatives. The following are a series of comments from Jo Rhett and myself relating to this issue, which was discovered after working on PUP-5233: Jo: Puppet inspect runs successfully, and it does properly determine which resources in the catalog have the audit attribute set, but it does not pick up on changes to the resources locally. # puppet inspect --verbose
Jira (PUP-6036) static catalogs cannot inline metadata for files requiring percent encoding
Title: Message Title Josh Cooper commented on PUP-6036 Re: static catalogs cannot inline metadata for files requiring percent encoding To verify, create a manifest where the source parameter contains special characters, and verify the agent applies the file correctly. Note prior to static catalogs, puppet does not correctly handle several special characters, e.g. ?, #, [, ]. So when verifying this, we want to ensure that special characters that work when static catalogs are off, also work when static catalogs are on. See https://github.com/puppetlabs/puppet/pull/4775#issuecomment-194694258. I'm going to file a separate ticket about ensuring some special characters are handled correctly, e.g. #, independent of whether static catalogs are enabled or not. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6031) static catalogs do not copy source host and port to content_uri
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-6031 static catalogs do not copy source host and port to content_uri Change By: Michael Smith Assignee: qa Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6033) Recursive file resource in static catalog creates empty directory when source has trailing "/"
Title: Message Title
Josh Cooper commented on PUP-6033
Re: Recursive file resource in static catalog creates empty directory when source has trailing "/"
To verify, create a manifest with a file resource whose source parameter has a trailing slash, and contains subdirectories and files:
class example_mod {
file { '/tmp/empty':
ensure => directory,
recurse => true,
source => 'puppet:///modules/example_mod/example_dir/',
}
}
Verify puppet copies the tree as opposed to creating an empty directory.
Add Comment
Jira (PUP-6031) static catalogs do not copy source host and port to content_uri
Title: Message Title
Josh Cooper commented on PUP-6031
Re: static catalogs do not copy source host and port to content_uri
One way to verify this is to specify an alternate file server in the manifest, and use a reverse proxy to ensure the agent uses the specified host and port when retrieving file content. On the agent, add a hosts file entry for myfileserver whose IP matches that of the master:
10.0.10.5 myfileserver
On the master, create a manifest like:
class foo {
file { '/tmp/file':
ensure => file,
source => 'puppet:///myfileserver:/modules/foo/bar',
}
}
On the master wipe out the ssl directory and generate a cert whose dns alt names contains both the normal FQDN and myfileserver:
Jira (PUP-5233) puppet inspect is using wrong path for catalog data
Title: Message Title Jo Rhett commented on PUP-5233 Re: puppet inspect is using wrong path for catalog data Yes you have nailed what I believe exactly. Searching on stackexchange and ask Puppet will show you multiple reports of same going back about 2 years-ish. I believe the title needs a change. It would not be inappropriate to close this issue as fixed by your bug, and open a new issue for the follow-on problem. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5855) Deprecate inexact resource reference matches
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-5855 Deprecate inexact resource reference matches Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (NPUP-29) Parser does not parse resource override expressions for collectors correctly
Title: Message Title Henrik Lindberg commented on NPUP-29 Re: Parser does not parse resource override expressions for collectors correctly Merged to master at: f44be30 (as per agreements, jumping to test after merge for visibility). Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5941) Ensure a type mismatch involving a local type makes sense to a user
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-5941 Ensure a type mismatch involving a local type makes sense to a user Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-73) handle type aliases in 4.x ruby functions (introduced in PUP-5903)
Title: Message Title Henrik Lindberg created an issue Puppet Strings / PDOC-73 handle type aliases in 4.x ruby functions (introduced in PUP-5903) Issue Type: Bug Assignee: Unassigned Created: 2016/03/10 12:24 PM Fix Versions: PDOC 0.3.0 Priority: Normal Reporter: Henrik Lindberg In PUP-5903 the ability to define local type aliases inside a 4.x function was added. These types may need to be processed when producing documentation. It may also be just perfectly fine to display only the aliases, but users may want to see the type definitions. The first step is to ensure that the addition of type aliases does not trip up the extraction process. Second step is to possibly add a section that shows the type aliases. Add Comment
Jira (PUP-5939) Create tickets for PDOC
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-5939 Create tickets for PDOC Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (NPUP-29) Parser does not parse resource override expressions for collectors correctly
Title: Message Title Henrik Lindberg assigned an issue to qa Native Puppet / NPUP-29 Parser does not parse resource override expressions for collectors correctly Change By: Henrik Lindberg Status: Ready for Merge Test Assignee: Henrik Lindberg qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5768) Fix problematic usage of ENV for Windows
Title: Message Title Craig Gomes commented on PUP-5768 Re: Fix problematic usage of ENV for Windows Agree with Ryan Gard on this one. From what I'm reading on this and having discussed with Glenn we've completed what was outlined in the ticket. The concerns listed within are edge cases and the remaining previously existing issues will get picked up with subsequent tickets. I'm in favor of moving this to done. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6040) "puppet facts" outputs indirector object instead of simple fact list
Title: Message Title Nicholas Fagerlund moved an issue Puppet / PUP-6040 "puppet facts" outputs indirector object instead of simple fact list Change By: Nicholas Fagerlund Workflow: Documentation Scrum Team Workflow Issue Type: Improvement Bug Key: DOCUMENT PUP - 514 6040 Project: Documentation Puppet Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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
Jira (PUP-5233) puppet inspect is using wrong path for catalog data
Title: Message Title
William Hopper commented on PUP-5233
Re: puppet inspect is using wrong path for catalog data
Ah, I think I see now. When I setup a scenario like the one you described and do a regular puppet run, my report will contain audit notices such as:
message: "content changed '{md5}ec1bebaea2c042beb68f7679ddd106a4' to '{md5}025f253325b46929cd34f2a7c3c55e7c' (previously recorded value was {md5}025f253325b46929cd34f2a7c3c55e7c)"
...
message: "audit change: previously recorded value 2016-03-10 10:20:03 -0800 has been changed to 2016-03-10 10:23:02 -0800"
...
out_of_sync: true
changed: true
resource_type: File
title: /tmp/test
... while an inspect run on an agent which has an altered file doesn't give any indication whatsoever that anything has changed, thus completely defeating the purpose of the audit:
Jira (PDOC-63) Blizzard of errors and warnings when run against core code
Title: Message Title Nicholas Fagerlund commented on PDOC-63 Re: Blizzard of errors and warnings when run against core code I'm also in favor of ignoring non-puppet-y Ruby code. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6037) File Permissions are set wrong in puppet
Title: Message Title Kylo Ginsberg commented on PUP-6037 Re: File Permissions are set wrong in puppet Thanks for the bug report Patrick Thyen! Can you add information about what puppet version this was found with and what platform(s) you've observed this on? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6038) Puppet sets GID
Title: Message Title Kylo Ginsberg commented on PUP-6038 Re: Puppet sets GID Thanks for the bug report Patrick Thyen! Can you add information about what puppet version this was found with and what platform(s) you've observed this on? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1282) networking.ip should fall back to default route 'src' if networking.primary has no IP address
Title: Message Title Michael Smith updated an issue Facter / FACT-1282 networking.ip should fall back to default route 'src' if networking.primary has no IP address Change By: Michael Smith Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6031) static catalogs do not copy source host and port to content_uri
Title: Message Title Michael Smith updated an issue Puppet / PUP-6031 static catalogs do not copy source host and port to content_uri Change By: Michael Smith Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6036) static catalogs cannot inline metadata for files requiring percent encoding
Title: Message Title Michael Smith updated an issue Puppet / PUP-6036 static catalogs cannot inline metadata for files requiring percent encoding Change By: Michael Smith Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6036) static catalogs cannot inline metadata for files requiring percent encoding
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6036 static catalogs cannot inline metadata for files requiring percent encoding Change By: Kylo Ginsberg Labels: burnside-ss Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5968) Deprecate Symbol#<=> monkey patch
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-5968 Deprecate Symbol#<=> monkey patch Change By: Hailee Kenney Assignee: Hailee Kenney Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1362) Add facter platform identification support for huaweios
Title: Message Title Kenn Hussey updated an issue Facter / FACT-1362 Add facter platform identification support for huaweios Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5768) Fix problematic usage of ENV for Windows
Title: Message Title Ryan Gard commented on PUP-5768 Re: Fix problematic usage of ENV for Windows Ethan Brown Glenn Sarti Kenn Hussey I think this ticket is needs other components to make for a compelling FR case. I would suggest we move the ticket through as is since there is unit tests in place to cover these changes. From my manually testing thus far we have not made the situation any worse when dealing with Unicode users on Windows. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1345) Solaris automount entries in mountpoint result in huge fact lists
Title: Message Title Geoffrey Gardella commented on FACT-1345 Re: Solaris automount entries in mountpoint result in huge fact lists Eric Sorenson Yes, I would agree that you should exclude automount points from the fact list for mountpoints. In a large environment, you could end up with thousands of those. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1362) Add facter platform identification support for huaweios
Title: Message Title Scott Garman commented on FACT-1362 Re: Add facter platform identification support for huaweios Yes, it looks like this CI run succeeded: https://jenkins.puppetlabs.com/view/puppet-agent/view/stable/view/facter/job/platform_facter_init-van-component_stable/28/ Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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.
