Jira (PUP-10844) Agent failures with server_list when one puppetserver fails

[Vadym Chepkov (Jira)]

Title: Message Title

Vadym Chepkov commented on PUP-10844   Re: Agent failures with server_list when one puppetserver fails Something occurred to me. Is it possible the problem is on 'presentation' side and not on functionality? I looked through puppetserver.log on the replica and I do see nodes connecting to it during primary shutdown: 2021-03-03T07:27:53.295-05:00 INFO  [qtp1835431929-14632] [puppetserver] Puppet Not using expired facts for pubtstx-web104.example.com from cache; expired at 2020-09-01 11:55:17 -0400 2021-03-03T07:27:53.356-05:00 INFO  [qtp1835431929-14632] [puppetserver] Puppet Caching facts for pubtstx-web104.example.com 2021-03-03T07:27:55.563-05:00 ERROR [clojure-agent-send-off-pool-13553] [p.e.file-sync-errors] File Sync failure during sync or fetch phase: Couldn't connect to server (https://infdevx-puppet202.example.com:8140/file-sync/v1/latest-commits): (Connection refused). So, maybe the problem is with how agent handles the exception? Ideally, agent shouldn't through an error in the log and into submitted report if it was able to recover? At the end the problem manifests itself with splunk and report processor sounding false alerts     Add Comment   This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.381638.1608653215000.156018.1614778500024%40Atlassian.JIRA.