diff --git a/atomic_reactor/utils/retries.py b/atomic_reactor/utils/retries.py
index <HASH>..<HASH> 100644
--- a/atomic_reactor/utils/retries.py
+++ b/atomic_reactor/utils/retries.py
@@ -50,7 +50,10 @@ def hook_log_error_response_content(response, *args, **kwargs):
     :type response: requests.Response
     """
     if 400 <= response.status_code <= 599:
-        logger.error('Error response from %s: %s', response.url, response.content)
+        logger.debug(
+            'HTTP %d response from %s: %s',
+            response.status_code, response.url, response.content
+        )
 
 
 def get_retrying_requests_session(client_statuses=HTTP_CLIENT_STATUS_RETRY,
diff --git a/tests/utils/test_retries.py b/tests/utils/test_retries.py
index <HASH>..<HASH> 100644
--- a/tests/utils/test_retries.py
+++ b/tests/utils/test_retries.py
@@ -84,7 +84,7 @@ def test_log_error_response(http_code, caplog):
     session.get(api_url)
 
     content = json.dumps(json_data).encode()
-    expected = f"Error response from {api_url}: {content}"
+    expected = f"HTTP {http_code} response from {api_url}: {content}"
     if 400 <= http_code <= 599:
         assert expected in caplog.text
     else:
Do not log error responses from retries as errors

Sometimes error code is expected and shouldn't be treated as error. In
fact everything logged from retries should be just DEBUG.

Many errors in logs scary users.

Removing "Error" from log string and replacing it with http status code.

CLOUDBLD-<I>