Description of problem: kubevirt-apb doesn't use cdi manifests from kubevirt-cdi-manifests rpm to deploy CDI. Instead we use manifests from kubevirt-ansible/roles/cdi/templates which is not what was shipped. Version-Release number of selected component (if applicable): kubevirt-apb-v1.3.0-3 How reproducible: 100% Steps to Reproduce: 1. Deploy KubeVirt using APB Actual results: kubevirt-apb is using manifests from kubevirt-ansible to deploy CDI, instead of using manifests from kubevirt-cdi-manifests rpm. /usr/share/kubevirt-cdi/manifests/cdi-controller.yaml Expected results: kubevirt-apb should use manifests from kubevirt-cdi-manifests to deploy CDI, not from kubevirt-ansible. /usr/share/kubevirt-cdi/manifests/cdi-controller.yaml Additional info:
@Lukas, is there a diff between the tempaltes which is causing functional issue?
@Nelly I am not aware of that, but I am afraid that it does not matter. Templates which are used by APB are not the ones which were shipped in manifest rpm. In addition I can see that manifest rpm is being installed into APB container, and then it is not used. It doesn't feel right ... we should neither 1) remove that rpm from apb and use template from kubevirt-ansible. 2) OR add template to rpm and use it from apb . I don't mind what why we will go, but we should make it straight.
I changed it to use kubevirt-cdi-manifests. Build is blocked by https://projects.engineering.redhat.com/browse/FACTORY-3482
brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/cnv-tech-preview/kubevirt-apb:v1.3.0-5
Working with kubevirt-apb-v3.11-4 it looks good there.
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:3776