Bug 1816042

Summary:	[self-signed OSP16]Met x509 error when try to pull/push image from/to image registry
Product:	OpenShift Container Platform	Reporter:	Wenjing Zheng <wzheng>
Component:	Image Registry	Assignee:	Oleg Bulatov <obulatov>
Status:	CLOSED DUPLICATE	QA Contact:	Wenjing Zheng <wzheng>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.4	CC:	aos-bugs, wsun
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-23 13:20:45 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 Wenjing Zheng 2020-03-23 08:38:09 UTC

Description of problem:
Met below error when try to pull/push image from/to image registry:
error: build error: Failed to push image: error copying layers and metadata from "containers-storage:[overlay@/var/lib/containers/storage+/var/run/containers/storage]image-registry.openshift-image-registry.svc:5000/wzheng1/ruby-ex:latest" to "docker://image-registry.openshift-image-registry.svc:5000/wzheng1/ruby-ex:latest": Error trying to reuse blob sha256:bb13d92caffa705f32b8a7f9f661e07ddede310c6ccfa78fb53a49539740e29b at destination: Head https://10.8.100.190:13808/v1/AUTH_e4452838e3494c44a926a5a9863095b4/wzheng-5403-tqrbf-image-registry-lejkoyvwkuqxmfxjehllhbruximgd/files/docker/registry/v2/blobs/sha256/bb/bb13d92caffa705f32b8a7f9f661e07ddede310c6ccfa78fb53a49539740e29b/data?temp_url_sig=b1e996fb4ea34e3044882b314a331943f3b8c0a7&temp_url_expires=1584947061: x509: certificate signed by unknown authority

Version-Release number of selected component (if applicable):
4.4.0-0.nightly-2020-03-23-010639

How reproducible:
Always

Steps to Reproduce:
1.Set up a disconnected and self-signed OSP 16 cluster
2.Create a build
3.Restart image registry by changing log level
4.Trigger build again

Actual results:
2.Build cannot be pushed to internal registry; 
4.builder image cannot be pulled

Expected results:
Image can be pulled or pushed from or to internal registry

Additional info:

Comment 3 Oleg Bulatov 2020-03-23 13:20:45 UTC


*** This bug has been marked as a duplicate of bug 1810461 ***