-
Sub-task
-
Resolution: Done
-
Major
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
-
-
VMMgmt - Train-31
RoleAssignment status field should be handled from backend resource information. Active, Error and Pending status should be considered
one single status per roleAssignment, 1:1 relationship:
roleAssignmentsStatuses: - name: the RoleAssignment name status: failed reason: blah blah
so, in case of failure a tooltip showing the reason should be rendered too
see https://redhat-internal.slack.com/archives/C08N0NBMM2S/p1756798098907639?thread_ts=1756271815.228209&cid=C08N0NBMM2S