Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: When deploying Openshift Virtualization 2.5.0 using the following index image: registry-proxy.engineering.redhat.com/rh-osbs/iib:7848 SSP's KubeVirtMetricsAggregation CR is not exposing the "Available" condition. It has only the "Running" condition set to "true" indefinetly. This causes HCO not to become ready, and we are hitting https://bugzilla.redhat.com/show_bug.cgi?id=1868712 which affects both hco and nmo pods. Version-Release number of selected component (if applicable): SSP Operator image: registry-proxy.engineering.redhat.com/rh-osbs/container-native-virtualization-kubevirt-ssp-operator@sha256:8aa81bf1beab8bc7bb689bef2e68e1db594d2dccaa960baed8088c9365e74db7 https://access.redhat.com/containers/#/registry.access.redhat.com/container-native-virtualization/kubevirt-ssp-operator/images/v2.5.0-33 OCP: 4.6.0-fc.3 HCO image: registry-proxy.engineering.redhat.com/rh-osbs/container-native-virtualization-hyperconverged-cluster-operator@sha256:e93355c3e8d98e38630342116aca46186c8873dda08e2449801fb040880f8b82 https://access.redhat.com/containers/#/registry.access.redhat.com/container-native-virtualization/hyperconverged-cluster-operator/images/v2.5.0-29 index-image: registry-proxy.engineering.redhat.com/rh-osbs/iib:7848 How reproducible: 100% Steps to Reproduce: 1. Deploy CNV 2.5.0 using the above index-image as a catalog source. 2. 3. Actual results: KubeVirtMetricsAggregation doesn't have an "Available" condition Expected results: KubeVirtMetricsAggregation should eventually expose "Available=true" condition. Additional info: HCO CR conditions: - lastHeartbeatTime: "2020-09-08T13:28:09Z" lastTransitionTime: "2020-09-08T13:08:06Z" message: Reconcile completed successfully reason: ReconcileCompleted status: "True" type: ReconcileComplete - lastHeartbeatTime: "2020-09-08T13:28:09Z" lastTransitionTime: "2020-09-08T13:08:04Z" message: missing "Available" condition reason: KubeVirtMetricsAggregationNotAvailable status: "False" type: Available - lastHeartbeatTime: "2020-09-08T13:28:09Z" lastTransitionTime: "2020-09-08T13:10:01Z" message: Reconcile completed successfully reason: ReconcileCompleted status: "False" type: Progressing - lastHeartbeatTime: "2020-09-08T13:28:09Z" lastTransitionTime: "2020-09-08T13:08:04Z" message: Reconcile completed successfully reason: ReconcileCompleted status: "False" type: Degraded - lastHeartbeatTime: "2020-09-08T13:28:09Z" lastTransitionTime: "2020-09-08T13:10:01Z" message: Reconcile completed successfully reason: ReconcileCompleted status: "True" type: Upgradeable $ oc get KubeVirtMetricsAggregation metrics-aggregation-kubevirt-hyperconverged -o yaml [...] status: conditions: - ansibleResult: changed: 2 completion: 2020-09-08T13:08:48.894215 failures: 0 ok: 4 skipped: 0 lastTransitionTime: "2020-09-08T13:08:40Z" message: Awaiting next reconciliation reason: Successful status: "True" type: Running operatorVersion: v2.5.0 targetVersion: v2.5.0 SSP pod logs (complete): https://drive.google.com/file/d/1nosQgKzf2wqXKB8RWLbz2168R7SPGa3k/view?usp=sharing
A recurring error in the logs is: > fatal: [localhost]: FAILED! => {"msg": "template error while templating string: no filter named 'k8s_inject_ownership'. String: {{ objects | k8s_inject_ownership(cr_info) }}"} The k8s_inject_ownership filter is part of kubevirt-ssp-operator since upstream PR#202 (https://github.com/kubevirt/kubevirt-ssp-operator/pull/202). However it is missing from the downstream kubevirt-ssp-operator container image (registry-proxy.engineering.redhat.com/rh-osbs/container-native-virtualization-kubevirt-ssp-operator:v2.5.0-33). We need to backport upstream changes in the Dockerfile from PR#202 (https://github.com/kubevirt/kubevirt-ssp-operator/pull/202/files#diff-4bb306eddc70a07a963059d2c51ad097) to our downstream Dockerfile (http://pkgs.devel.redhat.com/cgit/containers/kubevirt-ssp-operator/tree/Dockerfile.in?h=cnv-2.5-rhel-7) to also copy the filter_plugins/ (https://github.com/kubevirt/kubevirt-ssp-operator/tree/master/filter_plugins) directory.
Hi, I am updating the DS container right now with the proper upstream commit and Dockerfile
Fix was submitted, waiting for automation to build the new container. Will update the bug when the container is built.
Waiting for an hco-bundle build, ssp-build is ready
Verified with registry-proxy.engineering.redhat.com/rh-osbs/iib:8258.
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 (OpenShift Virtualization 2.5.0 Images), 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-2020:5127