Jira (PUP-10157) Observe server_list for CA requests
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10157
Observe server_list for CA requests
Change By:
Josh Cooper
puppet does not observe the {{server_list}} setting when making CA requests. This is a regression introduced in https://tickets.puppetlabs.com/browse/PUP-10040 as it wasn't apparent that {{Puppet::Rest::Routes}} called {{Puppet::Util::Connection.determine_server}} to set the {{@default_server}}.We need to enable the server_list resolver such that:# If we successfully resolved the CA server/port once in a session, then we should always reuse that same server/port # -Next if {{ca_server}} is set explicitly on the CLI or puppet.conf, we should always use that regardless of SRV, {{server}} or {{server_list}}-# Next if SRV records are enabled, we should try that# Next if {{server_list}} is set, we should try each server/port combo# Otherwise Next fallback to {{ca_server}} setting which defaults to {{server}} # Raise no more routes to try All of those should already be working except (2) & (4).Questions:In step 1, if we fail to use a cached value, should resolution to performed again? Currently failures don't clear the cache.In step 2, if SRV records are enabled, the new code prefers SRV over the explicit server, which is wrong.In step 2, If the explicit server fails, should we fallback to other resolvers? NoIn step 4, the old behavior was to only try the first server/port in server list. However, I think that was a limitation of the code, as there wasn't a way using the context system for puppet to try multiple server/port combinations. Perhaps would be better (less crafty exceptional logic) to try all the server/ports in server_list.
Add Comment
Jira (PUP-10157) Observe server_list for CA requests
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10157
Observe server_list for CA requests
Change By:
Josh Cooper
puppet does not observe the {{server_list}} setting when making CA requests. This is a regression introduced in https://tickets.puppetlabs.com/browse/PUP-10040 as it wasn't apparent that {{Puppet::Rest::Routes}} called {{Puppet::Util::Connection.determine_server}} to set the {{@default_server}}.We need to enable the server_list resolver such that:# If we successfully resolved the CA server/port once in a session, then we should always reuse that same server/port # - Next if {{ca_server}} is set explicitly on the CLI or puppet.conf, we should always use that regardless of SRV, {{server}} or {{server_list}} - # Next if SRV records are enabled, we should try that# Next if {{server_list}} is set, we should try each server/port combo# Otherwise fallback to {{ca_server}} setting which defaults to {{server}}All of those should already be working except (2) & (4).Questions:In step 1, if we fail to use a cached value, should resolution to performed again? Currently failures don't clear the cache.In step 2, if SRV records are enabled, the new code prefers SRV over the explicit server, which is wrong.In step 2, If the explicit server fails, should we fallback to other resolvers? Currently we don't and we should probably keep that as-is. No In step 4, the old behavior was to only try the first server/port in server list. However, I think that was a limitation of the code, as there wasn't a way using the context system for puppet to try multiple server/port combinations. Perhaps would be better (less crafty exceptional logic) to try all the server/ports in server_list.
Add Comment
Jira (BOLT-1525) Add zypper implementation to package task
Title: Message Title Adrian Parreiras Horta commented on BOLT-1525 Re: Add zypper implementation to package task I couldn't fill out the correct release version since we switched to github issues, but it was 1.36.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.322358.1566923951000.54496.1575493740117%40Atlassian.JIRA.
Jira (BOLT-1525) Add zypper implementation to package task
Title: Message Title Adrian Parreiras Horta commented on BOLT-1525 Re: Add zypper implementation to package task This was merged a couple months ago, closing. 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.322358.1566923951000.54474.1575493080605%40Atlassian.JIRA.
Jira (PUP-10160) Puppet should not load types and providers during environment convergence
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10160 Puppet should not load types and providers during environment convergence 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.337880.157548855.54383.1575489180564%40Atlassian.JIRA.
Jira (PUP-10160) Puppet should not load types and providers during environment convergence
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10160 Puppet should not load types and providers during environment convergence Change By: Josh Cooper Sprint: Platform Core KANBAN 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.337880.157548855.54319.1575488580975%40Atlassian.JIRA.
Jira (PUP-10160) Puppet should not load types and providers during environment convergence
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10160 Puppet should not load types and providers during environment convergence Change By: Josh Cooper 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.337880.157548855.54317.1575488580968%40Atlassian.JIRA.
Jira (PUP-10160) Puppet should not load types and providers during environment convergence
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-10160 Puppet should not load types and providers during environment convergence Change By: Josh Cooper Assignee: Josh Cooper 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.337880.157548855.54316.1575488580965%40Atlassian.JIRA.
Jira (PUP-10160) Puppet should not load types and providers during environment convergence
Title: Message Title Josh Cooper created an issue Puppet / PUP-10160 Puppet should not load types and providers during environment convergence Issue Type: Bug Assignee: Unassigned Created: 2019/12/04 11:42 AM Priority: Normal Reporter: Josh Cooper During environment convergence, puppet loads types and providers for pluginsynced modules, potentially multiple times. Type/provider loading is triggered when writing the cached catalog and/or when converting the resource catalog to a RAL catalog. However, if the environment doesn't converge the first time, then puppet will switch environments, and pluginsync in a different environment, potentially receiving different versions of type/provider code. Puppet can reload new versions of types and providers, but can't reload helper code required by type/providers. This can result in newer providers calling methods in older helper code still in memory. This problem may occur when the classifier uses pluginsynced facts to determine environment, a node doesn't have that fact yet (or a wrong version of the fact), puppetdb doesn't have a facts for that node in the "final" environment, the node attempts to get a catalog, and there are different versions of a module in different environments. The problem may not occur, or may not be noticed if the different versions of modules don't conflict in a way that causes an exception. The problem won't occur if the agent resolves the environment during the node request (before pluginsync). However, the agent doesn't send facts with the node request (a long standing request), so this generally applies to nodes that have already resolved the environment once. Here's a stacktrace showing the inifile type/provider being loaded during the environment resolution process (using 5.5.17): # puppet --version
Jira (PDB-4479) Deactivate node commands sync after garbage collection
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4479 Deactivate node commands sync after garbage collection Change By: Nick Burgan Sprint: HA Team 2019-12-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.320599.1565648011000.54262.1575487560412%40Atlassian.JIRA.
Jira (PDB-4479) Deactivate node commands sync after garbage collection
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4479 Deactivate node commands sync after garbage collection Change By: Austin Blatt Fix Version/s: PDB 6.3.7 Fix Version/s: PDB 5.2.12 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.320599.1565648011000.54259.1575487560402%40Atlassian.JIRA.
Jira (PDB-4479) Deactivate node commands sync after garbage collection
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4479 Deactivate node commands sync after garbage collection Change By: Nick Burgan Story Points: 2 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.320599.1565648011000.54255.1575487500333%40Atlassian.JIRA.
Jira (PDB-4479) Deactivate node commands sync after garbage collection
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4479 Deactivate node commands sync after garbage collection Change By: Nick Burgan 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.320599.1565648011000.54249.1575487440931%40Atlassian.JIRA.
Jira (PUP-10157) Observe server_list for CA requests
Title: Message Title Melissa Stone updated an issue Puppet / PUP-10157 Observe server_list for CA requests Change By: Melissa Stone Sprint: Coremunity Hopper Platform Core KANBAN 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.337748.1575438009000.53679.1575479400435%40Atlassian.JIRA.
Jira (PUP-10157) Observe server_list for CA requests
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-10157 Observe server_list for CA requests Change By: Melissa Stone Assignee: Melissa Stone 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.337748.1575438009000.53676.1575479400423%40Atlassian.JIRA.
Jira (PUP-10157) Observe server_list for CA requests
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10157 Observe server_list for CA requests Change By: Josh Cooper Sprint: Coremunity Grooming Hopper 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.337748.1575438009000.53637.1575477660135%40Atlassian.JIRA.
Jira (PUP-10157) Observe server_list for CA requests
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10157 Observe server_list for CA requests Change By: Josh Cooper Sprint: Coremunity Grooming 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.337748.1575438009000.53635.1575477600357%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 Sprint: Coremunity Grooming 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.337392.1575326015000.53634.1575477600353%40Atlassian.JIRA.
Jira (PUP-10157) Observe server_list for CA requests
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10157 Observe server_list for CA requests Change By: Josh Cooper Sprint: Coremunity Grooming 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.337748.1575438009000.53632.1575477600346%40Atlassian.JIRA.
Jira (PUP-10157) Observe server_list for CA requests
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10157 Observe server_list for CA requests Change By: Josh Cooper Sprint: Coremunity Grooming 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.337748.1575438009000.53636.1575477660130%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 Sprint: Coremunity Grooming 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.337392.1575326015000.53631.1575477600340%40Atlassian.JIRA.
Jira (PUP-10157) Observe server_list for CA requests
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10157 Observe server_list for CA requests Change By: Josh Cooper 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.337748.1575438009000.53629.1575477600332%40Atlassian.JIRA.
Jira (PUP-10158) Filename with non-UTF8-encoding corrupts state.yaml
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10158 Filename with non-UTF8-encoding corrupts state.yaml Change By: Josh Cooper 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.337775.1575458448000.53593.1575477002515%40Atlassian.JIRA.
Jira (PUP-10158) Filename with non-UTF8-encoding corrupts state.yaml
Title: Message Title Josh Cooper commented on PUP-10158 Re: Filename with non-UTF8-encoding corrupts state.yaml Puppet assumes content written to state.yaml and transactionstore.yaml are UTF-8 encoded. It sounds like the data is being written to those files not as UTF-8, but using ruby's default encoding which on German Windows (I think) is Encoding::CP1252. This occurs in: Puppet::Util::Yaml.dump(@new_data, Puppet[:transactionstorefile]) and Puppet::Util::Yaml.dump(@@state, Puppet[:statefile]) We need to ensure strings in @new_data and @@state hashes are utf-8 encoded during serialization. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10159) Can't differentiate between cert and request on Puppet Server
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10159 Can't differentiate between cert and request on Puppet Server Change By: Josh Cooper Team: 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 visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.335692.1574091306000.53555.1575476460747%40Atlassian.JIRA.
Jira (PUP-10159) Can't differentiate between cert and request on Puppet Server
Title: Message Title Josh Cooper commented on PUP-10159 Re: Can't differentiate between cert and request on Puppet Server The puppet cert command is deprecated in 5.5.x and removed in 6. In 5.5.x there should be a leading +. $ bx puppet cert list --all Warning: `puppet cert` is deprecated and will be removed in a future release. (location: /Users/josh/work/puppet/lib/puppet/application.rb:370:in `run') + "foobar" (SHA256) B7:42:13:1D:2E:D9:16:07:88:CD:42:40:19:34:20:15:F2:3D:D0:E0:09:28:1B:5D:86:B3:38:27:F2:D4:A1:83 The replacement in Puppet 6 is puppetserver ca list. Most likely this can be closed. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-2156) Implement --list-block-groups
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2156 Implement --list-block-groups Issue Type: Task Assignee: Unassigned Created: 2019/12/04 6:29 AM Priority: Normal Reporter: Bogdan Irimie 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
Jira (FACT-2155) Add missing legacy facts
Title: Message Title
Bogdan Irimie created an issue
Facter / FACT-2155
Add missing legacy facts
Issue Type:
Task
Assignee:
Unassigned
Created:
2019/12/04 6:18 AM
Priority:
Normal
Reporter:
Bogdan Irimie
The fallowing legacy facts are missing:
architecture => x86_64
augeasversion => 1.12.0
dhcp_servers => {
en0 => "10.160.24.1",
system => "10.160.24.1"
}
domain => wifi.tsr.corp.puppet.net
Jira (FACT-2154) Fix integration tests on Windows
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2154 Fix integration tests on Windows Issue Type: Epic Assignee: Unassigned Created: 2019/12/04 6:15 AM Priority: Normal Reporter: Bogdan Irimie 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
Jira (PUP-9465) group resource type misunderstands/misuses libuser
Title: Message Title Gabriel Nagy commented on PUP-9465 Re: group resource type misunderstands/misuses libuser Melissa Stone any thoughts on this? With forcelocal implementation also requested for AIX (PUP-7113) I would work towards uncoupling the forcelocal parameter from the libuser feature (which is a Linux-only package), and implement a separate libuser provider for the user type. 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.293306.1548368109000.53358.1575467340203%40Atlassian.JIRA.
Jira (FACT-2153) Default folder for loading facts from load path should be 'facter'
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2153 Default folder for loading facts from load path should be 'facter' Change By: Bogdan Irimie Assignee: Bogdan Irimie 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.337787.1575466253000.53350.1575466260420%40Atlassian.JIRA.
Jira (FACT-2153) Default folder for loading facts from load path should be 'facter'
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2153 Default folder for loading facts from load path should be 'facter' Issue Type: Bug Assignee: Unassigned Created: 2019/12/04 5:30 AM Priority: Normal Reporter: Bogdan Irimie 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
Jira (FACT-2152) --no-external-facts and --external-dir options should generate error
Title: Message Title Oana Tanasoiu created an issue Facter / FACT-2152 --no-external-facts and --external-dir options should generate error Issue Type: Task Assignee: Oana Tanasoiu Created: 2019/12/04 5:22 AM Priority: Normal Reporter: Oana Tanasoiu 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
Jira (PUP-9966) add acceptance tests for package gem provider
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9966 add acceptance tests for package gem provider Change By: Mihai Buzgau Sprint: Community PRs 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.321292.1565960513000.53300.1575461160224%40Atlassian.JIRA.
Jira (PUP-9966) add acceptance tests for package gem provider
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9966 add acceptance tests for package gem provider Change By: Mihai Buzgau Team: Coremunity 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.321292.1565960513000.53298.1575461160217%40Atlassian.JIRA.
Jira (PUP-9943) User type has custom retrieve() with non-standard return values
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9943 User type has custom retrieve() with non-standard return values Change By: Mihai Buzgau Team: Coremunity 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.320115.1565272699000.53291.1575461100613%40Atlassian.JIRA.
Jira (PUP-9943) User type has custom retrieve() with non-standard return values
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9943 User type has custom retrieve() with non-standard return values Change By: Mihai Buzgau Sprint: Community PRs 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.320115.1565272699000.53294.1575461100629%40Atlassian.JIRA.
Jira (FACT-2146) facter not returning expected ipaddress details on Solaris 10 with IPMP
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2146 facter not returning expected ipaddress details on Solaris 10 with IPMP 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.337174.1575268168000.53248.1575459660560%40Atlassian.JIRA.
Jira (PUP-10152) Pacman provider shouldn't be doing partial upgrades
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10152 Pacman provider shouldn't be doing partial upgrades 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.337164.1575071653000.53243.1575459600234%40Atlassian.JIRA.
Jira (FACT-2134) Facter should distinguish between CentOS 8 and CentOS 8 Stream
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2134 Facter should distinguish between CentOS 8 and CentOS 8 Stream 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.336204.1574351826000.53237.1575459540436%40Atlassian.JIRA.
Jira (FACT-2134) Facter should distinguish between CentOS 8 and CentOS 8 Stream
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2134 Facter should distinguish between CentOS 8 and CentOS 8 Stream Change By: Mihai Buzgau Team: 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.336204.1574351826000.53239.1575459540444%40Atlassian.JIRA.
Jira (PUP-10159) Can't differentiate between cert and request on Puppet Server
Title: Message Title Mihai Buzgau commented on PUP-10159 Re: Can't differentiate between cert and request on Puppet Server Not sure if this is a PUP, Server or PE Console ticket. /cc Josh Cooper Maggie Dreyer We will try to do some digging into it. 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.335692.1574091306000.53232.1575459480203%40Atlassian.JIRA.
Jira (PUP-10159) Can't differentiate between cert and request on Puppet Server
Title: Message Title Mihai Buzgau moved an issue Puppet / PUP-10159 Can't differentiate between cert and request on Puppet Server Change By: Mihai Buzgau Key: PA PUP - 3017 10159 Project: Puppet Agent 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.335692.1574091306000.53230.1575459360147%40Atlassian.JIRA.
Jira (PUP-10158) Filename with non-UTF8-encoding corrupts state.yaml
Title: Message Title
Torsten Roloff created an issue
Puppet / PUP-10158
Filename with non-UTF8-encoding corrupts state.yaml
Issue Type:
Bug
Affects Versions:
PUP 6.10.1
Assignee:
Unassigned
Attachments:
test_from.zip
Components:
Windows
Created:
2019/12/04 3:20 AM
Priority:
Minor
Reporter:
Torsten Roloff
Puppet Version: Agent 5.5.14 Puppet Server Version: 6.7.2-1stretch OS Name/Version: Windows 7 ** I'm not an encoding nor puppet expert, this description is what happens from my point of view: I use a simple file resource to copy a directory test_from.zip to a windows client like this:
file { 'c:/test_to':
ensure => directory,
backup => false,
Jira (FACT-2151) ^ MILESTONE: Acceptance tests passing
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2151 ^ MILESTONE: Acceptance tests passing Change By: Mihai Buzgau Priority: Normal Blocker 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.337768.1575448988000.53163.1575449520118%40Atlassian.JIRA.
Jira (FACT-2151) ^ MILESTONE: Acceptance tests passing
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2151 ^ MILESTONE: Acceptance tests passing Change By: Mihai Buzgau Summary: ^ MILESTONE: Acceptance tests passing ^ 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.337768.1575448988000.53162.1575449100160%40Atlassian.JIRA.
Jira (FACT-2151) ^ MILESTONE: Acceptance tests passing ^
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2151 ^ MILESTONE: Acceptance tests passing ^ Change By: Mihai Buzgau Summary: ^ ^^ MILESTONE: Acceptance tests passing ^ ^^ 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.337768.1575448988000.53161.1575449100130%40Atlassian.JIRA.
Jira (FACT-2151) ^^^^^^^ MILESTONE: Acceptance tests passing ^^^^^^^
Title: Message Title Mihai Buzgau created an issue Facter / FACT-2151 ^^^ MILESTONE: Acceptance tests passing ^^^ Issue Type: Task Assignee: Unassigned Created: 2019/12/04 12:43 AM Priority: Normal Reporter: Mihai Buzgau 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
Jira (FACT-2150) Remove ruby fact when --no-ruby flact is true
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2150 Remove ruby fact when --no-ruby flact is true Change By: Mihai Buzgau Priority: High Normal 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.337485.1575387836000.53158.1575448920250%40Atlassian.JIRA.
Jira (FACT-2150) Remove ruby fact when --no-ruby flact is true
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2150 Remove ruby fact when --no-ruby flact is true Change By: Mihai Buzgau Priority: Normal High 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.337485.1575387836000.53155.1575448860228%40Atlassian.JIRA.
