kubevirt-hyperconverged sync error due to acm addon

[DanielFroehlich]

Argo is complaining
https://openshift-gitops-server-openshift-gitops.apps.isar.coe.muc.redhat.com/applications/openshift-gitops/operator-ocp-v?view=tree&node=hco.kubevirt.io%2FHyperConverged%2Fopenshift-cnv%2Fkubevirt-hyperconverged%2F0

Some of the configuration esp. around batchEviction that we have configured in git are not in live manifest.
A sync fixes the issue, but is reverted after a couple of minutes.

seems that a (new?) ACM addon kubevirt-hyperconverged now suddenly manages the hyperconverged object:
ClusterManagementAddOn/kubevirt-hyperconverged

[DanielFroehlich]

Need to figure out how to switch back to regular git config, without accidentally deleteing they hyperconverged object, i.e. removing ocp virt.

[DanielFroehlich]

Here's the config that is being applied, which is in conflict of what we have in gitops:

oc get addontemplates/kubevirt-hyperconverged -o=yaml -n open-cluster-management

[rbo]

Here's the config that is being applied, which is in conflict of what we have in gitops:

oc get addontemplates/kubevirt-hyperconverged -o=yaml -n open-cluster-management

BTW, addontemplates is a cluster-scoped object.

[rbo]

error when patching "/dev/shm/952457219": addontemplates.addon.open-cluster-management.io "kubevirt-hyperconverged" is forbidden: User "system:serviceaccount:openshift-gitops:openshift-gitops-argocd-application-controller" cannot patch resource "addontemplates" in API group "addon.open-cluster-management.io" at the cluster scope

[rbo]

Solved.

[rbo]

Reopen, AddOnTemplate is managed by other one...

An we have to add the annotation

kubevirt.kubevirt.io/jsonpatch: '[ {"op": "add", "path": "/spec/configuration/developerConfiguration/featureGates/-",
      "value": "VolumesUpdateStrategy"}, {"op": "add", "path": "/spec/configuration/developerConfiguration/featureGates/-",
      "value": "VolumeMigration"} ]'

as well.

[rbo]

Asked in our internal chat: https://redhat.enterprise.slack.com/archives/CTDEY6EEA/p1767033316677429

[rbo]

The CNV-Addon is part of the MTV-Integration: https://github.com/stolostron/rhacm-docs/blob/2.15_prod/virtualization/migrate_vm.adoc

We can disable the cnv-mtv-integrations-preview to solve for now: https://github.com/stormshift/clusters/blob/main/isar-apps/acm/MultiClusterHub/hub.yaml#L57-L59

Here is the source of the intration: https://github.com/stolostron/mtv-integrations

Asked in another more specific Slack channel: https://redhat-internal.slack.com/archives/C094HCLRXEK/p1767087773219009