Jira (BOLT-1489) WinRM: Misleading error message when cacert file cannot be found
Title: Message Title Cas Donoghue commented on BOLT-1489 Re: WinRM: Misleading error message when cacert file cannot be found Moved to github issue https://github.com/puppetlabs/bolt/issues/1164 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.318252.156416412.62647.1566311640116%40Atlassian.JIRA.
Jira (BOLT-1489) WinRM: Misleading error message when cacert file cannot be found
Title: Message Title Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-1489 WinRM: Misleading error message when cacert file cannot be found Change By: Yasmin Rajabi Labels: ghm 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.318252.156416412.61922.1566254700282%40Atlassian.JIRA.
Jira (BOLT-1489) WinRM: Misleading error message when cacert file cannot be found
Title: Message Title Edward Cullen created an issue Puppet Task Runner / BOLT-1489 WinRM: Misleading error message when cacert file cannot be found Issue Type: Bug Affects Versions: BOLT 1.26.0 Assignee: Unassigned Components: WinRM Created: 2019/07/26 11:02 AM Environment: Windows 10 Priority: Normal Reporter: Edward Cullen If a cacert file is specified in bolt.yaml and the specified file cannot be found, rather than returning an obvious/helpful error, such as "Configured cacert file cannot be found.", Bolt will attempt to connect and return the following error: [ { "node": "host.example.com",