Description of problem: - Related to bz#1459106, when containers has a lot of files, fsGroup(chmod+chown) causes time out. - The podAttachAndMountTimeout has fixed value (2min)[1], but it is not configurable. Version-Release number of selected component (if applicable): - OCP 3.x (we experienced 3.3) Steps to Reproduce: 1. Please refer to the description of bz#1459106. However, it might need small file for the fsGroup issue. Actual results: - Caused timeout after 2m. FirstSeen LastSeen Count From SubobjectPath Type Reason Message --------- -------- ----- ---- ------------- -------- ------ ------- 2m 2m 1 {default-scheduler } Normal Scheduled Successfully assigned <NODE_NAME> 14s 14s 1 {kubelet <NODE_NAME>} Warning FailedMount Unable to mount volumes for pod "jenkins-xxx(xxx)": timeout expired waiting for volumes to attach/mount for pod "jenkins-xxx"/"xxx-xx". list of unattached/unmounted volumes=[jenkins-xxx] 14s 14s 1 {kubelet <NODE_NAME>} Warning FailedSync Error syncing pod, skipping: timeout expired waiting for volumes to attach/mount for pod "jenkins-xxx"/"xxx-xx". list of unattached/unmounted volumes=[jenkins-data] - In the OpenShift Node log, there are tons of chown/chmod logs. Expected results: - We wanted to expand podAttachAndMountTimeout. Additional info: - Workaround is to remove fsGroup from DC[2]. [1] https://github.com/openshift/origin/blob/release-1.3/vendor/k8s.io/kubernetes/pkg/kubelet/volumemanager/volume_manager.go#L70 [2] https://github.com/openshift/origin/blob/master/vendor/k8s.io/kubernetes/pkg/volume/volume_linux.go#L35-L38
I don't think that it is a RFE ticket. Without configurable timeout value, if the users have a lot of files, fsGroup(chown+chgroup) causes timeout and the pod cannot start.
With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers. Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant. This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.