Description of problem:

During container push, we look up blobs in pulp which returns a 404 when blob doesn't exist. Even though the error 404 is expected and the push proceeds, the stacktrace shows the 404 exception which should not be shown. If at all, it can be added as a debug message.

How reproducible:

Easy to reproduce. You can see the 404 stacktrace in logs when doing the push.

Is this issue a regression from an earlier version:

No

Steps to Reproduce:

1. Push a container image to katello

2. Notice logs have a 404 stacktrace

3. Image push succeeds.

Actual behavior:

Stacktrace of the 404 from pulp is shown in logs and might confuse users.

Expected behavior:

The 404 exception from pulp should be hidden in the logs to not confuse users who'd see it as an error when it is not.

Business Impact / Additional info:

No impact on functionality of push but the unnecessary 404 stacktrace in logs can confuse users.