Jira (PUP-9151) Schedule resource weekly behavior inconsistent with other periods
Title: Message Title Jo Rhett commented on PUP-9151 Re: Schedule resource weekly behavior inconsistent with other periods I feel like one of the complications with touching this type is that it's used the most by (A) people who don't understand the other declarative approaches and (B) Enterprises who have very specific time bucket constraints... which are the two markets least prepared for a change in behavior Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9151) Schedule resource weekly behavior inconsistent with other periods
Title: Message Title
Jo Rhett commented on PUP-9151
Re: Schedule resource weekly behavior inconsistent with other periods
As it happens, I have run into this I agree completely with his analysis of the problem. Weekly doesn't properly implement number only distance. I think I recall hacking up a patch for this and then realizing that the current spec is a bit unclear to start with. I believe that Henrik Lindberg looked at it and gave a similar concern: it's kind of hard to fix the type without breaking a lot of working (if idiomatic) implementations. I believe that the following schedule will meet his needs. Use a daily schedule with a weekday limiter, and he'll get the effect he wants.
schedule { 'friday_night':
period => 'daily',
range => '18:00 - 23:59',
weekday => 'Friday',
repeat => 1,
}
This isn't the first periodmatch => number bug we've seen and I think there's too much cruft in existence to just change the delivery outright. Eric Sorenson for your purposes this is a general backlog thing you need to tackle eventually. I think a clear, testable spec needs to be written. I think it should use a different specification formation so that people can migrate to the new spec without breaking many old catalogs. This specification should be deprecated and eventually removed.
Jira (PUP-8530) Remove trusted_server_facts setting
Title: Message Title Jo Rhett commented on PUP-8530 Re: Remove trusted_server_facts setting The line in the release notes is grammatically incorrect, as it says that trusted facts are deprecated. Trusted server facts are always enabled and have been deprecated since 5.0. The facts weren't deprecated, the config setting was. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-186) Comprehensive strings style guide
Title: Message Title Jo Rhett commented on PDOC-186 Re: Comprehensive strings style guide https://puppet.com/docs/puppet/latest/puppet_strings_style.html for watchers Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8631) --tags should override individual --skip_tags
Title: Message Title Jo Rhett created an issue Puppet / PUP-8631 --tags should override individual --skip_tags Issue Type: New Feature Affects Versions: PUP 5.5.0 Assignee: Unassigned Created: 2018/04/04 11:37 AM Priority: Normal Reporter: Jo Rhett Puppet Version: 4.4 through 5.5 and HEAD Puppet Server Version: n/a OS Name/Version: all We were extremely grateful to see skip_tags added as a configuration option. This has been tremendously useful. However in practice we've started to see problems when multiple teams make use of the tag for different purposes. Example: skip_tags = monitoring_changes,app_deploy These tags are used by two different teams to limit changes to things the other team are unaware of, and not responsible for managing. Desired Behavior: If tags includes a tag in skip_tags then it should override that tag individually, rather than requiring the entire skip tags to be provided sans the one tag. So if this command is run: puppet agent --test --tags app_deploy It should not make monitoring changes, and vice versa. Actual Behavior: A person must lookup the current skip_tags and remove the desired tag. This is a manual process that involves some human failures as skip_tags can vary from node to node. It also makes automation tricky. grep skip_tags /etc/puppetlabs/puppet/puppet.conf | split -d= -f2 | awk...
Jira (PDOC-48) @author tag is swallowed up
Title: Message Title Jo Rhett commented on PDOC-48 Re: @author tag is swallowed up I was referring to that author tag. My idea was that if we are going to waste a few lines with that detail, let's use the tag. Since the PDF templates don't contain this it does seem to be going away so I agree that it's not helpful. I never loved that part of the template. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-48) @author tag is swallowed up
Title: Message Title Jo Rhett commented on PDOC-48 Re: @author tag is swallowed up So this answer would make sense if Author information didn't currently consume multiple lines in the template. Are you removing the author content from the module skeleton? My proposal doesn't increase the information, it makes it indexable and linkable. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5621) interface unable to create port-channels properly
Title: Message Title Jo Rhett commented on PUP-5621 Re: interface unable to create port-channels properly This is the puppet device interface which at the time of the bug report only included support for Cisco... 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-7904) return() errors inside iteration functions
Title: Message Title
Jo Rhett created an issue
Puppet / PUP-7904
return() errors inside iteration functions
Issue Type:
Bug
Affects Versions:
PUP 4.10.6
Assignee:
Unassigned
Created:
2017/09/04 1:06 PM
Priority:
Major
Reporter:
Jo Rhett
So the documentation for return() says plainly that it will return from a lambda, ending evaluation of the function.
https://docs.puppet.com/puppet/4.10/function.html#return:
If called from within a lambda the return will return from the function evaluating the lambda.
So let's build a short manifest and use a function that evaluates a lambda:
with(1) |$num| {
return()
Jira (PUP-893) Deprecate puppet inspect and the audit metaparameter
Title: Message Title Jo Rhett commented on PUP-893 Re: Deprecate puppet inspect and the audit metaparameter Decision was made to keep audit in PUP-7260 . Puppet 4.10 still reports this as going away, which is causing concern for my customers that use it Warning: /File[/etc/hosts]/audit: The `audit` metaparameter is deprecated and will be ignored in a future release. (at /vagrant/manifests/audit.pp:1) 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-7260) Remove puppet inspect
Title: Message Title Jo Rhett commented on PUP-7260 Re: Remove puppet inspect Puppet 4.10 still reports this as going away, which is causing concern for my customers that use it Warning: /File[/etc/hosts]/audit: The `audit` metaparameter is deprecated and will be ignored in a future release. (at /vagrant/manifests/audit.pp:1) 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-5206) Puppet filebucket --local uses $bucketdir instead of $clientbucketdir
Title: Message Title Jo Rhett commented on PUP-5206 Re: Puppet filebucket --local uses $bucketdir instead of $clientbucketdir Pretty please tell me this was fixed before Puppet 5 shipped. 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-7260) Remove puppet inspect and stop honoring the audit metaparameter
Title: Message Title Jo Rhett commented on PUP-7260 Re: Remove puppet inspect and stop honoring the audit metaparameter Ditto on what Vadym Chepkov said about tracking changes to files that Puppet doesn't manage. This is used by many sites for PCI and other compliance. Regarding inspect, there is the need to be able to pull or send specialized reports to specific people. The two most common cases I've seen are special reviews of configuration changes for application developers (without all the other Puppet meat) and compliance reports for security auditors. They want these weekly or monthly not every 30 minutes. In the back of my head I'm sure that this data would be much easier to pull from Puppet DB, however I haven't had a chance to figure this out yet and there's no linkage in the documentation. I grok that you're desperate to retire inspect. I don't have technical bits tied to inspect, I just have customers receiving value from its functionality. If you can direct us to get the same or better functionality from PuppetDB, we can likely let inspect pass away. 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-5206) Puppet filebucket --local uses $bucketdir instead of $clientbucketdir
Title: Message Title Jo Rhett commented on PUP-5206 Re: Puppet filebucket --local uses $bucketdir instead of $clientbucketdir diffing to grasp the changes made by a puppet run is very common and necessary. In large templates it is not always possible to recreate exactly what the output would be, or more specifically, why it wasn't what was expected without having a reference to the generated output. 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-7260) Remove puppet inspect and stop honoring the audit metaparameter
Title: Message Title Jo Rhett commented on PUP-7260 Re: Remove puppet inspect and stop honoring the audit metaparameter I'm a little mind-boggled that there is a belief that only one customer uses this. There were more than a dozen large customers commenting on the deprecation issue, plus others on the mailing list, how it was crucial for their work, and I had to build an alternative auditing system for one consulting customer at $7k billed to them. I could totally believe that PuppetDB has new functionality to obsolete or improve on this but I've seen no mention of that. 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-4376) $ssldir within $confdir is a violation of Linux FHS
Title: Message Title Jo Rhett commented on PUP-4376 Re: $ssldir within $confdir is a violation of Linux FHS Some documentation for management of the highly volatile certificate store would be appropriate. Especially in these days of containerization, nobody I know runs with mutable /etc directories on their puppet-server instances. It strikes me odd to have a default that I can't find a single site that retains... it's in random locations on every site I've seen. Nobody likes my /var/opt/puppetlabs/ suggestion apparently 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-2248) Provide a better way to connect and retrieve certificate without doing a client run.
Title: Message Title Jo Rhett commented on PUP-2248 Re: Provide a better way to connect and retrieve certificate without doing a client run. I'll check it out. I didn't manage to come up with those commands from the existing documentation, my bad. 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-2248) Provide a better way to connect and retrieve certificate without doing a client run.
Title: Message Title Jo Rhett commented on PUP-2248 Re: Provide a better way to connect and retrieve certificate without doing a client run. puppet cert has existed for many years, but it must be run from a machine which has direct file access to the certificate authority's keys. Furthermore, the signer then has access to the secret key. Yes it is possible to copy the public key and CRS file around to get it signed, however Puppet already provides a convenient request and delivery mechanism for creation of certificates. The command documented above provided a way for a user to request a key from their own machine, without ever sharing the secret key with the person who approves the request. This is required for PCI and other environments where identity must be provable. 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-731) Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments
Title: Message Title Jo Rhett commented on PUP-731 Re: Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments Really should update https://docs.puppet.com/puppet/latest/environments_limitations.html to indicate which versions the big warning at the top applies to, now that this is fixed. 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-1163) Need a mechanism to only execute if a tag is set
Title: Message Title Jo Rhett commented on PUP-1163 Re: Need a mechanism to only execute if a tag is set mc0e if you don't have interlapping dependencies, you might be able to put the "expensive" stuff in a different stage and not use that stage for every run. However, the thing which I specifically asked for and which will likely solve your problem appears to have been tracked as "skip tags" in issue PUP-1376 and committed from https://github.com/puppetlabs/puppet/pull/4491 so I believe we can close this now as solved. 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-5233) puppet inspect is using wrong path for catalog data
Title: Message Title Jo Rhett commented on PUP-5233 Re: puppet inspect is using wrong path for catalog data Any chance this will get into 4.4.1 or will it be 4.5? – for the Learning Puppet book Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5648) Add Iterable type and runtime object
Title: Message Title Jo Rhett commented on PUP-5648 Re: Add Iterable type and runtime object Still no mention of these types on https://docs.puppetlabs.com/puppet/4.4/reference/lang_data.html Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5233) puppet inspect is using wrong path for catalog data
Title: Message Title Jo Rhett commented on PUP-5233 Re: puppet inspect is using wrong path for catalog data Thanks for all your help guys! Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5206) Puppet filebucket --local uses $bucketdir instead of $clientbucketdir
Title: Message Title Jo Rhett commented on PUP-5206 Re: Puppet filebucket --local uses $bucketdir instead of $clientbucketdir Ping? It's been 3 months since this update. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6041) puppet inspect fails to report changes to resources on the agent
Title: Message Title Jo Rhett commented on PUP-6041 Re: puppet inspect fails to report changes to resources on the agent I'm also confused as to why the sync status of the resource is roughly half of the output, but I'm being told that sync status was not checked? (perhaps this was half implemented?) It may end up that this should be a feature request more than bug, I'm still trying to dig up history on previous output. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6041) puppet inspect fails to report changes to resources on the agent
Title: Message Title Jo Rhett commented on PUP-6041 Re: puppet inspect fails to report changes to resources on the agent I'm trying to track down older reports I used to pull using inspect to figure out what's missing. Is it possible that inspect used to provide verbose output when doing the comparison which it no longer does? I'm seeing evidence that collecting the e-mail output of inspect was done, as well as the report files. FWIW may I be the reporter of this issue? Then the blame goes to me Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5233) puppet inspect is using wrong path for catalog data
Title: Message Title Jo Rhett commented on PUP-5233 Re: puppet inspect is using wrong path for catalog data Yes you have nailed what I believe exactly. Searching on stackexchange and ask Puppet will show you multiple reports of same going back about 2 years-ish. I believe the title needs a change. It would not be inappropriate to close this issue as fixed by your bug, and open a new issue for the follow-on problem. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5233) puppet inspect is using wrong path for catalog data
Title: Message Title Jo Rhett commented on PUP-5233 Re: puppet inspect is using wrong path for catalog data So the inspect report is supposed return resources which don't match a previous report. This is an "audit-only" run of Puppet, I used to receive a report identical to only audited resources from running Puppet. Furthermore, the output shows that it is correctly finding the resources from the catalog. Strace shows that for each resource in the catalog it actually stats the file and generates the checksums, etc. So it's doing the work of evaluating the resource state on disk. However, unlike the puppet run, inspect finds nothing to report. It's a false negative. From the official man page: This command uses the cached catalog from the previous run of 'puppet agent' to determine which attributes of which resources have been marked as auditable with the 'audit' metaparameter. It then examines the current state of the system, writes the state of the specified resource attributes to a report, and submits the report to the puppet master. So it correctly uses the cached catalog from previous run of Puppet (agent or apply works equally well FYI) and does investigate the resource on disk, but returns no alarms or reports of the attribute changes like it used to. I agree that it doesn't seem to work in 3.6 or higher. The site which was relying on inspect was running 3.2 before I upgraded them. Weren't many of the catalog changes introduced ~3.5? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-893) Deprecate puppet inspect and the audit metaparameter
Title: Message Title Jo Rhett commented on PUP-893 Re: Deprecate puppet inspect and the audit metaparameter FWIW update on this, we now have it reading the JSON catalog correctly so restoring this functionality might be pretty trivial. Unfortunately, the comparison of node status always returns "no changes" whether they are there or not. The audit attribute on resources works as expected, so we simply need to find what changed in the catalog comparison to system state for audit, and bring the same change over to puppet inspect to restore this critical functionality. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5233) puppet inspect is using wrong path for catalog data
Title: Message Title Jo Rhett commented on PUP-5233 Re: puppet inspect is using wrong path for catalog data Do you mean the following patch? diff --git a/./puppet/lib/ruby/vendor_ruby/puppet/application/inspect.rb_orig b/./puppet/lib/ruby/vendor_ruby/puppet/application/inspect.rb index 3aec9fa..b630efa 100644 --- a/./puppet/lib/ruby/vendor_ruby/puppet/application/inspect.rb_orig +++ b/./puppet/lib/ruby/vendor_ruby/puppet/application/inspect.rb @@ -91,7 +91,7 @@ Copyright (c) 2011 Puppet Labs, LLC Licensed under the Apache 2.0 License set_log_level Puppet::Transaction::Report.indirection.terminus_class = :rest -Puppet::Resource::Catalog.indirection.terminus_class = :yaml +Puppet::Resource::Catalog.indirection.terminus_class =
Jira (PUP-5924) The default hiera.yaml file does not include the '::' prefix for the environment variable
Title: Message Title
Jo Rhett updated an issue
Puppet / PUP-5924
The default hiera.yaml file does not include the '::' prefix for the environment variable
Change By:
Jo Rhett
Comment:
I'm not following what you are saying, Rob. Both of those examples have a key ("datadir") which is a valid Ruby symbol (check) prefixed with a colon.I believe you are looking at the hash value, and interpolation within the hash value. Which might indeed have a bug, but that's not relevant to the referenced documentation.I am curious how you get different values for $environment and $::environment. That may not be a bug but certainly is confusing. Can you provide details of your environment? Does the client submit a different environment than the environment data provider or a node terminus / ENC?
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5644) puppet lookup command creates new SSL hierarchy with self-signed CA
Title: Message Title Jo Rhett commented on PUP-5644 Re: puppet lookup command creates new SSL hierarchy with self-signed CA Well one difference is that I was running as a non-root user, whereas you are not. Perhaps the code has differences in that situation? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Jo Rhett commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output While I personally would enjoy flexibility, I believe that most users tend to assume "with the same config I'm already using" unless overridden. Some of the less intuitive parts of Puppet were due to things that made no assumptions, which is good for the coder but confusing for the user. I think the expected and reasonable response is for puppet lookup this.that to use exactly the same context that "puppet agent" or "puppet apply noop.pp" would have with no other options. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Jo Rhett commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Actually agent defaults to --manifestdir manifests/ now doesn't it? (probably due to ignorance) I'm having trouble imagining why we'd care about code that isn't a data provider. So I think that would mean: 1. Read the global data (Hiera v3) for the lookup key 2. Read the environment.conf for an environment_data_source. Look for key if available. 3. Identify the classes to run, check each module for a data_provider and query that. Hm. Seems like a lot of work. Why not just grab the looked up values from the last catalog stored? tricky tricky stuff. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5644) puppet lookup command creates new SSL hierarchy with self-signed CA
Title: Message Title Jo Rhett commented on PUP-5644 Re: puppet lookup command creates new SSL hierarchy with self-signed CA Although I question whether creating the SSL directory structure makes any sense for Puppet apply? Not a big deal, but not useful for server-less nodes. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5644) puppet lookup command creates new SSL hierarchy with self-signed CA
Title: Message Title
Jo Rhett commented on PUP-5644
Re: puppet lookup command creates new SSL hierarchy with self-signed CA
Yes, no CA is created with the latter form.
[vagrant@client ~]$ cd .puppetlabs/etc/puppet/
[vagrant@client puppet]$ ls
puppet.conf ssl
[vagrant@client puppet]$ rm -rf ssl
[vagrant@client puppet]$ ls -la ssl
ls: cannot access ssl: No such file or directory
[vagrant@client puppet]$ puppet apply -e 'notify { hello: }'
Notice: Compiled catalog for client.example.com in environment production in 0.02 seconds
Notice: hello
Notice: /Stage[main]/Main/Notify[hello]/message: defined 'message' as 'hello'
Jira (PUP-1157) puppet should support data in modules
Title: Message Title Jo Rhett commented on PUP-1157 Re: puppet should support data in modules In the interest of closing old issues, this functionality is now available and seems to work as documented at https://docs.puppetlabs.com/puppet/latest/reference/lookup_quick.html Perhaps we can close this issue? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5644) puppet lookup command creates new SSL hierarchy with self-signed CA
Title: Message Title Jo Rhett created an issue Puppet / PUP-5644 puppet lookup command creates new SSL hierarchy with self-signed CA Issue Type: Bug Affects Versions: PUP 4.3.1 Assignee: Unassigned Created: 2016/01/03 2:38 AM Priority: Major Reporter: Jo Rhett Puppet lookup docs says it works on both masterless Puppet nodes, and nodes with a Puppet master (perhaps the docs should say server?). However it fails on agents, and produces an unexpected and unwelcome side effect on Puppet apply nodes. When using a masterless Puppet it creates a new SSL directory and populates a CA with a new key in the local node's name. [vagrant@client ~]$ cd .puppetlabs/etc/puppet
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Jo Rhett commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output This catalog production seems to have another effect. On non-server nodes, it creates a new SSL CA directory and populates it with a new key in the local node's name. See PUP-5644 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5628) Functions written in Puppet language errors don't mention the file
Title: Message Title Jo Rhett commented on PUP-5628 Re: Functions written in Puppet language errors don't mention the file Can you provide an example of the new output? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5629) Functions in Puppet language need local scope unique value for resources...
Title: Message Title Jo Rhett commented on PUP-5629 Re: Functions in Puppet language need local scope unique value for resources... Don't think you ever want a unique id for the function invocation - it is not a container. Which absolutely isn't documented. As the function passes the Duck test, I think it's important to make this clear. People are used to named blocks of Puppet code being containers... Regarding using notice() or warn() etc: I disagree that dumping random output (e.g. JSON in this case) into the Puppet server log is necessarily useful or practice. notify allows a user to debug their own code without having server access, and without triggering log monitoring issues... Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5629) Functions in Puppet language are double parsed / produce already declared errors?
Title: Message Title Jo Rhett assigned an issue to Henrik Lindberg Puppet / PUP-5629 Functions in Puppet language are double parsed / produce already declared errors? Change By: Jo Rhett 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-5629) Functions in Puppet language are double parsed / produce already declared errors?
Title: Message Title Jo Rhett created an issue Puppet / PUP-5629 Functions in Puppet language are double parsed / produce already declared errors? Issue Type: Bug Affects Versions: PUP 4.3.1 Assignee: Unassigned Created: 2015/12/21 12:34 AM Priority: Normal Reporter: Jo Rhett If you place a normal resource within a Puppet function you get an alert like this: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Resource Statement, Duplicate declaration: Notify[I am unique] is already declared in file :3; cannot redeclare at line 3 at line 3:3 on node client.example.com Warning: Not using cache on failed catalog Error: Could not
Jira (PUP-5629) Functions in Puppet language need local scope unique value for resources...
Title: Message Title Jo Rhett updated an issue Puppet / PUP-5629 Functions in Puppet language need local scope unique value for resources... Change By: Jo Rhett Summary: Functions in Puppet language are double parsed / produce already declared errors? need local scope unique value for resources... Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5628) Functions written in Puppet language errors don't mention the file
Title: Message Title Jo Rhett created an issue Puppet / PUP-5628 Functions written in Puppet language errors don't mention the file Issue Type: Bug Affects Versions: PUP 4.3.1 Assignee: Unassigned Created: 2015/12/21 12:12 AM Priority: Normal Reporter: Jo Rhett With Puppet 4 you've done a fantastic job of improving the error messages to indicate the specific file, and the underlying problem. Bravo! Could you add a bit of love to the functions written in the Puppet language? They don't mention which function name, which file name, nothing. All I know is that some Puppet function has an error in it: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Syntax error at ')' at line 26:38 on node client.example.com The same problem appears when calling log functions and fail() in particular.
Jira (PUP-5629) Functions in Puppet language are double parsed / produce already declared errors?
Title: Message Title
Jo Rhett commented on PUP-5629
Re: Functions in Puppet language are double parsed / produce already declared errors?
Yeah I'm probably not doing a good job of phrasing it. Tired jo
1. Just slammed into this 2. I suspect many others will 3. If using resources within a function is reasonable, then I think having a unique instance variable would be awful handy 4. If resources are bad juju, docs... 5. ...and perhaps code validation ("don't do that here!") might improve the user experience.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5629) Functions in Puppet language are double parsed / produce already declared errors?
Title: Message Title
Jo Rhett commented on PUP-5629
Re: Functions in Puppet language are double parsed / produce already declared errors?
Well I slammed into it trying to toss some debugging into a function super simple test case.
function mymodule::make_boolean( Variant[Undef,String,Numeric,Boolean] $inputvalue ) {
notify { $inputvalue: }
case $inputvalue {
Did a little testing, and realized that the only way I knew to make the resource unique would be to call rand() or something
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send
Jira (PUP-5621) interface unable to create port-channels properly
Title: Message Title Jo Rhett created an issue Puppet / PUP-5621 interface unable to create port-channels properly Issue Type: Bug Affects Versions: PUP 4.3.1 Assignee: Unassigned Created: 2015/12/16 10:38 PM Priority: Normal Reporter: Jo Rhett At this time the interface resource tries to create an port-channel group by accepting a single number input, and outputting: channel-group 10 port-group 10 I've gone through a stack of ancient Cisco devices and I can't find anything even 10 years old that uses this syntax.
Jira (PUP-5616) puppet device convergence impossibility, and improved error output
Title: Message Title Jo Rhett created an issue Puppet / PUP-5616 puppet device convergence impossibility, and improved error output Issue Type: Bug Affects Versions: PUP 4.3.1 Assignee: Unassigned Created: 2015/12/16 7:02 AM Priority: Normal Reporter: Jo Rhett In testing I found that error display was (and has always been) suboptimal, so I have a PR which improves this. First, some errors were never caught and shown to the user Notice: /Stage[main]/Device_hiera::Interfaces/Interface[FastEthernet0/14]/mode: mode changed 'access' to 'trunk' Debug: Updating interface FastEthernet0/14 Debug: ssh: send conf t
Jira (PUP-5392) 'bucketdir' is not used in Puppet 4
Title: Message Title Jo Rhett commented on PUP-5392 Re: 'bucketdir' is not used in Puppet 4 Actually, no it won't – see details in PUP-5206 that show it's using the bucketdir on the client too. Either there is a bug in the code or the documentation. Actually regardless of which, the existing documentation including usage examples is wrong. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5206) Puppet filebucket --local uses $bucketdir instead of $clientbucketdir
Title: Message Title Jo Rhett commented on PUP-5206 Re: Puppet filebucket --local uses $bucketdir instead of $clientbucketdir Isn't fixing things for master re-arranging chairs on the Titanic? That ship is doomed anyway. I think it might be better to just deprecate the old behavior and move forward with a simpler and easier to understand model. Server stores remote filebuckets in /opt/pl/server paths. Agent stores local filebuckets in /opt/pl/puppet paths. Deprecate $clientbucketdir and only use $bucketdir. Now --remote and --local mean exactly what you'd expect. For the small amount of customers using Puppet 4 master say that the buckets are merged together on the server unless they provide a different bucketdir for in the [master] config. I seriously doubt you'll hear many objections to this, and it's a simple straightforward fix. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5392) 'bucketdir' is not used in Puppet 4
Title: Message Title Jo Rhett commented on PUP-5392 Re: 'bucketdir' is not used in Puppet 4 FWIW I don't think that backing up to a PuppetServer by default is a bad choice. I think that's more in line with most customer's expectations. But do post a change notice about this, and also document a clear example of how to prevent this. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5206) Puppet filebucket --local uses $bucketdir instead of $clientbucketdir
Title: Message Title Jo Rhett commented on PUP-5206 Re: Puppet filebucket --local uses $bucketdir instead of $clientbucketdir AFAIK Puppet Server already does the necessary bits. The only changes would be to deprecate the clientbucketdir configuration parameter and change the Agent to always use bucketdir which would be so trivial I'd offer a PR if I wasn't on vacation right now. That said, a more customer-friendly move would be to back off and check the old clientbucketdir too. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5206) Puppet filebucket --local uses $bucketdir instead of $clientbucketdir
Title: Message Title Jo Rhett commented on PUP-5206 Re: Puppet filebucket --local uses $bucketdir instead of $clientbucketdir I don't work for Puppet Labs ... IDWFPL? ... but I would be concerned that many users will read this announcement https://docs.puppetlabs.com/puppet/4.3/reference/release_notes.html#new-features-miscellaneous and go try it out $ sudo puppet filebucket diff --local d2c3b4ba5e2eed78d25516f153351d6e f11ba2ba5e2eed78d25516f153351d6e Error: Could not run: File not 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5392) 'bucketdir' is not used in Puppet 4
Title: Message Title Jo Rhett commented on PUP-5392 Re: 'bucketdir' is not used in Puppet 4 Ah yes, sorry. This bug is similar to PUP-5206 but not the same at all. I think this falls down to a documentation issue of how the bucket is chosen when using puppetserver. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5392) 'bucketdir' is not used in Puppet 4
Title: Message Title Jo Rhett commented on PUP-5392 Re: 'bucketdir' is not used in Puppet 4 Works for config but not for filebucket. $ sudo puppet filebucket diff --section master --local d2c3b4ba5e Error: Could not parse application options: invalid option: --section C'mon man, test it before you provide it as an answer Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5206) Puppet filebucket --local uses $bucketdir instead of $clientbucketdir
Title: Message Title Jo Rhett commented on PUP-5206 Re: Puppet filebucket --local uses $bucketdir instead of $clientbucketdir Yes on the wrong puppet ticket reference. Fixed. Christopher Price I think the problem is that puppet filebucket uses the [user] section of Puppet config, not the [master], so making it work is not documented or mentioned anywhere. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5206) Puppet filebucket --local uses $bucketdir instead of $clientbucketdir
Title: Message Title Jo Rhett commented on PUP-5206 Re: Puppet filebucket --local uses $bucketdir instead of $clientbucketdir Christopher Price I think Michael Smith nailed it properly: PUP-5326 is a documentation and/or filebucket face option for querying Puppet Server directories, which I don't think is part of the server product but definitely a concern for you. PUP-5206 is concerned with local/client-side filebuckets so there's nothing about Puppet Server 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5206) Puppet filebucket get --local does not work
Title: Message Title Jo Rhett updated an issue Puppet / PUP-5206 Puppet filebucket get --local does not work Change By: Jo Rhett Affects Version/s: PUP 4.3.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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5206) Puppet filebucket --local uses $bucketdir instead of $clientbucketdir
Title: Message Title Jo Rhett updated an issue Puppet / PUP-5206 Puppet filebucket --local uses $bucketdir instead of $clientbucketdir Turns out that the filebucket commands are inconsistent on which variable they use. Puppet agent backs up files to $clientbucketdir but --local flag uses $bucketdir instead. [root@client vagrant]# puppet filebucket -l list --bucketdir=/opt/puppetlabs/puppet/cache/clientbucket dc9e5754ad2bb6f6c32b954c04431d0a 2015-09-06 20:30:59 /etc/ntp.conf ff26b20aa0c9fed35515afbcbf7190b0 2015-09-06 20:34:05 /etc/ntp.conf b751b9441d5057a503c13f5f5da3f1d5 2015-09-07 01:20:09 /etc/ntp.conf 73e68cfd79153a49de6f5721ab60657b 2015-09-08 06:55:17 /etc/puppetlabs/mcollective/server.cfg 7b87eea4021fe1a563f443aa493cf99a 2015-09-08 08:05:22 /etc/puppetlabs/mcollective/server.cfg Change By: Jo Rhett Summary:
Jira (PUP-5206) Puppet filebucket --local uses $bucketdir instead of $clientbucketdir
Title: Message Title Jo Rhett commented on PUP-5206 Re: Puppet filebucket --local uses $bucketdir instead of $clientbucketdir Workaround in puppet.conf [user] bucketdir = $clientbucketdir Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5206) Puppet filebucket get --local does not work
Title: Message Title Jo Rhett commented on PUP-5206 Re: Puppet filebucket get --local does not work This problem persists with Puppet 4.3, rendering the new bucket commands useless: [root@client vagrant]# puppet config --section user print |grep bucket bucketdir = /opt/puppetlabs/puppet/cache/bucket clientbucketdir = /opt/puppetlabs/puppet/cache/clientbucket [root@client vagrant]# puppet config --section agent print |grep bucket bucketdir = /opt/puppetlabs/puppet/cache/bucket clientbucketdir = /opt/puppetlabs/puppet/cache/clientbucket [root@client vagrant]# puppet filebucket -l list Error: Could not run: File not found [root@client vagrant]# find /opt/puppetlabs/puppet/cache/clientbucket -type f
Jira (PUP-5392) 'bucketdir' is not used in Puppet 4
Title: Message Title Jo Rhett commented on PUP-5392 Re: 'bucketdir' is not used in Puppet 4 Actually seems like $bucketdir is used for some commands, instead of $clientbucket # puppet config --section user print |grep bucket bucketdir = /opt/puppetlabs/puppet/cache/bucket clientbucketdir = /opt/puppetlabs/puppet/cache/clientbucket [root@client vagrant]# puppet config --section agent print |grep bucket bucketdir = /opt/puppetlabs/puppet/cache/bucket clientbucketdir = /opt/puppetlabs/puppet/cache/clientbucket [root@client vagrant]# puppet filebucket -l list Error: Could not run: File not found [root@client vagrant]# puppet filebucket -l list --bucketdir=/opt/puppetlabs/puppet/cache/clientbucket dc9e5754ad2bb6f6c32b954c04431d0a 2015-09-06 20:30:59
Jira (PUP-5289) puppet device can't handle mode=auto or encapsulation=negotiate
Title: Message Title Jo Rhett created an issue Puppet / PUP-5289 puppet device can't handle mode=auto or encapsulation=negotiate Issue Type: Bug Affects Versions: PUP 4.2.2 Assignee: Unassigned Created: 2015/09/29 12:12 AM Priority: Normal Reporter: Jo Rhett Widely reported that you must manually change all switchports to access mode before you can configure them with Puppet: http://serverfault.com/questions/512398/puppet-device-not-working-with-catalyst-2950 http://www.scottyob.com/2012/12/08/my-experiences-of-managing-a-cisco-switch-with-puppet/ https://groups.google.com/forum/#!topic/puppet-users/dkADnakeQlo $ puppet device switch01.example.com --verbose
Jira (PUP-5289) puppet device can't handle mode=auto or encapsulation=negotiate
Title: Message Title Jo Rhett commented on PUP-5289 Re: puppet device can't handle mode=auto or encapsulation=negotiate I've created PR https://github.com/puppetlabs/puppet/pull/4301 which fixes these bugs. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5291) puppet device fails during SSH session closure
Title: Message Title Jo Rhett created an issue Puppet / PUP-5291 puppet device fails during SSH session closure Issue Type: Bug Affects Versions: PUP 4.2.2 Assignee: Unassigned Created: 2015/09/29 4:30 AM Priority: Normal Reporter: Jo Rhett There is a widely reported problem with SSH sessions failing. Looking into this, closing the session causes the IO handles to error out https://ask.puppetlabs.com/question/1389/puppet-device-fails-halfway-through-fact-discovery-on-cisco-catalyst-2960/ http://gadgetsytecnologia.com/56775b756283c83d7/could-not-retrieve-local-facts-closed-stream.html $ puppet device switch01.example.com --verbose
Jira (PUP-5291) puppet device fails during SSH session closure
Title: Message Title Jo Rhett commented on PUP-5291 Re: puppet device fails during SSH session closure Tested and confirmed fix in https://github.com/puppetlabs/puppet/pull/4304 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-893) Deprecate puppet inspect and the audit metaparameter
Title: Message Title Jo Rhett commented on PUP-893 Re: Deprecate puppet inspect and the audit metaparameter Mike Andrewjeski well until PUP-5233 is fixed we have no inspect in Puppet 4. Alex Elman if you have a support contract I've been told that opening a support contract is likely the only way to get this prioritized. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5233) puppet inspect is using wrong path for catalog data
Title: Message Title Jo Rhett commented on PUP-5233 Re: puppet inspect is using wrong path for catalog data I'm a bit out of touch with the current Puppet catalog routines, which appear to have been redone completely since the last time I looked. This is important enough of a concern that the client might pay for me to fix this functionality and provide it back. Eric Sorenson or Kylo Ginsberg can you point me at the relevant bits of Puppet to escalate my uptake on this? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4910) Make `puppet module generate` compatible with strings
Title: Message Title Jo Rhett commented on PUP-4910 Re: Make `puppet module generate` compatible with strings Furthermore, the default skeleton includes a header for Examples that will always be empty as @examples are shown in their own section below the headers. See this image for what I mean. I believe that the Examples header should be removed in favor of a comment. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4910) Make `puppet module generate` compatible with strings
Title: Message Title Jo Rhett updated an issue Puppet / PUP-4910 Make `puppet module generate` compatible with strings This shows the redundant Examples header. Change By: Jo Rhett Attachment: Screen Shot 2015-09-17 at 10.59.14 PM.png Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4910) Make `puppet module generate` compatible with strings
Title: Message Title Jo Rhett commented on PUP-4910 Re: Make `puppet module generate` compatible with strings So just on the basic facts, this ticket is resolved incorrectly. If this functionality went out in Puppet 4.2.1 then it was reverted in Puppet 4.2.2. None of the files mentioned in the description exist. See as follows: [vagrant@client ~]$ puppet --version 4.2.2 [vagrant@client ~]$ puppet module generate jorhett-pup4910 --skip Notice: Generating module at /home/vagrant/pup4910... Notice: Populating templates... Finished; module generated in pup4910. pup4910/manifests pup4910/manifests/init.pp pup4910/spec
Jira (PUP-893) Deprecate puppet inspect and the audit metaparameter
Title: Message Title Jo Rhett commented on PUP-893 Re: Deprecate puppet inspect and the audit metaparameter Please, please, please don't do this. This is used extensively by many of my clients. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5233) puppet inspect is using wrong path for catalog data
Title: Message Title Jo Rhett created an issue Puppet / PUP-5233 puppet inspect is using wrong path for catalog data Issue Type: Bug Affects Versions: PUP 4.2.1 Assignee: Unassigned Created: 2015/09/14 12:35 AM Priority: Major Reporter: Jo Rhett Deploying Puppet 4 at a client which makes heavy use of puppet inspect and found that Puppet 4 uses the wrong path to find the client catalog. [vagrant@client ~]$ sudo puppet agent --test Info: Retrieving pluginfacts Info: Retrieving plugin
Jira (PUP-5233) puppet inspect is using wrong path for catalog data
Title: Message Title
Jo Rhett updated an issue
Puppet / PUP-5233
puppet inspect is using wrong path for catalog data
Change By:
Jo Rhett
Deploying Puppet 4 at a client which makes heavy use of {{puppet inspect}} and found that Puppet 4 uses the wrong path to find the client catalog.{code}[vagrant@client ~]$ sudo puppet agent --testInfo: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsInfo: Caching catalog for client.example.comInfo: Applying configuration version '1442215415'Notice: /Stage[main]/Main/File[/etc/hosts]/content: audit change: previously recorded value {md5}e2b06541983600068fff455f8c11861a has been changed to {md5}28c9f9f5a3d060a500d4b57f9875ba32Notice: Applied catalog in 0.39 seconds[vagrant@client ~]$ sudo puppet inspectError: Could not run: Could not find catalog for client.example.com{code}Strace shows us that it's looking in the {{client_yaml}} directory instead of {{client_data}}.{code}[pid 7817] lstat("/opt/puppetlabs", {st_mode=S_IFDIR|0755, st_size=42, ...}) = 0[pid 7817] lstat("/opt/puppetlabs/puppet", {st_mode=S_IFDIR|0755, st_size=102, ...}) = 0[pid 7817] lstat("/opt/puppetlabs/puppet/lib", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0[pid 7817] lstat("/opt/puppetlabs/puppet/lib/ruby", {st_mode=S_IFDIR|0755, st_size=47, ...}) = 0[pid 7817] lstat("/opt/puppetlabs/puppet/lib/ruby/vendor_ruby", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0[pid 7817] lstat("/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0[pid 7817] lstat("/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0[pid 7817] lstat("/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/yaml.rb", {st_mode=S_IFREG|0644, st_size=1940, ...}) = 0[pid 7817] stat("/etc/puppetlabs/puppet/routes.yaml", 0x7fff96c96bd0) = -1 ENOENT (No such file or directory)[pid 7817] stat("/opt/puppetlabs/puppet/cache/client_yaml/catalog/client.example.com.yaml", 0x7fff96c96bd0) = -1 ENOENT (No such file or directory)[pid 7817] write(2, "\33[1;31mError: Could not run: Cou"..., 78Error: Could not run: Could not find catalog for client.example.com) = 78{code}The catalog is actually stored in {{/opt/puppetlabs/puppet/cache/client_data/catalog/}}. Workaround implemented for Furthermore, the client: catalog is now in JSON format not YAML, and there's no documented command line option to read this properly. {code} file { ' $ ls -la /opt/puppetlabs/puppet/cache/ client_yaml client_data /catalog ': / ensure => link, total 24 target => '/opt/puppetlabs/puppet/cache/client_data/catalog', drwxr-xr-x 2 root root64 Sep 14 07:46 . } drwxr-x--- 3 root root20 Aug 2 22:49 .. -rw-rw 1 root root 16947 Sep 14 07:46 client.example.com.json {code}
Jira (PUP-5233) puppet inspect is using wrong path for catalog data
Title: Message Title Jo Rhett commented on PUP-5233 Re: puppet inspect is using wrong path for catalog data Believe it or not, this is a potential fail for the Puppet 4 upgrade at this client. I'm digging around with the puppet report and puppet catalog commands trying to find a way to generate a yaml report so that the inspect command can work. If I am unable to resolve this within 24 hours, I'll be forced to revert this customer back to Puppet 3. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-893) Deprecate puppet inspect and the audit metaparameter
Title: Message Title Jo Rhett commented on PUP-893 Re: Deprecate puppet inspect and the audit metaparameter The PUP-5233 issue relates to a customer who depends extensively on audit functionality, and is prepared to revert back from Puppet 4 to Puppet 3 if I cannot get inspect working tomorrow. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5233) puppet inspect is using wrong path for catalog data
Title: Message Title Jo Rhett commented on PUP-5233 Re: puppet inspect is using wrong path for catalog data It would appear that the following would be a viable workaround, however inspect fails to notice the differences: [root@client catalog]# puppet agent --catalog_cache_terminus=yaml [root@client catalog]# ls -la /opt/puppetlabs/puppet/cache/client_yaml/catalog total 36 drwxr-xr-x 2 root root36 Sep 14 08:42 . drwxr-x--- 3 root root20 Sep 14 08:11 .. -rw-rw 1 root root 36582 Sep 14 08:42 client.example.com.yaml [root@client catalog]# puppet inspect --verbose Notice: Finished inspection in 1.41 seconds [root@client catalog]# echo "#junk" >> /etc/hosts [root@client catalog]# puppet inspect --verbose
Jira (PUP-5224) the no-client option has been removed, preventing key creation
Title: Message Title Jo Rhett created an issue Puppet / PUP-5224 the no-client option has been removed, preventing key creation Issue Type: Bug Affects Versions: PUP 4.2.2 Assignee: Unassigned Created: 2015/09/11 4:34 AM Priority: Normal Reporter: Jo Rhett There are numerous reasons to acquire a key from a Puppet server, including 1. To create a code deployment key for invalidating the environment cache 2. To create per-user keys used for MCollective authentication ...etc. Manually generating the key on the server and then copying the private key across the network to the node is not ideal for many reasons. In some situations the client would rather not have someone else possess their private key for any reason. The connect/authorize model works very well for this. The old process was: $ puppet agent --certname code-deployment --no-client --test
Jira (FACT-1227) Facter returns exit code 1 when using "--puppet" option
Title: Message Title Jo Rhett commented on FACT-1227 Re: Facter returns exit code 1 when using "--puppet" option It outputs the facts. It works perfectly in every way, with zero output even at debug level indicating an error. This is why I am confused by the exit code. I'll get you the entire debug output as soon as I get back to the machine (Vagrant) I'm testing on. Oh, that's relevant. Sorry I should have mentioned I'm seeing it only on CentOS 7 machines running Puppet 4. The prod machines running Puppet 3 with CentOS 6 (and facter 2.4.4) do not have this problem. I don't have C7/P3 or C6/P4 options handy for testing. FWIW it's breaking the cron entry created to populate mcollective facts.yaml using the Puppetlabs cookbook. That's how I noticed. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1227) Facter returns exit code 1 when using "--puppet" option
Title: Message Title Jo Rhett commented on FACT-1227 Re: Facter returns exit code 1 when using "--puppet" option No custom facts, and I can reproduce it with an environment that has no files in it. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1227) Facter returns exit code 1 when using "--puppet" option
Title: Message Title Jo Rhett created an issue Facter / FACT-1227 Facter returns exit code 1 when using "--puppet" option Issue Type: Bug Affects Versions: FACT 3.0.2 Assignee: Unassigned Created: 2015/09/08 4:33 AM Environment: Linux client.example.com 3.10.0-123.el7.x86_64 #1 SMP Mon Jun 30 12:09:22 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Priority: Major Reporter: Jo Rhett Facter returns exit code 1 if Puppet option is called for no reason mentioned in verbose or debug output. # facter 2>&1 1> /dev/null ; echo $? 0
Jira (PUP-5207) spacing around commas incorrect when complaining about missing EPP values
Title: Message Title Jo Rhett commented on PUP-5207 Re: spacing around commas incorrect when complaining about missing EPP values Saying the reverse. Saying Optional[String] does not work. Instead you must "assign a non-value to an optional string" which isn't intuitive. But yes actually, String blah = undef will produce an error if no value is provided through Hiera because undef is not a valid String. That makes sense, too Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1388) Add 'list' subcommand to filebucket
Title: Message Title Jo Rhett commented on PUP-1388 Re: Add 'list' subcommand to filebucket Thank you, thank you, thank you... Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5206) Puppet filebucket get --local does not work
Title: Message Title Jo Rhett created an issue Puppet / PUP-5206 Puppet filebucket get --local does not work Issue Type: Bug Affects Versions: PUP 4.2.1 Assignee: Unassigned Created: 2015/09/07 2:53 AM Priority: Normal Reporter: Jo Rhett As I've noticed we are finally fixing filebucket I'd love to see the following long-standing bug fixed. # cat /opt/puppetlabs/puppet/cache/clientbucket/2/c/1/5/a/e/7/2/2c15ae72acdbd8878a6550275bc15fef/paths /etc/puppetlabs/puppet/puppet.conf
Jira (PUP-5206) Puppet filebucket get --local does not work
Title: Message Title
Jo Rhett updated an issue
Puppet / PUP-5206
Puppet filebucket get --local does not work
Change By:
Jo Rhett
As I've noticed we are finally fixing {{filebucket}} I'd love to see the following long-standing bug fixed.{code}# cat /opt/puppetlabs/puppet/cache/clientbucket/2/c/1/5/a/e/7/2/2c15ae72acdbd8878a6550275bc15fef/paths /etc/puppetlabs/puppet/puppet.conf# puppet filebucket get --local 2c15ae72acdbd8878a6550275bc15fefError: Could not run: File not found{code}The thing is, you can find the file just fine if you manually specify the clientbucket.{code}[root@client puppet]# puppet filebucket get -b /opt/puppetlabs/puppet/cache/clientbucket 2c15ae72acdbd8878a6550275bc15fefInfo: FileBucket read 2c15ae72acdbd8878a6550275bc15fef# This file can be used to override the default puppet settings.# See the following links for more details on what settings are available:{code}Looking at the code with strace, it is trying to read the {{$bucketdir}} instead of the {{$clientbucketdir}}, which makes no sense when using the {{ -- {{ local}} option.If there is some use for {{ -- {{ local}} that somehow makes sense, change this to a feature request for {{ -- {{ client}} or some such option?
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this
Jira (PUP-5207) spacing around commas incorrect when complaining about missing EPP values
Title: Message Title
Jo Rhett updated an issue
Puppet / PUP-5207
spacing around commas incorrect when complaining about missing EPP values
Change By:
Jo Rhett
If you don't supply all the necessary values for an EPP template, the error message has odd spacing around the commas.{code}Error: Evaluation Error: Error while evaluating a Function Call, Too few arguments; no value given for required parameters agent_loglevel ,apply_loglevel at /etc/puppetlabs/code/environments/test/modules/showme/manifests/init.pp:31:16 on node client.example.com{code}First of all, repeating the word Error three times in four words is a bit excessive ;) Second, the commas have a space before them and are snug up against the following value.
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5207) spacing around commas incorrect when complaining about missing EPP values
Title: Message Title Jo Rhett created an issue Puppet / PUP-5207 spacing around commas incorrect when complaining about missing EPP values Issue Type: Bug Affects Versions: PUP 4.2.1 Assignee: Unassigned Created: 2015/09/07 3:02 AM Priority: Normal Reporter: Jo Rhett If you don't supply all the necessary values for an EPP template, the error message has odd spacing around the commas. Error: Evaluation Error: Error while evaluating a Function Call, Too few arguments; no value given for required parameters agent_loglevel ,apply_loglevel at /etc/puppetlabs/code/environments/test/modules/showme/manifests/init.pp:31:16 on node client.example.com First of all, repeating the word Error three times in four words is a bit excessive Second, the commas have a space before them and are snug up against the following value.
Jira (PUP-4910) Make `puppet module generate` compatible with strings
Title: Message Title Jo Rhett commented on PUP-4910 Re: Make `puppet module generate` compatible with strings I disagree that this is a useful template. It generate a page which contains the headers as plain text appended to the previous paragraphs. Furthermore, it doesn't make use of the @param syntax which provides type validation on the page. At this time to generate useful pages I have to replace the headers with rdoc style headers "== Authors" and implement the @param and @example YARD syntax manually. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5207) spacing around commas incorrect when complaining about missing EPP values
Title: Message Title Jo Rhett commented on PUP-5207 Re: spacing around commas incorrect when complaining about missing EPP values This was the error generated when calling an EPP template that didn't have enough parameters. FWIW, I figured it out but I haven't seen it documented anywhere that the only way to make a parameter optional is like this: Optional[String] parameter = undef, Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2012) puppet module --modulepath command errors when run as non-root
Title: Message Title Jo Rhett commented on PUP-2012 Re: puppet module --modulepath command errors when run as non-root This appears to be fixed somewhere before Puppet 4.2.0. $ puppet module install puppetlabs-stdlib Notice: Preparing to install into /home/vagrant/.puppetlabs/etc/code/modules ... Notice: Created target directory /home/vagrant/.puppetlabs/etc/code/modules Notice: Downloading from https://forgeapi.puppetlabs.com ... Notice: Installing -- do not interrupt ... /home/vagrant/.puppetlabs/etc/code/modules └── puppetlabs-stdlib (v4.8.0) It also works non-root if the user has write access to other directories. $ puppet module install puppetlabs-stdlib --modulepath /etc/puppetlabs/code/environments/test/modules
Jira (PUP-4975) caching server certificate performed twice?
Title: Message Title Jo Rhett created an issue Puppet / PUP-4975 caching server certificate performed twice? Issue Type: Bug Affects Versions: PUP 4.2.1 Assignee: Kylo Ginsberg Components: Client Created: 2015/08/02 11:22 AM Priority: Normal Reporter: Jo Rhett The verbose output when connecting to a server indicates that the client is caching the server's certificate twice. Info: Creating a new SSL key for client.example.com Info: Caching certificate for ca
Jira (FACT-1111) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title Jo Rhett commented on FACT- Re: deprecation of 'facter --puppet' removes critically necessary functionality Peter: that is completely untrue. Not only have I written dozens of modules which sync down facts that are used in bash scripts on the host, but I've found that dozens of community modules I depend on do similar things, pushing down facts to be used for cron jobs, etc. That is why I opened this issue. This did and does today work with Facter 2. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1111) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title Jo Rhett commented on FACT- Re: deprecation of 'facter --puppet' removes critically necessary functionality look into a config file for facter (again, treating facter as the owner of facts) and have facter tell puppet where to put them Short-term, that would break the circular dependency concern of fact-96, but wouldn't address usage of 'facter -p' at sites that override the plugin sync directories. These two sentences seem pretty obviously related. Have facter check the puppet configuration for the plugin sync directories? Or, document that if you override the plugin sync directories you must also set facter's load path? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4798) 'puppet facts' should restore retrieval of a specified fact
Title: Message Title Jo Rhett updated an issue Puppet / PUP-4798 'puppet facts' should restore retrieval of a specified fact No, I'm sorry but whitewashing this into an Improvement is not acceptable. You are removing functionality which works today, the removal of which will break hundreds of customers, and at least three dozen modules on the Puppet Forge. This is a bug. Restoring the functionality is not an improvement, it's fixing your bug. Change By: Jo Rhett Issue Type: Improvement Bug Summary: 'puppetfacts'should allow restore retrievalofaspecifiedfact Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com.
Jira (PUP-4798) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title Jo Rhett updated an issue Puppet / PUP-4798 deprecation of 'facter --puppet' removes critically necessary functionality I'm restoring the original title since the title change was an attempt to whitewash this bug into a feature request, which it most absolutely is not. Change By: Jo Rhett Summary: deprecationof ' facter-- puppet facts ' shouldrestoreretrievalofaspecifiedfact removescriticallynecessaryfunctionality Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1015) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title Jo Rhett commented on FACT-1015 Re: deprecation of 'facter --puppet' removes critically necessary functionality Kylo: I'm asking about the ability to get ANY fact provided through puppet pluginsync on the command line after --puppet is removed. String, structured, etc. In my experience it is very common practice to make new facts available, and then use them in shell scripts run on the host – say for cron jobs, scripts invoked by jenkins, etc. The facter 3 functionality shown above would be nice, but is nearly irrelevant without the ability to see Puppet's facts. There's only a few structured facts available by default. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-96) Deprecate 'facter --puppet'
Title: Message Title
Jo Rhett commented on FACT-96
Re: Deprecate 'facter --puppet'
So there's a significant loss of functionality here. I see no method of retrieving a single value, which is very highly used within puppet functions for usage of puppet plugin-synced facts.
$ facter system_uptime
{seconds=532, hours=0, days=0, uptime=0:08 hours}
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1015) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title
Jo Rhett created an issue
Facter / FACT-1015
deprecation of 'facter --puppet' removes critically necessary functionality
Issue Type:
Bug
Assignee:
Unassigned
Created:
2015/05/21 11:53 PM
Priority:
Major
Reporter:
Jo Rhett
So while I understand the goal behind
FACT-96
. there's a significant loss of functionality there. I see no method of retrieving a single value, which is very highly used within external scripts which make use of puppet plugin-synced facts.
$ facter system_uptime
{seconds=532, hours=0, days=0, uptime=0:08 hours}
Note in this context, just from my personal source archives I found more than 1000 uses of this exact functionality, and I can attest to tens of thousands more uses at companies where I am not allowed to take their source offsite on my laptop.
Jira (PUP-4645) render-as string products an object
Title: Message Title Jo Rhett created an issue Puppet / PUP-4645 render-as string products an object Issue Type: Bug Affects Versions: PUP 4.1.0 Assignee: Unassigned Created: 2015/05/22 12:27 AM Priority: Normal Reporter: Jo Rhett The man page for Puppet tells the user they can output facts in string format: $ puppet man facts ...(snip)... * --render-as FORMAT: The format in which to render
