Bug 1827672 - Image registry logs cluttered with "localRegistry: unable to parse publicDockerImageRepository" messages
Summary: Image registry logs cluttered with "localRegistry: unable to parse publicDock...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.5.0
Assignee: Oleg Bulatov
QA Contact: Wenjing Zheng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-24 13:46 UTC by Adam Kaplan
Modified: 2020-07-13 17:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: the registry used to log warnings if publicDockerImageRepository is not set. Consequence: a lot of useless messages in logs Fix: ignore empty publicDockerImageRepository Result: less noise in the logs
Clone Of:
Environment:
Last Closed: 2020-07-13 17:31:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift image-registry pull 236 0 None closed Bug 1827672: Only warn if PublicDockerImageRepository is set 2020-10-01 11:22:33 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:31:42 UTC

Description Adam Kaplan 2020-04-24 13:46:04 UTC 
Description of problem:

The image registry logs are cluttered with "localRegistry: unable to parse publicDockerImageRepository" messages, which are always logged if the image registry does not have a public route.

Version-Release number of selected component (if applicable): 4.5.0


How reproducible: Always


Steps to Reproduce:
1. Create a new-app build -> deployment pipeline (ex oc new-app nodejs)
2. Wait for the build and deployment to complete
3. Review the image registry logs

Actual results:

"localRegistry: unable to parse publicDockerImageRepository" messages appears when the built image is pulled.


Expected results:

"unable to parse publicDockerImageRepository" message should not appear.

Additional info:
Comment 4 Wenjing Zheng 2020-05-11 07:52:59 UTC 
Verified on 4.5.0-0.nightly-2020-05-10-180138.
Comment 5 errata-xmlrpc 2020-07-13 17:31:25 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2409
Note You need to log in before you can comment on or make changes to this bug.