[integ-tests] Verify NFS v3 client mount has lockd pinned to port 4045

[hanwen-cluster]

Description of changes

Among our integration tests, only FSx Ontap supports v3 mount. Therefore, the check is added to the end of test_multiple_fsx. The check mounts FSx Ontap again with v3, and checks lockd register port 4045 in rpcbind.

This commit also allows 4045 port in the security group of the FSx Ontap, because v3 mount also requires lockd port on the server, which is defined as 4045 in Ontap too

Tests

The following tests have passed:

test-suites:
  storage:
    test_ebs.py::test_ebs_single:
      dimensions:
        - regions: ["us-east-1"]
          instances: ["m6g.xlarge"]
          oss: ["alinux2023", "ubuntu2204", "ubuntu2404", "rhel8", "rocky8", "rocky9", "rhel9"]
          schedulers: ["slurm"]
    test_fsx_lustre.py::test_multiple_fsx:
      dimensions:
        - regions: ["eu-west-2"]
          instances: ["m6g.xlarge"]
          oss: ["alinux2023", "ubuntu2204", "ubuntu2404", "rhel8", "rocky8", "rocky9", "rhel9"]
          schedulers: ["slurm"]

References

• Cookbook default port change Move NFS lockd port from 32768 to 4045 to avoid ephemeral-range collision aws-parallelcluster-cookbook#3217

Checklist

• Make sure you are pointing to the right branch.
• If you're creating a patch for a branch other than develop add the branch name as prefix in the PR title (e.g. [release-3.6]).
• Check all commits' messages are clear, describing what and why vs how.
• Make sure to have added unit tests or integration tests to cover the new/modified code.
• Check if documentation is impacted by this change.

Please review the guidelines for contributing and Pull Request Instructions.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.