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:
Verified on 4.5.0-0.nightly-2020-05-10-180138.
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