Jira (PUP-7777) Append "source_permissions=use" to 3.x file_metadata requests
Title: Message Title Jeremy Barlow assigned an issue to Unassigned Puppet / PUP- Append "source_permissions=use" to 3.x file_metadata requests Change By: Jeremy Barlow Assignee: Jeremy Barlow Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7647) All Puppet components should support SCEP
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-7647 All Puppet components should support SCEP Change By: Jeremy Barlow Component/s: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7737) Add HTTP report processor setting for including system truststore
Title: Message Title Jeremy Barlow created an issue Puppet / PUP-7737 Add HTTP report processor setting for including system truststore Issue Type: Task Assignee: Unassigned Created: 2017/06/27 5:22 PM Priority: Normal Reporter: Jeremy Barlow This ticket is dependent upon the work being discussed in SERVER-1543 and PUP-5069 to enhance Puppet::Network::HttpPool with configurable support for setting whether or not the "system" truststore should be included for HTTP client requests. For this ticket, we would introduce a new Puppet setting that the HTTP report processor would use to control how the corresponding HttpPool setting is configured. We'll need to decide what the default for the setting would be. As Charlie Sharpsteen argued in this comment in SERVER-1543, it may make set to set this to "true" by default to make it easier for users to use the HTTP report processor with an externally hosted receiver which is using a cert issued outside of Puppet's PKI, e.g., on a public AWS instance. Defaulting to "true" may constitute a security risk for users accustomed to only having the Puppet PKI cert bundle used. Add Comment
Jira (PDB-3558) Update puppetdb-termini 5 package to dep on puppet-agent >= 5
Title: Message Title Jeremy Barlow commented on PDB-3558 Re: Update puppetdb-termini 5 package to dep on puppet-agent >= 5 >= 4.99.0 or greater appears to work fine for each of the OSes we package for puppetserver. I put up a puppetserver PR here: https://github.com/puppetlabs/puppetserver/pull/1431. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3558) Update puppetdb-termini 5 package to dep on puppet-agent >= 5
Title: Message Title Jeremy Barlow commented on PDB-3558 Re: Update puppetdb-termini 5 package to dep on puppet-agent >= 5 Geoff Nichols, I'm doing some testing with that right now with puppetserver packages. I can confirm that our CI would blow up if we tried to pin puppetserver's dependency on puppet-agent to >= 5.0.0, as Moses Mendoza had suspected. >= 4.9.9 might work fine with current packages, though. I'll do a little more testing with that as a sanity check. If it works, I'll get a PR up for that today. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6708) Agent does not save local copy of last_run_report.yaml if submission to report server fails
Title: Message Title Jeremy Barlow commented on PUP-6708 Re: Agent does not save local copy of last_run_report.yaml if submission to report server fails This one came up again in a recent puppetserver acceptance test run, here: 20:34:20 * master_field should not appear when no master could be conatacted 20:34:20 20:34:20 rus6ehbzrplkj51.delivery.puppetlabs.net (redhat6-32-2) 03:34:20$ puppet agent -t --config /tmp/puppet_conf_test.vM9ww0 --server_list=badmaster:1 --http_connect_timeout=5s --report_server=f9sy80hlxm12sz1.delivery.puppetlabs.net 20:34:20 Warning: Could not select a functional puppet master 20:34:22 Warning: Unable to fetch my node definition, but the agent run will continue: 20:34:27 Warning: execution expired 20:34:27 Info: Retrieving pluginfacts 20:34:27 Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': execution expired 20:34:32 Error:
Jira (PUP-7657) Providers requiring files in other modules might cause intermittent compilation failures
Title: Message Title Jeremy Barlow commented on PUP-7657 Re: Providers requiring files in other modules might cause intermittent compilation failures Henrik Lindberg just responding to the ping from earlier. It seems like in order for the file containing the Puppet::Provider::Nova class to be able to resolve the puppet/provider/openstack require without using a fully-qualified path that a plugin sync of the openstack module would have needed to happen. The pluginsync might explain why in this case that the problem only seemed to happen during the first agent run. In any event, I agree with you that it would seem best to avoid having any of the provider code be sourced during compilation on the master since it seems like that code should only run client side. Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3558) Update puppetdb-termini 5 package to dep on puppet-agent >= 5
Title: Message Title Jeremy Barlow commented on PDB-3558 Re: Update puppetdb-termini 5 package to dep on puppet-agent >= 5 I think for interim CI we'd be okay there, though, right? Currently, we pin puppet-agent to >= 1.6.0 but install a SHA version of puppet-agent during CI runs. The package managers all seem to (dumbly?) tolerate that okay. If we bump the pin to 5.0.0, I was thinking we'd see the same behavior. It'd just mean that we couldn't test those with an older released version of puppet-agent but not sure if we care about that for Puppet 5-based builds in CI at present. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3558) Update puppetdb-termini 5 package to dep on puppet-agent >= 5
Title: Message Title Jeremy Barlow commented on PDB-3558 Re: Update puppetdb-termini 5 package to dep on puppet-agent >= 5 Moses Mendoza, our puppetserver packages do already have a minimum puppet-agent version pin, although it is still set to 1.6.0 or newer today, not 5.0.0. See here for RedHat and here for Debian. I assumed it was a given that we were going to update puppetserver to require puppet-agent 5.0. I'll create a ticket now to remind us to do that before we do our release - thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7652) Update catalog_uuid acceptance test for Ruby yaml serialization changes
Title: Message Title Jeremy Barlow commented on PUP-7652 Re: Update catalog_uuid acceptance test for Ruby yaml serialization changes Puppet tests are still passing in the puppet-agent pipeline following this change so I'm going to mark this resolved. Will reopen if any issues reappear in future JRuby 9k pipeline runs. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7654) Upgrade to puppet5-nightly: undefined method `key_attributes' for nil:NilClass
Title: Message Title Jeremy Barlow commented on PUP-7654 Re: Upgrade to puppet5-nightly: undefined method `key_attributes' for nil:NilClass Moses Mendoza - I seem to recall that you might have run into this error recently. Did you dig into it any further? Where this appears to be in the puppetdb terminus code, maybe Russell Mull has some thoughts on this? 2017-06-13 03:48:21,920 ERROR [qtp752600666-66] [puppetserver] Puppet undefined method `key_attributes' for nil:NilClass /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/catalog/puppetdb.rb:222:in `add_namevar_aliases' org/jruby/RubyArray.java:1613:in `each' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/catalog/puppetdb.rb:213:in `add_namevar_aliases' ... If this hasn't been done already, I think it would be good to update all three packages - puppet-agent, puppetserver, and puppetdb - to their latest puppet5_nightly versions and restart the puppetserver and puppetdb services (if not reboot the node). I'm not sure if this issue has something to do with an older PuppetDB terminus running with incompatible / newer puppet-agent code. Add Comment
Jira (PUP-7652) Update catalog_uuid acceptance test for Ruby yaml serialization changes
Title: Message Title Jeremy Barlow commented on PUP-7652 Re: Update catalog_uuid acceptance test for Ruby yaml serialization changes Josh Cooper discovered that the change in behavior was done intentionally in the newer version of psych in order to support a new feature in YAML 1.2, where a value with a leading 0 like 03... could be implicitly interpreted as a float unless wrapped in single quotes. This explains why we were only seeing the quotes with the 0308... string but not with the caaf... string in Ruby 2.3.2++ and JRuby 9k. See: https://bugs.ruby-lang.org/issues/11988 https://github.com/ruby/psych/commit/b737f0811a9687cf86f44f0a35f61cbde9eac673 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7652) Update catalog_uuid acceptance test for Ruby yaml serialization changes
Title: Message Title Jeremy Barlow assigned an issue to Jeremy Barlow Puppet / PUP-7652 Update catalog_uuid acceptance test for Ruby yaml serialization changes Change By: Jeremy Barlow Assignee: Jeremy Barlow Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7652) Update catalog_uuid acceptance test for Ruby yaml serialization changes
Title: Message Title Jeremy Barlow created an issue Puppet / PUP-7652 Update catalog_uuid acceptance test for Ruby yaml serialization changes Issue Type: Task Assignee: Unassigned Created: 2017/06/12 10:29 AM Fix Versions: PUP 5.0.0 Priority: Normal Reporter: Jeremy Barlow The "catalog_uuid_correlates_catalogs_with_reports" test inspects the serialized content of the "catalog_uuid" field in the Puppet::Transaction::Report that the master stores. The test expects the value for the "catalog_uuid" field to not be quoted. With MRI Ruby 2.3.2 and later (and with JRuby 9.1.9.0, which emulates Ruby language version 2.3.3), some string-based UUID values are serialized to yaml with single quotes around them. On Ruby 2.3.1, for example, the following value is serialized without any surrounding quotes: › ruby -ryaml -e "puts '03080442-0449-43cb-8ec2-f26658f958ac'.to_yaml" --- 03080442-0449-43cb-8ec2-f26658f958ac
Jira (PUP-3486) Update jetty_external_root_ca acceptance test to use disabled CA service
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3486 Update jetty_external_root_ca acceptance test to use disabled CA service Change By: Jeremy Barlow Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6123) remove ruby code that backs resource_type endpoint
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-6123 remove ruby code that backs resource_type endpoint Change By: Jeremy Barlow Release Notes Summary: The HTTP resource_type and resource_types endpoints and the resource_type puppet command line face have been removed. The environment_classes HTTP endpoint in Puppet Server replaces a subset of the resource_type functionality, including name and parameter metadata for classes. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6123) remove ruby code that backs resource_type endpoint
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-6123 remove ruby code that backs resource_type endpoint Change By: Jeremy Barlow Release Notes Summary: The HTTP resource_type and resource_types endpoints and the resource_type puppet command line face have been removed. Release Notes: Deprecation Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6359) Completely remove allow/deny rules from fileserver.conf syntax
Title: Message Title Jeremy Barlow commented on PUP-6359 Re: Completely remove allow/deny rules from fileserver.conf syntax Passed through latest puppet master component pipeline run here. puppet-agent master suite with code from this PR is still pending. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7628) Cannot run puppet commands or startup master when environment directory missing
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-7628 Cannot run puppet commands or startup master when environment directory missing Change By: Jeremy Barlow Sprint: Server 2017-07-26 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7628) Cannot run puppet commands or startup master when environment directory missing
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-7628 Cannot run puppet commands or startup master when environment directory missing Change By: Jeremy Barlow Summary: Cannot provision compile masters outside production run puppet commands or startup master when environment directory missing Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7628) Cannot provision compile masters outside production environment
Title: Message Title Jeremy Barlow moved an issue Puppet / PUP-7628 Cannot provision compile masters outside production environment Change By: Jeremy Barlow Affects Version/s: PE 2017.2.1 Component/s: puppet Component/s: Puppet Server Key: PE PUP - 20873 7628 Project: Puppet Enterprise [Internal] Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this
Jira (PUP-7628) Cannot provision compile masters outside production environment
Title: Message Title Jeremy Barlow commented on PUP-7628 Re: Cannot provision compile masters outside production environment Thanks, Dylan Ratcliffe. That makes sense. Given that this issue spans more conditions than just the startup of a Puppet master - e.g., various puppet CLI commands - I moved this ticket over to the PUP project for better visibility across the platform teams - and for open-source users. The ticket is now PUP-7628. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3551) Sanitize non-UTF-8 data in run reports
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3551 Sanitize non-UTF-8 data in run reports Change By: Jeremy Barlow Component/s: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6359) Completely remove allow/deny rules from fileserver.conf syntax
Title: Message Title Jeremy Barlow commented on PUP-6359 Re: Completely remove allow/deny rules from fileserver.conf syntax Earlier, Josh Cooper, wrote that as part of this work we should: Update the default auth.conf to only allow find/search for file_content and file_metadata, and find/search/save for file_bucket_file. Probably don't want to grant delete since file_bucket_file doesn't implement that method. The other method I think we need to continue allowing for file_bucket_file is head. Also, it doesn't appear to me that either file_content or file_bucket_file actually implement search, so we could probably leave that off too - although allowing access for it probably wouldn't hurt anything. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7555) Update default fileserver.conf that allow/deny are no longer allowed
Title: Message Title Jeremy Barlow assigned an issue to Jeremy Barlow Puppet / PUP-7555 Update default fileserver.conf that allow/deny are no longer allowed Change By: Jeremy Barlow Assignee: Jeremy Barlow Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6359) Completely remove allow/deny rules from fileserver.conf syntax
Title: Message Title Jeremy Barlow commented on PUP-6359 Re: Completely remove allow/deny rules from fileserver.conf syntax What do you think we should do in the case where an auth rule doesn't have any allow or deny directives? I went ahead and worked up an implementation which treats the absence of any security directives as though allow * were implicitly specified. I was thinking that through the PR discussion, we can hack through whether we think that's the right approach or not. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6359) Completely remove allow/deny rules from fileserver.conf syntax
Title: Message Title Jeremy Barlow commented on PUP-6359 Re: Completely remove allow/deny rules from fileserver.conf syntax So it might be better to only fail the request if there is a deny directive or an allow directive for something other than *. Josh Cooper, that sounds reasonable to me. What do you think we should do in the case where an auth rule doesn't have any allow or deny directives. For example, let's say the fileserver.conf file had this: [pe_packages] path /opt/puppetlabs/server/data/packages/public [pe_modules] path /opt/puppetlabs/server/share/installer/modules Today, any request to access either of the mount points would be denied. For Puppet 5, would you think the behavior should implicitly change to act like allow * instead? Assuming we're eventually intending to eliminate all use of the auth directives from the fileserver.conf file, I think this would make sense – although it could arguably be construed as a security issue if access to some mount points that had not previously been denied by auth.conf rules at a higher level started to be granted to all users after upgrading to Puppet 5. Add Comment
Jira (PUP-6359) Completely remove allow/deny rules from fileserver.conf syntax
Title: Message Title Jeremy Barlow assigned an issue to Jeremy Barlow Puppet / PUP-6359 Completely remove allow/deny rules from fileserver.conf syntax Change By: Jeremy Barlow Assignee: Jeremy Barlow Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7555) Update default fileserver.conf that allow/deny are no longer allowed
Title: Message Title Jeremy Barlow assigned an issue to Unassigned Puppet / PUP-7555 Update default fileserver.conf that allow/deny are no longer allowed Change By: Jeremy Barlow Assignee: Jeremy Barlow Sub-team: Server Team: Agent Systems Engineering Sprint: Puppet 5 Race to the Finish! Server 2017-06-14 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to 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-6359) Completely remove allow/deny rules from fileserver.conf syntax
Title: Message Title Jeremy Barlow assigned an issue to Unassigned Puppet / PUP-6359 Completely remove allow/deny rules from fileserver.conf syntax Change By: Jeremy Barlow Assignee: Jeremy Barlow Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6359) Completely remove allow/deny rules from fileserver.conf syntax
Title: Message Title Jeremy Barlow commented on PUP-6359 Re: Completely remove allow/deny rules from fileserver.conf syntax Update the fileserver parser to ignore allow/deny rules in fileserver.conf (this ticket). An open issue is whether to warn or fail to start, since ignoring the rules could be a security issue. Josh Cooper indicated that in a follow-up meeting, various folks expressed a preference for having any individual request which tries to use a mount point protected by an allow/deny in the fileserver.conf fail - as opposed to failing the ability to startup the service. This seems reasonable to me. /CC Eric Sorenson in the event you have any difference of opinion here before we do this work. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6359) Completely remove allow/deny rules from fileserver.conf syntax
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-6359 Completely remove allow/deny rules from fileserver.conf syntax Change By: Jeremy Barlow Sub-team: Server Team: Agent Systems Engineering Sprint: Puppet 5 Race to the Finish! Server 2017-06-14 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6359) Completely remove allow/deny rules from fileserver.conf syntax
Title: Message Title Jeremy Barlow commented on PUP-6359 Re: Completely remove allow/deny rules from fileserver.conf syntax Update comments in the default puppet fileserver.conf that talks about permissions to direct users to ruby auth.conf or tk-auth (PUP-TBD) Update the fileserver parser to ignore allow/deny rules in fileserver.conf (this ticket). An open issue is whether to warn or fail to start, since ignoring the rules could be a security issue. I'd be fine with having both of the above be done as part of this ticket, if others are. If we're going to break (by ignoring) the ability to deny some users via a fileserver.conf rule, I think I'd be in favor of having the server fail to start if an allow directive is found in a fileserver.conf rule. Letting the server continue to run in this state would seem bad from a security perspective since users could easily just ignore the warning. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-849) puppetdb install from source after rake package:boostrap RuntimeError
Title: Message Title Jeremy Barlow updated an issue PuppetDB / PDB-849 puppetdb install from source after rake package:boostrap RuntimeError Change By: Jeremy Barlow Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-849) puppetdb install from source after rake package:boostrap RuntimeError
Title: Message Title Jeremy Barlow commented on PDB-849 Re: puppetdb install from source after rake package:boostrap RuntimeError Thanks for reporting this issue. However, we haven’t been able to reproduce this against the current version of Puppet, and are closing this issue now as Cannot Reproduce. If you have additional information or reproduction scenarios that may be of use, please comment in this ticket with details. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-558) Design: PuppetDB should support granular access control for queries
Title: Message Title Jeremy Barlow updated an issue PuppetDB / PDB-558 Design: PuppetDB should support granular access control for queries Change By: Jeremy Barlow Labels: tiraged triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-532) Consider making zach's 'exports' tool part of the terminus core
Title: Message Title Jeremy Barlow updated an issue PuppetDB / PDB-532 Consider making zach's 'exports' tool part of the terminus core Change By: Jeremy Barlow Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-532) Consider making zach's 'exports' tool part of the terminus core
Title: Message Title Jeremy Barlow commented on PDB-532 Re: Consider making zach's 'exports' tool part of the terminus core We now have a PuppetDB query CLI which should provide this functionality so this should no longer be needed. Closing this as "Won't Do". Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-513) Add disk space requirements to sys req page
Title: Message Title Jeremy Barlow updated an issue PuppetDB / PDB-513 Add disk space requirements to sys req page Change By: Jeremy Barlow Labels: Deluxe PE_3.x triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3135) Square brackets in file names not handled properly
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3135 Square brackets in file names not handled properly Change By: Jeremy Barlow Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3135) Square brackets in file names not handled properly
Title: Message Title
Jeremy Barlow commented on PUP-3135
Re: Square brackets in file names not handled properly
I reproduced this issue with just a 'puppet apply' - no puppetserver involved - on a recent Puppet 5 nightly build. The manifest had:
file {'bracket_test':
path => '/tmp/hello.txt',
ensure => file,
source => 'puppet://puppet_data_development/[',
source_permissions => ignore,
}
The error I saw for the puppet apply was:
Error: Parameter source failed on File[bracket_test]: Could not understand source puppet://puppet_data_development/[: bad URI(is not URI?): puppet://puppet_data_development/[ at /root/somefile.pp:1
Jira (PUP-3230) Exported resource collectors don't support standard puppet expression set
Title: Message Title Jeremy Barlow commented on PUP-3230 Re: Exported resource collectors don't support standard puppet _expression_ set Trevor Vaughan - it was probably premature for us to close this one out, thanks for asking. There is some more general conversation happening now on PUP-7541 about the possibility of removing explore / collect / virtual / realize syntax in a future release. It may be better to hash through that conversation first before closing the door on this one completely. Moving this back to "Accepted" for now, /CC Eric Sorenson. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3141) PMT module list gives inaccurate warning message when module has bad semver
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3141 PMT module list gives inaccurate warning message when module has bad semver Change By: Jeremy Barlow Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3138) improve spec functions "produces" and "fails" in language.rb
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3138 improve spec functions "produces" and "fails" in language.rb Change By: Jeremy Barlow Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3145) pkgdmg.rb should report timeout failure if destination is not reachable
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3145 pkgdmg.rb should report timeout failure if destination is not reachable Change By: Jeremy Barlow Labels: needs_repro triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3145) pkgdmg.rb should report timeout failure if destination is not reachable
Title: Message Title Jeremy Barlow commented on PUP-3145 Re: pkgdmg.rb should report timeout failure if destination is not reachable Without trying to reproduce this error, I expect that the resulting message would still be the same. It does appear, however, that support for the NO_PROXY variable should be in place now per PUP-4030 . Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3145) pkgdmg.rb should report timeout failure if destination is not reachable
Title: Message Title
Jeremy Barlow updated an issue
Puppet / PUP-3145
pkgdmg.rb should report timeout failure if destination is not reachable
Change By:
Jeremy Barlow
If pkgdmg.rb is not able to open the URL to the specified package for download, it currently reports that the file is not found. It would be better if it would report a timeout failure instead, which is more descriptive. I trapped into that and didn't know what was going on given that the file was really present.So as best configure a proxy and have the package located at a URL which is not served by the proxy (no_proxy environment variable). There is currently a bug in puppet, which doesn't pick up this env variable. So Puppet will assume all URLs have to be reached through the proxy. Now try to install a package from that location. Curl will start but will run into a timeout.You will see a failure like: {noformat} Error: Could not set 'present' on ensure: No such file or directory -http://puppetmaster1.qa.scl3.mozilla.com/repos/DMGs/facter-2.0.2.dmg at38:/etc/puppet/production/modules/packages/manifests/pkgdmg.ppError: Could not set 'present' on ensure: No such file or directory -http://puppetmaster1.qa.scl3.mozilla.com/repos/DMGs/facter-2.0.2.dmg at38:/etc/puppet/production/modules/packages/manifests/pkgdmg.ppWrapped exception:No such file or directory -http://puppetmaster1.qa.scl3.mozilla.com/repos/DMGs/facter-2.0.2.dmgError:/Stage[main]/Packages::Puppet/Packages::Pkgdmg[facter]/Package[facter-2.0.2.dmg]/ensure:change from absent to present failed: Could not set 'present' on ensure: Nosuch file or directory -http://puppetmaster1.qa.scl3.mozilla.com/repos/DMGs/facter-2.0.2.dmg at38:/etc/puppet/production/modules/packages/manifests/pkgdmg.pp {noformat} For details about my original bug have a look at https://bugzilla.mozilla.org/show_bug.cgi?id=1053437.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-3152) If zone creation fails with an assigned dataset, the dataset can not be reused
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3152 If zone creation fails with an assigned dataset, the dataset can not be reused Change By: Jeremy Barlow Labels: needs_repro triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3159) Module tool generate does not use skeleton when run as root
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3159 Module tool generate does not use skeleton when run as root Change By: Jeremy Barlow Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3159) Module tool generate does not use skeleton when run as root
Title: Message Title Jeremy Barlow commented on PUP-3159 Re: Module tool generate does not use skeleton when run as root Thank you for filing this issue. We agree it is likely an improvement, but due to other issues demanding precedence, we don’t anticipate being able to address this any time soon. If you are interested in submitting a patch to the repository for this project at https://github.com/puppetlabs, please open a pull request and re-open this ticket. Pending that, we are closing this as “Won’t Fix.” We may revisit it at a later time, and if so will re-open this ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3169) Puppet::Util::Execution.execpipe does not allow to write to the pipe
Title: Message Title Jeremy Barlow commented on PUP-3169 Re: Puppet::Util::Execution.execpipe does not allow to write to the pipe Thank you for filing this issue. We agree it is likely an improvement, but due to other issues demanding precedence, we don’t anticipate being able to address this any time soon. If you are interested in submitting a patch to the repository for this project at https://github.com/puppetlabs/puppet, please open a pull request and re-open this ticket. Pending that, we are closing this as “Won’t Fix.” We may revisit it at a later time, and if so will re-open this ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3185) A puppet-passenger master fails with cryptic message for default directory environment setup with non-existent production directory.
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3185 A puppet-passenger master fails with cryptic message for default directory environment setup with non-existent production directory. Change By: Jeremy Barlow Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3185) A puppet-passenger master fails with cryptic message for default directory environment setup with non-existent production directory.
Title: Message Title Jeremy Barlow commented on PUP-3185 Re: A puppet-passenger master fails with cryptic message for default directory environment setup with non-existent production directory. Thank you for reporting this issue. However, we believe this issue only affects a feature in Puppet that is deprecated, the use of a puppet-passenger master, and is no longer receiving further improvements. As such we are closing this as “Won’t Fix.” Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3230) Exported resource collectors don't support standard puppet expression set
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3230 Exported resource collectors don't support standard puppet _expression_ set Change By: Jeremy Barlow Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3230) Exported resource collectors don't support standard puppet expression set
Title: Message Title Jeremy Barlow commented on PUP-3230 Re: Exported resource collectors don't support standard puppet _expression_ set Thank you for filing this issue. However, we believe this change represents a technical direction that we have decided not to follow in Puppet. As such, we are closing this as “Won’t Do”. If any watcher believes this is an error, please add a comment explaining Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3252) Regenerate man pages automatically
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3252 Regenerate man pages automatically Change By: Jeremy Barlow Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3309) puppet master --compile should be able to source facts from master inventory service
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3309 puppet master --compile should be able to source facts from master inventory service Change By: Jeremy Barlow Labels: catalog compile master needs_decision puppet puppetdb triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3316) When loading dynamic environments, ignore directories on EACCESS (with a logged warning) rather than bomb out
Title: Message Title Jeremy Barlow commented on PUP-3316 Re: When loading dynamic environments, ignore directories on EACCESS (with a logged warning) rather than bomb out Thanks for reporting this issue. However, we haven’t been able to reproduce this against the current version of Puppet, and are closing this issue now as Cannot Reproduce. The behavior may have changed at one point to reflect what we now see with SERVER-1717. If you have additional information or reproduction scenarios that may be of use, please comment in this ticket with details. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3321) config set adds a preceding newline to value if previous value was empty
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3321 config set adds a preceding newline to value if previous value was empty Change By: Jeremy Barlow Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3332) There should be a value? method to compliment the value and value= methods in properties
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3332 There should be a value? method to compliment the value and value= methods in properties Change By: Jeremy Barlow Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3368) nagios_contact no longer is able to parse utf-8 from nagios config files
Title: Message Title Jeremy Barlow commented on PUP-3368 Re: nagios_contact no longer is able to parse utf-8 from nagios config files Thanks for reporting this issue. However, we haven’t been able to reproduce this against the current version of Puppet on Ubuntu 14.04, and are closing this issue now as Cannot Reproduce. If you have additional information or reproduction scenarios that may be of use, please comment in this ticket with details. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3368) nagios_contact no longer is able to parse utf-8 from nagios config files
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3368 nagios_contact no longer is able to parse utf-8 from nagios config files Change By: Jeremy Barlow Labels: encoding naginator nagios triaged utf-8 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3375) File Diffs on Windows
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3375 File Diffs on Windows Change By: Jeremy Barlow Labels: triaged windows Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3386) Puppet Module Gem Dependency Metadata and Installation
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3386 Puppet Module Gem Dependency Metadata and Installation Change By: Jeremy Barlow Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3426) Exit code 2 being used for successful completion without errors
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3426 Exit code 2 being used for successful completion without errors Change By: Jeremy Barlow Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3432) More verbose logging on invalid parameters
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3432 More verbose logging on invalid parameters Change By: Jeremy Barlow Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3447) instances & mk_resource_methods is "undocumented" (not rendered)
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3447 instances & mk_resource_methods is "undocumented" (not rendered) Change By: Jeremy Barlow Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3452) Replace check for deprecated types in Puppet::Resource with more robust method method of emitting deprecation warnings
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3452 Replace check for deprecated types in Puppet::Resource with more robust method method of emitting deprecation warnings Change By: Jeremy Barlow Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3459) reports directory should have group write permissions and be setgid
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3459 reports directory should have group write permissions and be setgid Change By: Jeremy Barlow Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3466) Puppet should warn when it can not read a hiera data file
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3466 Puppet should warn when it can not read a hiera data file Change By: Jeremy Barlow Labels: SELinux debug hiera needs_repro output puppet triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3482) server-side only execution stub
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3482 server-side only execution stub Change By: Jeremy Barlow Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3483) Systemd provider doesn't scan for changed units
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3483 Systemd provider doesn't scan for changed units Change By: Jeremy Barlow Labels: systemd triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3486) Update jetty_external_root_ca acceptance test to use disabled CA service
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3486 Update jetty_external_root_ca acceptance test to use disabled CA service Change By: Jeremy Barlow Labels: maintenance triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3489) $confdir/environments/production is cached on startup even if not in configured environmentpath
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3489 $confdir/environments/production is cached on startup even if not in configured environmentpath Change By: Jeremy Barlow Labels: needs_repro triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3493) Error: Could not retrieve catalog from remote server: Could not intern from
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3493 Error: Could not retrieve catalog from remote server: Could not intern from Change By: Jeremy Barlow Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3493) Error: Could not retrieve catalog from remote server: Could not intern from
Title: Message Title Jeremy Barlow commented on PUP-3493 Re: Error: Could not retrieve catalog from remote server: Could not intern from Thanks for reporting this issue. However, we haven’t been able to reproduce this against the current version of Puppet, and are closing this issue now as Cannot Reproduce. If you have additional information or reproduction scenarios that may be of use, please comment in this ticket with details. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3495) acceptance pre-suite package install method should accept short SHA
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3495 acceptance pre-suite package install method should accept short SHA Change By: Jeremy Barlow Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3496) Ability to set default provider or require `provider` to be set
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3496 Ability to set default provider or require `provider` to be set Change By: Jeremy Barlow Labels: help_wanted triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2646) Option to compress / limit /var/lib/puppet/reports
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-2646 Option to compress / limit /var/lib/puppet/reports Change By: Jeremy Barlow Summary: Option to compress / limit /var/lib/ puppetdb puppet /reports Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-5020) cron type requires double quotes for multiline command strings
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-5020 cron type requires double quotes for multiline command strings Change By: Jeremy Barlow Labels: triaged need Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-5011) Helper methods for enumerating manifest files in environments
Title: Message Title Jeremy Barlow commented on PUP-5011 Re: Helper methods for enumerating manifest files in environments The solution we've been using is sufficient for now. Closing this but could reopen later if we find a need to make any further optimizations. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7521) Puppet Acceptance Test Failure in Imaging Acceptance Tests
Title: Message Title Jeremy Barlow assigned an issue to Adrien Thebo Puppet / PUP-7521 Puppet Acceptance Test Failure in Imaging Acceptance Tests Change By: Jeremy Barlow Assignee: Jeremy Barlow Adrien Thebo Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7261) Add/Honor charset parameter in Content-Type header
Title: Message Title Jeremy Barlow commented on PUP-7261 Re: Add/Honor charset parameter in Content-Type header modify the type argument in Puppet::Network::HTTP::Response#respond_with that we pass on to set_content_type ? Moses Mendoza This ^ was what I was thinking, if that would work. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7261) Add/Honor charset parameter in Content-Type header
Title: Message Title Jeremy Barlow commented on PUP-7261 Re: Add/Honor charset parameter in Content-Type header Thanks, Josh Cooper. Another approach which might work without changing the signature of the method - and, therefore, presumably would avoid breaking newer Ruby Puppet code which tries to call into older Puppet Server code which doesn't have an implementation with the optional parameter - might be to flatten the Puppet::Network::Format type object which is passed into the format argument to set_content_type from HTTP::Response into a String instead - with the value being a concatenation of format_to_mime + "; charset=". It appears that the format_to_mime method would already roundtrip any string passed into it. If we went with this approach, I also think we wouldn't need to update the Rack or WEBrick HTTP handlers, which also implement the set_content_type method in their handlers and call back to format_to_mime to compute the value like Puppet Server does. What do you think? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-7198 Puppet Server uses facts from the previous run (n-1) after agent switches masters Change By: Jeremy Barlow Component/s: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7453) utf8 test failures after upgrading puppet pin
Title: Message Title Jeremy Barlow created an issue Puppet / PUP-7453 utf8 test failures after upgrading puppet pin Issue Type: CI Blocker Assignee: Unassigned Created: 2017/04/18 11:22 AM Priority: Normal Reporter: Jeremy Barlow After upgrading puppetserver's puppet pins to 8e8866b, we started experiencing failures for three Ruby Puppet acceptance tests: language.binary_data_type.rb utf8.utf8-in-catalog.rb file.ticket_6448_file_with_utf8_source.rb See this CI job link. In each case, it seems that the agent is somehow having issues handling UTF-8 bytes returned from the server. For example, the following error appears in the agent output for the utf8-in-catalog.rb test: RuntimeError: PuppetAcceptance::DSL::Helpers.with_puppet_running_on failed (check backtrace for location) because: Host 'b1nf7ehap0olkfb.delivery.puppetlabs.net' exited with 1 running:
Jira (PUP-6359) Completely remove allow/deny rules from fileserver.conf syntax
Title: Message Title Jeremy Barlow commented on PUP-6359 Re: Completely remove allow/deny rules from fileserver.conf syntax Josh Cooper - thanks for the additional research on this. I hadn't been aware of the code in the fileserver which hardcodes disallowing any request methods other than find or search. Are you proposing that we'd eventually remove that code as well - so that all authorization is controlled only at the auth.conf layer - or do you think the fallback denial in fileserver still has value? If we decide to issue warnings based on auth.conf rules which allow save/delete for file_content / file_metadata, we'll presumably need to do that both at the Ruby Puppet auth.conf layer and the Puppet Server / tk-auth layer. I'd prefer not to put this kind of logic directly into the tk-auth code itself - since it doesn't have any Puppet-specific knowledge in it. We could consider having some Clojure code living in Puppet Server try to parse the auth.conf rules and issue the warning although it is nice that, in today's code, code in Puppet Server doesn't have any direct responsibility for handling the auth.conf file parsing. We'd have to think through some approaches for how to do this. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6123) remove ruby code that backs resource_type endpoint
Title: Message Title Jeremy Barlow assigned an issue to Ruth Linehan Puppet / PUP-6123 remove ruby code that backs resource_type endpoint Change By: Jeremy Barlow Assignee: Ruth Linehan Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6359) Completely remove allow/deny rules from fileserver.conf syntax
Title: Message Title
Jeremy Barlow commented on PUP-6359
Re: Completely remove allow/deny rules from fileserver.conf syntax
Josh Cooper Puppet Server's use-legacy-auth-conf setting doesn't have any bearing on the use of auth rule evaluation per the fileserver.conf file.
When use-legacy-auth-conf is set to false, which would now be the default in Puppet 5 per
SERVER-1732
, Puppet Server configures auth config for Puppet::Network to essentially be a no-op but it doesn't do any reconfiguration per the fileserver.conf rule evaluation. So if you had a fileserver.conf mount point which used a "deny *" directive, use-legacy-auth-conf was set to false or not set at all, and the tk-auth rules allow access to the file* endpoints, you would still get a deny error for a request made to the mount point. From the agent side output, for example:
Error: /Stage[main]/Simmons::Mount_point_binary_file/File[mount-point-binary-file]: Could not evaluate: Could not retrieve file metadata for puppet:///simmons_custom_mount_point/mount-point-binary-file: Error 500 on SERVER: Server Error: Not authorized to call find on /file_metadata/simmons_custom_mount_point/mount-point-binary-file with {:rest=>"simmons_custom_mount_point/mount-point-binary-file", :links=>"manage", :checksum_type=>"md5", :source_permissions=>"ignore"}
Josh Cooper Given the above, do you still think we should warn in Puppet 4.x and fail to start for any fileserver.conf rules containing any auth directive, maybe other than "allow *", in Puppet 5+?
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6359) Completely remove allow/deny rules from fileserver.conf syntax
Title: Message Title Jeremy Barlow commented on PUP-6359 Re: Completely remove allow/deny rules from fileserver.conf syntax Geoff Nichols It may make sense to postpone removing support for allow/deny rules from fileserver.conf completely until whatever release we remove the underlying Ruby Puppet auth.conf code from, since the two have overlapping code paths. The latter isn't going to happen for Puppet 5.0. Maybe at this point it would be better to start logging warning/deprecation messages in Puppet 5.0 and tentatively plan to kill it along with the rest of Ruby auth.conf in Puppet 6.0. Open to other suggestions though. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3377) Bump puppetdb to use clj-parent 0.6 and tk-metrics 1.0.0
Title: Message Title Jeremy Barlow commented on PDB-3377 Re: Bump puppetdb to use clj-parent 0.6 and tk-metrics 1.0.0 clj-parent dependency bumped to 0.6.0 for puppetdb#master in bd1d368. Ticket marked resolved. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3640) Puppet 5.0 Changes
Title: Message Title Jeremy Barlow commented on PUP-3640 Re: Puppet 5.0 Changes Kenn Hussey Sounds good, thanks. I moved the ones I mentioned in my prior comment to different epics and post PUP 5.0.0 versions. Will defer to the Agent/Platform team as to what we want to do with the remaining tickets in this epic. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3834) remove webrick/rack support from Puppet
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3834 remove webrick/rack support from Puppet Change By: Jeremy Barlow Fix Version/s: PUP 5.0.0 Fix Version/s: PUP 6.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3640) Puppet 5.0 Changes
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3640 Puppet 5.0 Changes Change By: Jeremy Barlow Sub-team: Emerald Jade emerald jade Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3658) delete webserver-related settings from puppet.conf
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3658 delete webserver-related settings from puppet.conf Change By: Jeremy Barlow Fix Version/s: PUP 5.0.0 Fix Version/s: PUP 6.0.0 At present, it It sounds like we are planning to pull support for the old web servers in favor of Puppet Server in a future Puppet 5 release . 0. We should go through and remove all of the settings from puppet.conf that would have been related to the other servers but will no longer be used. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3640) Puppet 5.0 Changes
Title: Message Title Jeremy Barlow commented on PUP-3640 Re: Puppet 5.0 Changes Kenn Hussey No, there are a number of these that I'm not expecting to land for Puppet 5, including: PUP-3309 PUP-3648 PUP-3649 PUP-3658 SERVER-990 SERVER-594 I'd be happy to move all of those to Puppet / Server 5.y, it that makes sense, and drop them from this epic. There are a few others in here, though, that'd I'd defer to the Agent/Platform team to comment on: FACT-1573 PUP-6060 PUP-7184 PUP-7260 PUP-6959 Ping Geoff Nichols, Moses Mendoza, and Josh Cooper. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6697) Allow full downloaded CA bundle to be stored to agent's localcacert file
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-6697 Allow full downloaded CA bundle to be stored to agent's localcacert file Change By: Jeremy Barlow Sub-team: Server Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3788) Puppet Agent does not support Chained CRLs
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3788 Puppet Agent does not support Chained CRLs Change By: Jeremy Barlow Sub-team: Server Team: Systems Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6123) remove ruby code that backs resource_type endpoint
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-6123 remove ruby code that backs resource_type endpoint Change By: Jeremy Barlow Sub-team: Server Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6123) remove ruby code that backs resource_type endpoint
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-6123 remove ruby code that backs resource_type endpoint Change By: Jeremy Barlow Sprint: Server 2017-04-19 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
