Epic Goal

• Fix bugs that affect our ability to understand what went wrong with the registry.

Why is this important?

• The registry is not doing a good job when it translates underlying errors to the client. The registry can return meaningless "500 Internal Server Error" or "unknown manifest" when it has problems with an external registry or the API server. It complicates troubleshooting.

Scenarios

1. when an external registry returns 429 (too many requests), the registry should translate it back to the client - https://bugzilla.redhat.com/show_bug.cgi?id=1923536
2. the registry generates too many logs that are quickly rotated - IR-190

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>