Bug 2074052

Summary: Internal registries with a big number of images delay pod creation due to recursive SELinux file context relabeling
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: Image RegistryAssignee: Ricardo Maraschini <rmarasch>
Status: CLOSED ERRATA QA Contact: Yaxin You <yyou>
Severity: high Docs Contact:
Priority: high    
Version: 4.8CC: aos-bugs, bdettelb, minmli, obulatov, pehunt, rmarasch, wking, xiuwang, yyou
Target Milestone: ---   
Target Release: 4.9.z   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-18 13:20:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 2074050    
Bug Blocks: 2074053    

Comment 9 XiuJuan Wang 2022-05-10 03:49:21 UTC
In comment #4 Yayin You used a baremetal cluster on vsphere, we ensure we had set annotation and runtimeclass on image-registry pod. Yes, the registry pod could come up finally. 
And I check on a common vpshere cluster today, the registry pod could be running fast after set annotation and runtimeclass with 13 milons files.

oc get pods -l docker-registry=default  -w
NAME                              READY   STATUS        RESTARTS   AGE
image-registry-69f7bc8d99-nfb6v   1/1     Terminating   0          4m3s
image-registry-69f7bc8d99-nfb6v   0/1     Terminating   0          4m21s
image-registry-69f7bc8d99-nfb6v   0/1     Terminating   0          4m21s
image-registry-69f7bc8d99-nfb6v   0/1     Terminating   0          4m21s
image-registry-fcc77b458-bx2xf    0/1     Pending       0          0s
image-registry-fcc77b458-bx2xf    0/1     Pending       0          0s
image-registry-fcc77b458-bx2xf    0/1     ContainerCreating   0          0s
image-registry-fcc77b458-bx2xf    0/1     ContainerCreating   0          11s
image-registry-fcc77b458-bx2xf    0/1     Running             0          12s
image-registry-fcc77b458-bx2xf    1/1     Running             0          13s

oc get pods image-registry-fcc77b458-bx2xf -o yaml | grep -i selinux  -A 1 -B 1
    imageregistry.operator.openshift.io/dependencies-checksum: sha256:134bfb909a388b54f8dc8ba191dcbcb3572f968c84d65499ef7cb3e091e21f51
    io.kubernetes.cri-o.TrySkipVolumeSELinuxLabel: "true"
    k8s.v1.cni.cncf.io/network-status: |-
  restartPolicy: Always
  runtimeClassName: selinux
  schedulerName: default-scheduler
    fsGroupChangePolicy: OnRootMismatch
      level: s0:c18,c17

Per comment #8, will approve the fix pr.

Comment 14 errata-xmlrpc 2022-05-18 13:20:29 UTC
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.9.33 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.


Comment 15 Peter Hunt 2022-09-13 13:31:29 UTC
*** Bug 2102510 has been marked as a duplicate of this bug. ***

Comment 16 Red Hat Bugzilla 2023-09-15 01:53:48 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days