Backport of Changed log level for retryable error Scenarios into release/1.20.x #22142
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport
This PR is auto-generated from #22141 to be assessed for backporting due to the inclusion of the label backport/1.20.
The below text is copied from the body of the original PR.
Description
For an enterprise ask as referred in an internal JIRA ticket.
Testing & Reproduction steps
Testing reproduction done -
1 - created a new build with consul changes in local and container image with binary.
2 - used the new image to start consul server with dev-binary inside a kind cluster
3 - start a service and shut down a service to see the above logs.
4 - Since only ACL change occurred and context cancelled are being handled currently with the corresponding understanding that they are retriable, others are cases will still be in error level .
5- As you can see in the last three lines - to get INFO level lines. run a consul server and try to shut down a service
6 - check that these log lines appear as INFO level
Links
Related past PR - #20876
PR Checklist
Overview of commits