Bug 2151462 - GRC policies are not getting propagated for cluster-admin users
Summary: GRC policies are not getting propagated for cluster-admin users
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: GRC & Policy
Version: rhacm-2.6.z
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: ---
Assignee: Chaitanya K
QA Contact: Derek Ho
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-07 08:18 UTC by Mihir Lele
Modified: 2023-07-06 19:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-02-09 14:00:00 UTC
Target Upstream Version:
Embargoed:
dho: qe_test_coverage-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 26984 0 None None None 2022-12-07 15:24:50 UTC

Description Mihir Lele 2022-12-07 08:18:08 UTC
Description of the problem:

GRC policies is not getting propagated for cluster-admin users. The policies get deployed on the managed clusters if the policies are created using the kubeadmin user.

Release version: ACM 2.6.2

Steps to reproduce:

Login to the ACM UI and create a GRC policy

Actual results:

Placementrule is not read by the propagator and hence policy does not get propagated to the managed clusters (local-cluster and one imported managed cluster)

Expected results:

Policy should get propagated to the managed clusters.

Additional info:

1) Policy gets propagated if the customer creates it using kubeadmin user
2) ACM UI is being used to create these policies
3) Customer does not have any gitops integration in this environment 
4) Users are externally authenticated AD users that have cluster-admin role assigned to them

Workaround:

Manually edit the placementrule and remove the user and group annotations.

Comment 4 Gus Parvin 2023-02-09 14:00:00 UTC
While the support case was closed with an unclear resolution, we believe the problem was with the syncing of the groups from LDAP to OpenSHift. The last recommendation was to redirect the support ticket to OpenShift for troubleshooting.  Please follow up if any additional support is needed here. Thanks


Note You need to log in before you can comment on or make changes to this bug.