Bug 1715361 - CDI ignores cdi-insecure-registries configmap contents
Summary: CDI ignores cdi-insecure-registries configmap contents
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Storage
Version: 2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 2.0
Assignee: Michael Henriksen
QA Contact: Kevin Alon Goldblatt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-30 08:05 UTC by Asher Shoshan
Modified: 2019-07-24 20:16 UTC (History)
5 users (show)

Fixed In Version: 1.9.3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-24 20:16:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt containerized-data-importer pull 832 0 None closed fix host:port not allowed in insecure registry configmap 2020-12-09 23:09:03 UTC
Red Hat Product Errata RHEA-2019:1850 0 None None None 2019-07-24 20:16:13 UTC

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


Note You need to log in before you can comment on or make changes to this bug.