Hello Adam, Thank you for reaching back   The ideal behaviour is below   A user can have only one role, and that role is determined by the last role assigned, depending in part on group membership. For example, if the role assignment rules are configured as follows: ROLE_SYS_ADMIN:u:User1, User2&ROLE_SYS_ADMIN:g:Group1, Group2&ROLE_AUDITOR:g:Group3, Group4&ROLE_USER:g:Group5 and if a user belongs to Group1 & Group5, then the role assigned to that user is ROLE_USER. Similarly, if a user belongs to Group2 & Group3, then the role assigned to that user is ROLE_AUDITOR. If the user does not belong to any of these groups (Group1, Group2, Group3, Group4, or Group5), then the default role assigned to the user is ROLE_USER. If the user belongs to only Group1, then the role assigned to the user is ROLE_SYS_ADMIN. ... View more

Hello @SKERR  No direct component upgrade is supported. However, I could see that the JIRA mentioned by you is already fixed in CDP 7.3.1   https://docs.cloudera.com/cdp-private-cloud-base/7.3.1/private-release-notes/topics/rt-fixed-issues-ozone.html ... View more

Hello @Leidy  Thank you for reaching out to cloudera Could you try the below steps   Stop CM Agent Remove the parcels form /opt/cloudera/parcel-repo directory on CM node Remove broken parcel dirs & symlinks under /opt/cloudera/parcels/ Clear parcel cache & .flood staging Ensure that on CM UI old parcles links are not present under CM UI >> Parcels >> Parcel configurations Restart Agent & CM Server Resync via CM UI → “Check for new parcels” Let me know how it goes   ... View more