-
Bug
-
Resolution: Won't Do
-
Critical
-
None
-
False
-
-
False
-
-
-
Critical
-
None
Description of problem:
in ACM 2.14 after enabling the tp feature
his is what I get by exporting d4f7f4a4-1474-4f2a-9002-4bfcbaca3331
apiVersion: rbac.open-cluster-management.io/v1alpha1 kind: ClusterPermission metadata: creationTimestamp: '2025-07-21T17:15:56Z' generation: 1 name: virtual-machine-actions resourceVersion: '694038430' uid: d4f7f4a4-1474-4f2a-9002-4bfcbaca3331 labels: app: search feature: virtual-machine namespace: aks-central spec: clusterRole: rules: - resources: - virtualmachines/start - virtualmachines/stop - virtualmachines/restart - virtualmachineinstances/pause - virtualmachineinstances/unpause apiGroups: - subresources.kubevirt.io verbs: - update clusterRoleBinding: subject: kind: ServiceAccount name: vm-actor namespace: open-cluster-management-agent-addon status: conditions: - status: 'True' lastTransitionTime: '2025-07-21T17:15:56Z' message: >- Run the following command to check the ManifestWork status: kubectl -n aks-central get ManifestWork virtual-machine-actions-d4f7f -o yaml reason: AppliedRBACManifestWork type: AppliedRBACManifestWork
so it seems the schema is not matching what it is expected on the UI, I'm checking it
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
- ...