Azure error being logged as debug message

[MJLongstreth-tiq]

python/kubernetes/client/rest.py

Lines 226 to 235 in 7a278c7

	if _preload_content:
	r = RESTResponse(r)
	# In the python 3, the response.data is bytes.
	# we need to decode it to string.
	if six.PY3:
	r.data = r.data.decode('utf8')
	# log response body
	logger.debug("response body: %s", r.data)

Ran into an issue here, where the rest call is returning a 200 code, but with an error message:

RawError: {"code":"SnapshotsLimitReached, "message": "The incremental snapshot count was exceeded the limit for disk REDACTED. Please delete an incremental snapshot before creating another one."}

Would be great if this could check the response for an error and log the error at error level, as opposed to debug

[roycaihw]

IIUC the log is written only when the debug logging is enabled, which seems working as intended to me.

Are you suggesting that we add additional error level logging, which will be written even when debug logging is disabled?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale