Created attachment 1789775 [details] attachment Sample config file for the cluster role Description of problem: On OCP 4.6.25, the webconsole does not show the pod count of deploymentconfig when checked by a user with a custom clusterrole. This is not a permission issue as the user will be able to view all other details on deploymentconfig page but the graphical representation with a blue circle with pod count in the center will not appear. It just shows 3 bubbles progressing, but will not show the count. Issue is observed on OCP 4.6.25 and 4.6.20, but the same clusterrole will work as expected in OCP 4.7.x Version-Release number of selected component (if applicable): no How reproducible: Always Steps to Reproduce: 1. Create a custom clusterole (using the yaml attached) and assign a user to this cluster role. 2. Create a project and create a deployment config in the project. 3. Login through webconsole as the user and check the deploymentconfig in the project. Note: It is not a issue with the custom role yaml attached. The issue persists even when clusterrole is created using "oc create clusterrole <name> --resource=projects,namespaces,deploymentconfigs,replicationcontrollers,pods --verb=*" Actual results: Pod count not visible in the Administrator view Expected results: Pod count should be visible. Additional info: The issue is particular to the OCP version as it will show the expected results in OCP 4.7.9.
Created attachment 1789874 [details] Webconsole shows pod count of deploymentconfig with custom clusterrole
Created attachment 1789879 [details] Webconsole shows pod count of deploymentconfig with custom clusterrole-2
Verified on build version: 4.7.0-0.nightly-2021-06-07-203428 Browser: Google Chrome 89
Created attachment 1791075 [details] Webconsole shows pod count of deploymentconfig in pod ring in details tab for custom role
OpenShift engineering has decided to not ship Red Hat OpenShift Container Platform 4.7.17 due a regression https://bugzilla.redhat.com/show_bug.cgi?id=1973006. All the fixes which were part of 4.7.17 will be now part of 4.7.18 and planned to be available in candidate channel on June 23 2021 and in fast channel on June 28th.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.7.18 bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:2502