Jira (PUP-5699) Inline symlink metadata
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-5699
Inline symlink metadata
Change By:
Josh Cooper
When inlining metadata, either add metadata about the link if {{links => manage}} or the thing the link points to if {{links => follow}}. The server already does this when handling {{file_metadata}} requests, we should be able to share the code for this code path.
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 Josh Cooper updated an issue Puppet / PUP-5118 Handle duplicate resources when inlining file metadata Change By: Josh Cooper Story Points: 2 3 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-5119) Handle file sources outside codedir
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5119 Handle file sources outside codedir Change By: Josh Cooper Story Points: 2 3 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-5709) Search for use of the Puppet Utils SID api within the forge
Title: Message Title Glenn Sarti created an issue Puppet / PUP-5709 Search for use of the Puppet Utils SID api within the forge Issue Type: Story Assignee: Unassigned Created: 2016/01/14 9:55 AM Priority: Normal Reporter: Glenn Sarti As part of PUP-5538 we're reworking the SID conversions to use Wide String API calls. However some parts of the SID class had to be modified. This ticket is a short piece of work to search through the Forge and find if anyone is using parts of the SID api which could change. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5683) $puppetversion and other top level variables not present when running tests
Title: Message Title Henrik Lindberg commented on PUP-5683 Re: $puppetversion and other top level variables not present when running tests I think Thomas Linkin's answer is the correct answer to this problem. I am therefore closing this 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-5709) Search for use of the Puppet Utils SID api within the forge
Title: Message Title Ryan Gard updated an issue Puppet / PUP-5709 Search for use of the Puppet Utils SID api within the forge Change By: Ryan Gard QA Status: Reviewed 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-5690) Test run the windows 10 acceptance tests
Title: Message Title Ryan Gard updated an issue Puppet / PUP-5690 Test run the windows 10 acceptance tests Change By: Ryan Gard QA Risk Assessment Reason: QA is interested in seeing how to perform this task for future reference. QA Risk Assessment: Medium QA Status: Reviewed 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
Jira (PUP-4339) Non-US paths in environment variables gets garbled on Windows
Title: Message Title Ryan Gard updated an issue Puppet / PUP-4339 Non-US paths in environment variables gets garbled on Windows Change By: Ryan Gard QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5683) $puppetversion and other top level variables not present when running tests
Title: Message Title
Thomas Linkin commented on PUP-5683
Re: $puppetversion and other top level variables not present when running tests
I believe this is a problem that exists firmly in how rspec-puppet is initiating the catalog compilation. While I do not know they issue exactly, I have seen a few other issues regarding facts in rspec-puppet lately. However, I believe the solution to this is actually a matter of testing methodology.
If you have code that uses the puppetversion fact, this is a part of the logic you should be trying to validate in the unit tests. As such, you should be setting puppetversion explicitly for the tests.
let(:facts) { {:puppetversion => '4.3.1' } }
In this particular case, since the value you're explicitly providing is tied so closely to the version of Puppet that tests will be run against, you don't want to run tests for Puppet 3 when Puppet 4 is installed and vice-versa (or whatever your versions you need are). In this case, you'll want to conditionalize certain sets of tests to only execute when rspec-puppet is run against the correct version of Puppet. To do this, you can use Puppet.version in your rspec code to prevent it from running certain tests that would otherwise fail due to the installed Puppet version.
The link below is an example of a module whose tests explicitly set puppetversion and conditionalize the running of certain tests with Puppet.version. https://github.com/puppetlabs/puppetlabs-puppet_agent/blob/4587e24654b8e1d225adcc7b899c3ba8488f/spec/classes/puppet_agent_windows_install_spec.rb#L18
Once you've improved the spec tests, add all the versions of Puppet you need to run the unit tests directly against to your CI build process (for example, a matrix build in Jenkins or TravisCI) assuming you've setup the Gemfile to allow control of the Puppet version used.
Add Comment
Jira (PUP-5709) Search for use of the Puppet Utils SID api within the forge
Title: Message Title Glenn Sarti assigned an issue to Glenn Sarti Puppet / PUP-5709 Search for use of the Puppet Utils SID api within the forge 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-5560) Look at Improving Unicode for all Windows gems
Title: Message Title Ryan Gard updated an issue Puppet / PUP-5560 Look at Improving Unicode for all Windows gems Change By: Ryan Gard QA Status: Reviewed 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 (HI-491) PSON error when hiera hash contains 'document_type' as a key
Title: Message Title Thomas Buts commented on HI-491 Re: PSON error when hiera hash contains 'document_type' as a key Maybe some extra information: We are running a mixed environment and I just noticed that we only have this problem on the servers where puppet is installed and not the puppet-agent package. Server: puppetserver-2.1.1-1.el6.noarch Agents with problems: puppet-3.7.1-1.el6.noarch puppet-3.8.3-1.el6.noarch Agents without a problem: puppet-agent-1.2.5-1.el6.x86_64 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-5115) Send code_id in all requests
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5115 Send code_id in all requests Not needed for Burnside. Change By: Josh Cooper Sprint: Client 2016-02-24 (Burn FF) 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-3077) When puppet agent fails to retrieve catalog from master, cached catalog is used without regard for the puppet.conf-declared environment
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3077 When puppet agent fails to retrieve catalog from master, cached catalog is used without regard for the puppet.conf-declared environment Change By: Josh Cooper Sprint: Client 2016-02- 24 (Burn FF) 10 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-5122) Acceptance tests for direct puppet running from cache
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5122 Acceptance tests for direct puppet running from cache Change By: Josh Cooper Sprint: Client 2016-02- 10 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-5120) Send checksum_value and static_catalog query params in catalog request
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5120 Send checksum_value and static_catalog query params in catalog request Change By: Josh Cooper Summary: Send checksum_value and static_catalog query params in catalog request 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
Josh Cooper updated an issue
Puppet / PUP-5703
Handle cached catalog and pluginsync inconsistencies
Change By:
Josh Cooper
If Currently, {{use_cached_catalog}} is false, then and {{pluginsync}} should default can be set to true "conflicting" values, causing the agent to use different versions of plugins than the catalog . If {{use_cached_catalog}} is true and {{$vardir/ For example, the catalog could contain a new resource parameter that the older pluginsync'ed lib }} /puppet/type/foo.rb doesn't exist or is empty know about. Ideally , then do pluginsync should only occur when requesting a new catalog, and skipped when applying a cached catalog . I think the latter is required However , because puppet settings may create we cannot ignore pluginsync without a deprecation cycle. For 4.4, we will instead change the directory just by running default value of {{ puppet apply pluginsync }} , but use whatever value is set explicitly on the command line or puppet . conf. For this ticket: If {{use_cached_catalog}} is true false , and then {{ $vardir/lib pluginsync }} should default to true.If {{use_cached_catalog}} is not empty true , then {{pluginsync}} should default to {{ false }} , so that we use the same set of plugins that matched the catalog when it was compiled. Long term we should deprecate and eliminate the If {{ pluginsync use_cached_catalog }} setting is true , since but it doesn't have a cached catalog, but due to {{ pluginsync usecacheonfailure }} has been on by default since 3.0 requests a new catalog , then we should only probably set {{ pluginsync based on =true}} unless the user explicitly set {{ use_cached_catalog pluginsync=false }} , and we can't expect correct behavior if we allow them both .There is a separate ticket to be set independently deprecate {{pluginsync}} .
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5703) Handle cached catalog and pluginsync inconsistencies
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5703 Handle cached catalog and pluginsync inconsistencies Change By: Josh Cooper Story Points: 2 3 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-1297) facter 2.4.5 2016-01-19 Release
Title: Message Title Michael Smith updated an issue Facter / FACT-1297 facter 2.4.5 2016-01-19 Release Change By: Michael Smith Summary: facter 2.4.5 2016-01- 13 19 Release 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-13) Allow class & define parameters to reference earlier parameters
Title: Message Title Henrik Lindberg assigned an issue to Peter Huene Native Puppet / NPUP-13 Allow class & define parameters to reference earlier parameters Change By: Henrik Lindberg 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-5693) benchmark:function_loading aborts with stack overflow
Title: Message Title Henrik Lindberg commented on PUP-5693 Re: benchmark:function_loading aborts with stack overflow I was just about to push this up to stable as a maint fix - so, I should wait with that? 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-997) Add Ubuntu 14.04/trusty to acceptance testing
Title: Message Title Kurt Wall assigned an issue to Kurt Wall PuppetDB / PDB-997 Add Ubuntu 14.04/trusty to acceptance testing Change By: Kurt Wall Assignee: Kurt Wall 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-5662) Update language spec reg. Hash data type being ordered
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5662 Update language spec reg. Hash data type being ordered Change By: Henrik Lindberg Component/s: DOCS 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-1985) Allow function & class & define parameters to reference earlier parameters
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-1985 Allow function & class & define parameters to reference earlier parameters 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-5662) Update language spec reg. Hash data type being ordered
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5662 Update language spec reg. Hash data type being ordered Change By: Henrik Lindberg Scope Change Category: Found Scope Change Reason: In order to change the implementation, we needed the spec to the updated We added the ticket then forgot about it. It is the change of 1 line of text. 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-5713) ClassInformationService.classes_per_environment errantly evaluates parameter default expression
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5713 ClassInformationService.classes_per_environment errantly evaluates parameter default _expression_ Change By: Henrik Lindberg Affects Version/s: PUP 4.2.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-5713) ClassInformationService.classes_per_environment errantly evaluates parameter default expression
Title: Message Title Henrik Lindberg commented on PUP-5713 Re: ClassInformationService.classes_per_environment errantly evaluates parameter default _expression_ Jeremy Barlow Note, that this is scheduled for 4.3.3 which means it will appear in such a maintenance release should we make one, else in 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-5713) ClassInformationService.classes_per_environment errantly evaluates parameter default expression
Title: Message Title
Jeremy Barlow created an issue
Puppet / PUP-5713
ClassInformationService.classes_per_environment errantly evaluates parameter default _expression_
Issue Type:
Task
Assignee:
Unassigned
Created:
2016/01/14 3:11 PM
Priority:
Normal
Reporter:
Jeremy Barlow
In doing some testing against the Puppet::InfoService::ClassInformationService.classes_per_environment() method, I found that the value for :default_source apparently tries to evaluate the _expression_ that it needs to return for a class parameter's default value rather than just retaining the original _expression_ verbatim from the Puppet manifest .pp file, passing that back as a String.
For example, I used a Puppet class with the following content...
class myclass (String $string_with_expression_default = "for os in family $::osfamily")
{
}
Jira (PUP-5713) ClassInformationService.classes_per_environment errantly evaluates parameter default expression
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5713 ClassInformationService.classes_per_environment errantly evaluates parameter default _expression_ Change By: Henrik Lindberg Sprint: Language 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-5713) ClassInformationService.classes_per_environment errantly evaluates parameter default expression
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5713 ClassInformationService.classes_per_environment errantly evaluates parameter default _expression_ Change By: Henrik Lindberg Fix Version/s: PUP 4.3.3 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-5713) ClassInformationService.classes_per_environment errantly evaluates parameter default expression
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5713 ClassInformationService.classes_per_environment errantly evaluates parameter default _expression_ Change By: Henrik Lindberg Issue Type: Task Bug 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 Sean Griffin updated an issue Puppet / PUP-5209 call_function and metadata.json: call a function from a different module, very strange behavior Change By: Sean Griffin 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-1974) Mechanism for securing sensitive catalog data
Title: Message Title Kylo Ginsberg commented on PUP-1974 Re: Mechanism for securing sensitive catalog data /me puts down light saber I had two more thoughts on this: 1) On the logging side, we need to call out what puppet options we should be considering. E.g. there's log_level of course (presumably all levels). Plus, I was forgetting about show_diff until I read Chris Barker's comments. Plus, and things get a bit tricky here, late in the 3.x series we added http_debug, which outputs full contents of the http requests/responses (so catalogs and reports). 2) I'm thinking we don't want to do full-resource redaction from the catalog or you'd be introducing some weird scenarios, e.g. if a catalog application failed with only one, sensitive, resource, you'd have a failed report and no failed resources, etc. So I'm assuming we want to do something more surgical. We need to specify what. 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-5712) TypeParser cannot handle negative numbers
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5712 TypeParser cannot handle negative numbers Change By: Henrik Lindberg Fix Version/s: PUP 4.3.3 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-5712) TypeParser cannot handle negative numbers
Title: Message Title
Henrik Lindberg commented on PUP-5712
Re: TypeParser cannot handle negative numbers
Peter Huene good points (and sounds like a good implementation). Sounds like the result will be a type with literal values, only that it was constructed from constexprs. That would be ok in any context. I think we need to specify more clearly what is allowed when declaring the types of parameters - I think it may have access to global scope in the Ruby impl. Say someone did this:
function foo(Enum[$::osfamily, banana] $x) { ... }
(code}
I don't thing that should be allowed as the static type then depends on the evaluation context of a particular node.
It should however be ok to create an arbitrary (free) instance of a type anywhere:
{code:puppet}
$a = Enum[$::osfamily, banana]
Jira (PUP-5712) TypeParser cannot handle negative numbers
Title: Message Title
Henrik Lindberg commented on PUP-5712
Re: TypeParser cannot handle negative numbers
I should have added - any constexpr would be fine as long as it is never presented to the external world as anything besides literal values (not needed any computation. Obviously something like:
Integer[1, 1+1]
is trivial to implement, but this is also a constexpr:
{1 => Integer, 2 =>String, 3 => Integer}.filter |$k, $t| { $k % 2 == 0 }.map |$k,$v|{$v}
Which, if we want an implemetation of the type system in some other language would cause a lot of extra work.
Hence, when asking for the signature of a function, the native (in fact, any implementation) must have evaluated type parameters down to literal values.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5112) Add code_content model and REST terminus
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-5112 Add code_content model and REST terminus Change By: Josh Cooper Assignee: Josh Cooper 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-5714) Add a 'git' checksum type for file resource sources
Title: Message Title Eric Sorenson created an issue Puppet / PUP-5714 Add a 'git' checksum type for file resource sources Issue Type: Bug Assignee: Unassigned Created: 2016/01/14 5:12 PM Priority: Normal Reporter: Eric Sorenson One of the downsides of static catalog compilation is that the master needs to checksum all the files referenced in a catalog ahead of time, to include their checksums in the catalog, which can be intense on compute and i/o resources. With Direct Puppet, we're providing a linkage between a git-managed backing store and the file content but aren't (yet) leveraging the fact that git inherently knows the checksum of every file at every commit-ref under its control. This seems like it'd be a good idea from a resource-conservation standpoint, plus it's bloody awesome. Implementing this would require either embedding/requiring git on the agent or re-creating the algorithm git uses to generate its checksums ( see http://git-scm.com/book/en/v2/Git-Internals-Git-Objects#Object-Storage for the gory details ), but the server could simply query the file-sync service store (for PE) or user-specified git backend (for OSS) during catalog compilation and save some work. This isn't slated for a particular release but came up out of some internal discussion and I wanted to capture it in a ticket for future prioritization.
Jira (PUP-5612) Error message for declaring resource without title is confusing
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5612 Error message for declaring resource without title is confusing Change By: Henrik Lindberg Scope Change Category: Adopted Scope Change Reason: This was some time ago - IIRC, thomas was out of work in the then current sprint. 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-997) Add Ubuntu 14.04/trusty to acceptance testing
Title: Message Title Kurt Wall commented on PDB-997 Re: Add Ubuntu 14.04/trusty to acceptance testing Well, I've got PR 863 up against a branch on my fork. 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-5662) Update language spec reg. Hash data type being ordered
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-5662 Update language spec reg. Hash data type being ordered 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-5662) Update language spec reg. Hash data type being ordered
Title: Message Title Henrik Lindberg commented on PUP-5662 Re: Update language spec reg. Hash data type being ordered Merged to specifications master. Ping Nicholas Fagerlund - DOCS flag on this ticket as you may want to update/review documentation. There is no real change in the implementation of puppet only that from 4.x puppet complies with the spec that hashes retain the keys in order of insertion. (This because we no longer run on Ruby 1.8 and we can now make this guarantee, which we will maintain also in the native puppet implementation). 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-5534) (Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in /modules/*/files/*
Title: Message Title
Eric Sorenson updated an issue
Puppet / PUP-5534
(Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in /modules/*/files/*
Change By:
Eric Sorenson
As a puppet node, I should only be able to retrieve historical file content for files which I have permission to access.Static Catalog1. local file has drifted. So we need to retrieve the right original file content that is consistent with the one we are applying2. auth part: removing implicit path expansion of {{puppet:///modules/mod_name/file_name}} urls to {{modules/mod_name/files/file_name}}. So new auth rules on the endpoint. Today anyone with A valid client cert can access everything from any modules files directory. Make sure that as an anonymous user cannot get file content. Also make sure you cannot cause a path traversal attack even with a valid client cert.
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-5534) (Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in /modules/*/files/*
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-5534 (Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in /modules/*/files/* Change By: Eric Sorenson Summary: (Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in < my_env environment >/modules/*/files/* 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-5534) (Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in /modules/*/files/*
Title: Message Title
Eric Sorenson updated an issue
Puppet / PUP-5534
(Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in /modules/*/files/*
Change By:
Eric Sorenson
As a puppet node, I should only be able to retrieve historical file content for files which I have permission to access.Static Catalog1. local file has drifted. So we need to retrieve the right original file content that is consistent with the one we are applying2. auth part: removing implicit path expansion of {{puppet:///modules/mod_name/file_name}} urls to {{modules/mod_name/files/file_name}}. A valid client cert can access everything from any modules files directory. Make sure that as an anonymous user unauthenticated connection cannot get file content. Also make sure you cannot cause a path traversal attack even with a valid client cert.
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-5693) benchmark:function_loading aborts with stack overflow
Title: Message Title Henrik Lindberg commented on PUP-5693 Re: benchmark:function_loading aborts with stack overflow I found the cause of the problem. There were also additional problems as the 4.x version is more strict. Basically, the reason an OutOfStack occurs when a function i loaded is simply that it invokes he Ruby parser/interpreter and it adds a number of levels to the stack. therefore, when the stack is filled up for other reasons, calling a function for the first time will trigger loading of it, and then the stack blows. What has happened over time is that we have refactored code; there is now more delegation (more smaller methods delegating to more specialized version), and wrapping (e.g. doing the work in a lambda yielded to by a wrapper that does profiling). We also tend to use recursion more than in the past. For those reasons there will more frequent out of stack problems for legitimate reasons. Specifically the function_loading benchark loads and calls functions recursively to a depth of 1000. Reducing this to 800 made the benchmark work without an out of stack. There were also other problems as the benchmark generated module dependencies the wrong way. They are now needed to be correct as modules can only call functions in modules it depends on (bugs in earlier versions did not prevent that). The good news - it was easy to fix this specifically for the benchmark by reducing the recursion. The bad news is that it was not a bug that when fixed would make the out of stack problem others have reported go away. We should also for the future consider reducing the recursion/call-levels we use. We should also consider bumping the amount of stack we use in general when running puppet as we are too close to the edge. For more recent Ruby versions (> 2.x) it should be possible to set this with an environment variable. We should also try to design a solution for recursion in puppet; i.e. when users write recursive puppet functions. We could then prevent the ruby oout of stack from happening in favor of our own error that would be able to tell the user where the recursion is too deep (instead of the Booom - goodbye). The fix to the benchmark will be merged to stable. Add Comment This message was sent by Atlassian JIRA
Jira (PUP-5693) benchmark:function_loading aborts with stack overflow
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5693 benchmark:function_loading aborts with stack overflow Change By: Henrik Lindberg 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-5710) puppet config "unset"
Title: Message Title Kaitlin Carter moved an issue Puppet / PUP-5710 puppet config "unset" Change By: Kaitlin Carter Key: PE PUP - 13703 5710 Project: Puppet Enterprise [Internal] 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-5106) Add catalog_uuid to catalog
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-5106 Add catalog_uuid to catalog Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5534) (Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in /environments/*/modules/*/files/*
Title: Message Title Eric Sorenson commented on PUP-5534 Re: (Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in /environments/*/modules/*/files/* After further tweaks and f2f with Sean, this story is now an accurate reflection of the requirements. 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 (HI-491) PSON error when hiera hash contains 'document_type' as a key
Title: Message Title Henrik Lindberg commented on HI-491 Re: PSON error when hiera hash contains 'document_type' as a key In pson.rb # This is create identifier, that is used to decide, if the _pson_create_ # hook of a class should be called. It defaults to 'document_type'. attr_accessor :create_id # ... self.create_id = 'document_type' This could potentially be hard to fix - the only solution that I can think of that does not require throwing out the horrible pson format is to change it to a more magical key; say "_clown_S_hO_es_pson_wears_Clow_n_Shoe_S_nananananana". The real solution is to get rid of Pson. Not sure if it is possible to get rid of it in the data binding indirector (since that is the only difference between the cases (i.e. direct lookup with hiera, and via auto data binding)
Jira (PUP-5711) Uppercase characters in certname cause pain and sfufering
Title: Message Title Brian Rak created an issue Puppet / PUP-5711 Uppercase characters in certname cause pain and sfufering Issue Type: Bug Affects Versions: PUP 4.3.1 Assignee: Unassigned Created: 2016/01/14 11:55 AM Environment: CentOS 6 x64 Priority: Normal Reporter: Brian Rak I've just spent 5 hours debugging weird SSL issues that were ultimately caused by having uppercase characters in my certname. I have a simple config: certname = puppetclient.MELTbeforefailure.com server = puppetmaster.meltbeforefailure.com node_name = cert Which causes this: puppet agent -t Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/node/puppetclient.MELTbeforefailure.com [find] at :123 Info: Retrieving pluginfacts Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to
Jira (NPUP-14) Parameter default value evaluation should have its own match scope
Title: Message Title
Peter Huene updated an issue
Native Puppet / NPUP-14
Parameter default value evaluation should have its own match scope
Change By:
Peter Huene
The following code:{code}class foo($a = foo =~ /foo/, $b = $0) {notice $a, $b}include foo{code}outputs:{code}Notice: Scope(Class[foo]): true foo{code}This is incorrect because each parameter's default value evaluation should have its own match scope. The expected output is {{Notice: Scope(Class[foo]): true}} as {{$0}} should be undef. This will prevent the match variables (e.g. {{$0}}) from being available between parameters or inside the body.
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-5583) Remove host specific logic from puppet acceptance setup steps
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5583 Remove host specific logic from puppet acceptance setup steps 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-5583) Remove host specific logic from puppet acceptance setup steps
Title: Message Title Kylo Ginsberg assigned an issue to Steve Barlow Puppet / PUP-5583 Remove host specific logic from puppet acceptance setup steps 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 (NPUP-14) Parameter default value evaluation should have its own match scope
Title: Message Title
Peter Huene created an issue
Native Puppet / NPUP-14
Parameter default value evaluation should have its own match scope
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/01/14 8:22 PM
Priority:
Normal
Reporter:
Peter Huene
The following code:
class foo($a = foo =~ /foo/, $b = $0) {
notice $a, $b
}
include foo
Jira (FACT-380) Private ipaddress is used as ipaddress fact
Title: Message Title Kylo Ginsberg assigned an issue to qa Facter / FACT-380 Private ipaddress is used as ipaddress fact Change By: Kylo Ginsberg 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 (PDB-2322) (maint) Fix broken export test with a semver error message
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2322 (maint) Fix broken export test with a semver error message Change By: Andrew Roetker Scope Change Category: Adopted Scope Change Reason: fixing a broken 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-5712) TypeParser cannot handle negative numbers
Title: Message Title
Peter Huene commented on PUP-5712
Re: TypeParser cannot handle negative numbers
For what it's worth, the native compiler parses (at least once an outstanding PR is merged) type specification strings using a "postfix _expression_" parser, i.e. the same postfix _expression_ rule for the "puppet" parser. It then evaluates the resulting _expression_ in an "empty" evaluation context (no scope, node, or catalog access), ensuring the resulting value is a type. This allows for arbitrary expressions in a type specification without side-effects, e.g. notice assert_type('Integer[[10][0], 100+10-100]', 10) results in 10 being printed. It was done this way simply because I didn't want to have to write a separate parser / evaluator from what is used normally.
I see the Ruby implementation as a subset of the native compiler's functionality, so we don't need to make it accept arbitrary expressions; could just add support for unary negation operations.
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-1281) Remove host specific logic from facter acceptance setup steps
Title: Message Title Josh Cooper updated an issue Facter / FACT-1281 Remove host specific logic from facter acceptance setup steps Change By: Josh Cooper 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-5702) Add code_id and catalog_uuid to report
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-5702 Add code_id and catalog_uuid to report Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5583) Remove host specific logic from puppet acceptance setup steps
Title: Message Title Michael Smith assigned an issue to qa Puppet / PUP-5583 Remove host specific logic from puppet acceptance setup steps Change By: Michael Smith 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-5711) Uppercase characters in certname cause pain and suffering
Title: Message Title Brian Rak updated an issue Puppet / PUP-5711 Uppercase characters in certname cause pain and suffering Change By: Brian Rak Summary: Uppercase characters in certname cause pain and sfufering suffering I've just spent 5 hours debugging weird SSL issues that were ultimately caused by having uppercase characters in my certname.I have a simple config: certname = puppetclient.MELTbeforefailure.comserver = puppetmaster.meltbeforefailure.comnode_name = certWhich causes this: # puppet agent -tWarning: Unable to fetch my node definition, but the agent run will continue:Warning: Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/node/puppetclient.MELTbeforefailure.com [find] at :123Info: Retrieving pluginfactsError: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/file_metadata/pluginfacts [search] at :123Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Could not evaluate: Could not retrieve file metadata for puppet:///pluginfacts: Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/file_metadata/pluginfacts [find] at :123Info: Retrieving pluginError: /File[/opt/puppetlabs/puppet/cache/lib]: Failed to generate additional resources using 'eval_generate': Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/file_metadata/plugins [search] at :123Error: /File[/opt/puppetlabs/puppet/cache/lib]: Could not evaluate: Could not retrieve file metadata for puppet:///plugins: Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/file_metadata/plugins [find] at :123Error: Could not retrieve catalog from remote server: Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/catalog/puppetclient.MELTbeforefailure.com [find] at :123Warning: Not using cache on failed catalogError: Could not retrieve catalog; skipping runError: Could not send report: Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/report/puppetclient.MELTbeforefailure.com [save] at :123Getting rid of the uppercase characters makes this work fine: # puppet agent -tInfo: Using configured environment 'production'Info: Retrieving pluginfactsInfo: Retrieving pluginInfo: Caching catalog for puppetclient.meltbeforefailure.comInfo: Applying configuration version '1452801282'Notice: Applied catalog in 0.01 seconds *Please* add a warning or error here when the certname is uppercase. These errors are completely impossible to debug otherwise.
Jira (PUP-5711) Uppercase characters in certname cause pain and suffering
Title: Message Title
Brian Rak updated an issue
Puppet / PUP-5711
Uppercase characters in certname cause pain and suffering
Change By:
Brian Rak
I've just spent 5 hours debugging weird SSL issues that were ultimately caused by having uppercase characters in my certname.I have a simple config: {noformat} certname = puppetclient.MELTbeforefailure.comserver = puppetmaster.meltbeforefailure.comnode_name = cert < { / pre> noformat} Which causes this: {noformat} # puppet agent -tWarning: Unable to fetch my node definition, but the agent run will continue:Warning: Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/node/puppetclient.MELTbeforefailure.com [find] at :123Info: Retrieving pluginfactsError: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/file_metadata/pluginfacts [search] at :123Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Could not evaluate: Could not retrieve file metadata for puppet:///pluginfacts: Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/file_metadata/pluginfacts [find] at :123Info: Retrieving pluginError: /File[/opt/puppetlabs/puppet/cache/lib]: Failed to generate additional resources using 'eval_generate': Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/file_metadata/plugins [search] at :123Error: /File[/opt/puppetlabs/puppet/cache/lib]: Could not evaluate: Could not retrieve file metadata for puppet:///plugins: Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/file_metadata/plugins [find] at :123Error: Could not retrieve catalog from remote server: Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/catalog/puppetclient.MELTbeforefailure.com [find] at :123Warning: Not using cache on failed catalogError: Could not retrieve catalog; skipping runError: Could not send report: Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/report/puppetclient.MELTbeforefailure.com [save] at :123 < { / pre> noformat} Getting rid of the uppercase characters makes this work fine: {noformat} # puppet agent -tInfo: Using configured environment 'production'Info: Retrieving pluginfactsInfo: Retrieving pluginInfo: Caching catalog for puppetclient.meltbeforefailure.comInfo: Applying configuration version '1452801282'Notice: Applied catalog in 0.01 seconds < { / pre> noformat} *Please* add a warning or error here when the certname is uppercase. These errors are completely impossible to debug otherwise.
Jira (PUP-5711) Uppercase characters in certname cause pain and suffering
Title: Message Title
Brian Rak updated an issue
Puppet / PUP-5711
Uppercase characters in certname cause pain and suffering
Change By:
Brian Rak
I've just spent 5 hours debugging weird SSL issues that that were ultimately caused by having uppercase characters in my certname.I have a simple config:{noformat}certname = puppetclient.MELTbeforefailure.comserver = puppetmaster.meltbeforefailure.comnode_name = cert{noformat}Which causes this:{noformat}# puppet agent -tWarning: Unable to fetch my node definition, but the agent run will continue:Warning: Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/node/puppetclient.MELTbeforefailure.com [find] at :123Info: Retrieving pluginfactsError: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/file_metadata/pluginfacts [search] at :123Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Could not evaluate: Could not retrieve file metadata for puppet:///pluginfacts: Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/file_metadata/pluginfacts [find] at :123Info: Retrieving pluginError: /File[/opt/puppetlabs/puppet/cache/lib]: Failed to generate additional resources using 'eval_generate': Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/file_metadata/plugins [search] at :123Error: /File[/opt/puppetlabs/puppet/cache/lib]: Could not evaluate: Could not retrieve file metadata for puppet:///plugins: Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/file_metadata/plugins [find] at :123Error: Could not retrieve catalog from remote server: Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/catalog/puppetclient.MELTbeforefailure.com [find] at :123Warning: Not using cache on failed catalogError: Could not retrieve catalog; skipping runError: Could not send report: Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/report/puppetclient.MELTbeforefailure.com [save] at :123{noformat}Getting rid of the uppercase characters makes this work fine:{noformat}# puppet agent -tInfo: Using configured environment 'production'Info: Retrieving pluginfactsInfo: Retrieving pluginInfo: Caching catalog for puppetclient.meltbeforefailure.comInfo: Applying configuration version '1452801282'Notice: Applied catalog in 0.01 seconds{noformat}*Please* add a warning or error here when the certname is uppercase. These errors are completely impossible to debug otherwise.
Jira (PUP-5711) Uppercase characters in certname cause pain and suffering
Title: Message Title
Brian Rak updated an issue
Puppet / PUP-5711
Uppercase characters in certname cause pain and suffering
Change By:
Brian Rak
I've just spent 5 hours debugging weird SSL issues that that were ultimately caused by having uppercase characters in my certname.I have a simple config:{noformat}certname = puppetclient.MELTbeforefailure.comserver = puppetmaster.meltbeforefailure.comnode_name = cert{ / noformat}Which causes this:{noformat}# puppet agent -tWarning: Unable to fetch my node definition, but the agent run will continue:Warning: Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/node/puppetclient.MELTbeforefailure.com [find] at :123Info: Retrieving pluginfactsError: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/file_metadata/pluginfacts [search] at :123Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Could not evaluate: Could not retrieve file metadata for puppet:///pluginfacts: Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/file_metadata/pluginfacts [find] at :123Info: Retrieving pluginError: /File[/opt/puppetlabs/puppet/cache/lib]: Failed to generate additional resources using 'eval_generate': Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/file_metadata/plugins [search] at :123Error: /File[/opt/puppetlabs/puppet/cache/lib]: Could not evaluate: Could not retrieve file metadata for puppet:///plugins: Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/file_metadata/plugins [find] at :123Error: Could not retrieve catalog from remote server: Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/catalog/puppetclient.MELTbeforefailure.com [find] at :123Warning: Not using cache on failed catalogError: Could not retrieve catalog; skipping runError: Could not send report: Error 403 on SERVER: Forbidden request: 104.207.129.134.vultr.com(104.207.129.134) access to /puppet/v3/report/puppetclient.MELTbeforefailure.com [save] at :123{ / noformat}Getting rid of the uppercase characters makes this work fine:{noformat}# puppet agent -tInfo: Using configured environment 'production'Info: Retrieving pluginfactsInfo: Retrieving pluginInfo: Caching catalog for puppetclient.meltbeforefailure.comInfo: Applying configuration version '1452801282'Notice: Applied catalog in 0.01 seconds{ / noformat}*Please* add a warning or error here when the certname is uppercase. These errors are completely impossible to debug otherwise.
Jira (PUP-5711) Uppercase characters in certname cause pain and suffering
Title: Message Title Jeremy Barlow commented on PUP-5711 Re: Uppercase characters in certname cause pain and suffering Brian Rak - thanks for filing this one. Just to clarify, you saw these failures running with Puppet Server, right? If so, might be better to move this over to the SERVER project. Eric Sorenson - I swear I've heard you talk about various problems we've seen in the past with upper-case characters in certnames but I've forgotten the details of that now. Any knowledge you can drop here? 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-1313) fqdn acceptance test failing on Solaris 11
Title: Message Title John Duarte updated an issue Facter / FACT-1313 fqdn acceptance test failing on Solaris 11 Change By: John Duarte QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1313) fqdn acceptance test failing on Solaris 11
Title: Message Title John Duarte updated an issue Facter / FACT-1313 fqdn acceptance test failing on Solaris 11 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 (FACT-1313) fqdn acceptance test failing on Solaris 11
Title: Message Title John Duarte updated an issue Facter / FACT-1313 fqdn acceptance test failing on Solaris 11 Change By: John Duarte QA Risk Assessment Reason: Covered by CI execution 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-5693) benchmark:function_loading aborts with stack overflow
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5693 benchmark:function_loading aborts with stack overflow Change By: Kylo Ginsberg Fix Version/s: PUP 4.3.2 Fix Version/s: PUP 4.3.3 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-5693) benchmark:function_loading aborts with stack overflow
Title: Message Title Kylo Ginsberg commented on PUP-5693 Re: benchmark:function_loading aborts with stack overflow I created a PUP 4.3.3 for this to indicate it can land on stable but shouldn't hold the 4.3.2 release. 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 Kylo Ginsberg updated an issue Puppet / PUP-5465 Resource Collectors cannot use resource references in search expressions Change By: Kylo Ginsberg Scope Change Reason: Straightforward community contribution so pulled it in while we were looking at 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-5465) Resource Collectors cannot use resource references in search expressions
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5465 Resource Collectors cannot use resource references in search expressions Change By: Kylo Ginsberg Scope Change Category: Adopted 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-5711) Uppercase characters in certname cause pain and suffering
Title: Message Title Brian Rak commented on PUP-5711 Re: Uppercase characters in certname cause pain and suffering This was with Puppet server, yea. Interestingly the client and server both partially handled it. I had to sign 'puppet cert sign puppetclient.meltbeforefailure.com', and the cert itself was all lowercase. I don't know exactly where the error lies. 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-5534) (Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in /environments/*/modules/*/files/*
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-5534 (Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in /environments/*/modules/*/files/* Change By: Eric Sorenson Summary: (Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in < environment codedir >/ environments/*/ modules/*/files/* 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-1313) fqdn acceptance test failing on Solaris 11
Title: Message Title John Duarte created an issue Facter / FACT-1313 fqdn acceptance test failing on Solaris 11 Issue Type: Bug Assignee: Unassigned Created: 2016/01/14 12:06 PM Priority: Normal Reporter: John Duarte On Solaris 11, the ticket_1238_hostname_fqdn.rb acceptance test is failing because Solaris returns from executing from a hostname command before having committed the given hostname. This is causing the validation of the fqdn fact given a hostname change to fail because the Solaris hostname command returns the old hostname. Additional time is required for the hostname command to return the updated hostname. root@sol11:~# hostname sol11 root@sol11:~# hostname foo.bar.example.org && hostname sol11
Jira (FACT-1313) fqdn acceptance test failing on Solaris 11
Title: Message Title John Duarte updated an issue Facter / FACT-1313 fqdn acceptance test failing on Solaris 11 Change By: John Duarte Scope Change Category: Found 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-1313) fqdn acceptance test failing on Solaris 11
Title: Message Title John Duarte updated an issue Facter / FACT-1313 fqdn acceptance test failing on Solaris 11 Change By: John Duarte Scope Change Reason: CI 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-5534) (Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in /modules/*/files/*
Title: Message Title
Eric Sorenson updated an issue
Puppet / PUP-5534
(Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in /modules/*/files/*
Change By:
Eric Sorenson
As a puppet node, I should only be able to retrieve historical file content for files which I have permission to access.Static Catalog1. local file has drifted. So we need to retrieve the right original file content that is consistent with the one we are applying2. auth part: removing implicit path expansion of {{puppet:///modules/mod_name/file_name}} urls to {{modules/mod_name/files/file_name}}. A valid client cert can access everything from any modules module's files directory. Make sure that as an unauthenticated connection cannot get file content. Also make sure you cannot cause a path traversal attack even with a valid client cert.
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-5693) benchmark:function_loading aborts with stack overflow
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-5693 benchmark:function_loading aborts with stack overflow 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 (PDB-2321) (maint) stop deleting unassociated report statuses
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2321 (maint) stop deleting unassociated report statuses Change By: Wyatt Alt Scope Change Category: Adopted Scope Change Reason: very easy fix, issue came up in conversation 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-5708) Deprecate pluginsync setting
Title: Message Title Josh Cooper created an issue Puppet / PUP-5708 Deprecate pluginsync setting Issue Type: Task Assignee: Unassigned Created: 2016/01/14 8:38 AM Priority: Normal Reporter: Josh Cooper The pluginsync setting should be deprecated and instead the behavior of pluginsyncing or not should be based on whether we are applying a cached catalog or not. Otherwise, the catalog and plugins can be consistent. For example, the catalog may contain a new property that the older pluginsync'ed type (lib/puppet/type/foo.rb) doesn't know about. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-1974) Mechanism for securing sensitive catalog data
Title: Message Title Henrik Lindberg commented on PUP-1974 Re: Mechanism for securing sensitive catalog data Before deciding exactly what needs to be done - lets look at the problem with what we need to keep track of. A scrub of all logging is probably going to reveal that there are several layers of indirection before something is logged (that plus what is logged at the surface level inside a Resource). That means we will have plain old strings, ints etc that are being processed at some point in the logic, then logged if something is amiss. The next problem is that there will be processing of values that are derived from a sensitive value - say something like "to_lower" on a String. In a ideal solution every value would have a security attribute. I explored if we could perhaps use the Ruby "taint mechanism" to flag particular objects; but it works in reverse to what we want i.e. it gives the ability to reject processing of tainted things, and you can untaint. Everything read with a gets/read is considered tainted. In the infinite wisdom of the Ruby designers, you cannot however taint numbers. Thus, to be able to mark numbers as sensitive these classes have to be monkeypatched, or wrapped, or we need to create derived classes that we use to represent the runtime values. This means having to override all operations since secure(1) + number(2) should yield secure(3). Needless to say, that will be a bit of an effort and will have performance impact. If we do not do this on the individual value level, and instead set just a sensitive meta parameter, then we could perhaps construct a derived SensitiveResource instead of just a Resource as that would give opportunity to deal with resource specific methods. Otherwise we probably need to sprinkle the Resource (and provider code) with lots of is_sensitive? calls. This also seems like a lot of work, and potentially require changes to every type/provider. Next idea is to use a Secure[T, C, placebo] wrapper, where T is the wrapped type and C is a krypto/key reference say "node" to encrypt for the requesting node, and placebo is a replacement value to show instead of the real value, the placebo must be a valid instance of T (i.e. "*" for a password, '' for an int, etc.), if undef is a valid value, then naturally that can be used (and is perhaps the default for placebo). We cannot include this in a catalog given the current catalog format (every data type possible in say yaml, are already taken). What we can do is to add a top level attribute in the catalog called sensitive_resources (next to the existing resource). When we deserialize this, we post process the yaml to construct Resource (or SensitiveResource depending on what we decide is the best) instances and then set the values as Secure|[T, C, placebo] instances. A Secure[T, C, placebo] is serialized with an encrypted real value, and the type, and placebo values in clear text. An operation on the secure instance allows it to be operated on in real value mode. We still need to review code, but by using another runtime value, it is easier to find all places where the actual value is operated on, then we know all the places where we have to present an unencrypted value; when we do so, we can shift to a global "secure mode" that will prevent logging. To be completely secure we would need to make some monkey patches to stdout/stderr etc. but that may break too much. It may be enough to change logging to a different mode (maybe when entering the protected mode, we keep track of the secure instances, and when
Jira (PUP-5120) Send checksum_value and static_catalog query params in catalog request
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-5120
Send checksum_value and static_catalog query params in catalog request
Change By:
Josh Cooper
Currently, when the agent applies a catalog, it sends a {{file_metadata}} request for each file resource along with the {{checksum_type}} that the master should use to compute the checksum. The {{checksum_type}} originates in either the manifest (and preserved in the catalog), or if none was specified, the agent's default {{Puppet\[:digest_algorithm\]}}.When static catalogs are enabled, the file metadata inlining process will need to choose a digest algorithm if none is specified in the manifest. To ensure the master chooses a checksum suitable for the agent, the agent needs to send its desired checksum in the catalog request as a request parameter. The value should either be the value of {{Puppet\[:digest_algorithm\]}} or it should be an ordered list of algorithms the agent supports. The only reason for choosing the latter is for future proofing, and in the case where the agent's default is not supported by the master, which seems highly unlikely.See PUP-1840 for background. Also, 4.4 client should always request a static catalog by sending {{static_catalog=true}} query parameter. The server will decide (based on PUP-5694) whether to build a static catalog. As part of this ticket, update the catalog API docs.
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-5708) Deprecate pluginsync setting
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5708 Deprecate pluginsync setting Change By: Josh Cooper Sprint: Client 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 (PDB-2322) (maint) Fix broken export test with a semver error message
Title: Message Title gepetto-bot updated an issue PuppetDB / PDB-2322 (maint) Fix broken export test with a semver error message Change By: gepetto-bot Sprint: PuppetDB 2016-01-27 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-2322) (maint) Fix broken export test with a semver error message
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2322 (maint) Fix broken export test with a semver error message Issue Type: Bug Assignee: Unassigned Created: 2016/01/14 1:48 PM Priority: Normal Reporter: gepetto-bot This commit fixes a broken export test by using the PuppetDB extensions handlers to standup a PDB instead of the FOSS handlers. This is because the extensions handlers don't turn on the trapperkeeper-status service which pukes in Jenkins do to lein-voom/maven version incompatibility. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5712) TypeParser cannot handle negative numbers
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-5712 TypeParser cannot handle negative numbers Issue Type: Bug Assignee: Thomas Hallgren Created: 2016/01/14 2:08 PM Priority: Normal Reporter: Thomas Hallgren The Puppet::Pops::Types::TypeParser used when parsing dispatch declarations for a puppet functions written in Ruby is not capable of parsing negative numbers. It is therefor not possible to define a dispatch with a parameter with a like Integer[default,-1]. The regular parser does not have this problem however so puppet apply -e 'Integer[default,-1]' executes without errors. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5712) TypeParser cannot handle negative numbers
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-5712
TypeParser cannot handle negative numbers
Change By:
Thomas Hallgren
The {{Puppet::Pops::Types::TypeParser}} used when parsing dispatch declarations for a puppet functions written in Ruby is not capable of parsing negative numbers. It is therefor therefore not possible to define a dispatch with a parameter with a type like {{Integer\[default,-1\]}}. The regular parser does not have this problem however so {{puppet apply -e 'Integer\[default,-1\]'}} executes without errors.
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.
