Jira (PUP-3125) Add support for Windows .VSIX file to the package resource
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-3125 Add support for Windows .VSIX file to the package resource Change By: Geoff Nichols Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-396) Support msu windows packages
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-396 Support msu windows packages Change By: Geoff Nichols Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-395) Support msp windows packages
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-395 Support msp windows packages Change By: Geoff Nichols Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1759) facter should compute the correct logical and physical cpu count on Power for the processors.count and processors.physicalcount facts
Title: Message Title Geoff Nichols assigned an issue to Sean McDonald Facter / FACT-1759 facter should compute the correct logical and physical cpu count on Power for the processors.count and processors.physicalcount facts Change By: Geoff Nichols Assignee: Enis Inan Sean McDonald Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7983) Enable testing puppet-agent built against system openssl on RHEL in PA CI pipes
Title: Message Title Jayant Sane commented on PUP-7983 Re: Enable testing puppet-agent built against system openssl on RHEL in PA CI pipes PR: https://github.com/puppetlabs/puppet/pull/6271 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7983) Enable testing puppet-agent built against system openssl on RHEL in PA CI pipes
Title: Message Title Jayant Sane assigned an issue to Jayant Sane Puppet / PUP-7983 Enable testing puppet-agent built against system openssl on RHEL in PA CI pipes Change By: Jayant Sane Assignee: Jayant Sane Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-585) Test PA built against system openssl in CI test pipelines
Title: Message Title Jayant Sane commented on HI-585 Re: Test PA built against system openssl in CI test pipelines PR: https://github.com/puppetlabs/hiera/pull/408 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1774) Enable testing PA built against system openssl in CI test pipelines on RHEL platform
Title: Message Title Jayant Sane commented on FACT-1774 Re: Enable testing PA built against system openssl in CI test pipelines on RHEL platform PR: https://github.com/puppetlabs/facter/pull/1659 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8039) Puppet 4.10.x: Only warn once when gettext cannot be found
Title: Message Title Maggie Dreyer created an issue Puppet / PUP-8039 Puppet 4.10.x: Only warn once when gettext cannot be found Issue Type: Bug Assignee: Maggie Dreyer Created: 2017/10/09 4:53 PM Priority: Normal Reporter: Maggie Dreyer Currently in Puppet >4.10.5, if the gettext-setup gem cannot be found we will issue a warning for every single module that is loaded, each time that module is loaded. This causes a huge amount of log spam in environments that load a lot of modules, all with nearly the same message: 2017-09-26 00:05:19,103 WARN [qtp1394837016-64] [puppetserver] Puppet GettextSetup is not available, skipping GettextSetup initialization for . We should only issue this warning once. Add Comment This message was
Jira (PUP-8024) Delay loading module translations until 'translate' is used for that module
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8024 Delay loading module translations until 'translate' is used for that module Change By: Craig Gomes Fix Version/s: PUP 5.3.3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7924) Co-existence of Puppet versions on Windows
Title: Message Title Josh Cooper commented on PUP-7924 Re: Co-existence of Puppet versions on Windows Hi Jay Mav, it's not currently possible, because all Puppet MSI's use the same UpgradeCode. This is what windows installers uses to detect that a newer MSI is updating an already installed version. One option is to use Orca to edit the UpgradeCode in the MSI, so that they'll be viewed as unrelated applications. Note this isn't a supported workflow, so I'm going to close this ticket as won't fix. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7924) Co-existence of Puppet versions on Windows
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7924 Co-existence of Puppet versions on Windows Change By: Josh Cooper Fix Version/s: PUP 4.7.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8016) Updated module translations will not be loaded without restarting puppet
Title: Message Title Michael Smith commented on PUP-8016 Re: Updated module translations will not be loaded without restarting puppet Understood. I believe a fix for PUP-8024 would likely make this trivial to support. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8016) Updated module translations will not be loaded without restarting puppet
Title: Message Title Craig Gomes commented on PUP-8016 Re: Updated module translations will not be loaded without restarting puppet Waiting for customer feedback on this before moving forward with a fix. This could be a fairly complex fix and testing undertaking. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8016) Updated module translations will not be loaded without restarting puppet
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8016 Updated module translations will not be loaded without restarting puppet Change By: Craig Gomes Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8035) Failed Runs showing as Unchanged in Console due to Cached Catalog
Title: Message Title Josh Cooper commented on PUP-8035 Re: Failed Runs showing as Unchanged in Console due to Cached Catalog The error in the zendesk ticket shows there is a problem compiling the catalog: Error while evaluating a Resource Statement, Duplicate declaration: File[/XXX/.rhosts] is already declared in file /etc/puppetlabs/puppet/environments/production/modules/compliance/manifests/solaris/users.pp:148 When running from the command line, it looks like the user is running puppet agent --test --debug which implicitly sets usecacheonfailure to false, which is why the agent doesn't fallback to the cached catalog. If you want the same behavior when the agent is running on scheduled runs, then set usecacheonfailure=false in puppet.conf Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8028) Puppet considers directories as tasks
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8028 Puppet considers directories as tasks Change By: Craig Gomes Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8028) Puppet considers directories as tasks
Title: Message Title Craig Gomes assigned an issue to Thomas Hallgren Puppet / PUP-8028 Puppet considers directories as tasks Change By: Craig Gomes Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8035) Failed Runs showing as Unchanged in Console due to Cached Catalog
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8035 Failed Runs showing as Unchanged in Console due to Cached Catalog Change By: Craig Gomes Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1722) off-by-one error in using gethostname()
Title: Message Title Geoff Nichols commented on FACT-1722 Re: off-by-one error in using gethostname() Merged to facter#master at https://github.com/puppetlabs/facter/commit/32358935d38380b6b8e1a6e2ff29c29e37ead2f9. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8038) rubocop-i18n GetText/DecorateString is broken
Title: Message Title Eric Delaney created an issue Puppet / PUP-8038 rubocop-i18n GetText/DecorateString is broken Issue Type: Task Assignee: Eric Delaney Created: 2017/10/09 1:21 PM Priority: Normal Reporter: Eric Delaney in the rubocop-i18n cops' there is a cop GetText/DecorateString which appears to be incorrect. I believe the intent was for it to complain when it found a string that does not have a decorator method around it. Need to update the cop Need to add more spec tests Need to add the cop to the README.md Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-8008) puppet module install fails to install apt 4.2.0
Title: Message Title Josh Cooper commented on PUP-8008 Re: puppet module install fails to install apt 4.2.0 It would be helpful to run an older (4.10.1) and newer (5.3.2) puppet with the --http_debug option to see how the agent/PMT is encoding HTTP parameters differently when there is more than 20 released versions of a module. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8024) Delay loading module translations until 'translate' is used for that module
Title: Message Title
Moses Mendoza updated an issue
Puppet / PUP-8024
Delay loading module translations until 'translate' is used for that module
Change By:
Moses Mendoza
Currently, we attempt to initialize translations machinery for all modules as soon as they are loaded, despite the fact in many contexts we do not need to display any translations (e.g. {{module list}}). We do this even for modules that do not have any translation files or marked strings.We also attempt to cache translations after they're loaded, but not associated with any existing cache lifetimes. So the only way to cause a translation to be reloaded is to restart the process.Instead, we should look into only initializing gettext for modules when we first need to call the {{translate()}} or {{_()}} functions in module code. This would spread out expensive initialization and avoid it altogether in contexts where it is unnecessary. *Notes on decoupling module naming from locales/config.yaml project name*From comment below:{quote}As part of this, we should remove the requirement that the module have metadata (relies on forge_name) and remove the coupling of metadata naming and locales/config.yaml's project_name.{quote}Benchmarks in puppet have shown a non-trivial performance degradation if there is a mismatch between the module's metadata name, and the locales/config.yaml's project_name:With matching names:{code}mkdir -p /var/folders/0_/6qt793gx6w706cq1q9kc0w78gq/T/many_modules20171009-2426-1l58rtz user system totalrealRun 13.70 0.46 4.17 ( 4.171436)Run 22.84 0.13 2.97 ( 2.974983)Run 32.89 0.12 3.01 ( 3.016188)Run 42.91 0.13 3.04 ( 3.036231)Run 52.77 0.15 2.92 ( 2.932649)Run 62.80 0.12 2.92 ( 2.910116)Run 73.24 0.11 3.35 ( 3.359197)Run 82.76 0.15 2.91 ( 2.909707)Run 93.26 0.15 3.41 ( 3.414169)Run 10 3.69 0.14 3.83 ( 3.835340)> total:30.86 1.66 32.53 ( 32.560017)> avg: 3.086000 0.166000 3.253000 ( 3.256002){code}with mismatched names:{code}mkdir -p /var/folders/0_/6qt793gx6w706cq1q9kc0w78gq/T/many_modules20171009-2350-11p565v user system totalrealRun 13.68 0.46 4.15 ( 4.157170)Run 23.30 0.25 3.55 ( 3.552481)Run 33.18 0.25 3.43 ( 3.430290)Run 43.40 0.26 3.66 ( 3.662123)Run 53.69 0.31 4.00 ( 4.010465)Run 63.60 0.26 3.86 ( 3.866366)Run 73.32 0.25 3.57 ( 3.571592)Run 83.61 0.32 3.93 ( 3.943484)Run 93.56 0.31 3.87 ( 3.866563)Run 10 3.99 0.26 4.25 ( 4.247610)> total:35.33 2.93 38.27 ( 38.308143)> avg: 3.533000 0.293000 3.827000 ( 3.830814){code}Note ~ 6 second cumulative runtime increase
Jira (PUP-8020) Add data types Nodes and Node to puppet for tasks/plans
Title: Message Title Thomas Hallgren commented on PUP-8020 Re: Add data types Nodes and Node to puppet for tasks/plans If a target is multiple nodes already, then that's not a good term. The name must signify one URI and the options to pass along with that URI. It's difficult to come up with a descriptive term given that we don't yet know what those options are or how they will be used. One way to resolve this would of course be to prefix the name with a namespace, e.g. Bolt::Node, or alternatively, use a concatenated name for the type such as BoltNode or TargetNode. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8037) Configuring "server_urls" causes connection attempts to port 0
Title: Message Title Erik Hansen commented on PUP-8037 Re: Configuring "server_urls" causes connection attempts to port 0 Also, in some situations these connection attempts are made to an actual server and not one called 'nil': Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': Connection refused - connect(2) for "puppet" port 0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8037) Configuring "server_urls" causes connection attempts to port 0
Title: Message Title Erik Hansen created an issue Puppet / PUP-8037 Configuring "server_urls" causes connection attempts to port 0 Issue Type: Bug Affects Versions: PUP 4.10.8 Assignee: Unassigned Created: 2017/10/09 12:43 PM Priority: Normal Reporter: Erik Hansen When configuring an agent with "server_urls", failover events that exhaust the list of servers result in connection attempts to port 0: Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': Connection refused - connect(2) for nil port 0 I couldn't find this behavior documented anywhere. Is it intentional?
Jira (PUP-8036) Use of server_urls can cause misleading agent errors
Title: Message Title
Erik Hansen updated an issue
Puppet / PUP-8036
Use of server_urls can cause misleading agent errors
Change By:
Erik Hansen
h3. The issue:the "server_urls" configuration setting can mask server-side issues by mistakingly pointing to a connectivity issue on port 0:{noformat}Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': Connection refused - connect(2) for nil port 0{noformat}h3. Replication: Configure an agent to connect to a master with the server_list setting:{noformat}[agent]#server = pe-201724-master.puppetdebug.vlanserver_list = pe-201724-master.puppetdebug.vlan:8140{noformat}Revoke the agent's certificate on the master and observer observe the error on the next agent run:h3. Actual result:{noformat}Warning: Could not select a functional puppet masterWarning: Unable to fetch my node definition, but the agent run will continue:Warning: Connection refused - connect(2) for nil port 0Info: Retrieving pluginfactsError: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': Connection refused - connect(2) for nil port 0Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Could not evaluate: Could not retrieve file metadata for puppet:///pluginfacts: Connection refused - connect(2) for nil port 0Info: Retrieving pluginError: /File[/opt/puppetlabs/puppet/cache/lib]: Failed to generate additional resources using 'eval_generate': Connection refused - connect(2) for nil port 0Error: /File[/opt/puppetlabs/puppet/cache/lib]: Could not evaluate: Could not retrieve file metadata for puppet:///plugins: Connection refused - connect(2) for nil port 0Info: Loading factsError: Could not retrieve catalog from remote server: Connection refused - connect(2) for nil port 0Warning: Not using cache on failed catalogError: Could not retrieve catalog; skipping runError: Could not send report: Connection refused - connect(2) for nil port 0{noformat}h3. Expected result:Change the agent's configuration to use the "server" setting and observe the difference. The error points more clearly to an SSL issue:{noformat}Warning: Unable to fetch my node definition, but the agent run will continue:Warning: SSL_connect SYSCALL returned=5 errno=0 state=unknown stateInfo: Retrieving pluginfactsError: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': SSL_connect SYSCALL returned=5 errno=0 state=unknown stateError: /File[/opt/puppetlabs/puppet/cache/facts.d]: Could not evaluate: Could not retrieve file metadata for puppet:///pluginfacts: SSL_connect SYSCALL returned=5 errno=0 state=unknown stateInfo: Retrieving pluginError: /File[/opt/puppetlabs/puppet/cache/lib]: Failed to generate additional resources using 'eval_generate': SSL_connect SYSCALL returned=5 errno=0 state=unknown stateError: /File[/opt/puppetlabs/puppet/cache/lib]: Could not evaluate: Could not retrieve file metadata for puppet:///plugins: SSL_connect SYSCALL returned=5 errno=0 state=unknown stateInfo: Loading factsError: Could not retrieve catalog from remote server: SSL_connect SYSCALL returned=5 errno=0 state=unknown stateWarning: Not using cache on failed catalogError: Could not retrieve catalog; skipping runError: Could
Jira (PUP-8036) Use of server_urls can cause misleading agent errors
Title: Message Title Erik Hansen created an issue Puppet / PUP-8036 Use of server_urls can cause misleading agent errors Issue Type: Bug Affects Versions: PUP 4.10.8 Assignee: Unassigned Created: 2017/10/09 12:25 PM Priority: Normal Reporter: Erik Hansen The issue: the "server_urls" configuration setting can mask server-side issues by mistakingly pointing to a connectivity issue on port 0: Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': Connection refused - connect(2) for nil port 0 Replication: Configure an agent to connect to a master with the server_list setting:
Jira (PUP-8020) Add data types Nodes and Node to puppet for tasks/plans
Title: Message Title
Alex Dreyer commented on PUP-8020
Re: Add data types Nodes and Node to puppet for tasks/plans
In out terminology elsewhere a target is already multiple nodes. Targets or Target[] may confuse that.
Also targets can be described in forms other than a list of nodes. They could be a pql query or something from an arbitrary inventory plugin.
If we are going to parse a string to create a target we should take this opportunity to split on the same regex we use in puppet-task. {boost::regex("[[:space:],]+")}
{/[\w,]+/}
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8022) apt.puppetlabs.com repo cannot be mirrored via debmirror using https connection
Title: Message Title Moses Mendoza commented on PUP-8022 Re: apt.puppetlabs.com repo cannot be mirrored via debmirror using https connection fyi Rob Braden Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8027) gem provider does not work behind proxy
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-8027 gem provider does not work behind proxy Change By: Moses Mendoza Sprint: Platform Core Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8027) gem provider does not work behind proxy
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-8027 gem provider does not work behind proxy Change By: Moses Mendoza Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8022) apt.puppetlabs.com repo cannot be mirrored via debmirror using https connection
Title: Message Title Moses Mendoza assigned an issue to Rob Braden Puppet / PUP-8022 apt.puppetlabs.com repo cannot be mirrored via debmirror using https connection Change By: Moses Mendoza Assignee: Rob Braden Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8035) Failed Runs showing as Unchanged in Console due to Cached Catalog
Title: Message Title Daniel Mcilhagga assigned an issue to Unassigned Puppet / PUP-8035 Failed Runs showing as Unchanged in Console due to Cached Catalog Change By: Daniel Mcilhagga Assignee: Ryan Coleman Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8035) Failed Runs showing as Unchanged in Console due to Cached Catalog
Title: Message Title Daniel Mcilhagga moved an issue Puppet / PUP-8035 Failed Runs showing as Unchanged in Console due to Cached Catalog Change By: Daniel Mcilhagga Key: ENTERPRISE PUP - 1099 8035 Project: Puppet Enterprise Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8020) Add data types Nodes and Node to puppet for tasks/plans
Title: Message Title Thomas Hallgren commented on PUP-8020 Re: Add data types Nodes and Node to puppet for tasks/plans Given the terminology conflict, I'd like to call the new type Target instead of Node. I think that term fits well with the domain. "Upload file to target x and y", "execute the command on the following targets", "The target host is x.y.z", etc. Eric Sorenson, Alex Dreyer, I'd like to hear your opinion on this. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8020) Add data types Nodes and Node to puppet for tasks/plans
Title: Message Title Thomas Hallgren commented on PUP-8020 Re: Add data types Nodes and Node to puppet for tasks/plans A complicating factor when implementing the new Node data type type is that node is a keyword in Puppet which parses into a NodeDefinition which is subsequently transformed into a special Puppet::Resource::Type. It is still possible to use Node as a type name (with upper-case 'N') when running with --tasks but do we really want to deliberately create this conflict? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6040) "puppet facts" outputs indirector object instead of simple fact list
Title: Message Title Reid Vandewiele updated an issue Puppet / PUP-6040 "puppet facts" outputs indirector object instead of simple fact list Change By: Reid Vandewiele Labels: cspapercuts Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
