Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1827672

Summary:	Image registry logs cluttered with "localRegistry: unable to parse publicDockerImageRepository" messages
Product:	OpenShift Container Platform	Reporter:	Adam Kaplan <adam.kaplan>
Component:	Image Registry	Assignee:	Oleg Bulatov <obulatov>
Status:	CLOSED ERRATA	QA Contact:	Wenjing Zheng <wzheng>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.5	CC:	aos-bugs
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-13 17:31:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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