Bug 1715361

Summary:	CDI ignores cdi-insecure-registries configmap contents
Product:	Container Native Virtualization (CNV)	Reporter:	Asher Shoshan <ashoshan>
Component:	Storage	Assignee:	Michael Henriksen <mhenriks>
Status:	CLOSED ERRATA	QA Contact:	Kevin Alon Goldblatt <kgoldbla>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	2.0	CC:	alitke, cnv-qe-bugs, igoihman, sgordon, ycui
Target Milestone:	---
Target Release:	2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	1.9.3	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-07-24 20:16:06 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 Asher Shoshan 2019-05-30 08:05:54 UTC

Description of problem:

When creating cdi-insecure-registries configmap to contain an insecure private registry, CDI importer (when creating datavolume registry source) ignores the configmap contents, and skopeo keeps the https protocol, and failing. 


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


How reproducible:
create cdi-insecure-registries configmap with registry url

Steps to Reproduce:
1. create datavolume yaml with registry source
2. whatch the importer pod failing


Actual results:
Importer failing

Expected results:
Respect the insecure registry and download the image

Additional info:

Comment 1 Kevin Alon Goldblatt 2019-07-01 16:14:28 UTC

Verified with the following code:
--------------------------------------

HCO:v2.0.0-27

Verified with the following scenario:
--------------------------------------
Steps to Reproduce:
1.Create cdi-insecure-registries configmap with registry url
2.Create datavolume yaml with registry source
3.Whatch the importer pod - successfully imports the image and datavolume is created


Moving to VERIFIED!

Comment 3 errata-xmlrpc 2019-07-24 20:16:06 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/RHEA-2019:1850