Log response body if config server returns non-JSON#2638
Merged
rkoster merged 1 commit intocloudfoundry:mainfrom Nov 6, 2025
Merged
Conversation
* in a fresh bbl environment we often get the error "Config Server returned a NON-JSON body while generating value for ..." without further information what went wrong
aramprice
approved these changes
Nov 5, 2025
rkoster
approved these changes
Nov 6, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What is this change about?
Log full response body if a credential generation request to the config_server fails.
Please provide contextual information.
In a fresh bosh-bootloader environment, we often get stacktraces like this when creating the first deployment:
The second attempt usually succeeds. From the given logs, it's however unclear why the config server (i.e. the "credhub" instance running on the bosh director VM) fails.
What tests have you run against this PR?
None, adapted unit test.
How should this change be described in bosh release notes?
Doesn't need to be mentioned.
Does this PR introduce a breaking change?
No.