Jira (PDB-2446) (maint) Simplify core.async/AMQ use in benchmark
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2446 (maint) Simplify core.async/AMQ use in benchmark Issue Type: Bug Assignee: Unassigned Created: 2016/02/18 5:15 PM Priority: Normal Reporter: gepetto-bot Wrap the temp AMQ instance in a custom core.async Buffer, allowing us to use a single channel with the custom buffer instead of two separate channels. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PDB-2446) (maint) Simplify core.async/AMQ use in benchmark
Title: Message Title gepetto-bot updated an issue PuppetDB / PDB-2446 (maint) Simplify core.async/AMQ use in benchmark Change By: gepetto-bot Sprint: PuppetDB 2016-02-24 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-5872) Static catalog acceptance: Correlate all agent run reports to a catalog, Story PUP-5533
Title: Message Title Erik Dasher commented on PUP-5872 Re: Static catalog acceptance: Correlate all agent run reports to a catalog, Story PUP-5533 Josh Cooper Why not both? I understand you want to check the agent side close to the ruby code. This makes sense. I want an end to end test. I've set this ticket back to the way I found it. I'm going to make a PE acceptance test ticket and link it to PUP-5533 (the story) and get to work. 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-5872) Static catalog acceptance: Correlate all agent run reports to a catalog, Story PUP-5533
Title: Message Title Erik Dasher assigned an issue to Unassigned Puppet / PUP-5872 Static catalog acceptance: Correlate all agent run reports to a catalog, Story PUP-5533 Change By: Erik Dasher Assignee: Erik Dasher 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-5533) (Static Catalog) As a puppet administrator, I should be able to correlate all agent run reports to a catalog.
Title: Message Title Erik Dasher commented on PUP-5533 Re: (Static Catalog) As a puppet administrator, I should be able to correlate all agent run reports to a catalog. Test outline performed in PE: create or install a hello_world module in production. FileSync Commit puppet agent -t Record returned "configuration_version" query PDB reports for that configuration_version: curl -s -G http://localhost:8080/pdb/query/v4/reports --data-urlencode 'query=["=", "configuration_version", "1455842614"]' | python -m json.tool | less -N (note the above query ought to be expanded to include a certname) The report will provide a transaction_uuid -query puppetdb for the catalog curl -s -G http://localhost:8080/pdb/query/v4/catalogs --data-urlencode 'query=["=", "transaction_uuid", "bd2176ef-34fa-4daa-b5fa-1084c3a07c5d"]' | python -m json.tool | less 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-5925) Optional data type and data binding with undef as default value
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5925 Optional data type and data binding with undef as default value Thomas Hallgren, I thought this should work. Any reason why it should not be allowed? - i.e. define data binding of undef Change By: Henrik Lindberg Scrum Team: Language 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-5925) Optional data type and data binding with undef as default value
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-5925 Optional data type and data binding with undef as default value 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-5925) Optional data type and data binding with undef as default value
Title: Message Title
Francois Lafont created an issue
Puppet / PUP-5925
Optional data type and data binding with undef as default value
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
test.zip
Created:
2016/02/18 4:58 PM
Environment:
Ubuntu Trusty with puppet-agent 1.3.5
Priority:
Normal
Reporter:
Francois Lafont
Hi,
All the files are in .zip attached file. I have a (very basic) module with the function data.pp as data provider and the default value of a parameter is undef:
function test::data {
{
Jira (PUP-5121) Add profiling for file inlining
Title: Message Title Kevin Corcoran commented on PUP-5121 Re: Add profiling for file inlining Josh Cooper - A couple additions to Chris Price's list above, based on a discussion we just had: It'd be nice to have a metric for the reason why file metadata wasn't inlined for a resource (i.e. which of the corner cases it falls into that prevent inlining from happening. Another idea we had was to aggregate/group these metrics per-environment. (i.e. # of static catalogs per-environment). 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-4818) PUP-121 (relative namespacing) was never fully resolved in 3.x future parser
Title: Message Title
John Duarte commented on PUP-4818
Re: PUP-121 (relative namespacing) was never fully resolved in 3.x future parser
Validated on puppet#3.8.x at SHA fc18dd19e9dbf313cae24591236c539e248cd3f2 using --parser=future and the manifests shown in the description of this ticket.
root@ip4oq3bswniurrv:~# puppet --version
3.8.6
root@ip4oq3bswniurrv:~# cat thing.pp
class foo::thing {
notify {"from foo::thing":}
}
class thing {
notify {"from ::thing":}
Jira (PUP-5735) Remove usage of win32-security gem
Title: Message Title Ethan Brown assigned an issue to Glenn Sarti Puppet / PUP-5735 Remove usage of win32-security gem Change By: Ethan Brown Assignee: Ethan Brown Glenn Sarti 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-4818) PUP-121 (relative namespacing) was never fully resolved in 3.x future parser
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-4818 PUP-121 (relative namespacing) was never fully resolved in 3.x future parser 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 (PUP-5701) Compare files using checksum_value
Title: Message Title Michael Smith updated an issue Puppet / PUP-5701 Compare files using checksum_value Change By: Michael Smith Release Notes Summary: Covered by PUP-5695. 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-5701) Compare files using checksum_value
Title: Message Title Michael Smith commented on PUP-5701 Re: Compare files using checksum_value I think the release notes for PUP-5695 cover 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 (PUP-5479) segfault with augeas type when changes attribute is too long
Title: Message Title Michael Stahnke commented on PUP-5479 Re: segfault with augeas type when changes attribute is too long If the desire is not to have augeas segfault with an invalid path, I would think we'd close this and open an issue upstream. If the issue is with the education stuff Krb5, that should be fixed. I'm unclear on what would be puppet-agent related. 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-5701) Compare files using checksum_value
Title: Message Title John Duarte updated an issue Puppet / PUP-5701 Compare files using checksum_value Change By: John Duarte QA Risk Assessment: Medium 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-5872) Static catalog acceptance: Correlate all agent run reports to a catalog, Story PUP-5533
Title: Message Title Erik Dasher commented on PUP-5872 Re: Static catalog acceptance: Correlate all agent run reports to a catalog, Story PUP-5533 Josh Cooper On the other hand, the catalog_uuids and code_id must be passed into PDB via the server, and then pulled back out via a report right? 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-5872) Static catalog acceptance: Correlate all agent run reports to a catalog, Story PUP-5533
Title: Message Title Erik Dasher assigned an issue to Erik Dasher Puppet / PUP-5872 Static catalog acceptance: Correlate all agent run reports to a catalog, Story PUP-5533 Change By: Erik Dasher Assignee: Erik Dasher 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-5533) (Static Catalog) As a puppet administrator, I should be able to correlate all agent run reports to a catalog.
Title: Message Title Erik Dasher commented on PUP-5533 Re: (Static Catalog) As a puppet administrator, I should be able to correlate all agent run reports to a catalog. PDB-2126 is marked Completed. Time to get busy with this story / 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-5769) Windows MSI overriding puppet.conf values with defaults
Title: Message Title Rob Reynolds commented on PUP-5769 Re: Windows MSI overriding puppet.conf values with defaults So you can set a value in an inifile, you can update a value in an inifile, but you want to KNOW the value for some reason? Well then you need a custom action. Oh by the way, don't use custom actions, you shouldn't need them and they are an anti-pattern. http://wixtoolset.org/documentation/manual/v3/xsd/wix/inifilesearch.html can be used, but you have to make a copy of the ini file in the Windows system folders first. 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-4450) Cannot load 'provider/network_route/routes.rb'
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet / PUP-4450 Cannot load 'provider/network_route/routes.rb' Change By: Michael Smith Assignee: 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-5118) Handle duplicate resources when inlining file metadata
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-5118 Handle duplicate resources when inlining file metadata Change By: William Hopper Status: Ready for CI Test Assignee: 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-5479) segfault with augeas type when changes attribute is too long
Title: Message Title Geoff Williams commented on PUP-5479 Re: segfault with augeas type when changes attribute is too long David Lutterkort Classroom VMs are downlable at http://downloads.puppetlabs.com/training/ I was able to reproduce the issue with a plain cento6 VM and the attached testcase when I first spotted this which was a while ago. I would imagine that if your now unable to reproduce the issue with the testcase then its probably fixed. 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-5899) Empty hiera data in modules causes whole lookup to fail
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-5899 Empty hiera data in modules causes whole lookup to fail Change By: William Hopper Status: Ready for CI Test Assignee: 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-4818) PUP-121 (relative namespacing) was never fully resolved in 3.x future parser
Title: Message Title Henrik Lindberg assigned an issue to qa Puppet / PUP-4818 PUP-121 (relative namespacing) was never fully resolved in 3.x future parser Change By: Henrik Lindberg Status: Ready for CI Test Assignee: 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-5892) Alias types are presented with the wrong name in type mismatches
Title: Message Title Henrik Lindberg assigned an issue to qa Puppet / PUP-5892 Alias types are presented with the wrong name in type mismatches Change By: Henrik Lindberg Status: Ready for CI Test Assignee: 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-5845) Add the function type()
Title: Message Title Henrik Lindberg assigned an issue to qa Puppet / PUP-5845 Add the function type() Change By: Henrik Lindberg Status: Ready for CI Test Assignee: 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-5761) when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing
Title: Message Title Henrik Lindberg assigned an issue to qa Puppet / PUP-5761 when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing Change By: Henrik Lindberg Status: Ready for CI Test Assignee: 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-5895) puppet parser validate fails for functions
Title: Message Title Henrik Lindberg assigned an issue to qa Puppet / PUP-5895 puppet parser validate fails for functions Change By: Henrik Lindberg Status: Ready for CI Test Assignee: 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-5526) (Static Catalog) As a puppet administrator, I want the catalog that I apply to produce the same results regardless of the updates that happen to out-of-band file content.
Title: Message Title Erik Dasher assigned an issue to Erik Dasher Puppet / PUP-5526 (Static Catalog) As a puppet administrator, I want the catalog that I apply to produce the same results regardless of the updates that happen to out-of-band file content. Change By: Erik Dasher Assignee: Erik Dasher 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-5526) (Static Catalog) As a puppet administrator, I want the catalog that I apply to produce the same results regardless of the updates that happen to out-of-band file content.
Title: Message Title Erik Dasher updated an issue Puppet / PUP-5526 (Static Catalog) As a puppet administrator, I want the catalog that I apply to produce the same results regardless of the updates that happen to out-of-band file content. Change By: Erik Dasher Sub-team: Jade Story Points: 1 Sprint: Server Jade 2016-02-24 Scrum Team: Puppet Server 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
Jira (PUP-5769) Windows MSI overriding puppet.conf values with defaults
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-5769 Windows MSI overriding puppet.conf values with defaults Change By: Rob Reynolds Summary: Windows MSI overriding server with default value of " puppet " .conf values with defaults 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-5769) Windows MSI overriding server with default value of "puppet"
Title: Message Title Rob Reynolds commented on PUP-5769 Re: Windows MSI overriding server with default value of "puppet" This affects every one of these values: server archive_file_server environment certname ca_server 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-5769) Windows MSI overriding server with default value of "puppet"
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-5769 Windows MSI overriding server with default value of "puppet" Change By: Rob Reynolds Affects Version/s: PUP 4.3.2 Affects Version/s: PUP 3.7.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-5769) Windows MSI overriding server with default value of "puppet"
Title: Message Title Rob Reynolds commented on PUP-5769 Re: Windows MSI overriding server with default value of "puppet" I fully agree with Ethan Brown's thoughts channelling Josh: I think it works mostly as advertised, except it is not respecting the value already specified in the conf file like it should. It does it due to this section: https://github.com/puppetlabs/puppet_for_the_win/blob/1b2da81cc8f562d44b9607b30c78c5a03a4cea72/wix/puppet.wxs#L323-L349. The documentation for IniFile talks of the differences in the actions addLine/createLine - http://wixtoolset.org/documentation/manual/v3/xsd/wix/inifile.html This change was made for 3.7.0 (it was supposed to target 3.4.0, not sure if it did or not based on github right now at https://github.com/puppetlabs/puppet_for_the_win/commit/167999a13afd622b0bc823650efbe303106b5ad0) to support another issue related to being able to override those value with values passed in - http://projects.puppetlabs.com/issues/20281. The relevant details from Josh Cooper - When you next install (or during an upgrade) the GUI gives you the option to re-enter the puppet master, but any value you enter is ignored, which is very surprising. I would expect that the GUI display the value that is currently in puppet.conf, or default to puppet as it does now. And if I specify a value in the GUI, it should overwrite the value in puppet.conf. And same if the property is specified on the command line. 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
Jira (PUP-5769) Windows MSI overriding server with default value of "puppet"
Title: Message Title Rob Reynolds commented on PUP-5769 Re: Windows MSI overriding server with default value of "puppet" We may want to backport this into the 3.x series if it is critical enough of an issue. Although most folks upgrading are moving to 4.x something anyways. 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-5769) Windows MSI overriding server with default value of "puppet"
Title: Message Title Rob Reynolds commented on PUP-5769 Re: Windows MSI overriding server with default value of "puppet" I can confirm it's not just the value for server. ANY value is overwritten. I just made the same changes for environment and server and it overwrote BOTH of 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-5769) Windows MSI overriding server with default value of "puppet"
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-5769 Windows MSI overriding server with default value of "puppet" Change By: Rob Reynolds Priority: Normal Major 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-5701) Compare files using checksum_value
Title: Message Title Michael Smith commented on PUP-5701 Re: Compare files using checksum_value I think the only place you'd see it is using the --http_debug flag, and seeing a lack of metadata requests. You'd want to confirm that updating a file still occurs when the file on-disk doesn't match. I'm not sure this needs much FR other than that file resources are still applied correctly. It will be important as a larger piece of static catalogs, but that can be handled with system testing of that 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-5769) Windows MSI overriding server with default value of "puppet"
Title: Message Title Rob Reynolds commented on PUP-5769 Re: Windows MSI overriding server with default value of "puppet" Behavior confirmed. I'll be looking at what causes 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 (PDB-2445) (maint) Fix summary cache NPE on command failure
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2445 (maint) Fix summary cache NPE on command failure Change By: Russell Mull Scope Change Category: Found Scope Change Reason: Found in the logs of a related test failure 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-5701) Compare files using checksum_value
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-5701 Compare files using checksum_value 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 (PUP-5924) The default hiera.yaml file does not include the '::' prefix for the environment variable
Title: Message Title
Jo Rhett updated an issue
Puppet / PUP-5924
The default hiera.yaml file does not include the '::' prefix for the environment variable
Change By:
Jo Rhett
Comment:
I'm not following what you are saying, Rob. Both of those examples have a key ("datadir") which is a valid Ruby symbol (check) prefixed with a colon.I believe you are looking at the hash value, and interpolation within the hash value. Which might indeed have a bug, but that's not relevant to the referenced documentation.I am curious how you get different values for $environment and $::environment. That may not be a bug but certainly is confusing. Can you provide details of your environment? Does the client submit a different environment than the environment data provider or a node terminus / ENC?
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-5923) Administration token detection doesn't work in legacy Windows OS (2003/XP)
Title: Message Title Rob Reynolds commented on PUP-5923 Re: Administration token detection doesn't work in legacy Windows OS (2003/XP) Merged into master at https://github.com/puppetlabs/puppet/commit/6883defef58c56c567613848764525142b2c9c6d 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-1290) Does not check if '-U' is valid for dhcpcd, fails to report dhcp servers
Title: Message Title
Michael Smith updated an issue
Facter / FACT-1290
Does not check if '-U' is valid for dhcpcd, fails to report dhcp servers
Change By:
Michael Smith
When determining network facts, facter calls /sbin/dhcpcd -U for each interface on the machine. However the SuSE version of dhcpcd does not support that option. This causes the {{dhcp_servers}} and individual interface's {{dhcp}} facts to be unresolved. ie:{code}# /opt/puppetlabs/bin/facter --debug network2015-12-25 11:48:03.993167 INFO puppetlabs.facter - executed with command line: --debug network.2015-12-25 11:48:03.994678 INFO leatherman.ruby:124 - ruby loaded from "/opt/puppetlabs/puppet/lib/libruby.so.2.1.0".2015-12-25 11:48:04.004364 INFO leatherman.ruby:145 - using ruby version 2.1.62015-12-25 11:48:04.062908 INFO puppetlabs.facter - requested queries: network.2015-12-25 11:48:04.063178 DEBUG puppetlabs.facter - fact "facterversion" has resolved to "3.1.0".2015-12-25 11:48:04.064183 DEBUG puppetlabs.facter - searching "/opt/puppetlabs/facter/facts.d" for external facts.2015-12-25 11:48:04.064468 DEBUG puppetlabs.facter - skipping external facts for "/etc/facter/facts.d": No such file or directory2015-12-25 11:48:04.064694 DEBUG puppetlabs.facter - skipping external facts for "/etc/puppetlabs/facter/facts.d": No such file or directory2015-12-25 11:48:04.064878 DEBUG puppetlabs.facter - no external facts were found.2015-12-25 11:48:04.066249 DEBUG puppetlabs.facter - loading all custom facts.2015-12-25 11:48:04.066498 DEBUG puppetlabs.facter - resolving networking facts.2015-12-25 11:48:04.069586 DEBUG puppetlabs.facter - searching "/var/lib/dhclient" for dhclient lease files.2015-12-25 11:48:04.069834 DEBUG puppetlabs.facter - searching "/var/lib/dhcp" for dhclient lease files.2015-12-25 11:48:04.070082 DEBUG puppetlabs.facter - searching "/var/lib/dhcp3" for dhclient lease files.2015-12-25 11:48:04.070352 DEBUG puppetlabs.facter - searching "/var/lib/NetworkManager" for dhclient lease files.2015-12-25 11:48:04.070575 DEBUG puppetlabs.facter - searching "/var/db" for dhclient lease files.2015-12-25 11:48:04.071038 DEBUG leatherman.execution:87 - executing command: /sbin/dhcpcd -U eth02015-12-25 11:48:04.073172 DEBUG !!! - dhcpcd: invalid option -- 'U'2015-12-25 11:48:04.073477 DEBUG | - usage: dhcpcd [-adknpEGHKMNRSTYD] [-c script] [-h hostname] [-i classID]2015-12-25 11:48:04.073666 DEBUG | - [-l leasetime] [-m metric] [-r ipaddress] [-s ipaddress]2015-12-25 11:48:04.073854 DEBUG | - [-t timeout] [-u userclass] [-F none | ptr | both]2015-12-25 11:48:04.074034 DEBUG | - [-I clientID] [ --netconfig ] 2015-12-25 11:48:04.074306 DEBUG leatherman.execution:521 - process exited with status code 1.2015-12-25 11:48:04.074697 DEBUG leatherman.execution:87 - executing command: /sbin/dhcpcd -U eth12015-12-25 11:48:04.076676 DEBUG !!! - dhcpcd: invalid option -- 'U'2015-12-25 11:48:04.077022 DEBUG | - usage: dhcpcd [-adknpEGHKMNRSTYD] [-c script] [-h hostname] [-i classID]2015-12-25 11:48:04.077295 DEBUG | - [-l leasetime] [-m metric] [-r ipaddress] [-s ipaddress]2015-12-25 11:48:04.077557 DEBUG | - [-t timeout] [-u userclass] [-F none | ptr | both]2015-12-25 11:48:04.077811 DEBUG | - [-I clientID] [ --netconfig ] 2015-12-25 11:48:04.078144 DEBUG leatherman.execution:521 - process
Jira (FACT-1290) Does not check if '-U' is valid for dhcpcd, fails to report dhcp servers
Title: Message Title Michael Smith updated an issue Facter / FACT-1290 Does not check if '-U' is valid for dhcpcd, fails to report dhcp servers Change By: Michael Smith Summary: Does not check if '-U' is valid for dhcpcd , fails to report dhcp servers 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-5876) Enable static catalogs by default
Title: Message Title
William Hopper commented on PUP-5876
Re: Enable static catalogs by default
TL;DR FR: looks good! When a code-id-command script is provided, the server correctly inlines file metadata by default.
Verified (using puppet-agent build 9d6ed6fb9ff96306d4737c9f148d48a4e362fbcf) that the static_catalogs setting defaults to true:
[root@yrsprbv3x8dxzvg ~]# puppet config print static_catalogs
true
All tests below use the following manifests / files:
Manifest:
cat site.pp
node default {
file { '/tmp/test':
ensure => file,
source => 'puppet:///modules/foo/test.txt',
Jira (FACT-1290) Does not check if '-U' is valid for dhcpcd
Title: Message Title
Michael Smith updated an issue
Facter / FACT-1290
Does not check if '-U' is valid for dhcpcd
Change By:
Michael Smith
When determining network facts, facter calls /sbin/dhcpcd -U for each interface on the machine. However the SuSE version of dhcpcd does not support that option.ie: {code} # /opt/puppetlabs/bin/facter --debug network2015-12-25 11:48:03.993167 INFO puppetlabs.facter - executed with command line: --debug network.2015-12-25 11:48:03.994678 INFO leatherman.ruby:124 - ruby loaded from "/opt/puppetlabs/puppet/lib/libruby.so.2.1.0".2015-12-25 11:48:04.004364 INFO leatherman.ruby:145 - using ruby version 2.1.62015-12-25 11:48:04.062908 INFO puppetlabs.facter - requested queries: network.2015-12-25 11:48:04.063178 DEBUG puppetlabs.facter - fact "facterversion" has resolved to "3.1.0".2015-12-25 11:48:04.064183 DEBUG puppetlabs.facter - searching "/opt/puppetlabs/facter/facts.d" for external facts.2015-12-25 11:48:04.064468 DEBUG puppetlabs.facter - skipping external facts for "/etc/facter/facts.d": No such file or directory2015-12-25 11:48:04.064694 DEBUG puppetlabs.facter - skipping external facts for "/etc/puppetlabs/facter/facts.d": No such file or directory2015-12-25 11:48:04.064878 DEBUG puppetlabs.facter - no external facts were found.2015-12-25 11:48:04.066249 DEBUG puppetlabs.facter - loading all custom facts.2015-12-25 11:48:04.066498 DEBUG puppetlabs.facter - resolving networking facts.2015-12-25 11:48:04.069586 DEBUG puppetlabs.facter - searching "/var/lib/dhclient" for dhclient lease files.2015-12-25 11:48:04.069834 DEBUG puppetlabs.facter - searching "/var/lib/dhcp" for dhclient lease files.2015-12-25 11:48:04.070082 DEBUG puppetlabs.facter - searching "/var/lib/dhcp3" for dhclient lease files.2015-12-25 11:48:04.070352 DEBUG puppetlabs.facter - searching "/var/lib/NetworkManager" for dhclient lease files.2015-12-25 11:48:04.070575 DEBUG puppetlabs.facter - searching "/var/db" for dhclient lease files.2015-12-25 11:48:04.071038 DEBUG leatherman.execution:87 - executing command: /sbin/dhcpcd -U eth02015-12-25 11:48:04.073172 DEBUG !!! - dhcpcd: invalid option -- 'U'2015-12-25 11:48:04.073477 DEBUG | - usage: dhcpcd [-adknpEGHKMNRSTYD] [-c script] [-h hostname] [-i classID]2015-12-25 11:48:04.073666 DEBUG | - [-l leasetime] [-m metric] [-r ipaddress] [-s ipaddress]2015-12-25 11:48:04.073854 DEBUG | - [-t timeout] [-u userclass] [-F none | ptr | both]2015-12-25 11:48:04.074034 DEBUG | - [-I clientID] [ --netconfig ] 2015-12-25 11:48:04.074306 DEBUG leatherman.execution:521 - process exited with status code 1.2015-12-25 11:48:04.074697 DEBUG leatherman.execution:87 - executing command: /sbin/dhcpcd -U eth12015-12-25 11:48:04.076676 DEBUG !!! - dhcpcd: invalid option -- 'U'2015-12-25 11:48:04.077022 DEBUG | - usage: dhcpcd [-adknpEGHKMNRSTYD] [-c script] [-h hostname] [-i classID]2015-12-25 11:48:04.077295 DEBUG | - [-l leasetime] [-m metric] [-r ipaddress] [-s ipaddress]2015-12-25 11:48:04.077557 DEBUG | - [-t timeout] [-u userclass] [-F none | ptr | both]2015-12-25 11:48:04.077811 DEBUG | - [-I clientID] [ --netconfig ] 2015-12-25 11:48:04.078144 DEBUG leatherman.execution:521 - process exited with status code 1.2015-12-25 11:48:04.078558 DEBUG leatherman.execution:87 - executing command: /sbin/dhcpcd -U
Jira (PUP-5924) The default hiera.yaml file does not include the '::' prefix for the environment variable
Title: Message Title Henrik Lindberg moved an issue Puppet / PUP-5924 The default hiera.yaml file does not include the '::' prefix for the environment variable Change By: Henrik Lindberg Scrum Team: Language Component/s: Puppet Client/Agent Component/s: Website & IA Workflow: Documentation Scrum Team Workflow Key: DOCUMENT PUP - 491 5924 Project: Documentation Puppet Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5922) Create recursive directory feature flag
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5922 Create recursive directory feature flag Change By: Josh Cooper Fix Version/s: PUP 4.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-4450) Cannot load 'provider/network_route/routes.rb'
Title: Message Title
Henrik Lindberg commented on PUP-4450
Re: Cannot load 'provider/network_route/routes.rb'
We can use the 4.x loaders to load helper code - even in such a way that it is loaded anonymously. But we cannot transitively load code it in turn depends on - gems etc. That would be considered part of the runtime.
It would be a bit special though, but would enable loading multiple versions of the helper code. We could define this as (winging it from the top of my mind):
# require/load it
puppet_require 'module_realtive/path/to_my_helper'
# instead of using PuppetX::MyName::MyModule - a reference to the class is done indirectly
my_helper = Puppet.get_helper('MyModule::MyHelper')
x = my_helper.new
x.hello("auto loaded helper class")
Instead of making the helper a regular ruby class it is written like the functions are:
Puppet.create_helper_class('MyModule::MyHelper')
Jira (PUP-5916) Arista transient test failure on puppet_mcollective_service_management.rb
Title: Message Title Kylo Ginsberg commented on PUP-5916 Re: Arista transient test failure on puppet_mcollective_service_management.rb Ping Michael Stahnke or Stan Duffy, I don't know who might have insight into this. It's happened twice recently so somehow there's a (new?) race condition or something in the mcollective service on arista4-32. 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-5703) Handle cached catalog and pluginsync inconsistencies
Title: Message Title
John Duarte updated an issue
Puppet / PUP-5703
Handle cached catalog and pluginsync inconsistencies
Change By:
John Duarte
Release Notes Summary:
* By default, the value of {{pluginsync}} will be coerced to be compatible with value of {{use_cached_catalog}}.* If {{pluginsync}} is explicitly set via command-line or {{puppet.conf}}, then that setting will be honored even when it may result in an inconsistent state between the catalog and the plugins that support 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 (PUP-5916) Arista transient test failure on puppet_mcollective_service_management.rb
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5916 Arista transient test failure on puppet_mcollective_service_management.rb Change By: Kylo Ginsberg Scrum Team: Client Platform Release Engineering 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-5703) Handle cached catalog and pluginsync inconsistencies
Title: Message Title John Duarte updated an issue Puppet / PUP-5703 Handle cached catalog and pluginsync inconsistencies 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-5703) Handle cached catalog and pluginsync inconsistencies
Title: Message Title John Duarte commented on PUP-5703 Re: Handle cached catalog and pluginsync inconsistencies Using puppet-agent at SHA b08cfa0 containing puppet at SHA 717e9bd all expectations for pluginsync pass. Expectations Default value of pluginsync should be coerced to be compatible with value of use_cached_catalog If pluginsync is explicitly set via command-line or puppet.conf, then that setting will be honored. Default pluginsync Given no cached catalog rm /opt/puppetlabs/puppet/cache/client_data/catalog/* puppet agent -t --use_cached_catalog expect pluginsync expect no cached catalog Given a cached catalog puppet agent -t --use_cached_catalog expect no pluginsync expect cached catalog
Jira (PUP-5923) Administration token detection doesn't work in legacy Windows OS (2003/XP)
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-5923 Administration token detection doesn't work in legacy Windows OS (2003/XP) Change By: Glenn Sarti Sprint: Client Windows 2016-02-24 (Burn FF) 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-5923) Administration token detection doesn't work in legacy Windows OS (2003/XP)
Title: Message Title Glenn Sarti assigned an issue to Rob Reynolds Puppet / PUP-5923 Administration token detection doesn't work in legacy Windows OS (2003/XP) Change By: Glenn Sarti Assignee: Rob Reynolds 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-5735) Remove usage of win32-security gem
Title: Message Title Glenn Sarti assigned an issue to Ethan Brown Puppet / PUP-5735 Remove usage of win32-security gem Change By: Glenn Sarti Assignee: Ethan Brown 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-5864) Static catalog acceptance: Server should only allow access to /environments/*/modules/*/files/*, Story PUP-5534
Title: Message Title Kevin Corcoran commented on PUP-5864 Re: Static catalog acceptance: Server should only allow access to /environments/*/modules/*/files/*, Story PUP-5534 Agree that this should be in Puppet Server. However, SERVER-1143 is simply about setting up the default tk-auth rule for /static_file_content. The actually restriction referred to in the title of this ticket was implemented in SERVER-882. 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-5923) Administration token detection doesn't work in legacy Windows OS (2003/XP)
Title: Message Title Glenn Sarti assigned an issue to Glenn Sarti Puppet / PUP-5923 Administration token detection doesn't work in legacy Windows OS (2003/XP) Change By: Glenn Sarti Assignee: Glenn Sarti 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-5923) Administration token detection doesn't work in legacy Windows OS (2003/XP)
Title: Message Title Glenn Sarti created an issue Puppet / PUP-5923 Administration token detection doesn't work in legacy Windows OS (2003/XP) Issue Type: Bug Assignee: Unassigned Created: 2016/02/18 10:40 AM Fix Versions: PUP 4.4.0 Labels: windows Priority: Normal Reporter: Glenn Sarti As part of PUP-5735 it was found that the administrative token detection for legacy operating systems always evaluated as true. This was due to a simple typo at https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/windows/user.rb#L46 The helper function returns a bool type however the check is against an integer. Therefore is_admin is always returns because bool <> int32 is always true. Changing the line to is_admin = ismember_pointer.read_win32_bool
Jira (PUP-5923) Administration token detection doesn't work in legacy Windows OS (2003/XP)
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-5923 Administration token detection doesn't work in legacy Windows OS (2003/XP) Change By: Glenn Sarti Scope Change Category: Found Scope Change Reason: Bug found as part of PUP5735 and is a simple 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-5844) Add the Object type to the Puppet Type system
Title: Message Title Henrik Lindberg commented on PUP-5844 Re: Add the Object type to the Puppet Type system I think I went too much meta - it is enough that this is special: type Runtime[...] = T We don't need to be able to define new implementations of Type[Type]] in Puppet . e.g. this is not needed: type Type[Runtime[...]] = T That is simply too much meta programming as it would introduce a new way of handling a type - we can leave that to the implementation side. 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
Jira (PUP-5844) Add the Object type to the Puppet Type system
Title: Message Title Henrik Lindberg commented on PUP-5844 Re: Add the Object type to the Puppet Type system I made a map to illustrate how instance - type - and meta type levels fit together and how that is combined with implementation type. https://drive.mindmup.com/map/0ByU-vDA-zPu2NUJabU4wODF5Y2c That mind map illustrates an Integer, a Locator, and an ArithmeticExpression in the AST. At each node we clearly have two distinct cases; the "type isA" (what it is in the puppet type system), and "impl isA" (what it is in Ruby). In many cases the type system has a static binding (e.g. the value 42 is a Ruby FixNum, its type is Integer, which is implemented by PIntegerType, and its type is Type[Integer] implemented by PType). What is needed is the mechanism to define these dynamically using puppet. The diagram only illustrates the relationships . not how they are expressed in Puppet syntax. It is also important that we differentiate between an object and its attributes vs what a runtime instance may contain. As an example, a Hash does not have its values as an attribute - the attributes are something like elements => Array[Tuple[K, V]], and derived attributes "size", "keys", "values". The fact that it is a Struct i.e. contains something that can be accessed via key is something else. Our type alias construct binds Type to Name. We can use that to bind implementation. We can exploit the fact that the Type of a Type is Type[Type]] - and say that if you are binding to a meta type then you are defining the implementation. As an example - we have a Foo Ruby class. We want to be able to serialize it. At the other end some other implementation will either use a dynamic instance or have a concrete implementation (depending of what they want to do). We must define that: type Foo = Object[ ] If that is all we have, we have no concrete implementation and the system would use a dynamic representation of Foo instances. If we want to bind the implementation of puppet Foo to Ruby Foo we can do that by: type Runtime[ruby, "Foo"] = Foo This special binding only applies when the LHS is a Runtime[, ]. We can allow multiple such bindings e.g.
Jira (PUP-5479) segfault with augeas type when changes attribute is too long
Title: Message Title David Lutterkort commented on PUP-5479 Re: segfault with augeas type when changes attribute is too long Augeas does not segfault because of an invalid path; there's some other interaction going on here. I also can not reproduce the segfault with 2015.3 or with plain augeas-1.4.0 (by issuing the same commands as the augeas type manually) Where would I get the student VM where this issue happened so I can poke some more at 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 (PDB-2445) (maint) Fix summary cache NPE on command failure
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2445 (maint) Fix summary cache NPE on command failure Issue Type: Bug Assignee: Unassigned Created: 2016/02/18 10:18 AM Priority: Normal Reporter: gepetto-bot 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 (PDB-2445) (maint) Fix summary cache NPE on command failure
Title: Message Title gepetto-bot updated an issue PuppetDB / PDB-2445 (maint) Fix summary cache NPE on command failure Change By: gepetto-bot Sprint: PuppetDB 2016-02-24 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-5735) Remove usage of win32-security gem
Title: Message Title Glenn Sarti commented on PUP-5735 Re: Remove usage of win32-security gem Confirmed facter code is correct in all three OSes 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-2441) Commands should be submitted only as bytes
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-2441 Commands should be submitted only as bytes Change By: Rob Browning Assignee: Rob Browning Scope Change Category: Adopted Scope Change Reason: Time available Story Points: 2 Sprint: PuppetDB 2016- 03 02 - 09 24 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
Jira (PUP-5735) Remove usage of win32-security gem
Title: Message Title Glenn Sarti commented on PUP-5735 Re: Remove usage of win32-security gem Confirmed the current WIP PR for Facter works on 2008R2 and 2012R2. It is always reporting as true on 2003R2 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-5922) Create recursive directory feature flag
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-5922 Create recursive directory feature flag Change By: Michael Smith Assignee: 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-5922) Create recursive directory feature flag
Title: Message Title Michael Smith created an issue Puppet / PUP-5922 Create recursive directory feature flag Issue Type: Task Assignee: Unassigned Created: 2016/02/18 9:01 AM Priority: Normal Reporter: Michael Smith Create a feature flag (which will be a Puppet setting with a special attribute to mark it for internal use) that disables inlining metadata for recursive directories. Will have to disable both the functionality and tests. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5122) Acceptance tests for direct puppet running from cache
Title: Message Title Josh Cooper assigned an issue to qa Puppet / PUP-5122 Acceptance tests for direct puppet running from cache Change By: Josh Cooper Status: Ready for CI Test Assignee: 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-1829) Define PCore - the Puppet Meta Meta Model
Title: Message Title Henrik Lindberg commented on PUP-1829 Re: Define PCore - the Puppet Meta Meta Model 1. We must support different mapping of name to type in different contexts (at runtime this would be an environment, but we should not build the mechanism on that). I think we have a hierarchy (two levels). The runtime itself has one mapping - something like the AST, the Locator etc. It will not change between environments contexts - we only have one implementation (or at least - we do not intend to have multiple versions). I think that a ModelSet refers to a parent set and that it is possible to override in the derived ModelSet. In many cases, you can just use the master runtime ModelSet (e.g. AST and locators as there are no user defined types there, only instructions that when evaluated creates types). 2. What I proposed at 1. probably solves 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-5844) Add the Object type to the Puppet Type system
Title: Message Title
Thomas Hallgren commented on PUP-5844
Re: Add the Object type to the Puppet Type system
I've been thinking about default values. Isn't that a property of a type rather than something that you'd want to declare in (almost) each and every place that the type is used? Consider the following:
type TemperatureUnit = Enum[kelvin, fahrenheit, celcius]
function set_temp(Integer temp, TemperatureUnit unit = 'celcius') {}
function set_lower_threshold(Integer temp, TemeratureUnit unit = 'celcius') {}
function set_upper_threshold(Integer temp, TemeratureUnit unit = 'celcius') {}
# and so on
We have an Optional type. Why not enhance that type with an additional argument that is default value? We'd then get:
type TemperatureUnit = Optional[Enum[kelvin, fahrenheit, celcius],celcius]
Jira (PUP-5912) Implement a human friendly PCore serialization format
Title: Message Title Henrik Lindberg commented on PUP-5912 Re: Implement a human friendly PCore serialization format Agree that it is not required to do the native puppet parser integration; so lower prio. Also of higher prio is to have implementations of the MSgPack or/and Json efficient formats in Ruby/C++ with JVM/Java/Clojure (if not done natively) coming next. Also, depending how it is done, the community will want support in Go, Python, PHP and even Shelll-scripts. Some of those could perhaps be covered with the C++ implementation (a library that can be used to create plugins for various environments perhaps). The Shell-script and low-tech solutions do need a format though. While it may not be the same at the lowest level in serialization, in needs to fit in with the upper layers and there at least I think it should be a "flavour of serialization". In the human "low-tech" format there should be no tabulation and everything is done by containment except references that are done via name. I.e. this is like it is done now where everything is turned into a hash and then serialized. We need a better version of that that can represent the extended data types. Essentially everything is encoded as Objects == a hash, and everything has a type attribute . except integers strings and possibly arrays. 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-5844) Add the Object type to the Puppet Type system
Title: Message Title Henrik Lindberg commented on PUP-5844 Re: Add the Object type to the Puppet Type system But maybe there is a difference between an interface and an implementation - not sure about that. What I posted above is an implementation since it has functions and invariants - from a strict type API standpoint those are not needed (although invariants is valuable external information as it defines states that are legal/illegal). Think we need to talk about 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-5844) Add the Object type to the Puppet Type system
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5844
Add the Object type to the Puppet Type system
Change By:
Henrik Lindberg
In the Puppet Core Type Model (PCore) that will be used to describe all serialization using the Puppet Type System it is essential to have an {{Object\[T]}} type that matches instances of user defined type {{T}}. We also need the run time abstract {{Object}} from which the concrete instances of user defined data types are derived.This work is also required to enable the full user defined type definition using the syntax:{code:puppet}type TypeName inhirts inherits SuperTypeName { # attribute definitions }{code}Which will be added in a separate ticket.
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-5844) Add the Object type to the Puppet Type system
Title: Message Title
Henrik Lindberg commented on PUP-5844
Re: Add the Object type to the Puppet Type system
I want this to be:
type MyType inherits OtherType {
attr Integer name { default => "40", another_option => 42, and_so_on => 43 }
attr T name2
# ...
function f () { }
# ...
# later additional rules for invariants
}
When/if presented as a struct, all options and functions are
Jira (FACT-1346) Provide Environment Variables as a Structured Fact
Title: Message Title Rob Reynolds commented on FACT-1346 Re: Provide Environment Variables as a Structured Fact This could also be focused on just the environment variables that are necessary for Puppet to work, we already provide Path as a variable, but not things like SystemDir, TEMP, etc. Those would be beneficial to provide. 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-1346) Provide Environment Variables as a Structured Fact
Title: Message Title Rob Reynolds updated an issue Facter / FACT-1346 Provide Environment Variables as a Structured Fact Change By: Rob Reynolds Scrum Team: Client Platform 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-1346) Provide Environment Variables as a Structured Fact
Title: Message Title Rob Reynolds updated an issue Facter / FACT-1346 Provide Environment Variables as a Structured Fact Change By: Rob Reynolds Sprint: Windows Triage 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-5912) Implement a human friendly PCore serialization format
Title: Message Title Thomas Hallgren commented on PUP-5912 Re: Implement a human friendly PCore serialization format To accomplish this is not trivial. A serializer needs to take a couple of things into account: A lot of objects may be serialized which means that streaming capabilities is of essence. Objects must be able to reference objects that have been serialized (tabulation) Hashes must allow arbitrary keys to exist. Various object types, not supported by the protocol, must be recognized (extensions) The current prototype The way this is done in the prototype is by using a stream where essentially only extensions and protocol supported scalar objects are written in a long sequence. The MessagePack and JSON backends use the exact same approach (they even use the same extension callbacks). The result is a lot of integers intermixed with occasional String, Float, Boolean or null values. In JSON, an extension is indicated using an Array construct. The format is extremely easy to tabulate and stream in both directions. To read? Not so easy. Debug output The prototype also has a MessagePack debug output. It's output uses formatted Lisp syntax and it indents containers such as arrays, hashes, or objects. It's also capable of turning off parts of the tabulation and write extensions with symbolic names instead of integers. The output is produced to a separate stream (original output is still binary and produced simultaneously) and there is currently no programmatic reader for it. It's sole purpose is to provide something that is human readable. Thanks to the indent, it's somewhat readable but it is still hard, given that no attributes are named and all in-stream references are integers. A similar output could be produced a JSON debug output. I doubt that using json-query would help much though, since the structure consists of nested arrays with anonymous value. I don't see what value it would bring to add this in addition to the debugger that's present for MessagePack already. What we need to improve this IMO, to be really human readable we must use a totally different approach which will have an impact on both the serialization layer and the backends that is beneath. Here's a summary of things that I think would be needed: invent a readable object reference (XPath for JSON style, there's a couple of them around) to use for tabulation. make the writer and reader keep track of the path to each object that it writes/reads.
Jira (FACT-1347) puppetversion only contains a number
Title: Message Title
Gerhardus Geldenhuis commented on FACT-1347
Re: puppetversion only contains a number
/opt/puppetlabs/puppet/modules/puppet_enterprise/lib/facter/pe_version.rb makes these facts available: is_pe, pe_version, pe_major_version, pe_minor_version, pe_patch_version as an apparent replacement for STDLIB
and mentions that you should use pe_master_version() function to get the PE version on a client since the above facts is only available on the master.
I created a simple class with the following and classified my master with the class by adding the class as part of the PE Master Group. notify { "TEST1:$ {is_pe}
": } notify { "TEST2:$ {pe_version}
": } notify { "TEST3:$ {pe_major_version}
": } notify { "TEST4:$ {pe_minor_version}
": } notify { "TEST5:$ {pe_patch_version}
": }
All of these notifies returns empty values so I am not convinced that these replacement facts works as intended. Note that this is a clean PE install on a clean Ubuntu 14.04 install.
Secondly there is no function called pe_master_version that I could find in order to use.
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-1347) puppetversion only contains a number
Title: Message Title Gerhardus Geldenhuis created an issue Facter / FACT-1347 puppetversion only contains a number Issue Type: Bug Assignee: Unassigned Created: 2016/02/18 2:06 AM Priority: Normal Reporter: Gerhardus Geldenhuis I have been trying to use a vmware module which makes use of the puppetversion fact. It appears that at some stage the puppetversion fact would typically contain a value like: "3.6.2 (Puppet Enterprise 3.3.0)". Currently in PE2015.3.2 puppetversion fact only returns "4.3.2". This means that the module in question fails to make a sound decision on whether it is being used in PE or not. There is number of facts in Puppet's stdlib module that makes use of this fact for facts like is_pe, pe_major_version, etc. These facts all fail now. I have not yet been able to find a viable alternative for determining whether an agent is running PE or not. Also a quick search: root@puppet:/opt/puppetlabs/puppet# grep puppetversion * -R on a clean PE2015.3.2 installation reveals that at least according to the spec files, quite a lot of software still depends on getting more information from the puppetversion fact. I have read https://tickets.puppetlabs.com/browse/PUP-4359 which seems to be related but there was no clear solution with regards to the content of puppetversion fact.
Jira (PUP-5844) Add the Object type to the Puppet Type system
Title: Message Title
Thomas Hallgren commented on PUP-5844
Re: Add the Object type to the Puppet Type system
The solution that I'm working on now is using a literal hash to represent the block. This makes it look very similar to the member definition block of a Struct and has the benefit of that the user does not need to learn yet another syntax:
type MyType {
height => Integer[0,default],
width => Integer[0,default],
description => String[1],
comment => Optional[String],
validate=> Callable[[] >> Boolean]
}
This means that the attr keyword isn't needed.
One thought here is if we should allow that it looks exactly like a struct and wrap the block in [] so that other arguments can follow. A second block could indicate private attributes for instance.
type MyType [{
