Jira (FACT-2260) remove deprecation of facter --puppet
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2260 remove deprecation of facter --puppet Change By: Mihai Buzgau Sprint: PR - Triage 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340538.1576868667000.13767.1578383940219%40Atlassian.JIRA.
Jira (FACT-2258) Facter does not detect t3a instances on AWS
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2258 Facter does not detect t3a instances on AWS Change By: Mihai Buzgau Sprint: PR - Triage 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340118.1576692534000.13758.1578383760683%40Atlassian.JIRA.
Jira (FACT-1903) facter doesn't recognize EC2 i3.metal instances
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1903 facter doesn't recognize EC2 i3.metal instances Change By: Mihai Buzgau Team: Platform OS Night's Watch 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.291000.1547052341000.13752.1578383760460%40Atlassian.JIRA.
Jira (FACT-1903) facter doesn't recognize EC2 i3.metal instances
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1903 facter doesn't recognize EC2 i3.metal instances Change By: Mihai Buzgau Sprint: PR - Triage 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.291000.1547052341000.13755.1578383760551%40Atlassian.JIRA.
Jira (PUP-10177) yum provider does not allow array of strings
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10177 yum provider does not allow array of strings Change By: Mihai Buzgau Sprint: PR - Triage 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.339935.157660745.13748.1578383580475%40Atlassian.JIRA.
Jira (FACT-2250) Facter ignores signals while waiting for external commands to run
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2250 Facter ignores signals while waiting for external commands to run Change By: Mihai Buzgau Sprint: PR - Triage 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.339252.1576183486000.13739.1578383460323%40Atlassian.JIRA.
Jira (FACT-1472) Ensure the collection has enough information about external facts to cache them.
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1472 Ensure the collection has enough information about external facts to cache them. Change By: Mihai Buzgau Sprint: PR - Triage 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.143279.1469463305000.13732.1578383340439%40Atlassian.JIRA.
Jira (FACT-2096) Windows system32 environment variable issue after installation of "RDS-RD-Server"
Title: Message Title Steven Towill commented on FACT-2096 Re: Windows system32 environment variable issue after installation of "RDS-RD-Server" I have been testing a fix for an unrelated issue using the puppet nightly build (6.12.0 - 2019-12-30 18:15:25) which includes facter 3.14.7. From my quick and limited testing this has now resolved the issue. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332946.1572508394000.13722.1578375300427%40Atlassian.JIRA.
Jira (FACT-2195) facter not returning correct 'os.windows.system32' fact on Windows Server 2012 R2
Title: Message Title Steven Towill commented on FACT-2195 Re: facter not returning correct 'os.windows.system32' fact on Windows Server 2012 R2 I have been testing a fix for an unrelated issue using the puppet nightly build (6.12.0 - 2019-12-30 18:15:25) which includes facter 3.14.7. From my quick and limited testing this has now resolved the issue. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.338159.1575596749000.13714.1578375060101%40Atlassian.JIRA.
Jira (PUP-10057) User resource on Windows confuses domain and local accounts
Title: Message Title Steven Towill commented on PUP-10057 Re: User resource on Windows confuses domain and local accounts 6.12.0 is not fixed and I suspect the other versions will have the same issue. It breaks the user resource when creating and maintaining a user. See comment placed in PA-30363 here: https://tickets.puppetlabs.com/browse/PA-3063?focusedCommentId=710339=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-710339 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327453.1569921077000.13713.1578373020243%40Atlassian.JIRA.
Jira (PUP-10214) Unexpected results on "replace => false" on symlinks
Title: Message Title Corey Hickey commented on PUP-10214 Re: Unexpected results on "replace => false" on symlinks Josh Cooper I thought the links parameter was for how to handle files local to the puppetmaster, but it would seem appropriate to extend the parameter to this case, especially as in your example where the default behavior fixes the bug. Jorie Tappa thanks for your comment. I took a look at PUP-5830 and I think I would characterize that ticket as describing "strange behavior when given pathological parameters", whereas my ticket here is more "incorrect behavior under some circumstances when given appropriate parameters". So, I don't think it would be fair to consider PUP-5830 as precedent. -Corey 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340916.1578010636000.13690.1578362760259%40Atlassian.JIRA.
Jira (PUP-10213) Do not create exceptions for stacktrace information when we know we won't use that information
Title: Message Title Justin Stoller updated an issue Puppet / PUP-10213 Do not create exceptions for stacktrace information when we know we won't use that information Change By: Justin Stoller Fix Version/s: PUP 6.12.0 Fix Version/s: PUP 6.4.5 Fix Version/s: PUP 5.5.18 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340907.1578000208000.13579.1578355500046%40Atlassian.JIRA.
Jira (PUP-10213) Do not create exceptions for stacktrace information when we know we won't use that information
Title: Message Title Justin Stoller updated an issue Puppet / PUP-10213 Do not create exceptions for stacktrace information when we know we won't use that information Change By: Justin Stoller Release Notes Summary: Some compilation warnings will now take less time to compute. Release Notes: Enhancement 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340907.1578000208000.13578.1578355440045%40Atlassian.JIRA.
Jira (PUP-10142) Make Puppet settings not changed after a request is initiated
Title: Message Title Justin Stoller commented on PUP-10142 Re: Make Puppet settings not changed after a request is initiated Initially going through the code I looked to see if there were any refactors where we could pass the values of these settings into the methods that require information about the settings, or initialize different versions of the existing objects/subsystems that use them, storing these objects in the context and switching between them from calling code rather than munging the settings object. I failed to see how to refactor the existing objects w/o partitioning most of the server side code from the serialization through the compiler and down to the lexer. That set of changes seemed beyond the scope of this work. From there I investigated two less ideal ways to make these settings threadsafe. One was to move the settings in question into the context (https://github.com/puppetlabs/puppet/pull/7746). The other was to attempt to make the settings context itself threadsafe (https://github.com/puppetlabs/puppet/pull/7745). After some discussion we decided to go with moving the settings into the context because of two reason: ultimately we want the settings to be immutable with the context holding mutable info, and the settings code is entangled enough that we were concerned about edge cases with the threadsafe settings approach. However, there were some additional changes/gotchas with the context approach that we highlighted. I may be missing some here but if memory serves me they are: We need to keep the settings api to be backwards compatible. When a user attempts to read a moved setting a deprecation warning should be emitted and the actual value should be looked up in the context. When a user attempts to set a moved setting a deprecation warning should be emitted and the context should have the new value pushed onto it. Attempting to set any setting should result in a deprecation warning. I unfortunately don't remember what, if anything, we came up with regarding clearing settings? I do know we mentioned having alternate implementations for when running in a multithreaded environment (eg JRuby vs MRI) though I don't remember why or what changes in behavior were expected between them? Add Comment
Jira (PUP-10057) User resource on Windows confuses domain and local accounts
Title: Message Title Josh Cooper commented on PUP-10057 Re: User resource on Windows confuses domain and local accounts Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/c8c0ab6a31ae4d70ccd34aa148c5b9e45a6b40f5 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327453.1569921077000.13484.1578352620315%40Atlassian.JIRA.
Jira (PUP-10057) User resource on Windows confuses domain and local accounts
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10057 User resource on Windows confuses domain and local accounts Change By: Josh Cooper Fix Version/s: PUP 6.12.0 Fix Version/s: PUP 6.4.5 Fix Version/s: PUP 5.5.18 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327453.1569921077000.13488.1578352620491%40Atlassian.JIRA.
Jira (PUP-10154) Detect connection errors when using TLS 1.3 and using post-handshake authentication
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10154
Detect connection errors when using TLS 1.3 and using post-handshake authentication
Change By:
Josh Cooper
Prior to TLS 1.3, the client always sends it its certificate (if it has one) during the TLS handshake. As a result, the {{OpenSSL::SSL::SSLSocket#connect}} method only returns success if the server accepted our client cert (or we didn't have one) . This way we can differentiate between connection errors and other types of errors, like HTTP 302, when processing our server list, finding a suitable server using SRV, etc.When using TLS 1.3, the client cert *may* be sent after the server completes its side of the TLS handshake. This is referred to as post handshake authentication. This means the client won't know if the server accepted its client cert until after {{SSLSocket#connect}} returns and we try to send application data. If the server rejected our cert, then we'll get a {{ECONNRESET}}.It also appears TLS 1.3 can send the client during the handshake (it was on by default in openssl 1.1.0, but [changed to opt-in in 1.1.1|https://github.com/openssl/openssl/pull/6938]) to reduce the number of TLS packages that are needed to connect/resume. It appears ruby hardcodes the use of {{post_connection_auth}}. See [https://github.com/ruby/openssl/pull/239] However that version of ruby-openssl hasn't been promoted into any branch of ruby yet.If there was a way to set disable that extension via {{Net::HTTP}} then we wouldn't need to account for the different protocol behaviors.
Add Comment
Jira (PUP-10150) Ruby stacktraces no longer interleave Puppet Code stacktraces
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-10150 Ruby stacktraces no longer interleave Puppet Code stacktraces Change By: Maggie Dreyer Release Notes Summary: Fixes a bug where stacktraces from errors no longer had the Ruby stack frames interleaved with the Puppet stack frames when using `trace`. Also introduces a new setting `puppet_trace`, that will cause the Puppet stack to be printed without the Ruby frames interleaved. If `trace` is enabled, it overrides the value of `puppet_trace`. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.336155.1574344871000.13360.1578350220223%40Atlassian.JIRA.
Jira (PUP-10148) Include X-Puppet-Profiling header
Title: Message Title Josh Cooper commented on PUP-10148 Re: Include X-Puppet-Profiling header Merged to master in https://github.com/puppetlabs/puppet/commit/3e5acd3e540c60b35d10d47afdd01346bc49d2f4 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.335811.157412461.13354.1578350100715%40Atlassian.JIRA.
Jira (PUP-10150) Ruby stacktraces no longer interleave Puppet Code stacktraces
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-10150 Ruby stacktraces no longer interleave Puppet Code stacktraces Change By: Maggie Dreyer Release Notes: Bug Fix 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.336155.1574344871000.13346.1578350100364%40Atlassian.JIRA.
Jira (PUP-10150) Ruby stacktraces no longer interleave Puppet Code stacktraces
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-10150 Ruby stacktraces no longer interleave Puppet Code stacktraces Change By: Maggie Dreyer Fix Version/s: PUP 6.4.5 Fix Version/s: PUP 5.5.18 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.336155.1574344871000.13340.1578350040238%40Atlassian.JIRA.
Jira (PUP-10150) Ruby stacktraces no longer interleave Puppet Code stacktraces
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-10150 Ruby stacktraces no longer interleave Puppet Code stacktraces Change By: Maggie Dreyer Fix Version/s: PUP 6.12.0 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.336155.1574344871000.13335.1578349980788%40Atlassian.JIRA.
Jira (PUP-10210) puppet fails with JSON error when a fact value equals Infinity
Title: Message Title Henrik Lindberg commented on PUP-10210 Re: puppet fails with JSON error when a fact value equals Infinity Jorie Tappa Pcore does not have the notion of Infinity and it does not exists in the Puppet Language as a concept. If a Ruby Float::INFINITY is returned to the puppet language it will consider it to be a Float data type value and it will print as Float[Infinity]. That is however not 100% correct since Infinity isn't a recognized data type. The only way to get a constant representing Infinity would be to write a function that returns Ruby Float::INFINITY and then that the type of that using the function type(). You now have a data type that represents Infinity. The same cannot be done statically - i.e. you cannot define a parameter of a function to be of that data type. Since there are issues with representation of Infinity in JSON (as well as in other formats), it would be "best" if this became an integral part of Pcore since it could have the special provisions for it when serializing/deserializing. Ping Thomas Hallgren. I am however concerned that we may be opening a bit of Pandora's box here. If we do add an Infinity data type it may be best if this is a subtype of Float as we have a very precise definition of what an Integer is in terms of max/min value. Worth considering is also that PDB then needs to be able to handle this data type. Another approach would be to define Infinite as an Object data type. Then it is a matter of handling Float::INFINITY as being instances of that type - which is not trivial. The conservative (and safe) solution would be to not allow Ruby Float::INFINITY as a Float, and force all such values that are to be processed by Puppet to be transformed to some supported data type. (That is what I think it means with the suggested approach above - the infinite numeric value is turned into the string ”unlimited". Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10214) Unexpected results on "replace => false" on symlinks
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10214 Unexpected results on "replace => false" on symlinks Change By: Josh Cooper Labels: beginner 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340916.1578010636000.13283.1578348660251%40Atlassian.JIRA.
Jira (PUP-10214) Unexpected results on "replace => false" on symlinks
Title: Message Title Josh Cooper commented on PUP-10214 Re: Unexpected results on "replace => false" on symlinks Corey Hickey you'd need to take into account whether puppet is managing the symlink or following, which is controlled via the links parameter. So the logic would need to be something like: def insync?(currentvalue) if [:nochange, :notlink].include?(self.should) or @resource.recurse? return true elsif ! @resource.replace? begin if @resource[:links] == :follow Puppet::FileSystem.stat(@resource[:path]) else Puppet::FileSystem.lstat(@resource[:path]) end true rescue Errno::ENOENT false
Jira (PDB-4600) Investigate OOM errors during resource_events partitioning migration
Title: Message Title Zachary Kent commented on PDB-4600 Re: Investigate OOM errors during resource_events partitioning migration yep, done 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.339229.1576177499000.13231.1578347160223%40Atlassian.JIRA.
Jira (PDB-4600) Investigate OOM errors during resource_events partitioning migration
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4600 Investigate OOM errors during resource_events partitioning migration Change By: Zachary Kent Fix Version/s: PDB 6.7.4 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.339229.1576177499000.13224.1578347040219%40Atlassian.JIRA.
Jira (PDB-4600) Investigate OOM errors during resource_events partitioning migration
Title: Message Title Nick Walker commented on PDB-4600 Re: Investigate OOM errors during resource_events partitioning migration Zachary Kent can we add fixversions on there? 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.339229.1576177499000.13194.1578346140199%40Atlassian.JIRA.
Jira (PUP-10211) 'puppet module install --module_repository' never finishes
Title: Message Title Josh Cooper commented on PUP-10211 Re: 'puppet module install --module_repository' never finishes Can you double check the URL? I think it's suppose to be http://:/artifactory/api/puppet/puppet, not a URL ending with /puppet-forge. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340717.1577458334000.13039.1578340440499%40Atlassian.JIRA.
Jira (PUP-10174) Make the environment caching of settings in puppet work properly with threads
Title: Message Title Maggie Dreyer assigned an issue to Unassigned Puppet / PUP-10174 Make the environment caching of settings in puppet work properly with threads Change By: Maggie Dreyer Assignee: Justin Stoller 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323045.1567197294000.12918.1578336720239%40Atlassian.JIRA.
Jira (PUP-10217) Puppet Agent cannot connect to Puppet CA if ipv6 is enabled on Windows client machine
Title: Message Title Jorie Tappa commented on PUP-10217 Re: Puppet Agent cannot connect to Puppet CA if ipv6 is enabled on Windows client machine Currently we're using Ruby's Net::HTTP's method and it doesn't know to fall back to ipv4 if it can't find the ipv6 address. Net::HTTP only takes one arg, an IP address OR a hostname, so this would require an upstream patch to Ruby for us to resolve so that SSL cert verification still works properly. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340614.1577066791000.12780.1578335400255%40Atlassian.JIRA.
Jira (PUP-10217) Puppet Agent cannot connect to Puppet CA if ipv6 is enabled on Windows client machine
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-10217 Puppet Agent cannot connect to Puppet CA if ipv6 is enabled on Windows client machine Change By: Jorie Tappa Team: Coremunity 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340614.1577066791000.12766.1578335280317%40Atlassian.JIRA.
Jira (PUP-10217) Puppet Agent cannot connect to Puppet CA if ipv6 is enabled on Windows client machine
Title: Message Title Jorie Tappa moved an issue Puppet / PUP-10217 Puppet Agent cannot connect to Puppet CA if ipv6 is enabled on Windows client machine Change By: Jorie Tappa Affects Version/s: SERVER 6.7.0 Component/s: Puppet Server Key: SERVER PUP - 2711 10217 Project: Puppet Server 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 view this discussion on the web
Jira (PUP-10209) User feedback: Run a status on a puppet agent in the Windows environment
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-10209 User feedback: Run a status on a puppet agent in the Windows environment Change By: Jorie Tappa I'm not sure if this is the right place to file this, but feel free to move it or change it as needed. Techpubs received feedback from a user to add a --status command for checking the Puppet agent status in the Windows environment. Here is the feedback:"There is a command called ‘puppet’ you can run in a DOS command environment on Windows. Currently, there is no way to run a status on the puppet client.My suggestion.Add '—status' as a switch that would return details on the status of the puppet agent." The user said he would want to see the status for things like agent disabled, enabled, running, when was it last started, etc. His email [joe.br...@thomsonreuters.com|mailto:is%c2%a0joe.br...@thomsonreuters.com] Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to
Jira (PUP-10209) User feedback: Run a status on a puppet agent in the Windows environment
Title: Message Title Jorie Tappa commented on PUP-10209 Re: User feedback: Run a status on a puppet agent in the Windows environment You can use puppet resource service puppet to see enabled, disabled, running status, but not 'last run', not sure if that's something we can track from there. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340636.1577137427000.12749.1578335160379%40Atlassian.JIRA.
Jira (PUP-10210) puppet fails with JSON error when a fact value equals Infinity
Title: Message Title Thomas Kishel commented on PUP-10210 Re: puppet fails with JSON error when a fact value equals Infinity Insert Infinity War Cereal joke here 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340709.1577387077000.12746.1578335100167%40Atlassian.JIRA.
Jira (PUP-10210) puppet fails with JSON error when a fact value equals Infinity
Title: Message Title Jorie Tappa commented on PUP-10210 Re: puppet fails with JSON error when a fact value equals Infinity ping Henrik Lindberg can pcore handle numeric values like this, and if so can you please help Coremunity to get this type of behavior working here as well? 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340709.1577387077000.12739.1578334980227%40Atlassian.JIRA.
Jira (PUP-10210) puppet fails with JSON error when a fact value equals Infinity
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-10210 puppet fails with JSON error when a fact value equals Infinity Change By: Jorie Tappa Acceptance Criteria: Puppet needs to be able to serialize infinite data/rich data 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340709.1577387077000.12729.1578334860140%40Atlassian.JIRA.
Jira (PUP-10210) puppet fails with JSON error when a fact value equals Infinity
Title: Message Title
Jorie Tappa updated an issue
Puppet / PUP-10210
puppet fails with JSON error when a fact value equals Infinity
Change By:
Jorie Tappa
*Puppet Version: 6.10 and possibly earlier* A ANY fact converted to / interpreted as (Ruby) {{Infinity}} generates a JSON error when executing {{puppet agent}} or {{puppet facts}} The same error does not occur when executing {{facter -p}}*Desired Behavior:*No JSON error via {{puppet}}*Actual Behavior:* Given: {code} puppet config print maxwaitforcertunlimited{code} Create a custom fact for {{maxwaitforcert}}: {code} Facter.add('maxwaitforcert') do setcode doPuppet.settings['maxwaitforcert'] endend{code} {code} [root@pe-201921-master ~]# puppet factsError: 862: Infinity not allowed in JSONError: Try 'puppet help facts find' for usage{code} {code} [root@pe-201921-master ~]# puppet agent -tInfo: Using configured environment 'production'Info: Retrieving pluginfactsInfo: Retrieving pluginInfo: Retrieving localesInfo: Loading factsError: Failed to apply catalog: Could not render to json: 862: Infinity not allowed in JSON{code} Versus: {code} [root@pe-201921-master ~]# facter -p maxwaitforcertinf{code}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10214) Unexpected results on "replace => false" on symlinks
Title: Message Title Jorie Tappa commented on PUP-10214 Re: Unexpected results on "replace => false" on symlinks Hi Corey Hickey, we'll try and investigate this issue, but because it seems to relate to other symlink behavior we've already closed as "won't fix" it's unlikely we'll be able to triage this into our work. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340916.1578010636000.12703.1578334560427%40Atlassian.JIRA.
Jira (PUP-10216) Failure to fetch node definition may result in bad pluginsync and cascading failure
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-10216 Failure to fetch node definition may result in bad pluginsync and cascading failure Change By: Jorie Tappa Team: Coremunity 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341077.1578089491000.12659.1578334140427%40Atlassian.JIRA.
Jira (PUP-10216) Failure to fetch node definition may result in bad pluginsync and cascading failure
Title: Message Title Jorie Tappa commented on PUP-10216 Re: Failure to fetch node definition may result in bad pluginsync and cascading failure Using last-run info seems like the preferred route for this 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341077.1578089491000.12656.1578334140367%40Atlassian.JIRA.
Jira (PUP-8900) "puppet facts upload" face only tries first master in server_list
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8900 "puppet facts upload" face only tries first master in server_list Change By: Josh Cooper Fix Version/s: PUP 5.5.z Fix Version/s: PUP 6.y 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.255723.1527812608000.12501.1578331200228%40Atlassian.JIRA.
Jira (PUP-10211) 'puppet module install --module_repository' never finishes
Title: Message Title Josh Cooper commented on PUP-10211 Re: 'puppet module install --module_repository' never finishes Lee Lowder do you get the same behavior with puppet versions < 6.10? 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340717.1577458334000.12478.1578330960159%40Atlassian.JIRA.
Jira (PUP-9993) lookup's knockout_prefix cannot be undef, contrary to the documentation
Title: Message Title Jean Bond commented on PUP-9993 Re: lookup's knockout_prefix cannot be undef, contrary to the documentation That's very helpful, thank you Fabien Wernli! 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323217.1567511185000.12421.1578329880484%40Atlassian.JIRA.
Jira (PUP-9993) lookup's knockout_prefix cannot be undef, contrary to the documentation
Title: Message Title Jean Bond assigned an issue to Unassigned Puppet / PUP-9993 lookup's knockout_prefix cannot be undef, contrary to the documentation Change By: Jean Bond Assignee: Jean Bond 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323217.1567511185000.12428.1578329880680%40Atlassian.JIRA.
Jira (FACT-2229) load_averages fact for AIX
Title: Message Title
Ciprian Badescu commented on FACT-2229
Re: load_averages fact for AIX
The dlopen subroutine can be used to load a module that is a member of an archive https://www.ibm.com/support/knowledgecenter/ssw_aix_71/d_bostechref/dlopen.html require 'ffi' module Hello extend FFI::Library @ffi_lib_flags=0x0004|0x0001|0x0004 ffi_lib "libc.a(shr.o)" attach_function :puts, [ :string ], :int end Hello.puts("Hello, World")
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.338936.1576054336000.12399.1578328440319%40Atlassian.JIRA.
Jira (PUP-9993) lookup's knockout_prefix cannot be undef, contrary to the documentation
Title: Message Title Fabien Wernli commented on PUP-9993 Re: lookup's knockout_prefix cannot be undef, contrary to the documentation Here's what I found using the puppetlabs docs search interface: https://puppet.com/docs/puppet/latest/hiera_merging.html : "'knockout_prefix' - string or undef; default is undef" "'knockout_prefix' (String or undef) - Use with a string prefix to indicate a value to remove from the final result. Defaults to undef, which turns off this option." https://puppet.com/docs/puppet/6.4/hiera_merging.html (same as above) https://puppet.com/docs/puppet/5.5/hiera_merging.html (same as above) So this is still in the latest documentation 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323217.1567511185000.12273.1578315900212%40Atlassian.JIRA.
