-
Bug
-
Resolution: Unresolved
-
Normal
-
None
Description of problem:
If there are role assignments in error and pending status, the MulticlusterRoleAssignment ready condition only shows the error message. In the case where there are pending and error role assignments, the ready condition message should mention both in the message. MRA example:
mjs@b91cf1b6b45e:/UbuntuSync$ oc get multiclusterroleassignment -A -oyaml apiVersion: v1 items: - apiVersion: rbac.open-cluster-management.io/v1beta1 kind: MulticlusterRoleAssignment metadata: creationTimestamp: "2026-01-22T03:26:34Z" finalizers: - finalizer.rbac.open-cluster-management.io/multiclusterroleassignment generation: 15 labels: open-cluster-management.io/managed-by: console name: role-assignment-1769052394055-x15v4qcn0 namespace: open-cluster-management-global-set resourceVersion: "3399945" uid: 0fad0d39-4daa-4b13-9626-21de1995594b spec: roleAssignments: - clusterRole: kubevirt.io-acm-hub:admin clusterSelection: placements: - name: clusters-local-cluster namespace: open-cluster-management-global-set type: placements name: fba19cc50ec015d1 - clusterRole: kubevirt.io:view clusterSelection: placements: - name: clusters-sno-1-vxpqx-and-sno-1-xztwb-and-sno-2-pk2t4 namespace: open-cluster-management-global-set type: placements name: 66ebec165f933ce3 targetNamespaces: - analytics-jobs - auth-proxy - backend-services - billing-services - ci-runners - database-storage - default - frontend-apps - non-existing - matttest - monitoring-agents - user-data - clusterRole: kubevirt.io-acm-managed:view clusterSelection: placements: - name: clusters-sno-1-vxpqx-and-sno-1-xztwb-and-local-cluster-and-sno-2-pk2t4 namespace: open-cluster-management-global-set type: placements name: f54acc455266efab targetNamespaces: [] - clusterRole: kubevirt.io:view clusterSelection: placements: - name: clusters-local-cluster namespace: open-cluster-management-global-set type: placements name: cba31bcb0e3a5093 targetNamespaces: [] - clusterRole: kubevirt.io-acm-managed:admin clusterSelection: placements: - name: clusters-sno-1-vxpqx-and-sno-1-xztwb-and-local-cluster-and-sno-2-pk2t4 namespace: open-cluster-management-global-set type: placements name: fcde35ee388555d2 targetNamespaces: [] - clusterRole: kubevirt.io-acm-managed:view clusterSelection: placements: - name: clusters-sno-1-vxpqx-and-sno-1-xztwb-and-sno-2-pk2t4 namespace: open-cluster-management-global-set type: placements name: 77d493a2f9b42d19 targetNamespaces: - analytics-jobs - clusterRole: kubevirt.io:edit clusterSelection: placements: - name: cs01 namespace: open-cluster-management-global-set type: placements name: 47afd3acccbf1778 targetNamespaces: [] subject: kind: User name: mattshort status: appliedClusters: - local-cluster - sno-1-vxpqx - sno-1-xztwb - sno-2-pk2t4 conditions: - lastTransitionTime: "2026-01-22T04:15:24Z" message: 4 out of 4 ClusterPermissions applied successfully observedGeneration: 15 reason: Applied status: "True" type: Applied - lastTransitionTime: "2026-01-22T04:11:41Z" message: 1 out of 7 role assignments failed observedGeneration: 15 reason: AssignmentsFailure status: "False" type: Ready roleAssignments: - createdAt: "2026-01-22T03:26:34Z" message: Applied to 1 clusters name: fba19cc50ec015d1 reason: SuccessfullyApplied status: Active - createdAt: "2026-01-22T03:51:47Z" message: 'Failed on 3 cluster(s): RoleBinding non-existing/kubevirt.io-view-3db0af26f7b4d702 failed on cluster sno-1-vxpqx: Failed to apply manifest: namespaces "non-existing" not found; RoleBinding non-existing/kubevirt.io-view-3db0af26f7b4d702 failed on cluster sno-1-xztwb: Failed to apply manifest: namespaces "non-existing" not found; RoleBinding non-existing/kubevirt.io-view-3db0af26f7b4d702 failed on cluster sno-2-pk2t4: Failed to apply manifest: namespaces "non-existing" not found' name: 66ebec165f933ce3 reason: ApplicationFailed status: Error - createdAt: "2026-01-22T03:54:20Z" message: No clusters match Placement selectors name: f54acc455266efab reason: NoMatchingClusters status: Pending - createdAt: "2026-01-22T03:55:00Z" message: Applied to 1 clusters name: cba31bcb0e3a5093 reason: SuccessfullyApplied status: Active - createdAt: "2026-01-22T04:11:08Z" message: No clusters match Placement selectors name: fcde35ee388555d2 reason: NoMatchingClusters status: Pending - createdAt: "2026-01-22T04:11:32Z" message: Applied to 3 clusters name: 77d493a2f9b42d19 reason: SuccessfullyApplied status: Active - createdAt: "2026-01-22T04:11:41Z" message: Applied to 1 clusters name: 47afd3acccbf1778 reason: SuccessfullyApplied status: Active kind: List metadata: resourceVersion: ""
Version-Release number of selected component (if applicable): 2.16.0-173
How reproducible: always
Steps to Reproduce:
- Create error and pending status role assignments
Actual results:
The ready condition status message will only mention the failing (error) role assignments.
Expected results:
The ready condition status message should reflect both pending and error statuses in a single message.