Hide Forgot
I’m adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. I will revisit this bug next sprint.
Moving the bug to verified state as i see that rangeallocations.data is updated whenever a project is deleted. 4.3.0-0.nightly-2020-09-02-201249 Below are the steps followed to verify the bug: ================================================= 1) Install 4.3.z cluster 2) Create more than 10K projects and see that rangeallocations.data is updated as below [ramakasturinarra@dhcp35-60 cucushift]$ oc get projects | wc -l 54 [ramakasturinarra@dhcp35-60 cucushift]$ oc get rangeallocations scc-uid -o yaml | grep -o "/" | wc -l 15 [ramakasturinarra@dhcp35-60 ~]$ oc get projects | wc -l 9986 [ramakasturinarra@dhcp35-60 ~]$ oc get rangeallocations scc-uid -o yaml | grep -o "/" | wc -l 1763 [ramakasturinarra@dhcp35-60 cucushift]$ oc get projects | wc -l 10100 [ramakasturinarra@dhcp35-60 cucushift]$ oc get rangeallocations scc-uid -o yaml | grep -o "/" | wc -l 1792 [ramakasturinarra@dhcp35-60 cucushift]$ oc get projects | wc -l 10154 [ramakasturinarra@dhcp35-60 cucushift]$ oc get rangeallocations scc-uid -o yaml | grep -o "/" | wc -l 1808 [ramakasturinarra@dhcp35-60 cucushift]$ oc get projects | wc -l 54 [ramakasturinarra@dhcp35-60 cucushift]$ oc get rangeallocations scc-uid -o yaml | grep -o "/" | wc -l 318 [ramakasturinarra@dhcp35-60 cucushift]$ oc get projects | wc -l 54 [ramakasturinarra@dhcp35-60 cucushift]$ oc get rangeallocations scc-uid -o yaml | grep -o "/" | wc -l 15 When the projects are deleted it came down to its original value which is 15. Based on the above data moving the bug to verified state.
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.3.38 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-2020:3609