Jira (PUP-10157) Observer server_list for CA requests

[Josh Cooper (JIRA)]

Josh Cooper created an issue

Puppet / PUP-10157 Observer server_list for CA requests Issue Type: Bug Affects Versions: PUP 6.11.0 Assignee: Unassigned Created: 2019/12/03 9:40 PM Fix Versions: PUP 6.12.0 Priority: Normal Reporter: Josh Cooper Puppet Version: Puppet Server Version: OS Name/Version: Describe your issue in as much detail as possible… Describe steps to reproduce… Desired Behavior: Actual Behavior: Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue. Examples: Run puppet agent with --test --trace --debug Relevant sections of /var/log/puppetlabs/puppetserver/puppetserver.log or any applicable logs from the same directory. For more detailed information turn up the server logs by upping the log level in the server's logback.xml Relevant sections of configurations files (puppet.conf, hiera.conf, Server's conf.d, defaults/sysconfig) For memory issues with server heap dumps are also helpful. Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

[Josh Cooper (JIRA)]

Josh Cooper updated an issue

Puppet / PUP-10157 Observer 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 Version : * * :Rest::Routes}} called {{ Puppet Server Version : * *OS Name/Version : *

Describe your issue in as much detail as possible… Describe steps to reproduce…

*Desired Behavior Util : * *Actual Behavior : * Connection.determine_server}}. Please take # If we successfully resolved the CA once in a moment and attach any relevant log output and session, then we should reuse that same server / or manifests. This will help us immensely when troubleshooting port # Next if {{ca_server}} is set explicitly on the issue. Examples: Run CLI or puppet agent with --test --trace --debug Relevant sections .conf, we should always use that regardless of {{ /var/log/puppetlabs/puppetserver/puppetserver.log server }} or any applicable logs from the same directory. {{server_list}} # Next if SRV records are enabled, we should try that For more detailed information turn up the # Next if {{server_list}} is set, we should try each server logs by upping the log level in the /port combo # Otherwise fallback to {{ca_server}} setting which defaults to {{ server 's logback.xml }} Relevant sections All of configurations files those should already be working except ( puppet 4) . conf Questions: In step 2 , hiera if SRV records are enabled, the new code prefers SRV over the explicit server, which is wrong . conf In step 2 , Server If the explicit server fails, should we fallback to other resolvers? Currently we don ' s conf t and we should probably keep that as-is . d In step 4 , defaults the old behavior was to only try the first server / sysconfig 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 ) For memory issues with to try all the server heap dumps are also helpful /ports in server_list .

Add Comment