You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently added "notice" level messages specifying the server that the agent is requesting a catalog from and the server that actually handled the request, e.g. Notice: Requesting catalog from puppet.example.com:8140. See #9126
As described in #9223, the agent may hang for 2 minutes trying to resolve the DNS name into an IPv6 address. Other users have reported not wanting these messages to be printed (or at least not at the Notice level).
Describe the Solution You Would Like
Add a boolean puppet setting to allow the DNS resolution to be disabled. It should be enabled by default.
Describe Alternatives You've Considered
Creating an enum to allow the behavior to be disabled or logged at a different verbosity level.
Use Case
We recently added "notice" level messages specifying the server that the agent is requesting a catalog from and the server that actually handled the request, e.g.
Notice: Requesting catalog from puppet.example.com:8140.
See #9126As described in #9223, the agent may hang for 2 minutes trying to resolve the DNS name into an IPv6 address. Other users have reported not wanting these messages to be printed (or at least not at the
Notice
level).Describe the Solution You Would Like
Add a boolean puppet setting to allow the DNS resolution to be disabled. It should be enabled by default.
Describe Alternatives You've Considered
Creating an enum to allow the behavior to be disabled or logged at a different verbosity level.
Additional Context
https://puppetcommunity.slack.com/archives/C0W298S9G/p1706879255760149
https://puppetcommunity.slack.com/archives/C0W298S9G/p1705964713457719
The text was updated successfully, but these errors were encountered: