Skip to content

Commit

Permalink
Remove FSx mount on access after reboot
Browse files Browse the repository at this point in the history
The options were added to avoid long cluster creation. However, during cluster creation, the FSx is mounted anyway by the cookbook because of `action %i[mount enable]`. So the mount on access only takes effect after instance reboot for CentOS and Amazon Linux. Removing these options make behavior more consistent between cluster creation and instance reboot, and across OSes.

Signed-off-by: Hanwen <[email protected]>
  • Loading branch information
hanwen-cluster committed Jun 23, 2021
1 parent 2d99c22 commit ed4ad69
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 2 deletions.
1 change: 1 addition & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,7 @@ This file is used to list changes made in each version of the AWS ParallelCluste
- yum-6.1.1 (from yum-5.1.0)
- yum-epel-4.1.2 (from yum-epel-3.3.0)
- Drop ``lightdm`` package install from Ubuntu 18.04 DCV installation process.
- Remove Lustre mount on access options from `fstab`. FSx Lustre will be mounted immediately after reboot.

2.10.4
-----
Expand Down
2 changes: 0 additions & 2 deletions recipes/fsx_mount.rb
Original file line number Diff line number Diff line change
Expand Up @@ -43,8 +43,6 @@
mountname = node['cfncluster']['cfn_fsx_mount_name']
mount_options = %w[defaults _netdev flock user_xattr noatime]

mount_options.concat(%w[noauto x-systemd.automount]) if node['init_package'] == 'systemd'

# Mount FSx over NFS
mount fsx_shared_dir do
device "#{dns_name}@tcp:/#{mountname}"
Expand Down

0 comments on commit ed4ad69

Please sign in to comment.