Bug 1624914 - 1.2 CDI deployment manifest template uses wrong image name & variables and is not part of the D/S kubevirt APB dockerfile
Summary: 1.2 CDI deployment manifest template uses wrong image name & variables and is...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Installation
Version: 1.2
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: ---
: 1.2
Assignee: Ryan Hallisey
QA Contact: Irina Gulina
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-03 15:09 UTC by Nelly Credi
Modified: 2018-10-22 14:55 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-22 14:55:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:2963 0 None None None 2018-10-22 14:55:04 UTC

Description Nelly Credi 2018-09-03 15:09:39 UTC 
Description of problem:

CDI is not part of the d/s kuebvirt dockerfile
and
the CDI manifest has wrong image names as well as wrong variables - 
cdi-controller, cdi-importer, cdi-cloner instead of virt-cdi-X
and .DockerTag & .DockerRepo instead of docker_tag & registry_url/registry_namespace 


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


How reproducible:


Steps to Reproduce:
1.install the manifest rpm https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=759948
2. look at cdi-controller.yaml.in
3. 

Actual results:


Expected results:


Additional info:
Comment 1 Eyal Edri 2018-09-04 08:34:05 UTC 
This isn't a problem with the build system, moving to installation, the maintainers of the kubevirt-apb should handle it.

Honestly, I'm not sure which items should fall under 'build' yet, as each team is essentially in charge of their own builds.
Comment 5 Ryan Hallisey 2018-09-11 10:18:37 UTC 
kubevirt-apb:1.2-2
Comment 7 errata-xmlrpc 2018-10-22 14:55:00 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-2018:2963
Note You need to log in before you can comment on or make changes to this bug.