We recently got mail from AWS about the fact they'll enforce new settings for EFS and that will impact the way our own Openshift cluster are mounting the EFS volumes :
Starting October 1, 2023, EFS will begin a network upgrade to deliver lower-latency access to your EFS file system data. As with most routine EFS updates, this upgrade will cause existing NFS clients to reestablish connectivity with your EFS file system(s). If you do not update these clients to use EFS’s recommended mount settings, this upgrade may require you to restart compute instances running the affected NFS clients in order to recover their access to your EFS file system data. # Action Required: To minimize the risk of disruption, we recommend you re-mount your EFS file system(s) using the EFS mount helper [2] (or manually apply the 'noresvport' option if you are unable to use the EFS mount helper) by October 1, 2023.
So we just need to :
noresvport
As we'll have the cluster[s] updated before October, that would mean that we'd be safe before the AWS rollout plan in October. Testing this in the .stg. OCP cluster is mandatory before applying this to prod cluster (obviously)
Metadata Update from @arrfab: - Issue tagged with: centos-ci-infra, high-gain, medium-trouble
Metadata Update from @arrfab: - Issue assigned to arrfab
Updating first Staging cluster with modified settings to see that it works fine and modifying then the prod ocp cluster PVs
Done and modified in prod, so next time @dkirwan will proceed with ocp upgrade, all RHCOS hosts and pods will be restarted and mounting volumes with new settings
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.