Jira (FACT-2104) Create load average resolver for fedora
Title: Message Title Gheorghe Campean created an issue Facter / FACT-2104 Create load average resolver for fedora Issue Type: Task Assignee: Gheorghe Campean Created: 2019/11/04 11:35 PM Priority: Normal Reporter: Gheorghe Campean 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 (PDB-2423) Limit initial sync to catalogs, factsets, and deactivate node commands
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-2423 Limit initial sync to catalogs, factsets, and deactivate node commands Change By: Austin Blatt To limit start up time for PuppetDB replicas, we need to limit the amount of data that is transferred.Currently we sync* Catalogs* Factsets* Reports* Node deactivation* Catalog Inputs (for cd4pe)By far the two largest sets of data are reports and catalog inputs, so I recommend think that initial sync is should be limited to the following to ensure a somewhat fast startup time .* Catalogs* Factsets* Node deactivationThe most commonly suggested modification to this list is to also sync _only_ the latest reports. I haven't heard a compelling reason to spend startup time syncing the latest report for a replica PuppetDB because all the time PDB spends in startup sync it is drifting out of alignment. If someone has a good reason that a replica PuppetDB should have the latest reports when it starts up, I would be happy to add that to the list of things to sync. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-2423) Limit initial sync to catalogs, factsets, and deactivate node commands
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-2423 Limit initial sync to catalogs, factsets, and deactivate node commands Change By: Austin Blatt Assignee: Austin Blatt 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.116056.1455149697000.19218.1572912180445%40Atlassian.JIRA.
Jira (PDB-2423) Limit initial sync to catalogs, factsets, and deactivate node commands
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-2423 Limit initial sync to catalogs, factsets, and deactivate node commands Change By: Austin Blatt This should help replica provisioning To limit start up time while providing enough consistency for PuppetDB replicas, we need to limit the things amount of data that is transferred.Currently we care about sync* Catalogs* Factsets* Reports* Node deactivation* Catalog Inputs (for cd4pe)By far the two largest sets of data are reports and catalog inputs, so I recommend that initial sync is limited to the following.* Catalogs* Factsets* Node deactivationThe most commonly suggested modification to this list is to sync _only_ the latest reports. I haven't heard a compelling reason to spend startup time syncing the latest report for a replica PuppetDB because all the time PDB spends in startup sync it is drifting out of alignment. If someone has a good reason that a replica PuppetDB should have the latest reports when it starts up, I would be happy to add that to the list of things to sync. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-2423) Limit initial sync to catalogs, factsets, and deactivate node commands
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-2423 Limit initial sync to catalogs, factsets, and deactivate node commands Change By: Austin Blatt Summary: Limit initial sync to latest catalogs , factsets, and reports deactivate node commands 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.116056.1455149697000.19199.1572911820161%40Atlassian.JIRA.
Jira (PDB-3417) New install of PE 2017.1.1 has store_report and 'store report' metrics
Title: Message Title Zachary Kent commented on PDB-3417 Re: New install of PE 2017.1.1 has store_report and 'store report' metrics Looks like the PR which fixed the broken command size metrics reintroduced this bug. Before this pr the block that would add the incorrect `store_report` metric type wouldn't run because of the missing `Content-Length` header with compressed requests. Now that this has been fixed duplicate metrics are being incorrectly added again. Will fix shortly. 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.184151.1491345731000.18865.1572902820240%40Atlassian.JIRA.
Jira (PDB-3417) New install of PE 2017.1.1 has store_report and 'store report' metrics
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-3417 New install of PE 2017.1.1 has store_report and 'store report' metrics Change By: Zachary Kent Assignee: Zachary Kent 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.184151.1491345731000.18853.1572902520396%40Atlassian.JIRA.
Jira (FACT-2018) Google Compute Engine metadata facts need endpoint change
Title: Message Title James Wen commented on FACT-2018 Re: Google Compute Engine metadata facts need endpoint change Just curious, why was this fix for removing/updating the calls to the legacy GCE metadata endpoints not added to the 3.12.x release line? 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.324465.156829223.18733.1572899700160%40Atlassian.JIRA.
Jira (PDB-4485) Remove Ubuntu 14.04 from puppetdb pipelines
Title: Message Title Sara Meisburger updated an issue PuppetDB / PDB-4485 Remove Ubuntu 14.04 from puppetdb pipelines Change By: Sara Meisburger Sprint: Release Engineering 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.321534.156631181.18385.1572893760471%40Atlassian.JIRA.
Jira (PUP-9937) Docker Image - wrong version
Title: Message Title Sara Meisburger updated an issue Puppet / PUP-9937 Docker Image - wrong version Change By: Sara Meisburger Sprint: Release Engineering 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.319591.1565013862000.18376.1572893640463%40Atlassian.JIRA.
Jira (PUP-2019) Expose catalog version
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2019 Expose catalog version 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.29636.1395577137000.18272.1572891840731%40Atlassian.JIRA.
Jira (PUP-2019) Expose catalog version
Title: Message Title Josh Cooper commented on PUP-2019 Re: Expose catalog version The catalog.version and catalog.environment are serialized with the catalog, so are available on the agent side. However, puppet doesn't support interpolating values in the pre/post run command. I can imagine that being useful though. 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.29636.1395577137000.18265.1572891840704%40Atlassian.JIRA.
Jira (PUP-2019) Expose catalog version
Title: Message Title Henrik Lindberg commented on PUP-2019 Re: Expose catalog version Rob Braden I don't have anything to add as the request is for the version to be available agent side - maybe Josh Cooper has an idea for how you can get that. 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.29636.1395577137000.18169.1572890340340%40Atlassian.JIRA.
Jira (BOLT-1528) Bolt returning json data for many nodes causing memory contention and very slow bolt task runs.
Title: Message Title Chris Webster updated an issue Puppet Task Runner / BOLT-1528 Bolt returning json data for many nodes causing memory contention and very slow bolt task runs. Change By: Chris Webster Bolt returning json JSON data for many nodes can cause the local system to use an excessive amount of memory. This does not cause the bolt Bolt run to fail but causes the run to stall and take much longer to complete the more nodes being executed on. We have requested that they verify this theory by monitoring memory usage during a bolt task run but have not received a response to that request. As seen with this ticket a local run of the Powershell script completes in 30 seconds. Running with bolt Bolt on 40 servers it takes 20 to 30 minutes and can result in inconsistent errors. Adding more agents only makes the issue whorse worse .Lowing concurrency from 100 to 25 did not have any effect on performance as reported by the client. ~* Please see Zendesk Support tab for further comments and attachments.~ Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-2019) Expose catalog version
Title: Message Title Rob Braden commented on PUP-2019 Re: Expose catalog version Henrik Lindberg or Nathan Grubb - were you able to work out a solution for this? Does this still need attention? 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.29636.1395577137000.18148.1572889800314%40Atlassian.JIRA.
Jira (BOLT-1528) Bolt returning json data for many nodes causing memory contention and very slow bolt task runs.
Title: Message Title Chris Webster updated an issue Puppet Task Runner / BOLT-1528 Bolt returning json data for many nodes causing memory contention and very slow bolt task runs. Change By: Chris Webster Attachment: Screen_Shot_2019-10-24_at_5.02.30_PM_thumb.png 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.333408.1572889303000.18138.1572889740351%40Atlassian.JIRA.
Jira (PUP-10115) "glob" matches are not sorted in alphanumerical order as documented, but in directory order instead
Title: Message Title Rob Braden updated an issue Puppet / PUP-10115 "glob" matches are not sorted in alphanumerical order as documented, but in directory order instead Change By: Rob Braden Sub-team: Language 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.332258.1572282843000.18131.1572889680368%40Atlassian.JIRA.
Jira (PUP-10115) "glob" matches are not sorted in alphanumerical order as documented, but in directory order instead
Title: Message Title Rob Braden updated an issue Puppet / PUP-10115 "glob" matches are not sorted in alphanumerical order as documented, but in directory order instead Change By: Rob Braden 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.332258.1572282843000.18128.1572889680360%40Atlassian.JIRA.
Jira (BOLT-1528) Bolt returning json data for many nodes causing memory contention and very slow bolt task runs.
Title: Message Title Chris Webster updated an issue Puppet Task Runner / BOLT-1528 Bolt returning json data for many nodes causing memory contention and very slow bolt task runs. Change By: Chris Webster Bolt returning json data for many nodes can cause the local system to use an excessive amount of memory. This does not cause the bolt run to fail but causes the run to stall and take much longer to complete the more nodes being executed on. We have requested that they verify this theory by monitoring memory usage during a bolt task run but have not received a response to that request.As seen with this ticket a local run of the Powershell script completes in 30 seconds. Running with bolt on 40 servers it takes 20 to 30 minutes and can result in inconsistent errors. Adding more agents only makes the issue whorse. Lowing concurrency from 100 to 25 did not have any effect on performance as reported by the client. - original message - Hello Jose, We haven't heard from you in a while and wanted to check in to see if you needed any additional help. In the meantime, I'm setting this issue to resolved; but if you'd like to return to working on this, you're welcome to reply at https://support.puppetlabs.com/requests/36583 to re-open the issue. Thank you,Chris ~* Please see Zendesk Support tab for further comments and attachments.~ Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10119) ZFS delegations/permissions
Title: Message Title Rob Braden updated an issue Puppet / PUP-10119 ZFS delegations/permissions Change By: Rob Braden 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.54.1572725749000.18118.1572889620355%40Atlassian.JIRA.
Jira (BOLT-1528) Bolt returning json data for many nodes causing memory contention and very slow bolt task runs.
Title: Message Title Austin Boyd updated an issue Puppet Task Runner / BOLT-1528 Bolt returning json data for many nodes causing memory contention and very slow bolt task runs. Change By: Austin Boyd Labels: jira_escalated 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.333408.1572889303000.18094.1572889320887%40Atlassian.JIRA.
Jira (BOLT-1528) Bolt returning json data for many nodes causing memory contention and very slow bolt task runs.
Title: Message Title Austin Boyd updated an issue Puppet Task Runner / BOLT-1528 Bolt returning json data for many nodes causing memory contention and very slow bolt task runs. Change By: Austin Boyd Zendesk Ticket IDs: 36583 Zendesk Ticket Count: 1 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.333408.1572889303000.18092.1572889320876%40Atlassian.JIRA.
Jira (BOLT-1528) Bolt returning json data for many nodes causing memory contention and very slow bolt task runs.
Title: Message Title Chris Webster created an issue Puppet Task Runner / BOLT-1528 Bolt returning json data for many nodes causing memory contention and very slow bolt task runs. Issue Type: Improvement Assignee: Unassigned Created: 2019/11/04 9:41 AM Priority: Normal Reporter: Chris Webster Bolt returning json data for many nodes can cause the local system to use an excessive amount of memory. This does not cause the bolt run to fail but causes the run to stall and take much longer to complete the more nodes being executed on. We have requested that they verify this theory by monitoring memory usage during a bolt task run but have not received a response to that request. As seen with this ticket a local run of the Powershell script completes in 30 seconds. Running with bolt on 40 servers it takes 20 to 30 minutes and can result in inconsistent errors. Adding more agents only makes the issue whorse. Lowing concurrency from 100 to 25 did not have any effect on performance as reported by the client. - original message - Hello Jose, We haven't heard from you in a while and wanted to check in to see if you needed any additional help. In the meantime, I'm setting this issue to resolved; but if you'd like to return to working on this, you're welcome to reply at https://support.puppetlabs.com/requests/36583 to re-open the issue. Thank you, Chris * Please see Zendesk Support tab for further comments and attachments. Add
Jira (FACT-2103) dmidecode resolver for redhat 5
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2103 dmidecode resolver for redhat 5 Issue Type: Task Assignee: Unassigned Created: 2019/11/04 7:38 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-2102) Google Compute Engine metadata facts need endpoint change <= 2.5.6
Title: Message Title Eric Johnson created an issue Facter / FACT-2102 Google Compute Engine metadata facts need endpoint change <= 2.5.6 Issue Type: Bug Affects Versions: FACT 2.5.1, FACT 2.5.2 Assignee: Gabriel Nagy Created: 2019/11/04 6:17 AM Environment: Ruby-based facter versions <= 2.5.6 Priority: Major Reporter: Eric Johnson Google Compute Engine's internal metadata service will be deprecating the 'v1beta1' endpoint sometime before end of calendar year 2019. The GCE metadata-helper[1] should be updated to use the 'v1' endpoint instead. NOTE: FACT-2018 addressed this issue for Facter 3.x, but the ruby based 2.x also needs to be fixed. Note that using the 'v1' endpoint also requires setting a custom User-Agent header that was not necessary in the old 'v1beta1' endpoint. Using 'curl' in a simple bash script as an example, I would need to change, curl http://metadata.google.internal/computeMetadata/v1beta1/instance/name to this, curl -H "Metadata-flavor: Google" http://metadata.google.internal/computeMetadata/v1/instance/name For more details about GCE metadata, please see https://cloud.google.com/compute/docs/storing-retrieving-metadata [1] https://github.com/puppetlabs/facter/blob/2.x/lib/facter/gce/metadata.rb#L20
Jira (PUP-9041) AIX nim provider can't be used on a NIM master
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9041 AIX nim provider can't be used on a NIM master Change By: Mihai Buzgau Sprint: Windows Imaging Hopper, NW - 2019-08-07, NW - 2019-08-21, NW - 2019-09-03, NW - 2019-09-18, NW - 2019-10-02, NW - 2019-10-16, NW - 2019-10-30 , 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.267945.153332494.17750.1572875100522%40Atlassian.JIRA.
Jira (PUP-9562) User resource does not respect forcelocal for the comment parameter
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-9562 User resource does not respect forcelocal for the comment parameter Change By: Gabriel Nagy Release Notes Summary: Prior to this fix, a user resource configured with forcelocal would still try to sync the comment with the external directory services, meaning that subsequent Puppet runs would not be idempotent.To fix this, we compare the `in_sync` with the contents of the local `/etc/passwd` file. 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.300292.1552589325000.17711.1572866640146%40Atlassian.JIRA.
Jira (PUP-10023) Expand the apt provider to support virtual packages
Title: Message Title Alexandru Popa updated an issue Puppet / PUP-10023 Expand the apt provider to support virtual packages Change By: Alexandru Popa Release Notes Summary: Apt and dpkg providers now supports virtual packages.Mandatory fields in puppt resource file is allow_virtual=> true.By default allow_virtual is set to false. 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.324926.1568705952000.17704.1572866280766%40Atlassian.JIRA.
Jira (FACT-2101) Create filesystems resolver for fedora.
Title: Message Title Gheorghe Campean created an issue Facter / FACT-2101 Create filesystems resolver for fedora. Issue Type: Task Assignee: Gheorghe Campean Created: 2019/11/04 2:47 AM Priority: Normal Reporter: Gheorghe Campean 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-2100) SSH facts for Sles
Title: Message Title Alexandru Popa assigned an issue to Alexandru Popa Facter / FACT-2100 SSH facts for Sles Change By: Alexandru Popa Assignee: Alexandru Popa 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.58.1572860365000.17662.1572860400301%40Atlassian.JIRA.
Jira (FACT-2100) SSH facts for Sles
Title: Message Title Alexandru Popa created an issue Facter / FACT-2100 SSH facts for Sles Issue Type: Task Assignee: Unassigned Created: 2019/11/04 1:39 AM Priority: Normal Reporter: Alexandru Popa 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-9963) The 'value' field of 'selboolean' should accept Booleans
Title: Message Title Ciprian Badescu commented on PUP-9963 Re: The 'value' field of 'selboolean' should accept Booleans Trevor Vaughan, PR 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.320668.1565704234000.17644.1572857040117%40Atlassian.JIRA.
Jira (PUP-10116) Add GKE hypervisor to pxp-agent and puppet
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-10116 Add GKE hypervisor to pxp-agent and puppet Change By: Ciprian Badescu Sprint: NW - 2019-11-13 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.332952.1572515789000.17638.1572856200132%40Atlassian.JIRA.
Jira (FACT-2090) Investigate config file for Facter 3.x
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2090 Investigate config file for Facter 3.x 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.332606.1572424923000.17636.1572854760059%40Atlassian.JIRA.
