Bug 1638634

Summary: kubevirt apb d/s deploys cdi into golden-images instead of kube-system namespace
Product: Container Native Virtualization (CNV) Reporter: Lukas Bednar <lbednar>
Component: InstallationAssignee: Ryan Hallisey <rhallise>
Status: CLOSED CURRENTRELEASE QA Contact: Lukas Bednar <lbednar>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.2CC: cnv-qe-bugs, fdeutsch, lbednar, ncredi, pousley, rhallise
Target Milestone: ---   
Target Release: 1.3   
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: 2019-01-15 14:05:56 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 Lukas Bednar 2018-10-12 06:44:29 UTC 
Description of problem:

When deploying KubeVirt using APB it deploys CDI into golden-images namespace.

Based on https://access.redhat.com/articles/3500741 article CDI should land in kube-system namespace.

Version-Release number of selected component (if applicable):
kubevirt-apb-1.2-5

How reproducible: Always


Steps to Reproduce:
1. Deploy KubeVirt using APB
2. Wait for pods to roll out
3. Observe what is namespace of CDI pod

Actual results: it is running in golden-images namespace


Expected results: It should run in kube-system namespace


Additional info:
Comment 1 Ryan Hallisey 2018-10-22 12:52:39 UTC 
Lukas should this be for both upstream and downstream?
Comment 2 Lukas Bednar 2018-10-22 14:11:51 UTC 
@Ryan since that document [1] is related to d/s, I am good with this change being done on d/s only.
Here [2] is u/s guide, which says default is good to go for testing that out ...

I believe the best practice is add parameter for APB, so in that way it is configurable.

[1] https://access.redhat.com/articles/3500741
[2] https://github.com/kubevirt/containerized-data-importer/#deploying-cdi
Comment 3 Nelly Credi 2018-11-06 15:28:31 UTC 
@Ryan, whats the status here? should the bug move to post/modified/qe?
can we target it to 1.3?
Comment 4 Ryan Hallisey 2018-11-06 16:54:45 UTC 
The latest kubevirt-ansible build has the fix:  https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=19079025


But, I'm still not able to build the apb because of https://projects.engineering.redhat.com/browse/FACTORY-3482.
Comment 5 Nelly Credi 2018-11-07 14:50:44 UTC 
Thanks Ryan, we will wait for it
please move to ON_QA & fill in the 'fixed in version' once the build is ready
Comment 6 Ryan Hallisey 2018-11-08 15:33:56 UTC 
brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/cnv-tech-preview/kubevirt-apb:v1.3.0-5
Comment 7 Lukas Bednar 2018-11-13 11:36:27 UTC 
It is fixed in kubevirt-apb-v3.11-4
Comment 8 Fabian Deutsch 2018-11-15 12:47:08 UTC 
I think this is targeted for 1.3