Description of problem: We need to Introduce a new feature gate DisableMDEVConfiguration at HCO CR level. https://github.com/kubevirt/hyperconverged-cluster-operator/blob/main/api/v1beta1/hyperconverged_types.go#L295 ]$ oc annotate --overwrite -n openshift-cnv hyperconverged kubevirt-hyperconverged kubevirt.kubevirt.io/jsonpatch='[{ "op": "add", "path": "/spec/configuration/developerConfiguration/featureGates/-", "value": "DisableMDEVConfiguration" }]' Version-Release number of selected component (if applicable): CNV 4.13 How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: No way to configure "DisableMDEVConfiguration" FeatureGate Expected results: Need tunable featureGate to configure DisableMDEVConfiguration via HCO CR Additional info: Jira Issue for 4.14: https://issues.redhat.com/browse/CNV-27645
This is not a bug fix but an RFE for the next release, please justify the business case otherwise let's defer to the next release.
Re-opening this bug, after discussing with Installation Team.
https://github.com/kubevirt/kubevirt/pull/9343 landed on the upstream release-0.59 stabilization branch but we still lack a tagged upstream v0.59.1 release exposing it. Do we have an ETA?
Postponing to 4.13.2 since we are not able to get it merged upstream due to CI test blockers.
This needs to be backported all the way to 4.12 line.
Oren, can you take a look and let me know if we should wait for Simone, or we can continue with backporting his PR while he is away.
We need to consume a newer kubevirt release in upstream HCO that included this fix: https://github.com/kubevirt/kubevirt/pull/9856 For the CI to pass in the DisableMDEVConfiguration feature gate PR.
I have logged, https://bugzilla.redhat.com/show_bug.cgi?id=2215286 to cover the upgrade scenario from 4.12.4.
Verified against CNV-v4.13.2.rhel9-37 ===================== [cloud-user@ocp-ipi-executor-xl ~]$ oc get hco kubevirt-hyperconverged -n openshift-cnv -o json | jq ".spec.featureGates" { "deployKubeSecondaryDNS": false, "deployTektonTaskResources": false, "disableMDevConfiguration": false, "enableCommonBootImageImport": true, "nonRoot": true, "withHostPassthroughCPU": false } [cloud-user@ocp-ipi-executor-xl ~]$ [cloud-user@ocp-ipi-executor-xl ~]$ oc get kubevirt kubevirt-kubevirt-hyperconverged -n openshift-cnv -o json | jq ".spec.configuration.developerConfiguration" { "diskVerification": { "memoryLimit": "2G" }, "featureGates": [ "DataVolumes", "SRIOV", "CPUManager", "CPUNodeDiscovery", "Snapshot", "HotplugVolumes", "ExpandDisks", "GPU", "HostDevices", "DownwardMetrics", "NUMA", "VMExport", "DisableCustomSELinuxPolicy", "KubevirtSeccompProfile", "WithHostModelCPU", "HypervStrictCheck" ] } [cloud-user@ocp-ipi-executor-xl ~]$ On edit: [cloud-user@ocp-ipi-executor-xl ~]$ oc get hco kubevirt-hyperconverged -n openshift-cnv -o json | jq ".spec.featureGates" { "deployKubeSecondaryDNS": false, "deployTektonTaskResources": false, "disableMDevConfiguration": true, "enableCommonBootImageImport": true, "nonRoot": true, "withHostPassthroughCPU": false } [cloud-user@ocp-ipi-executor-xl ~]$ [cloud-user@ocp-ipi-executor-xl ~]$ oc get kubevirt kubevirt-kubevirt-hyperconverged -n openshift-cnv -o json | jq ".spec.configuration.developerConfiguration" { "diskVerification": { "memoryLimit": "2G" }, "featureGates": [ "DataVolumes", "SRIOV", "CPUManager", "CPUNodeDiscovery", "Snapshot", "HotplugVolumes", "ExpandDisks", "GPU", "HostDevices", "DownwardMetrics", "NUMA", "VMExport", "DisableCustomSELinuxPolicy", "KubevirtSeccompProfile", "WithHostModelCPU", "HypervStrictCheck", "DisableMDEVConfiguration" ] } [cloud-user@ocp-ipi-executor-xl ~]$
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 4.13.2 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-2023:4028