Jira (PUP-1072) support HTTP(S) URL as the file 'source'
Title: Message Title Felix Frank commented on PUP-1072 Re: support HTTP(S) URL as the file 'source' Yes, this is currently a known limitation. For most HTTP(S) sources, the resource will only work properly when using checksum => 'mtime', 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-1072) support HTTP(S) URL as the file 'source'
Title: Message Title John Duarte commented on PUP-1072 Re: support HTTP(S) URL as the file 'source' Thanks Felix Frank. I missed your earlier comment to that effect. This is issue is considered resolved. 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-5209) call_function and metadata.json: call a function from a different module, very strange behavior
Title: Message Title Thomas Hallgren commented on PUP-5209 Re: call_function and metadata.json: call a function from a different module, very strange behavior Additional tests added to the PR. 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-5209) call_function and metadata.json: call a function from a different module, very strange behavior
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-5209 call_function and metadata.json: call a function from a different module, very strange behavior Change By: Henrik Lindberg Assignee: Thomas Hallgren 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-5651) A puppet function declaration must be a top level construct
Title: Message Title
Thomas Hallgren created an issue
Puppet / PUP-5651
A puppet function declaration must be a top level construct
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/01/05 8:19 AM
Priority:
Normal
Reporter:
Thomas Hallgren
It's currently possible to write:
class foo {
function bar() {
}
}
This should not be possible since a function is a top
Jira (PUP-1072) support HTTP(S) URL as the file 'source'
Title: Message Title
John Duarte updated an issue
Puppet / PUP-1072
support HTTP(S) URL as the file 'source'
Change By:
John Duarte
Release Notes Summary:
This adds support for 'http' and 'https' URLS as source attributes to the file resource.Since the checksum metadata is not available from the URL, applying a file resource with an http/s source will always be detected as a content change. This can be avoided by using {{mtime}} as the checksum.
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-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Henrik Lindberg assigned an issue to Unassigned merged to stable at: 08fc9a5 Puppet / PUP-5461 puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output 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-3) Implement produce/consume expressions in the parser
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Native Puppet / NPUP-3 Implement produce/consume expressions in the parser 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-1072) support HTTP(S) URL as the file 'source'
Title: Message Title John Duarte updated an issue Puppet / PUP-1072 support HTTP(S) URL as the file 'source' Change By: John Duarte 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-5644) puppet lookup command creates new SSL hierarchy with self-signed CA
Title: Message Title Henrik Lindberg commented on PUP-5644 Re: puppet lookup command creates new SSL hierarchy with self-signed CA merged to stable at: 9ae4c58 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-5644) puppet lookup command creates new SSL hierarchy with self-signed CA
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5644 puppet lookup command creates new SSL hierarchy with self-signed CA Change By: Henrik Lindberg Release Notes Summary: The lookup command needlessly created a separate SSL hierarchy with self-assigned CA. Now it does not. 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-1613) Puppet parsing rpm versions incorrectly, uses downgrade which causes Multilib errors
Title: Message Title John Simpson commented on PUP-1613 Re: Puppet parsing rpm versions incorrectly, uses downgrade which causes Multilib errors I'm not 100% sure if this is the same issue, but it feels like it's closely related. Error: /Stage[main]/Base/Util::Packagemin[openssl]/Package[openssl]/ensure: change from 1.0.1e-42.el6 to 1.0.1e-42.el6_7.1 failed: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install openssl-1.0.1e-42.el6_7.1' returned 1: Error: Multilib version problems found. This often means that the root cause is something else and multilib version checking is just pointing out that there is a problem. Eg.: 1. You have an upgrade for openssl which is missing some dependency that another package requires. Yum is trying to solve this by installing an older version of openssl of the different architecture. If you exclude the bad architecture yum will tell you what the root cause is (which package
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5461 puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Change By: Henrik Lindberg Release Notes Summary: The lookup command always compiled the entire catalog before performing the actual lookup of the given key. While correct, it can potentially be very time consuming, and produce unwanted logging. Since a full compilation is typically a special case (normally values does no interpolate arbitrary global puppet variables). A full compilation is now available for those that have data that is configured with interpolation of arbitrary (non fact/ENC variables) by using the flag --compile. Without this flag the command uses an empty catalog 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-5584) Cached catalogs are loaded using the agent's string locale which can result in corrupted data
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-5584 Cached catalogs are loaded using the agent's string locale which can result in corrupted data Change By: Rob Reynolds Component/s: PE 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-5209) call_function and metadata.json: call a function from a different module, very strange behavior
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-5209 call_function and metadata.json: call a function from a different module, very strange behavior Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-2782) Yumrepo target attribute does not work
Title: Message Title Thomas Lowry commented on PUP-2782 Re: Yumrepo target attribute does not work I have confirmed this to be an issue for me as well. 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-5593) Update Cumulus Node config to use VM from VMpooler
Title: Message Title Stan Duffy assigned an issue to Stan Duffy Puppet / PUP-5593 Update Cumulus Node config to use VM from VMpooler Change By: Stan Duffy Assignee: Stan Duffy 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-5593) Update Cumulus Node config to use VM from VMpooler
Title: Message Title Stan Duffy commented on PUP-5593 Re: Update Cumulus Node config to use VM from VMpooler Updated: cumulus-25-x86_64: roles: - agent platform: cumulus-2.5-x86_64 hypervisor: vcloud template: cumulus-vx-25-x86_64 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-5461 puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-5650) $::hostname, $::fqdn not available when using puppet master compile
Title: Message Title Tom De Vylder commented on PUP-5650 Re: $::hostname, $::fqdn not available when using puppet master compile Finally managed to resolve this undocumented feature. For future reference and anyone who ends up here googling the same problem: The location to store (custom) facts for "puppet master compile" is $vardir/yaml/facts/$certname.yaml. The expected format is this: --- !ruby/object:Puppet::Node::Facts values: hostname: test01 fqdn: test01.example.org certname: test01 ipaddress: "172.0.0.1" Add Comment
Jira (PDB-2267) puppetdb-access.log does not log access requests to a hostname/IP it is not listening to
Title: Message Title Rob Nelson commented on PDB-2267 Re: puppetdb-access.log does not log access requests to a hostname/IP it is not listening to Seems like a sane default to suppress and it's nice to know how to elevate on demand, when a connection appears to be failing or you think you're flooded. I'll see about a documentation PR so this is captured somewhere other than JIRA. 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-3238) puppet reports "end of file reached" if server closes HTTP connection
Title: Message Title Josh Cooper commented on PUP-3238 Re: puppet reports "end of file reached" if server closes HTTP connection For folks watching this ticket, Marc Fournier submitted a PR to puppet to enable TCP keepalive https://github.com/puppetlabs/puppet/pull/4508 which should allow the agent to detect when the remote side closes the idle connection, and not reuse a stale connection. 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-5267) puppet dies with "Illegal instruction: 4" on Xeon 5500 Mac Pro, including VMs on that host
Title: Message Title
Jason Schroeder commented on PUP-5267
Re: puppet dies with "Illegal instruction: 4" on Xeon 5500 Mac Pro, including VMs on that host
I also have this issue on an older Mac Pro aluminum tower running OSX 10.10.5 Facter v3.8 (which works fine) provides this info about the hardware:
{{sp_cpu_type => 6-Core Intel Xeon sp_current_processor_speed => 2.4 GHz sp_kernel_version => Darwin 14.5.0 sp_l2_cache_core => 256 KB sp_l3_cache_processor => 12 MB sp_machine_model => MacPro5,1 sp_machine_name => Mac Pro sp_number_processors => 12 sp_os_version => OS X 10.10.5 (14F1509)}}
I have the same "Illegal instruction: 4" for all of these packages:
puppet-agent-1.2.0-osx-10.9-x86_64.dmg
puppet-agent-1.2.4-1.mavericks.dmg
puppet-agent-1.2.4-1.yosemite.dmg
puppet-agent-1.3.1-1.osx10.10.dmg
puppet-agent-1.3.2-1.osx10.10.dmg
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
Jira (PDB-2267) puppetdb-access.log does not log access requests to a hostname/IP it is not listening to
Title: Message Title Rob Nelson commented on PDB-2267 Re: puppetdb-access.log does not log access requests to a hostname/IP it is not listening to Some scribbles at https://github.com/rnelson0/puppetdb/blob/PDB-2267/logging/documentation/trouble_session_logging.markdown. Let me know what tweaks you'd like to see before I submit the PR. Thanks! 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-5209) call_function and metadata.json: call a function from a different module, very strange behavior
Title: Message Title Josh Cooper commented on PUP-5209 Re: call_function and metadata.json: call a function from a different module, very strange behavior I thought we fixed this problem in PUP-3121 in https://github.com/puppetlabs/puppet/commit/372da25acf7bbec994b97baa07a9d0c501ac737e, or was the fix incomplete? 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-5623) Callable type should be able to describe return type
Title: Message Title
Peter Huene commented on PUP-5623
Re: Callable type should be able to describe return type
I'll add that, aesthetically speaking, I do prefer the hash option as you previously mentioned as it's more explicit:
Callable[{ params => [P1, P2, ..., PN, BlockType], min => x, max => y, returns => R }]
I guess I'm not a fan of having min and max in the array, despite being parameter-related. Specifying the block type as the last (Callable) type in the params array seems consistent with how we might someday take a block parameter in a Puppet function.
Still, I don't have a strong opinion on this.
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-5578) parse_string doesnt interpolate %{key} with Puppet 4.0
Title: Message Title
John Duarte commented on PUP-5578
Re: parse_string doesnt interpolate %{key} with Puppet 4.0
Daniel Scott we have recently been performing updates to our CI infrastructure. It looks like the publishing of the puppet-agent nightly builds were broken in the process of rolling out these updates.
We are currently working on correcting this situation and adding additional monitoring to make sure that it does not go unnoticed going forward. This issue should be resolved in the next couple of days.
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-5598) Subkeys of lookup_options are found when using Hiera data binding
Title: Message Title John Duarte updated an issue Puppet / PUP-5598 Subkeys of lookup_options are found when using Hiera data binding Change By: John Duarte QA Risk Assessment Reason: Covered by unit 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 unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-5598) Subkeys of lookup_options are found when using Hiera data binding
Title: Message Title John Duarte updated an issue Puppet / PUP-5598 Subkeys of lookup_options are found when using Hiera data binding 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-5598) Subkeys of lookup_options are found when using Hiera data binding
Title: Message Title John Duarte updated an issue Puppet / PUP-5598 Subkeys of lookup_options are found when using Hiera data binding 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-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Sean Griffin assigned an issue to Sean Griffin Puppet / PUP-5461 puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Change By: Sean Griffin Assignee: Sean Griffin 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-5652) Windows Package provider does not work with Installshield with MSI files
Title: Message Title Aaron Armstrong assigned an issue to Unassigned Puppet / PUP-5652 Windows Package provider does not work with Installshield with MSI files Change By: Aaron Armstrong Assignee: Aaron Armstrong 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-5341) Tag fields in reports accidentally changed to Puppet::Util::TagSet objects
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-5341 Tag fields in reports accidentally changed to Puppet::Util::TagSet objects Change By: Nicholas Fagerlund Summary: Report format should have gone to 5 Tag fields in Puppet 4.0.0, due reports accidentally changed to a change in the tags field Puppet::Util::TagSet objects 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-5341) Tag fields in reports accidentally changed to Puppet::Util::TagSet objects
Title: Message Title
Nicholas Fagerlund updated an issue
Puppet / PUP-5341
Tag fields in reports accidentally changed to Puppet::Util::TagSet objects
Change By:
Nicholas Fagerlund
Puppet reports contain `tags` fields in each Puppet::Util::Log and Puppet::Resource::Status object; these fields are supposed to be arrays of strings. In Puppet 4.0.0, the tags fields in a YAML-dumped Puppet::Transaction::Report object changed from arrays to Puppet::Util::TagSets, as described in DOCUMENT-436. This was a side-effect of:{code}commit 7b0eed2b52bad0d5c3fc3a9fbe37d097eabc9fc2Author: Britt Gresham Date: Wed Nov 12 09:17:30 2014 -0800(PUP-1019) Remove ZAMLBefore this commit we were using ZAML by monkey patching the `to_yaml`function to use ZAML.dump instead of YAML.dump. After removing `zaml.rb`tests started failing because of the way that ZAML serialized YAML soassertions in those tests were changed.This commit also adds in a patch to YAML.Psych to handle the cases whereruby objects were being encoded improperly.This commit removes the use of ZAML in puppet as part of the Puppet 4.xcode removal efforts.{code}{code}diff --git a/lib/puppet/util/tag_set.rb b/lib/puppet/util/tag_set.rbindex e74f228..613859d 100644--- a/lib/puppet/util/tag_set.rb+++ b/lib/puppet/util/tag_set.rb@@ -24,12 +24,6 @@ class Puppet::Util::TagSet < Set to_data_hash.to_pson end- # this makes puppet serialize it as an array for backwards- # compatibility- def to_zaml(z)-to_data_hash.to_zaml(z)- end- def join(*args) to_a.join(*args) end{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-4281) Autoload metaparams from modules.
Title: Message Title Eric Sorenson commented on PUP-4281 Re: Autoload metaparams from modules. I feel like this is a rarely used extension point (this is the first time I've seen a request for metaparams-in-modules) and it would be better to work to get your code incorporated into core rather than make this fully supported as a plugin API. Dean Wilson would you be willing to work it into a PR against 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-5652) Windows Package provider does not work with Installshield with MSI files
Title: Message Title Corey Osman created an issue Puppet / PUP-5652 Windows Package provider does not work with Installshield with MSI files Issue Type: Bug Affects Versions: PUP 3.8.0 Assignee: Aaron Armstrong Components: PE, Types and Providers Created: 2016/01/05 1:46 PM Environment: PE 3.8 Priority: Normal Reporter: Corey Osman Reference Material: http://unattended.sourceforge.net/installers.php (InstallShield with MSI) The windows package provider incorrectly quotes or adds a space when combining the install options. Because the Installshield installer is a wrapper exe for another installer, options must be specially quoted and passed in as an argument. However, puppet can't seem to get the quotes right no matter what I do. Example:
Jira (NPUP-4) Implement the Callable type
Title: Message Title Peter Huene assigned an issue to Peter Huene Native Puppet / NPUP-4 Implement the Callable type Change By: Peter Huene Assignee: Peter Huene 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-5596) Puppet agent freezes
Title: Message Title Matt Stith commented on PUP-5596 Re: Puppet agent freezes Turns out this was just a massive dependency cycle caused by the way that our overall puppet repo is structured. I'm happy closing this, though an easier way to detect big cycles would be nice! 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-5648) Descending range semantics are broken in the compiler
Title: Message Title
Peter Huene commented on PUP-5648
Re: Descending range semantics are broken in the compiler
I am also in agreement that the "descending" property really shouldn't be on a type, for consistency's sake alone. It should really be an argument to each that says "we want to enumerate in reverse order".
Integer[0, 10].each(true) |$x| {}
But perhaps with a construct that makes it clearer than passing a boolean, such as an expected string, e.g. each(reverse), where the default value is undef meaning 'in-order'?
The nice thing about doing it this way is that we can now enumerate arrays and hashes in reverse-order too, not just ranges.
Backwards compatibility concerns aside, I'd also like the compiler to error if max < min for all types that support them.
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-5648) Descending range semantics are broken in the compiler
Title: Message Title Henrik Lindberg commented on PUP-5648 Re: Descending range semantics are broken in the compiler It snowballs with reverse_map, reverse_reduce, ... etc. So I don't like that much. Better to use a function to do a reverse instead. The problem is naturally that it requires a copy to be made as we have no enumeration runtime type (which I would really like to have, now that is implemented as a crutch with a special - is_enumerable or something like that). For an integer range it would need to create an array with every number to be able to iterate over it. Regarding Integer and Type as ranges - I don't think it is odd that the range is specified with two values is min/max or max/min order - not if you think of these types as "type in a range of values" - it is after all the exact same range of values (since it is inclusive at both ends). I can understand the dislike though. I can imagining supporting a Range runtime object (of a new type Range[T]), that can be specified with min/max, and Integer, a direction, and or a step value (negative for reversed stepping). It could be a subtype of Integer if we like. I can also imagine adding direction to the Integer type even if that is only of value for iteration (as that makes it clear what min/max are, and they must be in order). What I think would be the best and most flexible though is to support an Iterable[T] type (and corresponding runtime object), we can then write functions like "in_reverse", step_in_reverse(2) and what not. This is the most flexible solution. There is more to implement for that I think, but not much. We may even want both. They are both good to have. 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
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-5461 puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Change By: Henrik Lindberg Assignee: Thomas Hallgren 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-5650) $::hostname, $::fqdn not available when using puppet master compile
Title: Message Title
Tom De Vylder created an issue
Puppet / PUP-5650
$::hostname, $::fqdn not available when using puppet master compile
Issue Type:
Bug
Affects Versions:
PUP 4.3.1, PUP 3.8.4
Assignee:
Unassigned
Created:
2016/01/05 5:13 AM
Environment:
puppet 3.8.4 puppet 4.3.1
Priority:
Normal
Reporter:
Tom De Vylder
Consider following snippet:
$ cat /etc/puppet/manifests/site.pp
notice("hostname: ${::hostname}")
Jira (PUP-5650) $::hostname, $::fqdn not available when using puppet master compile
Title: Message Title
Tom De Vylder updated an issue
Puppet / PUP-5650
$::hostname, $::fqdn not available when using puppet master compile
Change By:
Tom De Vylder
*Consider following snippet:*{code}$ cat /etc/puppet/manifests/site.ppnotice("hostname: ${::hostname}")notice("fqdn: ${::fqdn}") notice("certname: ${::certname}") $ puppet master \ --hiera_config /etc/puppet/hiera.yaml \ --manifest /etc/puppet/manifests/site.pp \ --modulepath /etc/puppet/modules \ --compile test01 --debug{code}*Output on Puppet 3.8.4:*{code}Info: Caching node for test01Notice: Scope(Class[main]): hostname:Notice: Scope(Class[main]): fqdn:Notice: Scope(Class[main]): certname:{code}*Output on Puppet 4.3.1*{code}Info: Caching node for test01Warning: Scope(Class[main]): Could not look up qualified variable '::hostname';Notice: Scope(Class[main]): hostname:Warning: Scope(Class[main]): Could not look up qualified variable '::fqdn';Notice: Scope(Class[main]): fqdn:Warning: Scope(Class[main]): Could not look up qualified variable '::certname';Notice: Scope(Class[main]): certname:{code}*Question:*According to "puppet help master" it uses facts contained in $vardir/yaml/ to compile the catalog. However custom facts (hostname, fqdn, ...) added to "~/.puppet/var/yaml/node/test01.yaml" are never used by "puppet master compile". Aftwards said file is cleared to default.What's the advised way to provide a number of facts to "puppet master compile"?
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
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Henrik Lindberg commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Ok, good to know. Then it is fine. 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-5462) small improvements to module generator
Title: Message Title Kylo Ginsberg assigned an issue to Anderson Mills Puppet / PUP-5462 small improvements to module generator Change By: Kylo Ginsberg Assignee: Anderson Mills 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-5653) Remove static node config for Cumulus
Title: Message Title Kylo Ginsberg assigned an issue to Steve Barlow Puppet / PUP-5653 Remove static node config for Cumulus Change By: Kylo Ginsberg Assignee: Steve Barlow 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-5653) Remove static node config for Cumulus
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5653 Remove static node config for Cumulus Change By: Kylo Ginsberg 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-5654) Remove static node config for Arista
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5654 Remove static node config for Arista Change By: Kylo Ginsberg 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-5654) Remove static node config for Arista
Title: Message Title Kylo Ginsberg assigned an issue to Steve Barlow Puppet / PUP-5654 Remove static node config for Arista Change By: Kylo Ginsberg Assignee: Steve Barlow 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-5596) Puppet agent freezes
Title: Message Title Kylo Ginsberg commented on PUP-5596 Re: Puppet agent freezes Matt Stith: thanks for following up here on the ultimate cause of the problem. Much appreciated! I like the idea of improving cycle detection - that might be a serious undertaking; I'm not quite sure. If you're able to take your case and boil it down to a simple-ish recipe to reproduce, please file another ticket focussed on that issue with details on how to reproduce. I can't promise an easy or immediate fix, but we'd definitely take a look to think about what it would take. Thanks either way! 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-1293) service status is ignored ( puppet 3.2 + upstart provider )
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1293 service status is ignored ( puppet 3.2 + upstart provider ) Change By: Kylo Ginsberg Fix Version/s: PUP 3.8.5 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-5623) Callable type should be able to describe return type
Title: Message Title Henrik Lindberg commented on PUP-5623 Re: Callable type should be able to describe return type I can see that working, even if min/max is outside of the array, there is nothing stopping them from not being supported when/if "by name" parameter specification is later added - we simply overlay different signatures. Spelling out the names is easier to read for sure. 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-5465) Resource Collectors cannot use resource references in search expressions
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5465 Resource Collectors cannot use resource references in search expressions Change By: Josh Cooper Fix Version/s: PUP 4.4.0 Fix Version/s: PUP 4.3.2 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-5465) Resource Collectors cannot use resource references in search expressions
Title: Message Title Josh Cooper commented on PUP-5465 Re: Resource Collectors cannot use resource references in search expressions Backported to stable in https://github.com/puppetlabs/puppet/commit/0f680387b21758bc5cde7cc670a2a96864b118c9 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-5640) Windows package provider can crash with "Memory access is out of bounds" when registry values are corrupt
Title: Message Title Ryan Gard updated an issue Puppet / PUP-5640 Windows package provider can crash with "Memory access is out of bounds" when registry values are corrupt Change By: Ryan Gard QA Contact: Ryan Gard 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-5640) Windows package provider can crash with "Memory access is out of bounds" when registry values are corrupt
Title: Message Title Ryan Gard updated an issue Puppet / PUP-5640 Windows package provider can crash with "Memory access is out of bounds" when registry values are corrupt Change By: Ryan Gard QA Risk Assessment Reason: Unit test sufficiently covers this bug. Exposure to customer is 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-5465) Resource Collectors cannot use resource references in search expressions
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5465 Resource Collectors cannot use resource references in search expressions Change By: Josh Cooper Affects Version/s: PUP 4.x Affects Version/s: PUP 4.0.0 Story Points: 1 Sprint: Client 2016-01-13 Scrum Team: Client Platform 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
Jira (PUP-5640) Windows package provider can crash with "Memory access is out of bounds" when registry values are corrupt
Title: Message Title Ryan Gard updated an issue Puppet / PUP-5640 Windows package provider can crash with "Memory access is out of bounds" when registry values are corrupt Change By: Ryan Gard 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-5653) Remove static node config for Cumulus
Title: Message Title Stan Duffy assigned an issue to Stan Duffy Puppet / PUP-5653 Remove static node config for Cumulus Change By: Stan Duffy Assignee: Stan Duffy 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-5653) Remove static node config for Cumulus
Title: Message Title Stan Duffy created an issue Puppet / PUP-5653 Remove static node config for Cumulus Issue Type: Task Assignee: Unassigned Created: 2016/01/05 4:31 PM Environment: Puppet Agent CI Pipelines Priority: Normal Reporter: Stan Duffy Now that we have a Cumulus VM in the VMpooler and the beaker-hostgenerator has the ability to define a Cumulus node, we will remove the static node config file for Cumulus Add Comment
Jira (PUP-5640) Windows package provider can crash with "Memory access is out of bounds" when registry values are corrupt
Title: Message Title Ryan Gard updated an issue Puppet / PUP-5640 Windows package provider can crash with "Memory access is out of bounds" when registry values are corrupt Change By: Ryan Gard 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-5654) Remove static node config for Arista
Title: Message Title Stan Duffy created an issue Puppet / PUP-5654 Remove static node config for Arista Issue Type: Task Assignee: Stan Duffy Created: 2016/01/05 4:31 PM Environment: Puppet Agent CI Pipelines Priority: Normal Reporter: Stan Duffy Now that we have a Cumulus VM in the VMpooler and the beaker-hostgenerator has the ability to define a Cumulus node, we will remove the static node config file for Cumulus Add Comment This message was
Jira (PUP-5640) Windows package provider can crash with "Memory access is out of bounds" when registry values are corrupt
Title: Message Title Ryan Gard updated an issue Puppet / PUP-5640 Windows package provider can crash with "Memory access is out of bounds" when registry values are corrupt Change By: Ryan Gard 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-5654) Remove static node config for Arista
Title: Message Title Stan Duffy updated an issue Puppet / PUP-5654 Remove static node config for Arista Change By: Stan Duffy Now that we have a Cumulus Arista VM in the VMpooler and the beaker-hostgenerator has the ability to define a Cumulus Arista node, we will remove the static node config file for Cumulus Arista 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-5593) Update Cumulus Node config to use VM from VMpooler
Title: Message Title Stan Duffy commented on PUP-5593 Re: Update Cumulus Node config to use VM from VMpooler Going to close this ticket, as we will be using beaker-hostgen going forward. 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-5571) Missing API docs for /puppet/v3/environment endpoint
Title: Message Title Kylo Ginsberg commented on PUP-5571 Re: Missing API docs for /puppet/v3/environment endpoint I merged while doing some spring cleaning. I moved this over to Ready for Review for any team-specific last rites. 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-5462) small improvements to module generator
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5462 small improvements to module generator Change By: Kylo Ginsberg Scrum Team: Code Management 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-5545) Use rubocop in module generator
Title: Message Title Kylo Ginsberg assigned an issue to Anderson Mills Puppet / PUP-5545 Use rubocop in module generator Change By: Kylo Ginsberg Assignee: Anderson Mills 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-5545) Use rubocop in module generator
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5545 Use rubocop in module generator Change By: Kylo Ginsberg Scrum Team: Code Management 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-5462) small improvements to module generator
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5462 small improvements to module generator Change By: Kylo Ginsberg Component/s: PMT 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-5545) Use rubocop in module generator
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5545 Use rubocop in module generator Change By: Kylo Ginsberg Component/s: PMT 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-2287) Add styling to small ERD diagram
Title: Message Title Verne Lindner created an issue PuppetDB / PDB-2287 Add styling to small ERD diagram Issue Type: Task Assignee: Jason Gurley Created: 2016/01/05 3:01 PM Priority: Normal Reporter: Verne Lindner Wireframe (pw: reductive!) To reside on this page Please provide visual styling for the diagram referenced above. Deliverable should be a PNG, sized to fit the page reference above. Once complete, please ping Verne and Michelle Fredette: Michelle will help us place and test the image on the live page. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PDB-2288) Use the historical-catalogs endpoint in export
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2288 Use the historical-catalogs endpoint in export Issue Type: Task Assignee: Unassigned Created: 2016/01/05 3:30 PM Fix Versions: PDB 4.0.0 Priority: Normal Reporter: Andrew Roetker Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message
Jira (FACT-718) Allow for disabling certain facts within Facter
Title: Message Title Charlie Sharpsteen updated an issue Facter / FACT-718 Allow for disabling certain facts within Facter Change By: Charlie Sharpsteen CS Priority: Needs Priority Reviewed CS Impact: In Facter 2.x, core facts could be disabled globally by removing the relevant .rb files. However, with Facter 3.x, this is no longer possible. Additionally, there are facts, such as network drives, which may be expensive to run on certain systems. The ability to conditionally disable core and custom facts would provide a workaround to both problems. 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-5651) A puppet function declaration must be a top level construct
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5651 A puppet function declaration must be a top level construct There is already constraints checking available for other top level constructs and it should be relatively easy to include puppet function definitions in the same checking. Maybe it is already reusing the same checks that are there (which allows classes and user defined types to be nested). If so, support for the special case is needed. (Still simple to do). Later, we want to be able to define functions inside data type definitions - but we can relax the validation then. Change By: Henrik Lindberg Story Points: 1 Sprint: Language Triage Release Notes: Not Needed Fix Version/s: PUP 4.3.2 Add Comment This message was sent by Atlassian JIRA
Jira (PDB-2289) Use historical-catalogs endpoint in sync
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2289 Use historical-catalogs endpoint in sync Issue Type: Task Assignee: Unassigned Created: 2016/01/05 3:31 PM Fix Versions: PDB 4.0.0 Priority: Normal Reporter: Andrew Roetker Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because
Jira (PDB-2290) Align edges and resources jsonb storage with the `catalogs` endpoint view
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2290 Align edges and resources jsonb storage with the `catalogs` endpoint view Issue Type: Improvement Assignee: Unassigned Created: 2016/01/05 3:34 PM Fix Versions: PDB 4.0.0 Priority: Normal Reporter: Andrew Roetker Currently we have to do some munging to transform edges and resources (jsonb columns) to the format used in the catalogs view, we should just store them the way they're going to be viewed to avoid the munging in our endpoints and sync. Add Comment
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Henrik Lindberg commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output From a user perspective, I don't think it is confusing and technically loading and evaluating functions for a data provider is not compilation per se (it is loading, parsing, validation, evaluation). This, since "compilation" means "to compile a catalog" in puppet terminology. And from a user perspective; a catalog with a class noop (or some other empty construct we may even manage with completely empty input), is essentially the same as not compiling a catalog. It only happens that we technically choose to implement it as a compilation. 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-5209) call_function and metadata.json: call a function from a different module, very strange behavior
Title: Message Title Henrik Lindberg commented on PUP-5209 Re: call_function and metadata.json: call a function from a different module, very strange behavior Moved back to "doing" as there are more tests needed for functions defined and loaded outside of the loaders (e.g. a function defined in a module's init.pp). 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-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Thomas Hallgren commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output The submitted PR adds the --compile option. As long as it stays there and we don't also add a --no-compile then I think it's clear enough. 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-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Henrik Lindberg commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output I think binary flag arguments automatically gets the no option. I don't care if it is available or not; we do not want to add it explicitly, but it does no harm if we get it automatically. 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-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Thomas Hallgren commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output The no option is only added for binary settings. It's not added for options for a specific application. For instance, there's no --no-debug or --no-verbose. 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-5648) Descending range semantics are broken in the compiler
Title: Message Title Thomas Hallgren commented on PUP-5648 Re: Descending range semantics are broken in the compiler I'm against having direction as the property of a type. A type describes a constraint and it's purpose is to validate instances of a type. I would be in favor of instead adding a check that asserts that min <= max at all times. This would also resolve the second issue regarding types that doesn't support "descending" semantic (and other weirdness). Iterating backwards can be resolved in other ways. It's hardly a motivation for allowing "descending" semantic in this context. 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.
